Unpronounceable Names: What Readers Actually Do With Them

Here is what a reader does when they hit a name they cannot pronounce. They do not stop and work it out. They glance at the shape of the word, register something like "the one starting with X", and read on. The name becomes a visual token rather than a sound.

This matters more than it sounds. A name held as a shape rather than a sound is harder to recall, harder to distinguish from other names of similar shape, and impossible to discuss out loud, which means readers cannot easily recommend your book by talking about your characters. It also collapses entirely the moment the work becomes an audiobook, where a narrator has to make a decision you never made.

None of this is an argument for naming everyone Dave. It is an argument for knowing what difficulty costs, so you spend it where it earns something.

What actually makes a name hard

Difficulty is not length. Alessandria is long and easy; Xzq is short and impossible. Four things drive it.

Consonant clusters the reader's language does not permit. Every language has rules about which consonants may sit together and where. English tolerates str- at the start of a word and -nths at the end, but not tl- initially or ng- initially, which is why Nahuatl and Vietnamese names give English readers trouble in a specific, predictable place. When you invent a name, you are unconsciously either obeying or breaking your reader's cluster rules.

Ambiguous vowels. English spelling maps sounds to letters loosely, so an invented name with ea, ou, or a bare y in it has several defensible pronunciations and the reader must guess. Two readers will guess differently, which is how book clubs end up arguing.

No obvious stress. Readers need to know which syllable carries the weight. Familiar patterns supply this automatically; invented four-syllable names often do not, leaving the reader to place stress arbitrarily and inconsistently, sometimes differently on different pages.

Visual similarity to another name in the same book. The most damaging and the least noticed. Two hard names of similar shape are not twice as hard as one; they are effectively the same token, and readers will conflate the characters.

The apostrophe question

The apostrophe in fantasy names has been mocked for decades, mostly fairly, but the mockery obscures a real distinction.

In real writing systems, an apostrophe in a transliterated name usually encodes something specific: a glottal stop, an ejective consonant, a syllable boundary, a dropped element. It is doing linguistic work.

In most invented names it is doing decorative work. It signals "this is exotic" without specifying anything, and because it specifies nothing, the reader cannot pronounce it and simply skips it. Ka'lith and Kalith are read identically by almost everyone, so the apostrophe has added visual noise and no sound.

The rule that follows is straightforward. Use an apostrophe only if you can state what it does, and only if you use it consistently for that one job everywhere in the setting. If it marks a glottal stop, it must always mark a glottal stop. If you cannot finish the sentence "this apostrophe means...", delete it. The name loses nothing, because the reader was already deleting it.

Keeping strangeness that survives

Strangeness is worth having. The goal is strangeness that a reader can still hold as a sound. Three reliable methods.

Familiar sounds, unfamiliar order. Build only from phonemes your reader's language already contains, but combine them in arrangements it does not use. Every syllable is individually pronounceable, so the reader never stalls, yet the whole is clearly not from here. This is the highest-value technique available and it is underused.

One difficult element, not four. A name can carry a single unusual feature and stay usable. Give it one, and make the rest of the word plain. Difficulty compounds far faster than it accumulates.

Spell it the way it sounds. If you have invented the language, you also control the transliteration, and there is no reason for it to be irregular. Fictional cultures do not owe us historical spelling drift unless you specifically want that.

Generators grounded in a real tradition help here because their output inherits a real phonology that a real population of speakers already found sayable. An island name generator or a forest name generator gives strangeness with the pronounceability already solved, which you can then adjust rather than construct from scratch.

Difficulty is a budget

The most useful way to think about this is as a budget spent across the whole book. A reader will absorb a small number of genuinely difficult names and hold them, because those names came with enough repetition and importance to justify the effort. Spend the budget on the protagonist, the antagonist, and the one place name that recurs constantly.

Spend it on a minor lieutenant who appears in three chapters and the reader will not pay, and that lieutenant becomes "the one with the Z" forever. Minor characters should have the easiest names in the book, which is the exact opposite of what usually happens, because minor characters are named quickly and the writer reaches for the generator's most striking output.

Two tests

First, the cold-reader test. Give someone the name written down and ask them to say it. If their pronunciation surprises you, your spelling is not communicating your intention, and the spelling should change rather than the reader.

Second, the narrator test. Imagine an audiobook narrator encountering the name with no glossary. What do they do? If the honest answer is that they would have to email you, you have written a name that only exists correctly inside your own head. That is a fine place for it to start and a poor place for it to stay.