A Guide to Epithets, Titles and Bynames
The Bold, of Gondor, Ironside, Your Grace — three different systems doing three different jobs. How each one is earned, and how to use them.
"Aragorn the Mighty." "Ivan the Terrible." "Duke of York." Three names, same shape — a first name plus something bolted on. Writers and game masters reach for a name generator and treat that bolt-on as one interchangeable thing: an epithet, a title, a byname, whatever, just a cool tag after the name. It isn't one thing. It's three different systems, each with its own rules for who hands it out, whether it survives the person who first earned it, and how it disappears.
Get the system wrong and the name rings false the moment someone who knows the history looks at it — a peasant blacksmith doesn't get "of York," and a deposed king doesn't keep being called "the King" once the crown is gone. This guide untangles the three, shows the real history behind each, and gives you the vocabulary to pick the right one on purpose.
Three systems, one confusing word
Start with plain definitions, because the confusion begins here. An epithet describes a quality or trait, usually in a narrative or poetic register — it tells you something about the person's character or role. A title is a granted position inside a hierarchy — a crown, an order, a senate confers it, and it marks office, not personality. A byname is a name the surrounding community hangs on someone to tell them apart from the next person with the same first name — earned by a deed, a feature, or a trade, often unflattering, and it belongs to the person, not to a role or a poem.
All three take the same grammatical shape in English — "Name + the/of + descriptor" — which is exactly why they get lumped together. "Alexander the Great" (epithet), "Sir Alexander" (title), and "Alexander Smith" (byname turned surname) look like cousins. They aren't. They come from different sources, obey different rules of transmission, and vanish in different ways. The rest of this guide walks through each one on its own, then puts all three side by side.
Epithets — descriptive, poetic, sometimes formulaic
An epithet attaches a quality to a name, usually to make a point about character, reputation, or role rather than to distinguish one Alexander from another Alexander walking down the same street. There are two flavors worth separating, because they behave differently.
The first is the formulaic epithet, best known from Homer. "Rosy-fingered Dawn," "swift-footed Achilles," "bright-eyed Athena" — these aren't one-off descriptions someone thought up for a single scene. They're fixed phrases that recur every time the name is spoken, built to fit the meter of oral poetry and to help a reciting bard hold a very long poem in memory without a script. The epithet is practically part of the name — you rarely get "Achilles" without some variant of "swift-footed" trailing behind him, and the phrase doesn't change to fit what's happening in that particular scene.
The second is the isolated epithet: a single, unique tag attached to one specific person because of what they did, not because a poem's rhythm needed filler. "Alexander the Great" and "Catherine the Great" aren't formulaic — nobody calls every conquering monarch "the Great" as a matter of course, and the phrase doesn't repeat every single time their name appears in a text the way "swift-footed" does for Achilles. It's a one-time verdict that stuck. Grammarians have a term for this distinction: epitheton necessarium for an epithet needed to tell two people apart (closer to a byname's job), versus epitheton ornans, an ornamental epithet added for color or praise, which is what "the Great" really is.
Fantasy naming leans on the same instinct when it builds gods. Our god name generator pairs a divine name with a domain epithet — "of War," "of Love," "of Death," "of the Storm" — and that epithet functions exactly like a Homeric tag: it isn't optional flavor text, it's the part of the name that tells you what the god actually does. Say "Aurelia" alone and you've named a goddess with no portfolio. Say "Aurelia of the Storm" and every future mention carries the same phrase, the same way "rosy-fingered" rides along with Dawn in every book of the Odyssey.
Titles — granted, hierarchical, tied to office
A title is conferred by an institution — a crown, a chivalric order, a senate, a church — and it marks a position inside a hierarchy, not a personal trait. This is the cleanest of the three systems to define because it has the clearest rule: the title belongs to the office, not to the person wearing it at any given moment.
That single rule explains a lot of odd-sounding history. A deposed king stops being "the King" the instant he's deposed, even though he's still breathing and still answers to his own first name — the office moved to someone else, and the title moved with it. Compare that to an epithet: nobody strips "the Great" from Alexander after his death, because the epithet was never tied to an office he could lose. A title can be revoked by the same body that granted it; an epithet, once it sticks, just keeps being true or gets forgotten — there's no formal ceremony for taking it back.
"Sir" and "Dame" are a clean example of a title in miniature. Our knight name generator lets you attach a Sir/Dame prefix to a generated name, and it's worth noticing what that prefix does not do: it doesn't describe the knight, doesn't reward a specific deed by name, and isn't earned through reputation the way a byname is. It's granted in a dubbing ceremony by someone with the authority to grant it, and it marks membership in an order. Take away the ceremony — strip the knighthood — and "Sir" goes away too, exactly like the deposed king losing "the King." Compare that to the same generator's byname-style epithets ("Ironarm," "Crookback," "the Accursed") — those came from deeds and features, not from a knighting ceremony, and no institution can revoke them.
Bynames — earned, often blunt, never inherited (at first)
A byname is handed out by the people around someone — neighbors, a warband, rivals, a village — to mark them off from every other person carrying the same given name. Where an epithet is often literary and a title is always institutional, a byname is social: it comes from whoever is standing close enough to notice the limp, the trade, or the massacre, and it sticks because it's useful for gossip and record-keeping, not because anyone intended to honor the person.
That's why so many surviving bynames are blunt or outright unflattering. Our viking name generator draws on genuine saga-style byname pools split by tone: the fierce set includes "Bloodaxe," "Skull-Splitter," and "the Boneless" — names that describe exactly what a person did or looked like, with zero interest in flattering them — while the classic set has softer ones like "the Red," "the Tall," and "Iron-Hand." Neither set is describing a role or an office. Both are describing a specific person, based on something that person actually did or visibly was.
That's the second key difference from an epithet: a byname is tied to the individual, not to a genre convention or a recurring narrative formula. Nobody else in the same saga gets called "the Boneless" just because it sounds heroic — it describes one man, Ivar, and nobody else. A Homeric epithet like "swift-footed" could in principle apply to more than one fast runner; a byname like "Skull-Splitter" describes a single biography. And critically, at the moment it's coined, a byname is not inherited — it describes the person who earned it, full stop. What happens to it after that is a separate story, covered a few sections down.
Real bynames, real people
Ivar the Boneless, Erik Bloodaxe, Harald Fairhair, Aud the Deep-Minded, Ketil Flatnose — these are recorded Norse bynames attached to real historical and saga figures, not invented flavor text. Some describe appearance (Fairhair, Flatnose), some describe a trait or deed (the Deep-Minded), and at least one (the Boneless) has a disputed origin that later chroniclers themselves argued about — a reminder that even "real" bynames sometimes carry legend rather than fact by the time they reach a written source.
Epithet vs title vs byname at a glance
Put all three side by side and the differences that matter — who grants it, whether it survives the person, and how it disappears — line up cleanly.
| System | Who gives it | What it marks | Inherited? | How it's lost | Example |
|---|---|---|---|---|---|
| Epithet (formulaic) | The poetic tradition / narrator | A recurring quality tied to the name itself | No — it's fixed to one figure, not passed on | Only through the tradition itself falling out of use | "swift-footed Achilles," "rosy-fingered Dawn" |
| Epithet (isolated) | Later writers, chroniclers, popular memory | A single verdict on one person's reign or reputation | No | Fades if the reputation is reassessed or forgotten | Alexander the Great, Catherine the Great |
| Title | An institution — crown, order, church, senate | An office or rank inside a hierarchy | Only via formal succession rules (e.g. feudal inheritance), not automatically to any child | Revoked, resigned, or lost when the office ends | Sir / Dame, Duke of York, Your Grace |
| Byname | The surrounding community — neighbors, crew, rivals | A specific deed, trait, trade, or origin belonging to one person | Not at first — see below | Forgotten when the person dies, moves away, or a sharper byname replaces it | Erik Bloodaxe, Ivar the Boneless |
Five types of byname
Bynames cluster into a handful of recognizable categories, and several of them left a permanent mark on modern English surnames.
| Type | What it marks | Historical example | Modern surname it left behind (if any) |
|---|---|---|---|
| Appearance | A visible physical feature | Harald Fairhair, Ketil Flatnose | Rare direct survivals; mostly stayed as saga bynames |
| Deed / character | A specific action or a defining trait | Ivar the Boneless, Aud the Deep-Minded | Generally did not become surnames — too personal to one biography |
| Occupation | The person's trade | A village blacksmith known simply as "the smith" | Smith, Baker, Fletcher |
| Place / origin | Where the person came from or lived | "Ketill from the Hebrides," a settler identified by homeland | Names like Hall, Ford, Wood (locative surnames) |
| Mocking / insult (notname) | A blunt, sometimes cruel jab at a flaw or misfortune | A "Jón the Fat" recorded to distinguish him from a thinner Jón of the same name | Occasionally softened into surnames over generations, though most stayed nicknames |
That last category has its own name in the literature: a notname, literally a "necessity name" — coined not to flatter or condemn but purely to solve the practical problem of two people in one small parish sharing a first name. It's the most utilitarian of the five, and often the least fair to the person carrying it.
Who gives each one — and who can take it away
Line the three systems up by their loss mechanism and an asymmetry jumps out: only the title has a formal procedure for taking it away. A crown can strip a knighthood. A senate can strip a consulship. There's a ceremony for granting a title, so there's a matching ceremony — or at least a formal act — for revoking it.
Epithets and bynames don't work that way. Nobody "recalls" an epithet — it fades only when the tradition carrying it stops being told, or when later opinion simply moves on and stops repeating the phrase. A byname is even more fragile: it belongs to a living community's memory, so it disappears when the person dies without the byname being written down anywhere durable, when they move somewhere nobody remembers the story behind it, or when a sharper, newer byname simply replaces the old one in daily use. There's no institution and no ceremony involved in either loss — just time, distance, and a community's attention moving elsewhere.
This is worth sitting with if you're naming characters for a long-running story: a title can be dramatically stripped in a single scene ("you are no longer a knight of this order"), but an epithet or byname has to erode — it needs a slower scene, or several, where the old name just stops being said.
How a byname becomes a surname
Bynames start out describing exactly one person. They become hereditary surnames only once a community stabilizes enough to need consistent written records — a town census, a tax roll, a parish register — and at that point, the byname stops describing a trait and starts functioning as a label passed straight to the children, whether or not the trait still applies.
"Peter the Smith" is a byname earned by an actual blacksmith. "Peter Smith's" children, recorded in the same tax roll a generation later, become "Smith" regardless of whether any of them ever touch a forge. The byname has quietly stopped being a description and started being an inherited identifier — which is the entire difference between a byname and a surname: a surname is a byname that outlived the fact that made it true. The same pattern produced Baker (from Old English bæcere, "one who bakes") and, through a slightly different route, Johnson — originally a patronymic byname meaning "John's son," describing one specific relationship, that froze into a fixed family name carried by descendants who were nowhere near being anyone's actual son named John.
Titles do not make this same jump, and the reason is structural, not incidental. A title is tied to an office, and an office doesn't automatically pass to a child the way a settled community's naming habit does — succession has to be a deliberate, separate system (feudal inheritance, election, appointment) layered on top. A blacksmith's child inherits "Smith" just by being born into the household; a duke's child inherits "Duke" only if the rules of succession say so, and plenty of historical titles were non-hereditary by design specifically to prevent that automatic drift.
Patronymic bynames are a special case
Not every patronymic byname froze into a surname the way Johnson did. Old Norse naming used a strict patronymic system — a son takes his father's given name plus -sson, a daughter takes -sdóttir — and our viking name generator generates exactly this pattern. The important detail is that the patronymic resets every single generation: Björn Haraldsson's son isn't also a "Haraldsson," he's a new patronymic built from Björn's own given name. Nothing here ever calcifies into a fixed family name the way "Johnson" did in English record-keeping — it's the same raw material as a hereditary surname, but the system never lets it settle, because each generation's byname describes a real, current relationship rather than an inherited label.
Don't do this: turning an epithet into a video-game suffix
Here's the mistake almost everyone makes once they've heard that epithets sound cool: they staple "the Mighty" or "the Wise" onto every named character as a kind of status badge, the way an RPG stat sheet lists a title next to a level number. It reads cheap, and it reads cheap for a specific, fixable reason.
A real epithet — Homeric or isolated — does one of two things. Either it's formulaic and consistent, repeated the same way every time inside one work, doing a real job (meter, memory, characterization), or it's a one-off verdict earned by something the character actually did, the way "the Great" followed a specific set of conquests. A tag that shows up once in a character's introduction and then never gets used or justified again is neither of those things — it's decoration with no mechanism behind it, and readers register the gap even when they can't name what's wrong.
The fix is simple to state and only slightly harder to do: if you give a character an epithet, either make it earn its keep by recurring the way a Homeric tag does, or tie it to a specific, visible event the reader has already seen, the way "the Boneless" or "Bloodaxe" describe something concrete rather than a vague virtue. "The Wise" attached to a character we've never seen make a wise decision is worse than no epithet at all — it announces a trait instead of demonstrating one, and it borrows the shape of a real naming tradition without doing the work that tradition actually did.
Try it — give your character the right kind of name
Now that the three systems are untangled, pick the tool that matches what you're actually naming. Building a warlord defined by a deed? Pull an earned byname from the viking name generator. Naming someone who holds a rank inside an order? The knight name generator handles Sir/Dame titles alongside separate, deed-based epithets by style. Naming a deity whose domain should ride along with every mention of their name? The god name generator builds exactly that kind of formulaic epithet in.
Try it — give your character the right kind of name
A quick way to check your instinct: ask who would actually be saying this name out loud. If it's a narrator or a poetic tradition, you likely want an epithet. If it's an institution — a crown, an order, a council — you want a title. If it's the people who actually know the character, day to day, you want a byname. Match the source to the system, and the name will carry its own justification without you having to explain it in a footnote.
FAQ
Is an epithet the same as a nickname?
They overlap but aren't identical. A nickname is the broader, modern umbrella term for any informal name substitute. An epithet specifically describes a quality or trait and often carries a formal, narrative, or poetic register — "the Great" reads differently from a modern nickname like "Chuck." Bynames are historically closer to what we'd now call nicknames, just older and often blunter.
Can a byname be inherited?
Not at the moment it's coined — it describes one specific person. It only becomes hereditary once a stable community starts recording it consistently across generations, at which point it has effectively turned into a surname (see Smith, Baker, Johnson above). Until that shift happens, each new bearer of a similar description would, in principle, earn their own separate byname.
Why do Viking names sometimes have two nicknames attached?
Because a patronymic ("Haraldsson") and a byname ("Fairhair") are doing two different jobs on the same name. The patronymic states parentage and resets every generation; the byname describes something about that specific individual — a trait, deed, or feature — and neither one replaces the other, so a fully decorated Norse name can carry a given name, a patronymic, and a byname all at once.
What's the difference between a title and a rank?
In everyday use they're often treated as synonyms, but a title tends to mark a specific granted office with ceremony attached to both getting and losing it (a knighthood, a dukedom), while "rank" more often describes a position on a graded scale within an organization (a sergeant versus a captain) that can be climbed or demoted without necessarily involving a formal granting ceremony at each step.
Do epithets have to be flattering?
No — plenty of famous ones aren't. "Charles the Fat" and "Charles the Bald" are recorded epithets for real Carolingian rulers, and neither is complimentary. An epithet's job is to distinguish or characterize, not to praise; whether it flatters the bearer is beside the point.
Sources and further reading
Generators from this guide
Put any of this into practice — every tool below is free and needs no sign-up.