Goliath Names in 5e — Birth Name + Deed Nickname

A goliath's name in D&D 5e is really two names in one. There's the short, hard-syllable birth name their clan gave them — Kavaki, Ilma, Uthal — and then there's the nickname they earned by doing something the tribe won't forget. Kavaki "Stone-Skinned." Ilma "Wolf-Chaser." Uthal, the Cold-Hand. If you've been rolling goliath characters in isolation and stopping at the birth name, you're leaving the more interesting half of the tradition on the table.

The 2024 Player's Handbook made goliaths a lot more visible at the table. The lineage picked up powerful ties, small giant-blooded traits, and a size step that lets a level-one goliath actually feel like a mountain-clan warrior instead of a slightly taller human. That's driven a wave of new players asking the same question — what does a goliath actually name themselves? This is a walkthrough of the naming convention as written, the culture it points to, and how to run it in play so the nickname earns itself over the course of the campaign.

The two-name pattern, explained

Goliath convention as it appears in the 5e material breaks a name into three parts, though most players and DMs only ever say two of them out loud.

The birth name is short. One or two syllables, hard consonants, clipped vowels. Aukan. Gauth. Kavaki. Nalla. Uthal. The pool is intentionally small because names in a mountain clan get reused across generations — you might meet three Nallas in a single winter camp, distinguished only by which family they belong to and what they've done. Birth names carry no gender-specific ending in most published examples, and that's a real feature, not an oversight. More on that below.

The nickname is where the character lives. It's a compact reference to a deed, a physical trait, or a moment that stuck. Two forms show up in the source material:

• Subject + action — "Stone-Skinned," "Wolf-Chaser," "Cliff-Climber," "Storm-Bane." These read like short story titles. Somewhere behind "Stone-Skinned" is the day Kavaki survived a rockslide that killed her hunting partner, and behind "Wolf-Chaser" is the winter Uthal ran a wolf pack off a herd across two miles of frozen tundra.
• Solo epithet — "Two-Blade," "Silent-Step," "Broken-Tusk," "Kind-Voice." Same idea, but a single hyphenated word instead of the subject-verb pair. These tend to attach to quirks — how the goliath fights, how they carry themselves, a scar people can't stop noticing.

The clan name is the third piece, used at formal moments or when a goliath introduces themselves to outsiders who need to know which mountain they came from. It's rarely spoken casually. Most tables skip it unless the campaign is set in or near goliath territory, and that's fine — the birth-name-plus-nickname pair is the load-bearing wall.

The default written form puts the nickname in quotes right after the birth name: Kavaki "Stone-Skinned." You'll also see it unadorned (Uthal Wolf-Chaser, in the same slot a surname would occupy) or, for a more ceremonial feel, with a comma and article (Ilma, the Cold-Hand). All three are valid — pick the one that matches how your character introduces themselves in-fiction.

Why 2024 5e made goliaths a much bigger deal

Goliaths existed in previous editions, but the 2024 Player's Handbook did something structurally different: it moved the lineage into the core book and gave it real mechanical weight. New goliath characters get a small-giant ancestry bump, a size step that opens up unusual grapple and shove interactions, and giant-adjacent traits that reward playing the character as a physically dominant presence in the room. The mountain-clan flavor now sits alongside classic core options like elves and dwarves, and that visibility change alone put goliaths on a lot more character sheets.

The knock-on effect for naming: DMs are seeing more goliath NPCs in their prep queues, and players are workshopping goliath characters as first-time picks rather than as niche builds. The birth-name-plus-nickname pattern is a huge part of what makes those characters feel distinct from a tall human fighter, so leaning into it is worth doing early — ideally at session zero, before the character has any lived experience to draw a nickname from.

Gender-neutral by default

Read the goliath name pool as published and you'll notice something the source doesn't announce loudly: most goliath names aren't gender-coded. Aukan, Kavaki, Manneo, Nalla, Paavu, Thalai, Uthal, Vaunea — the same names show up on lists tagged female, male, and neutral because mountain-clan tradition, as the fluff frames it, ranks people by what they've done, not by the shape they were born in.

For a nonbinary or gender-nonconforming player, that means goliath is one of the more comfortable ancestries to inhabit without having to negotiate around the name pool. You don't have to pick a "female name" or a "male name" — you can pick a goliath name. The nickname does more of the identity work anyway: "Stone-Skinned" tells a table who Kavaki is, and no one at the table needs a pronoun to understand why she's the one standing in the front rank.

Practical suggestions for gender-neutral goliaths:

• Draw the birth name from the shared pool: Aukan, Manneo, Nalla, Thalai, Uthal, Vaunea, Kavaki, Meavoi. All appear as neutral in the published lists and read cleanly regardless of the character's gender presentation.
• Skip gendered pronouns in the nickname's implied story if you want the character read as ambiguous. "Kind-Voice" and "Silent-Step" work; a nickname like "The Widow-Maker" quietly ships assumptions.
• Let the clan name do more work. A goliath introducing themselves as "Meavoi of Karakset" tells the room what mountain they're from without ever needing to say what body they're in.

Skip the writing: use the goliath name generator

If you're at session zero and staring at a blank character sheet, the goliath name generator will spit out a birth-name-plus-nickname pair in the right convention every time you click. Pick a gender option (or leave it at "any" for the shared pool), decide whether you want the nickname included, and roll a few batches. Read them aloud — goliath names are meant to be spoken, and one that trips off the tongue at the table beats one that only reads well on paper.

A few workflow tips:

• Roll five or six results and pick the birth name from one, the nickname from another. The generator draws each independently and mix-and-matching is fair game.
• If you're building a party of NPC goliaths — a raiding band, a scouting party, an extended family — generate a batch, then hand-tune surnames or clan tags so it's clear who's related to whom.
• Use the "no nickname" option for a fresh recruit whose deed hasn't happened yet. Give them the birth name and let the table award the nickname mid-campaign. More on how to do that in a moment.

If your table plays multiple systems and you're building parallel characters, the Pathfinder name generator covers Golarion-flavored ancestries the same way, and if your D&D party needs a mixed lineup, the dragonborn name generator and the tabaxi name generator handle the two other ancestries with the strongest naming conventions in the 2024 rules.

How to earn a nickname mid-campaign

The best goliath characters don't show up at session one with a nickname already attached. They show up with the birth name, and somewhere between session three and session ten, the nickname arrives. Here's how to actually run that.

Ask the table to hold the naming rights. At session zero, tell the DM and the other players the character is unnamed past their birth name and that the nickname should come from something that happens in play. Then trust them to notice the moment. Players are usually generous about this — someone will remember the third session where Aukan tanked a fire-giant hurl and someone will say, "Aukan Firecatcher." That's it. That's the moment.

Pre-seed some contenders, but don't commit. Write four or five nickname candidates on the back of your character sheet and tick which one gets used most in play. If "Slow-Blink" keeps coming up because you play the character as unhurried and quiet, "Slow-Blink" it is. The candidate list is scaffolding — the table's use makes it real.

Let deeds override traits. A nickname earned from a trait ("Long-Stride" because the character is tall) is fine, but a nickname earned from a deed ("Bridge-Breaker" because the character felled a stone bridge to stop a pursuit) reads more like the tradition intends. If both are available, take the deed one.

Nicknames can change. Goliath fiction supports it — a character starts as "Wolf-Chaser" and becomes "Wolf-Speaker" after they parley with a spirit pack. Don't hoard the first nickname just because it landed. If the character grows, let the name grow.

Retire nicknames that stop fitting. A character whose defining trait was "Silent-Step" and who then loses a foot in a boss fight might carry a new one — "One-Foot," "Half-Stride," "Iron-Ankle" if the party's cleric fits them with a prosthesis. This is not tragedy for the character; it's the naming convention doing its job.

Full example characters

Here are three worked-through goliaths who show what the convention looks like when you take it seriously.

Kavaki "Stone-Skinned," goliath barbarian. Birth name from the mountain-clan pool, nickname earned at age seventeen when a rockslide caught her and her hunting partner on a scree slope. Her partner didn't make it. Kavaki did, with a torso full of bruises the color of slate and a story the clan told for a decade. She left the clan at twenty-three because staying meant being the girl who lived when the boy didn't, and Stone-Skinned was a name she wanted to earn a second reading of. She uses her clan name — Kavaki of Karakset — only when speaking to elders and to strangers who need the courtesy.

Uthal Wolf-Chaser, goliath ranger. Ungendered birth name, deed-earned nickname, no clan name in casual conversation because Uthal doesn't want the questions that follow it. The winter they were nineteen, a wolf pack drove a herd of goats off a cliff two miles from the winter camp; the clan would have starved. Uthal ran the pack for a day and a half across frozen tundra, killed the pack's lead wolf with a spear on the second morning, and the rest scattered. They carry the wolf's tooth in a pouch and they don't say much about it. The nickname is enough.

Ilma, the Cold-Hand, goliath druid. Ceremonial nickname form because Ilma is old and formal about it. "Cold-Hand" is not a deed but a trait — Ilma's hands have run cold since a childhood illness and she can hold ice bare-handed longer than any other goliath in the clan. The clan reads it as spirit-favor. Ilma is thirty years past caring what anyone reads it as; she uses the cold as a druidic focus and casts frost spells that other druids find fussy and precise. In her clan she is simply Ilma. In the wider world she is Ilma, the Cold-Hand, because outsiders want the two-name form and she's tired of correcting them.

Notice what these three have in common: the nickname is doing narrative work in every case. It hints at the past, it shapes the present, it's the kind of detail a DM can pick up in session two and hand back in session eight as a callback. That's what a working goliath name is for.

FAQ

Do I have to include the nickname at character creation? No, and it often plays better if you don't. Start with just the birth name and let the table award the nickname when it happens. If you need a nickname on the sheet for a session-one introduction, keep it provisional — a trait-based one you'd be willing to trade for a deed-based one later.

What about the clan name — is it required? The clan name is a formal-occasion tool, not a daily-use one. If your campaign spends time near or in goliath territory, having a clan name in your back pocket is useful. If it doesn't, most goliaths in the wider world introduce themselves with just birth name and nickname.

Are goliath names gendered? Most of them are functionally neutral. The published pools overlap heavily across gender labels, and mountain-clan culture as written cares more about deeds than about gender presentation. Pick from the shared list without worrying about matching your character's identity — the nickname carries the identity work.

How do the 2024 rules change how I should name my goliath? They don't change the naming convention itself — the birth-name-plus-nickname pattern is unchanged from previous editions. What changes is visibility: with goliath as a core lineage now, more people will hear your character's name across their tables, and the convention is more worth leaning into because the audience recognizes it.

Can a goliath have more than one nickname over their life? Yes. This is arguably the most interesting part of the tradition. A goliath can earn a new nickname when their deeds change what the tribe reads them as. Wolf-Chaser can become Wolf-Speaker; Stone-Skinned can become Stone-Breaker if their story turns. Retire old names when they stop fitting.

What if my nickname is too edgy or too silly? The tradition supports the full range. "Ash-Weeper" for a character who mourned a lost village. "Loud-Laugh" for a character whose laugh carries across a valley. Both are legitimate. The test isn't tone; it's whether the tribe would actually say it about the character. If the answer is yes, it works.