How to name characters and places
· The StoryProp team
A draft can move at a steady clip for weeks and then stop dead because a woman walks into a room and needs a name. You try three. One belongs to someone you went to school with. One sounds like a brand of paint. The third is fine, which is worse, because fine names slide off the page and take their characters with them. So you type NAME TK and keep going, and by chapter nine you have four placeholders and a decision you keep postponing.
It matters, but not mystically. Naming is a craft problem with a few levers: how a name sounds in the mouth, what era and place it belongs to, whether it can be confused with the other names in the book, and — in invented worlds — whether it looks like it came out of a language rather than off a keyboard. A name generator helps with none of those. It is a quarry, not an oracle: plausible strings by the page, and no judgment about which fits the person you have half-written.
Sound does half the work
Say the candidates aloud; the mouth knows things the eye does not. Plosives — b, d, g, k, p, t — stop the air and land like a struck object. Kit. Brack. Dov. They read as blunt, decisive, brittle. Liquids and continuants — l, m, n, r, s, and the long vowels that travel with them — pour rather than strike. Elowen. Marisol. Leander. They read as fluid, older, more ceremonial. None of it is a law: a hard man called Lyle is interesting precisely because the sound argues with him, and an argument between a name and its owner beats a match.
Length and stress do their own work. One-syllable names are hard to sentimentalize and easy to shout across a yard, which is why so many hard-bitten protagonists have them and so few epic queens do. Longer names buy formality, distance, and room for a diminutive — and who is permitted to use the short form is a fact about a relationship. A woman who is Katherine at work, Kate to her friends, and Kit only to her brother has been described before she says a word.
Names carry a time and a place
Names are the most reliably dated objects a person carries. Fashions move in waves: a name that sounds like a young mother in one generation sounds like a grandmother two generations on, then returns for a newborn. Readers rarely know why a name feels wrong for a character's age, but they feel it. The fix is among the cheapest research in fiction: find what was common where and when your character was born, then choose a little off the center of that list. Dead center is invisible; too far out and the name becomes the loudest thing about the person.
Then ask who did the naming. Parents name children out of their own lives: a saint, a grandfather, a singer they loved, a wish for the child to stand one rung higher than they did. That is why names carry class and region and faith so efficiently, and why the choice can plant a fact you never state outright. A boy named for an uncle who died young arrives with a family history attached. Naming is a small hinge into the larger work of building characters readers believe.
The confusion audit
Once the cast exists, stop judging names one at a time and look at them as a set. Readers do not really read names, they recognize shapes: first letter, rough length, one distinctive letter in the middle. Two characters whose names share an initial will blur, especially minor ones met once and rediscovered eighty pages later. So will two names with the same syllable count and stress pattern, and two that end alike. Marla and Carla is a joke everyone sees coming; Anders and Ambrose in one scene is a real problem nobody notices while drafting.
The audit takes ten minutes. List every named character in one column, alphabetized, with the place names beside them. Look for repeated initials, repeated endings, repeated rhythm — and check the columns against each other, since a reader asked to keep Ashford and Ashbourne apart in the same county is being taxed for nothing. Then read both lists aloud, fast; anything you stumble over or blend is a candidate for change.
Take a quiet realist manuscript — call it “The Quiet House” — with Mara and Daniel at its center. They sit well apart: different initials, different rhythm, one soft and one formal. Had the second been Marcus, every page holding both would have taxed the reader for nothing. That is the whole test — not whether a name is beautiful, but whether it is unmistakable in company.
Fantasy place names, and how places actually get named
Invented place names go wrong in one particular way: made all at once, by one person, in one mood, they come out sounding like siblings. Real place names are sediment. Most began as a description (Blackwater, Longbridge, Redhill), a possession (Aldric's ford, worn down over generations into Aldford), a function (Saltmarket, the Tanneries, Gallows Lane), or a commemoration — a saint, a battle, a king who needed flattering. Borrow the mechanism, not the syllables: decide who named the place, in what language, and what they were pointing at, and the name comes out with grain.
The richest trick is disagreement. Places get renamed by whoever takes them, and the people already living there go on using the old name in their kitchens. One town with two names — the official one on the tax rolls, the one the locals say — tells a reader about occupation, memory, and grudge without a paragraph of history. You never have to write that history; keep both names straight and let each character choose. This is naming doing worldbuilding's job, a subject of its own — see worldbuilding without the wiki trap — but the narrow point holds: the name is an artifact, and artifacts imply.
Invented names without the apostrophe soup
The apostrophe has become fantasy's default seasoning, sprinkled over names to signal otherness: Ka'thal, Ry'ven, Dae'nur. In real writing systems the mark does a job — it stands for a glottal stop, a sound the alphabet has no letter for, or a syllable that dropped out. Used as decoration it carries no information, so the reader cannot pronounce the name, and an unpronounceable name gets skimmed. Skimmed names do not stick, and a cast of unstuck names makes a book hard to follow for reasons unrelated to its plot.
The alternative is not building a language but building a small habit. Choose a handful of sounds a culture likes and one or two it never uses — the river people favor l, sh, and long vowels, and have no hard g — then settle on a syllable shape and keep to it. Invent two or three pieces that mean something: a suffix for “of the river,” a prefix for “child of.” Now Ashelin and Sheloa look related, because they are, and the names up the mountain sound like a different mouth made them, because it did. That contrast — kin within a culture, strangers across it — is the payoff, and it costs a page of notes rather than a grammar.
Renaming late without breaking the book
You will sometimes get it wrong and find out at chapter twenty. Rename anyway; a name you flinch at every time you type it costs more than the change does. But do it deliberately, because a blind find-and-replace is a small demolition. Names that are also words are the classic trap: replacing Will, Rose, Reed, or Grace rewrites sentences with no bearing on the character. Then come the derivatives no search will catch — a nickname, a surname shared with a cousin, initials on a monogrammed case, a pun in dialogue, the letter someone signs at the bottom of a note.
The subtler damage is acoustic, because prose absorbs its names. A line built on a name's rhythm — a shout that fits one syllable, an alliterative run, a sentence whose last beat lands on the old vowel — goes limp when the new name drops in and the sentence stays as it was. A rename is really two passes: the substitution, then a reading of every scene where the name is spoken. The derivatives and the ruined rhythms surface in that reading, not in a search box, and finding them is your eye's job. What software decides is what happens after you find them, which is why the working method of your novel writing software counts more than its cleverness. Pointed revision — select the line you flagged, say what you want changed, and watch unrelated material stay as it was — keeps each repair local instead of scattering fresh damage through the scene. Because StoryProp keeps your earlier drafts, the swap can be its own pass, compared against what came before and restored if the new name proves worse in the mouth than on the list. A confirmed name becomes a record the agent reads before writing, so new pages work from it rather than the old one.
Naming rewards a little system and punishes agonizing. Say it aloud. Check it against where and when the character was born, and against every other name in the manuscript, characters and places together. If it is invented, check it against the sounds of its own culture and take the apostrophes out. Then commit, write the placeholder out of the draft, and get back to the scene. Almost nobody abandons a book over a name. Plenty of readers abandon one over four characters they cannot tell apart.
Renaming is the piece of naming craft that gets more expensive the longer you wait. StoryProp makes the repair a pass rather than a scramble: point at the line you found and say what should change, keep the earlier version to compare against and restore from, and let a settled name become canon the agent reads before writing.