To name fantasy characters and places well, treat naming as world-building rather than decoration. Give each culture its own consistent sound, so names from the same people rhyme with each other and names from a rival people clearly do not, because that internal consistency is what makes an invented world feel real. Let the sound of a name do work before its meaning does, since readers feel a harsh name as harsh and a soft one as soft long before they learn what it refers to. Keep names pronounceable, because a reader silently skips over a name they cannot say and the character blurs. Name places as if they have history, since real place names are almost always compressed descriptions of what happened there. And in a long web serial, keep every name distinct and recorded, so you never accidentally reuse one or introduce two that a reader will confuse.
How do you name fantasy characters and places?
You name fantasy characters and places by working from the culture down to the individual rather than inventing each name in isolation, because a name's job is to tell the reader where it came from, and that only happens when names from the same world share an underlying logic. The single most common naming failure I see is not ugliness, it is randomness: a cast where one character is Kael, the next is Brynjolf, the third is Ashwe'ynn, and the fourth is Bob, with no sense that any of them come from the same place or even the same book. The fix is to decide, per people or region, what their names should sound like, how long they run, which consonants and vowels they favor, whether they carry surnames or patronymics or house names, and then to generate every individual name to fit that shape. Do that and a name starts to imply a whole culture the moment it appears on the page, which is the entire point of naming in fantasy and the thing a random name can never do.
This matters more in web fiction than almost anywhere else, because a serialized story introduces names a few at a time across hundreds of chapters, and the reader has to absorb each one on first contact without a cast list to lean on. Running a web fiction platform, I see the authors who name well pull ahead not because their names are prettier but because their names are legible and consistent, so a reader meets a new character and immediately files them with the right faction because the name sounds like the faction. Naming is one of those craft skills that looks like flavor and is actually structure, and it sits alongside the harder world-building problems I laid out in the broader guide to world-building for web fiction, because a name, like a magic system, is a promise about how the world holds together.
Make each culture sound like itself
The foundation of good fantasy naming is internal phonetic consistency, meaning that all the names from one culture should feel like they were drawn from the same language, and names from a different culture should feel audibly foreign to it. This is the principle J.R.R. Tolkien built his entire Middle-earth around, having invented Quenya and Sindarin as two distinct Elvish languages with their own sound systems before the stories that used them, which is why Elvish names like Galadriel and Celeborn hang together while a Dwarvish name like Gimli or a Rohirric name like Éomer sits in an obviously different register. You do not need to construct a working grammar the way Tolkien did, and almost no one should, but you do need each people to have a recognizable palette of sounds. Brandon Sanderson does this without invented languages in The Stormlight Archive, where the Alethi favor names built on symmetry and a cluster of sounds like the sh and th that make Shallan, Dalinar, and Jasnah feel of a piece, while the Herdazians and Thaylens sound different on purpose.
The most efficient way to get this consistency, if you are not going to invent a language, is to borrow the phonetics of a real one and file off the recognizable words. Pick a language whose sound you want, Welsh for something lilting and consonant-rich, Old Norse for something hard and northern, Swahili or Finnish or Nahuatl for something a Western reader will not immediately place, and let its typical syllable shapes and letter combinations guide the names you build. George R.R. Martin does a version of this in A Song of Ice and Fire, where the Valyrian names carry a distinctive vowel pattern, the doubled and ae-heavy sound of Rhaegar, Daenerys, and Viserys, that instantly marks a character as Targaryen blood before you are told anything else. That is naming doing structural work, and it costs you nothing once you have decided the pattern. My feeling is that if you fix only one thing about your naming, fix this, because a consistent sound-world is what turns a list of names into a place.
Sound carries meaning before definition does
A fantasy name communicates through its sound long before the reader learns what it means, which is why phonaesthetics, the felt quality of a name's sounds, matters more than any hidden etymology you might bury in it. Readers experience a name with hard stops and clustered consonants as harsh or dangerous, and a name with open vowels and soft consonants as gentle or noble, entirely independent of definition, and the skilled namer uses this rather than fighting it. Tolkien, who thought about this more than any writer in the genre, famously held that the phrase cellar door was among the most beautiful-sounding in English despite its mundane meaning, precisely to make the point that sound and sense are separable. The practical lesson is that you can make a villain feel threatening through the mouth-feel of their name alone, without the embarrassment of naming them something like Lord Deathstrike, which crosses from connotation into parody and breaks the spell.
Sound can also be used for deliberate contrast, and knowing when to undercut the fantasy register is part of the craft. Matt Dinniman's Dungeon Crawler Carl, which began on Royal Road before moving to print in 2024, gets a great deal of its comedy from naming its heroes Carl and Princess Donut, aggressively ordinary names dropped into a lethal cosmic game show, and the mismatch is the joke. That works because Dinniman is in full control of the register and breaking it on purpose, which is different from breaking it by accident. Meaning can also be made literal when the story is about naming itself, as in Ursula K. Le Guin's A Wizard of Earthsea from 1968, where knowing a thing's true name grants power over it and names are therefore guarded, or in Patrick Rothfuss's The Name of the Wind from 2007, where Naming is the deepest form of magic. But those are cases where the story has made names its subject. For the ordinary run of characters, let the sound carry the weight and keep the literal meaning under the surface where the reader can feel it without being told.
The apostrophe trap and the pronounceability tax
The most damaging naming habit in the genre is reaching for apostrophes and consonant clusters to signal exotic, because an unpronounceable name is one the reader silently skips, and a skipped name is a character who never fully lands. When a reader hits something like Xyl'gth'aa or Vr'nakssh, they do not stop and work out the phonetics, they assign it a vague mental placeholder and read past it, which means every appearance of that character arrives blurred. The apostrophe convention is not baseless, and it has honorable roots. Anne McCaffrey's Pern novels use it with real logic, where a dragonrider's name contracts after they Impress a dragon, so a man named Fallarnon becomes F'lar, and the apostrophe marks an actual dropped sound. The trouble is that the convention got copied without the logic, so a generation of names now sport apostrophes that represent nothing at all except an author's wish to seem otherworldly.
My advice is to use an apostrophe only when it stands for a real sound your reader can produce, most often a glottal stop, the little catch in the middle of uh-oh, and to keep the number of unusual names in play at any one time low. A world can absolutely contain a hard-to-pronounce name or two, and sometimes difficulty is the point, but if every name taxes the reader, the cumulative friction pushes them out of the story. This is the same instinct behind a lot of what makes prose readable, and it rhymes with the way readers quietly bail on passages that make them work too hard, which I got into from a different angle in why readers skip your descriptions. A name is a tiny piece of prose the reader has to process every single time the character appears, sometimes thousands of times across a serial, so a name that is a pleasure to say pays that dividend over and over, and a name that is a chore charges the same tax just as often.
Naming places is naming history
Place names should read as compressed history, because that is what real toponyms almost always are, which means the most grounded fantasy geography is built from the world's own words rather than from pure invented sound. Look at how real places got their names and the pattern is overwhelmingly descriptive: Oxford was a ford where oxen crossed, Newcastle was a new castle, Los Angeles was named for angels by its founders, and the plainness of that origin is exactly why those names feel solid rather than confected. A fantasy town called Blackwater Crossing, Gravemark, or Saltmarsh tells the reader something true about the terrain and the past in the act of being said, whereas a town called Zynthoria tells them only that the author wanted an exotic sound. Will Wight's Cradle, completed at twelve books in 2023, names its stages of power after plain, evocative materials, Copper and Iron and Jade and Gold, and the very ordinariness of those words makes the ladder feel like something a real culture would have named.
The deeper payoff of descriptive place names is that they start to imply a map and a history you never have to explicitly write. If your world has a Kingsford and a Queensbridge and a Grey Watch, the reader infers a monarchy, a river system, and a militarized frontier without a word of exposition, and that inference is the cheapest and most convincing world-building there is. This is naming doing the same job that a good magic system does, encoding the logic of the world into something the reader can read off the surface, which is why I treat it as continuous with the work of building a magic system that holds together rather than as a separate cosmetic layer. Build your places out of your world's own vocabulary, layer in a few names that are clearly older or borrowed from a conquered people to suggest deep time, and the geography will feel lived-in for the same reason the character names do, because it looks like it came from somewhere.
Keeping a long cast of names straight
In a web serial the naming problem does not end at inventing good names, it extends to keeping every name distinct and recorded across a story too long for you to hold in memory, because the failure mode at scale is not an ugly name but a confusing or duplicated one. Two problems compound over hundreds of chapters. The first is similarity: a cast with Jon, Jorah, Joffrey, and Jaime, to borrow from Martin, forces the reader to disambiguate every time, because we recognize names mostly by their first letter and overall silhouette rather than by reading them fully, so names that share a shape blur into each other. The second is accidental reuse, where an author names a throwaway innkeeper in an early arc and, three hundred chapters later, having long forgotten, gives the same name to a major antagonist. Both are invisible while you are drafting and glaring to a reader who has the whole serial in their head, and in a genre with an audience this attentive, as The Wandering Inn by pirateaba and its reader-maintained wiki of hundreds of names demonstrate, someone always notices.
The reliable fix is the same infrastructure that keeps the rest of a long serial coherent, which is a searchable record of every name you have committed to the page, checked before you commit a new one. This is where naming folds directly into the larger discipline of tracking a cast across a long serial, because a wiki that already holds each character's traits and relationships is also the list you scan to make sure your new swordsman is not the fourth name starting with Kae and is not reusing a name you burned on a corpse two hundred chapters back. The wiki in IlorisNovel is built to carry exactly this, with an @mention that ties a name in your draft to its entry so the cast stays searchable, and the AI world builder can rough out a set of culturally consistent names for a new faction, names that already share a sound-world, for you to edit rather than inventing each one cold. The point is not the feature, it is the principle that at web fiction scale, keeping your names distinct has to become a lookup rather than a feat of memory, the same way every other thread of continuity does.
A workable naming order for most web serial authors, then, is to decide each culture's sound before you name anyone from it, generate individual names to fit that pattern, say every name out loud to check that it is pronounceable and distinct from the cast you already have, build place names out of the world's own descriptive words, and record every name the moment it lands on the page so the serial never contradicts or repeats itself. Naming looks like the most decorative part of world-building and is quietly one of the most structural, because a name is the first and most frequent piece of the world a reader touches. If you want to feel out how a set of names reads before you commit a serial's worth of them to the page, you can open the editor and world builder with no account, which is the lowest-friction way to see whether the names you are imagining actually hold up once the cast starts to grow.
Common questions about naming fantasy characters and places
How do you come up with fantasy names?
Start from the culture, not the character. Decide what a given people's names should sound like, harsh or flowing, short or long, and which sounds they favor, then build individual names to fit that pattern so they feel related. Real languages give the best raw material, because borrowing the phonetics of Welsh, Old Norse, or Swahili yields names that feel coherent without being recognizable. The goal is names that sound like they came from somewhere, which is what separates an invented world that feels real from one that feels assembled at random.
Why do fantasy names have so many apostrophes?
Apostrophes became a genre shorthand for exotic, borrowed loosely from real conventions like Anne McCaffrey's Pern dragonriders, whose names contract after they bond a dragon. The problem is that a scattered apostrophe rarely encodes anything and mostly tells the reader a name is meant to feel foreign. A name like Q'thal'zx signals difficulty without signaling meaning, and readers respond by skipping it. Use apostrophes only when they represent a real sound, such as a glottal stop, and never as decoration.
How do you name places in a fantasy world?
Name places the way real places got their names, which is almost always as a compressed description of a feature, an event, or a founder. Oxford was a ford for oxen and Newcastle was a new castle, and that plainness is exactly why real toponyms feel grounded. A fantasy town called Blackwater Crossing or Gravemark tells the reader something about the world's history and geography for free, whereas a name invented purely for sound tells them nothing. Build place names out of the world's own words and they will start to imply a map.
How do you keep fantasy names from being too similar?
Vary the first letter and the shape of your names deliberately, because readers distinguish names largely by their opening sound and overall silhouette, not by reading them fully each time. A cast with Jon, Jorah, Joffrey, and Jaime forces the reader to slow down and disambiguate, which pulls them out of the story. In a long web serial the risk compounds, so keeping a searchable list of every name you have used lets you check a new one against the whole cast before you commit it to the page.
Should fantasy names mean something?
They can, but the meaning should usually stay beneath the surface rather than announcing itself. A villain literally named Lord Deathstrike reads as parody, while a name whose harsh sounds simply feel dangerous does the same work without breaking the spell. The strongest fantasy names carry connotation through their sound and their cultural fit, and reserve overt meaning for cases where the character or reader is meant to notice it, the way true names carry literal power in Ursula K. Le Guin's Earthsea.
by Jacob Tam · July 22, 2026
I run IlorisNovel, a platform for writers of web fiction. If you want to see what naming and building a world here feels like, you can try the editor with no account.