Town & Village Name Generator
This town name generator builds fantasy town names, village names, and medieval settlement names from the same morphemes real English and Norse place names used — compound endings like -ton, -ham, -wick, and -bury, descriptive registers for grim or golden villages, trade names like Saltmarket, and Norse and Celtic-flavored variants for Danelaw-style or highland settlements. Hit Generate for ten new names at once, ready for a map, campaign, or novel.
How Real Town and Village Names Were Built
English place names are rarely invented from scratch — they're built from a small toolbox of Old English, Old Norse, and Celtic word-parts, each describing what a settlement actually was. -ton comes from the Old English tūn, an enclosed farmstead. -ham is hām, a homestead. -wick traces to wīc, from the Latin vicus, a dairy farm or trading post. -shire marked a governed district, -stead a site or place, and -bury or -borough comes from burh, a fortified settlement. Two endings arrived with later settlers: -combe is a Celtic cwm, a steep valley, and -thorpe is Old Norse þorp, an outlying settlement — both still common across England. Knowing what a suffix meant is how this generator builds a believable name: pick a root, add the ending that matches the place, and the result reads like it carries centuries of history rather than being invented on the spot.
The Naming Registers Behind This Generator
This town name generator and village name generator mixes six real registers rather than one repeating pattern:
- English compounds — a landscape or animal root fused to a toponymy suffix: Ashcombe, Millbury, Fenworth.
- Descriptive compounds — an adjective doing the same job: Greenford, Oldham, Netherton.
- Noun + geography — two separate words, the pattern behind names like Raven Hollow or Fox Ford.
- Trade and market names — settlements that grew up around a single traded good: Saltmarket, Fishgate, Wool Row.
- Norse (Danelaw) names — the -by, -thorpe, and -toft endings Viking settlers left across northern and eastern England: Ulfby, Ravnthorpe.
- Celtic and highland names — Pen-, Aber-, and Dun- prefixes from the older Brythonic and Gaelic layer beneath English place names: Pencombe, Abermoor.
Example Town and Village Names
- Ashcombe
- Millbury
- Greenford
- Oldham
- Raven Hollow
- Fox Ford
- Miller's Cross
- Saltmarket
- Fishgate
- Market Green
- Ulfby
- Pencombe
Who Uses a Town Name Generator
Novelists and dungeon masters reach for a random town name generator the moment a map needs filling in — a region with fifteen unlabeled dots stops feeling generic once every dot has a name that sounds like it grew there. Fantasy town names built from real morphemes read as lived-in rather than decorative. Tabletop groups running a hex-crawl often generate a batch at once, keeping a castle name generator result on hand for whichever village sits in a lord's shadow. Homebrew builders lean on the Norse and Celtic registers when a region should feel like its own culture rather than reused English vocabulary.
Writers of medieval and low-fantasy fiction use the same tool for medieval town names that need to sound plausible rather than invented, since readers notice when every settlement in a manuscript shares one pattern. And a village always needs somewhere to drink — pair a result here with a tavern name generator pick and the map's central square is finished.
Choosing the Right Register for Your Settlement
Match the register to the place's history, not just its vibe. A trading crossroads earns a trade name — Saltmarket, Corngate — because that's literally how English market towns got their names. A quiet farming village suits the plain English compound or the noun-plus-geography pattern: Ashcombe, Raven Hollow. Coastal or river regions settled by raiders-turned-farmers should pull from the Norse register, and a highland frontier should lean Celtic. Generate ten, read them aloud, and keep the one that already sounds like somewhere a caravan would stop for the night.
Frequently Asked Questions
What do town name endings like -ton, -ham, and -bury actually mean?
They're Old English words for different kinds of settlement, not decoration. -ton (tūn) meant an enclosed farmstead, -ham (hām) a homestead or village, -bury/-borough (burh) a fortified place, -wick (wīc) a dairy farm or trading post, -stead a general site, and -shire a governed district. Reading a real town's suffix tells you what kind of place it started life as, which is exactly the logic this generator uses to build new ones.
What's the difference between a town name generator and a village name generator?
Functionally nothing here — the same six registers (English compound, descriptive compound, noun-plus-geography, trade name, Norse, and Celtic) produce results that read as anything from a hamlet to a market town depending on which pattern comes up. Smaller-sounding results like Raven Hollow or Fenworth suit a village; trade names like Saltmarket or Corngate read more like an established town.
Why do some of these names sound Norse or Celtic instead of English?
Because real England isn't linguistically uniform. Viking settlers left -by, -thorpe, and -toft endings across the north and east (Whitby, Scunthorpe), while older Celtic and Brythonic roots survive underneath English place names in the west and in Scotland and Wales — Pen-, Aber-, and Dun- prefixes among them. This generator keeps those two registers separate so a highland or Danelaw-flavored region in your world doesn't sound like the same county as everywhere else.
Can I use these fantasy town names in a book, campaign, or game commercially?
Yes. Every result is assembled from generic English, Norse, and Celtic word-roots and toponymy suffixes, not copied from any trademarked setting or franchise, so they're free to use in novels, homebrew D&D campaigns, or games you sell. A handful will coincidentally resemble real English towns (English place names have been recombining these same roots for over a thousand years) — that's expected, not a licensing concern.
