Generate fictional city and town names using the real morphology of English place names — a modifier fused to a settlement suffix like -haven, -ford, -mere or -stead. Northstead, Silverhaven, Greyport. They read as places because they are built the way places are.
Settings
Recent results
Generated locally in your browser — your settings and results never leave this page.
Real place names are built, not invented
English place names are almost never arbitrary. They are compounds: a modifier fused to a settlement word that once meant something specific — a ford, a haven, a stead, a mere, a wick, a burn.
That is why invented place names built by joining random syllables never quite convince, and why Northstead, Silverhaven and Greyport do. The generator uses the real morphology, so the results are constructed the way places actually are.
The tool defaults to fusing the two halves into one word for that reason, because that is what real place names do over time.
The suffix carries the geography
Each settlement word implies a landscape, and readers pick it up without noticing.
-ford, -bridge, -mere imply water and a crossing.
-haven, -port imply the coast.
-stead, -wick imply a farm or a small settlement.
-gate, -crest, -reach imply a boundary or a height.
Choosing one that contradicts your map is a small, persistent wrongness. If your city is inland, do not call it a port — readers will picture the sea and be quietly corrected every time it appears.
How places get their modifiers
The first half is usually a colour, a direction, a material, a size or a personal name. Grey, North, Salt, Iron, Upper, High.
Those are the words that describe a place from outside, which is how settlements are named: by the people who lived somewhere else and needed to distinguish it. That is also why the modifier is nearly always plain — nobody named a village something poetic on purpose.
Put your own word in the keyword box if the place has a reason for its name in your setting. A place named after a founder, a river or an event carries an implied history at no cost.
Fused or separated
Both are real. Fused names — Ashford, Silverhaven — read as older, because centuries of use wear the gap away. Separated names — High Reach, Salt March — read as newer or more formal, and are common for administrative districts and planned settlements.
Using both in one setting is worth doing deliberately: old towns fused, new ones separated. Readers will not articulate the pattern and will feel it.
Names that scale from village to city
A settlement in a long story frequently grows, and a name that fits a hamlet can sit oddly on a capital.
Small suffixes — wick, stead, hollow — stay small in a reader’s mind however large you say the place is. If the city is meant to be significant, choose a suffix with room in it: reach, gate, port, march. If it is meant to be a backwater, the small ones do that work for you.
Districts, and the layer below
A city needs its parts named too, and those follow their own convention: usually simpler and more functional than the city name — a trade, a gate, a river bank, a hill.
Keeping the district names plainer than the city name is what makes the city read as the larger thing. A district with a grander name than its city inverts the hierarchy and confuses the reader about what matters.
Reading the score
A score out of 100 sits on each result, weighing how the name is said and spelled against how long it runs, and “Why this score” explains it.
Pronounceability is the one to watch. Place names are read constantly in a narrative, often several times a page, and one that snags becomes a small irritation the reader cannot locate.
Names that tell you what happened there
The most useful place names in fiction do a second job: they record something. A ford where an army crossed, a haven that was not one, a mill that burned.
You get that by putting the event in the keyword box rather than by choosing a poetic-sounding name. A place named for a plain fact carries an implied history the reader assembles themselves, which is far more effective than being told the history directly.
It also gives you somewhere to put exposition without stopping the narrative, since a character can simply mention why the place is called what it is.
Non-English settings
This tool builds from English settlement morphology, which suits a great deal of fantasy and almost all of it set in an English-speaking world.
If your setting is meant to read as somewhere else, the construction will fight you: the suffixes are recognisably English and readers hear that. The honest options are to use the invented styles in the fantasy tool for something that belongs to no real language, or to research the morphology of the tradition you are drawing on and build the names the same way this tool builds English ones.
What does not work is attaching English suffixes to non-English roots, which reads as neither and satisfies nobody.
What is not checked
Nothing here checks whether a name matches a real place or one in an existing work, and no result suggests one is free to use.
Real place names are extremely likely to collide, because the generator uses the same morphology real places do. That is usually harmless and occasionally not — setting unpleasant fictional events in a real, findable town of the same name is worth avoiding. Search anything you intend to publish.
How to use the Fictional City Name Generator
- Keep the fused one-word style for older-sounding places.
- Choose a suffix that matches your map — do not call an inland city a port.
- Put a founder, river or event in the keyword box if the place is named for one.
- Press Generate city names and run several rounds.
- Use fused names for old towns and separated ones for new or administrative places.
- Search anything you publish — these collide with real places by design.
Frequently asked questions
Why do these sound more real than other invented place names?
Because English place names are almost never arbitrary — they are compounds, a modifier fused to a settlement word that once meant something specific: a ford, a haven, a stead, a mere. Names built by joining random syllables never quite convince. This generator uses the real morphology, so results are constructed the way places actually are.
Does the suffix matter?
It carries the geography, and readers pick it up without noticing. Ford, bridge and mere imply water and a crossing; haven and port imply the coast; stead and wick imply a farm or small settlement; gate, crest and reach imply a boundary or height. Choosing one that contradicts your map is a small persistent wrongness the reader keeps being corrected by.
Where does the first half come from?
Usually a colour, direction, material, size or personal name — Grey, North, Salt, Iron, Upper, High. Those are the words that describe a place from outside, which is how settlements get named: by people who lived somewhere else and needed to distinguish it. That is also why the modifier is nearly always plain.
Should the name be one word or two?
Both are real and they signal different things. Fused names like Ashford and Silverhaven read as older, because centuries of use wear the gap away. Separated names like High Reach read as newer or more formal, and are common for administrative districts and planned settlements. Using both deliberately — old towns fused, new ones separated — is a pattern readers feel without articulating.
What if the settlement grows during the story?
Choose a suffix with room in it. Small suffixes — wick, stead, hollow — stay small in a reader's mind however large you say the place is. If the city is meant to be significant, use reach, gate, port or march. If it is meant to be a backwater, the small ones do that work for you.
How should I name districts inside the city?
More plainly than the city itself — usually a trade, a gate, a river bank or a hill. Keeping district names simpler is what makes the city read as the larger thing. A district with a grander name than its city inverts the hierarchy and confuses the reader about what matters.
Will these collide with real place names?
Very likely, because the generator uses the same morphology real places do, and nothing here is checked against any register or map. That is usually harmless. What is worth avoiding is setting unpleasant fictional events in a real, findable town of the same name, so search anything you intend to publish.
