Read it in dialogue and UI
A name that looks fine in a shortlist can still break once it appears in spoken lines, menus, quest text, or map labels.
Guide
A practical review list for checking whether character, place, and faction names still feel coherent before you lock them in.
Definition
A fantasy naming checklist should catch the failures that look small on one page but compound across a manuscript, campaign, or game build. The point is not to make every result elegant. It is to confirm that names are readable, internally related, and matched to the role they need to carry on the map or in the cast.
A name that looks fine in a shortlist can still break once it appears in spoken lines, menus, quest text, or map labels.
Characters, cities, houses, and factions should sound like they belong to overlapping language families instead of isolated naming experiments.
Broad pages help early exploration, but specialist pages usually produce stronger final names when the brief narrows.
Patterns
If readers or players cannot comfortably say the name, visual flair will not rescue it.
Capitals, regions, districts, and demonyms should sound related without collapsing into one indistinguishable naming layer.
Remove names that feel too close to existing cast members, nearby places, or famous franchises.
Common mistakes
You miss world-level inconsistency when every item is judged in isolation.
A flexible first-pass name can become the weakest option once the project knows the exact naming lane.
Menu labels, codex entries, and subtitles often reveal awkward names faster than the main prose does.
Worked example
Treat this as a mini review board. The point is to decide what survives, what needs specialist revision, and what should be cut before the names become canon.
Keep it if the cast needs a readable lead. It passes the dialogue test and shares a root that can support later places.
Keep it if the map needs a trade city tied to the lead culture. It is readable and distinct from the personal form.
Revise it because the suffix feels generic and too close to the personal root. It may sound like filler worldbuilding.
Keep it if the faction is public and ceremonial. Reject it for thieves or frontier scouts because the tone is too polished.
Cut or split it. The compound is overloaded and reads more like a placeholder item than a usable relic.
Keep as a demonym if Caldrin exists on the map. It is compact enough for prose and adjective use.
Move it to the elf workflow. It may be strong, but it belongs to a narrower cadence than the broad shortlist.
Move it to a myth or archive-style project. The phrase has dossier texture that may not fit standard fantasy prose.
Application note
Make a small table with columns for role, pronunciation, neighbor conflict, culture root, and final surface. Review every candidate against those columns. This keeps the checklist from becoming a vague taste exercise where the most dramatic label always wins.
If a candidate fails, write the reason in operational language: too close to another NPC, too ceremonial for a district, unreadable in UI, wrong cadence for lineage, or no stable source place. A specific failure tells you which page or revision pass should come next.
Workflow checklist
Next step
This page works best when the next click happens after you have actual candidates to audit.
Fantasy Name Generator, City Name Generator and How Fantasy Names Work give you the broad reset, place-specific fix, and concept explanation when the shortlist fails a check.