Free author toolUnlimited spins · no signup

Free Goblin Name Generator

Get goblin names built the way a swarm actually names itself — short, cheap, loud, and mean, clustered into warren-names, mob-nicknames, and the self-styled titles a cunning goblin squeaks up to — so a whole tribe reads as one pestilent people, not ten unrelated monsters.

Instant · unlimited · no signup

Spin goblin names from scrap, shadow, and spite — unlimited and instant.

Short, clipped constructions from roots like wound, fang, mask, and night, with the glosses visible so every warren-name can be tied to a hole, a fight, or a theft without losing the swarm's shared sound.

Style

Tailor to your story

Make them fit YOUR book

What kind of goblins are these? The generator tunes its sound economy and naming layers to the warren you describe.

More controloptional

Three layers come back each pull — warren-names, mob-nicknames, and self-styled titles — rather than one flat column. Leave the warren undescribed for a quick squeaked set.

Give me goblin names that sound like one swarm — for a single tinker or a whole warren.

Goblin naming jobs this generator was bred for

Name a swarm that reads as one people

Feed it one warren culture and get personal names plus a shared mob-nickname pattern obeying the same cheap-clipped sound rules, so your tribe reads as a single breeding pestilent people rather than ten goblins scraped from ten bestiaries.

Give a lone goblin an inflated title

A tinker or sneak alone in the world often lies upward in its naming. Pick the tinker role and get a short real name plus a self-styled title several sizes too grand — comedy and character in one beat, no extra words needed.

Roll a tabletop mob in seconds

Your party just kicked in a warren door and six goblins need names before initiative. Get a session-ready set that all share one sound and one hole-name, so the swarm feels coherent even as your players cut it down.

Write a sympathetic goblin arc

Modern fantasy loves a goblin with a soul. The runty-underdog and exile roles return names with a built-in wound — the warren-name they were stripped of, the title they are too small to claim — giving a redemption arc its engine from line one.

Examples

What the warren coughs up for a given brief

Sewer scavenger-mob

A brief like "names itself after stolen scraps" returns one-syllable names with hissed sibilants and a shared mob-suffix, so the whole tribe sounds like it was named by the same hungry voice echoing off the same brickwork.

Shaman-led fear-god tribe

Ask for a fear-god warren and the sounds darken — more scraped consonants, more shadow-codas — and the shaman's name comes back longer and heavier, weighted with borrowed dread the common mob-names do not carry.

Lone tinker-goblin grifter

Pick the tinker role and you get a small honest personal name yoked to a comically inflated self-styled title — a goblin trying very hard to sound like someone a traveler should not rob, which tells you who the character is instantly.

Runty exile underdog

The runty role returns stripped names with the warren-line torn away, leaving a short bare name and the implication of a hole the goblin was thrown out of — a wound you can build a whole sympathetic subplot around.

Why it matters

Goblin names are the hardest test of swarm-consistency in fantasy naming

The thesis this page defends: a goblin name is the purest pressure-test of whether a writer can make a *group* sound like a group, because goblins almost never appear alone. A single dwarf or dragon name can be judged on its own merits, but a goblin name is heard in a crowd, and in a crowd the only thing that registers is whether every name in the mob shares one sound and one worldview. Random guttural syllables fail this instantly — the reader cannot tell six unrelated goblins apart, and worse, cannot tell them from the orcs, kobolds, and imps the same generator would have produced. The discipline that fixes it is a sound economy: a deliberately small kit of cheap, quick, mean sounds that every name in the warren is built from, so the swarm reads as one pestilent people even as individuals stay distinct. This generator treats the swarm as the unit, not the individual. The essays below give you the real mechanics — phonetics, canon, the sympathetic-goblin problem — so the mob you name sounds engineered, not spat out.

Why a goblin name is cheap, quick, and mean — and that is a system, not a slur

Goblin phonetics are an economy of scarcity. Where a dwarf name spends consonants like a guild spending iron, a goblin name spends them like a creature stealing scraps: short, sharp, and gone before you can grab it. The sounds that read as goblin across modern canon are high and front rather than low and back — squeaked vowels (i, short e, the clipped a of a yelp), hissing and spitting sibilants (s, z, sh, ts), and stop-and-release syllables that sound like they were bitten off mid-word. Grik. Snik. Yarg. Skab. Each one is one or two syllables, ends fast, and would survive being shrieked across a melee without losing its shape. That is not laziness; it is the phonetic profile of a creature that lives in tight spaces, communicates at speed, and needs a name a dozen cousins can shout in under a second.

What makes the economy work as a system rather than as random ugliness is consistency of kit. A goblin warren that draws every name from the same five or six sounds — say k, r, s, short i, and a clipped ending — will read as a coherent tribe, because the reader's ear learns the warren's accent after three names and starts pattern-matching. A warren where one goblin is Grik, another is Mortimer, and a third is Xelithiquesha has no accent at all, and the reader experiences it as a generator malfunction rather than a people. The rule is the same one that governs every constructed naming language: restriction creates identity. Pick a small palette and your warren sounds real; refuse to restrict and it sounds like noise.

The cheapness is a feature, not a bug, and defending it against the urge to ornament is most of the work. The instinct when naming a "low" fantasy creature is to make the name uglier and more elaborate to signal lowliness, which produces six-syllable tongue-rolling disasters that no goblin could actually shout. Resist it. A real goblin name should be possible to scream three times fast while running; if it is not, it is a wizard's idea of a goblin, not a goblin's idea of itself.

  • High front vowels (short i, e, clipped a) and hissing sibilants (s, z, sh, ts) are the goblin accent — squeaked, not growled.
  • One or two syllables, bitten-off endings: a goblin name should be screamable three times fast while running, or it is overbuilt.
  • Restriction creates identity: pick five or six sounds for the whole warren and every name built from them reads as one tribe.
  • A warren with no shared accent (Grik next to Mortimer next to Xelithiquesha) reads as generator noise, not a people — kill the outliers.
  • Defend the cheapness: the urge to make goblin names uglier and longer is what produces unshoutable tongue-rolling disasters no goblin would use.

From folklore pest to D&D mob to Pathfinder poet: what canon actually established

The goblin has one of the strangest character arcs in fantasy canon, and naming it well means knowing which goblin you are invoking. The folklore original — the continental European kobold, the English goblin, the Scottish bogle — was a household or mine spirit, often more nuisance than evil, named in scattered, regional, almost onomatopoeic forms that sounded like the mischief itself. Tolkien formalized the goblin (conflated with his orcs in The Hobbit) as a tunneled, mass-produced threat, and that mass-production is where the swarm instinct in modern goblin-naming truly begins. Then Dungeons and Dragons hardened the swarm into a type: small, chaotic, low-level, mob-tactical, almost always encountered in groups, which is why every D&D goblin-name table since the seventies has assumed you need a dozen names at once rather than one.

Pathfinder did something underappreciated: it gave its goblins a voice and a poetry of their own, with a whole in-world tradition of goblin songs, and that lyrical streak — crude, rhyming, darkly comic — is a goldmine for a writer who wants goblins that are vivid rather than merely numerous. The Labyrinth goblin, the Discworld goblin (in Pratchett's late, sympathetic Snuff), and the World of Warcraft goblin (the tinker-trader) each added another register: courtly-ugly, legally-a-people, and capitalist-huckster respectively. The point of the canon tour is not to pick a winner. It is to notice that "goblin" is not one naming problem but at least four: the pestilent swarm, the cunning tinker, the darkly comic poet, and the newly-recognized person. Decide which register your warren lives in before you name it, because a swarm's cheap squeaked names and a tinker's inflated self-styled titles obey completely different rules.

A stance worth taking: the most interesting modern goblin fiction refuses to leave the creature at "evil by default," and recent D&D editions have explicitly walked back the always-chaotic-evil framing. That shift is an opportunity, not a constraint, because a goblin with interiority is a goblin whose name matters to itself — which is exactly the condition under which a self-styled title (the tinker calling itself something grand) or a stripped warren-name (the exile who lost theirs) becomes a real character beat instead of a flavor detail.

The self-styled title: why the loudest goblin name is usually a lie

The most goblin-specific naming layer — and the one no other fantasy creature uses quite the same way — is the self-styled title, the name a goblin gives itself to sound more dangerous, more important, or more feared than it is. This works as a naming device because goblins sit low on every fictional food chain: too small to demand respect, too cunning to settle for being ignored, and too vain to introduce themselves honestly. So they lie upward. A lone tinker-goblin who is genuinely called Grik will introduce itself to strangers as Grik Many-Traps, Lord of the Ninth Pipe, Scourge of the Rat-Knights — and the gap between the real name and the claimed title is pure character, doing the work of paragraphs of description in a single line.

The mechanic to steal is the witness rule borrowed from orc deed-names and inverted: where an orc deed-name must be awarded by witnesses and is therefore honest, a goblin title is self-awarded and is therefore at least partly fiction. This asymmetry is a gift to dialogue and worldbuilding. A goblin's real reputation in its own warren is whatever the mob actually calls it (a mob-nickname earned by being the sneakiest, the loudest, the one who survived the last cave-in), while the title it gives outsiders is a sales pitch. A writer who runs both layers — the in-warren name and the out-warren name — gets a free running gag and a free characterization engine, because every introduction becomes a small negotiation between who the goblin is and who it claims to be.

A useful discipline: keep titles to two elements and make at least one of them concrete and slightly absurd. "Snik Iron-Tooth" works because iron-tooth is a specific, checkable claim (does he have iron teeth? probably not, but you can picture it). "Snik the Almighty Dread Lord of Endless Shadow" fails because it is inflation without object, the literary equivalent of a goblin shouting into a hole. Compression sells the comedy; inflation kills it.

A two-layer naming system — the name the warren actually uses and the title the goblin claims to outsiders — only pays off across a full manuscript if the book keeps the two straight. BookWriter's book bible pins every goblin's real mob-name alongside their self-styled title, so the lie they told in chapter two is still exactly the same lie when a returning traveler calls them on it in chapter thirty.

The mob, not the monster: naming a group so it reads as a single pestilent people

Because goblins arrive in crowds, the unit of goblin naming is the warren, not the individual, and the failure mode of every lazy goblin-name generator is that it names twelve goblins as if they were twelve unrelated creatures. The fix is structural: before you name a single goblin, name the warren — give the tribe a shared sound-kit (its accent), a shared mob-suffix or naming pattern (the thing that marks a name as belonging to this hole and no other), and a shared worldview that dictates what counts as name-worthy. A warren that worships a fear-god will reach for dread-codas; a sewer-scavenger mob will name itself after stolen food and broken things; a merchant-clan that has learned being underestimated pays will pick names engineered to sound harmless. The worldview generates the names, and because every goblin in the warren shares the worldview, the names share a sound.

The practical test for swarm-consistency is the roll-call: write all your named goblins in a list and read it aloud. If the list sounds like it could be one tribe answering to one chief in one hole, you have succeeded. If it sounds like a bestiary random table — a kobold here, an imp there, an orc-adjacent guttural there — you have failed, and the fix is to impose a tighter sound-kit and rebuild the outliers. Readers cannot articulate why a swarm feels real or fake, but they register the consistency instantly, the same way they register whether the extras in a movie scene seem to belong to the same village.

A subtler version of the same discipline: vary within the kit, not against it. A warren of goblins all named Grik, Grik, Grik is as unbelievable as a warren with no shared sound. The art is that every name should be clearly built from the same five or six sounds while still being instantly distinguishable — Grik, Skrik, Grika, Skab, Snik — so the reader can tell individuals apart without ever forgetting they are one people. That narrow-but-recognizable variation is exactly what a real village surname pool looks like, and it is what makes a mob feel inhabited rather than generated.

  • Name the warren before the goblin: pick a shared sound-kit, a mob-suffix, and a worldview before any individual name.
  • The worldview generates the sounds — a fear-god warren reaches for dread-codas; a scavenger mob names itself after scraps and breakage.
  • The roll-call test: read every named goblin aloud in a list; if it does not sound like one tribe answering one chief, tighten the kit and rebuild outliers.
  • Vary within the kit, not against it: Grik, Skrik, Grika, Skab are one family; Grik, Mortimer, Xelithiquesha are three different creatures.
  • Readers cannot articulate swarm-consistency but register it instantly — the same instinct that tells them whether movie extras belong to one village.

Female goblin names without the joke — and why goblins are the easiest fix

Goblin naming has a low bar to clear on gender and that is actually good news for writers, because the cheapest, most-mean goblin phonetic economy does not encode masculinity in the first place. The squeaked vowels, the hissing sibilants, the clipped one-and-two-syllable shapes — none of those are masculine or feminine, they are just small and sharp, which is why a female goblin name built from the same kit as a male one reads as completely natural where a female dwarf name built the same way would not. The lazy reshaped-ending failure mode (Grishna for a female goblin because Grishn was the male) is therefore unnecessary, and a writer who cares about it can clear the bar simply by varying within the warren's kit rather than appending gender markers.

What is more interesting is leaning into the parts of goblin culture that a matrilineal or mother-led warren would surface. If brood-mothers run the warren — and several canon traditions, plus basic pest-species biology, support this — then the oldest female goblins are the chiefs, and their names should be the heaviest in the warren, the ones with the most accumulated syllables or the most dread-codas, while the short squeaked names belong to the young and disposable. Inverting the usual fantasy assumption that female names are lighter produces a goblin warren where the matriarch's name is the one that terrifies, which is both accurate to how pest colonies work and a refreshing break from the genre default.

The test, as with dwarves, is whether a female goblin name could plausibly belong to the warren-chief and not just to someone's mate or daughter. In a brood-mother warren, the female names should be the authority names. Build your female goblins to command the mob and the names will follow; build them to decorate the mob and no amount of phonetic care will hide it.

  • Goblin phonetics are gender-neutral by nature — squeaked vowels and hissing sibilants read as small and sharp, not masculine, so female names need no special treatment.
  • Avoid the reshaped ending: do not make Grishna from Grishn; vary within the warren kit (Grika, Skess, Snith) instead of appending gender markers.
  • Lean into brood-mother biology: in a pest-species warren the oldest females are the chiefs, so their names should be the heaviest and most feared, not the lightest.
  • The warren-chief test: if your female goblin name would sound wrong on the matriarch running the mob, you have built decoration, not authority — rebuild for command.

From bred-in-bulk to a named mob: the working process

Breed before you cull, and breed in greater numbers than feels necessary. Squeak the tool across five or six runs of one warren brief and hoard every name that snags your ear — a mob's worth of names, fifty or sixty strong, is what it takes for a warren to feel real, and grabbing the first five that scuttle out guarantees a thin, bestiary-flavored tribe every time. Then sort the pile with cold rules before taste gets a hearing: read the whole mob aloud in roll-call and knife any name that cracks the swarm's accent, split any pair whose opening hiss is too close (Skrik and Skrig collapse into one goblin by page twenty), and run each survivor through a search before you settle, so the warchief in your finished manuscript is not unknowingly doubling as some copyrighted monster from a game you have never loaded.

Once the heap is sorted, lock the survivors in as a warren-grammar, not a heap. Note the warren's sound-kit, its mob-suffix, its naming worldview, and the rule for self-styled titles. One scratched page holding those rules is what lets you cough up goblin number forty in two minutes next month rather than two hours — and what keeps the warren first heard in chapter one legible as the same warren when it swarms back in chapter fifty. That scratched page is exactly what a book bible is for, maintained alive across the whole manuscript: BookWriter clings to every goblin's real mob-name alongside its claimed title and warren-line across each chapter it drafts, so the swarm bred at the start keeps its shape through a full book rather than scattering the way mob-names scatter across forty orphaned files.

Frequently asked questions

Related tools

Keep the workflow moving

These tools are linked by job sequence, not random popularity. Each one solves the step authors usually search for next.

A named swarm is how a warren begins, not where the search ends.

Haul your goblins into BookWriter and the book bible clings to every mob-name, claimed title, and warren-line across the whole manuscript without dropping one — so the warchief whose real name the tribe revoked in chapter six is never heard squeaking it again by chapter thirty.