Folkestone
town and civil parish in Kent, England
Folkestone ( FOHK-stən) is a coastal town on the English Channel, in Kent, south-east England. The town lies on the southern edge of the North Downs at a valley between two cliffs. It was an important harbour, shipping port, and fashionable coastal resort for most of the 19th and mid-20th centuries.
This location has had a settlement since the Mesolithic era. A nunnery was founded by Eanswith, granddaughter of Æthelberht of Kent in the 7th century, who is still commemorated as part of the town's culture. During the 13th century, it developed into a seaport, and the harbour developed during the early 19th century to defend against a French invasion. Folkestone expanded further west after the arrival of the railway in 1843 as an elegant coastal resort, thanks to the investment of the Earl of Radnor under the urban plan of Decimus Burton.
In its Edwardian-era heyday, Folkestone was considered the most fashionable resort of the time, visited by royalty — amongst them Queen Victoria and Edward VII and other members of the English aristocracy. The town's architecture, especially in the West End part, is a testimony of this period, with many impressive buildings, townhouses, villas, private squares, and large hotels built to accommodate the gentry. After two world wars and the boom of the overseas holiday package, the town quickly declined.
This brief starts where responsible research should: with the source description of “Folkestone” as town and civil parish in Kent, England. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the places & architecture register because the source frames it as town and civil parish in Kent, England. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Place names and jurisdictional language are key evidence: both can reveal earlier catalogue descriptions and overlooked record series. The source revision retrieved here is dated Sep 10, 2026. The linked authority identifier is Q375314. VIAF identifies the subject as 136090638. The Library of Congress control number is n84080071. Authority coordinates are 51.079, 1.179. 4 of 4 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1843.
Architectural summaries often privilege surviving fabric and can understate demolished phases, contested use or displaced communities. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Folkestone”, its source revision and the description used here.
- Expand the search: follow Folkestone primary sources, Folkestone archive and Folkestone research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Folkestone”?
- What physical evidence or contemporary plan supports the description?
- Which authority defined the place, boundary or structure at the relevant date?
Search terms from this dossier
This entry incorporates text from “Folkestone” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.