How to Name a Dragon for Your D&D Campaign

No monster's name gets said aloud more often than a dragon's. The party will hear it in a tavern rumour three sessions before the lair, curse it at the bottom of the initiative order, and, if you named it well, still be quoting it a year after the campaign ends. That is a lot of work for one word, so it pays to choose it like a game master rather than a novelist: at the table, a dragon's name is a tool that has to survive being spoken badly, often, and under pressure. This guide walks through the five decisions that matter, with original examples you are free to lift straight into your notes.

Start with the role, not the name

Before any syllables, decide what the dragon is for. A campaign villain needs a name the players can grow to dread. A one-scene wandering terror needs a name that lands instantly and never comes up again. An ally, patron, or rescued wyrmling needs a name the party will enjoy saying, because they will say it constantly and voluntarily. Each role points at a different register, and our list of 200+ dragon name ideas is sorted by exactly those registers if you want to browse before you build.

Colour is tone: chromatic and metallic conventions

Most fantasy tabletop settings sort true dragons into two broad families. The evil, predatory family (the chromatic archetype: reds, blacks, greens, whites, blues) tends toward harsh, guttural names full of hard stops and growls. The noble or lawful family (the metallic archetype: golds, silvers, bronzes, coppers, brasses) tends toward sonorous, rolling names that sound closer to an elven court than a slaughterhouse. You do not need any publisher's lore to use this; it is simply tone-matching. A swamp-dwelling ambush predator wears a name like Vraxxus or Zarvokh comfortably. A gold-scaled guardian of a mountain monastery sits better as Aurelianos or Orovandel. Players pick up on the split without being told, which means you can also break it deliberately: a silver dragon with a chromatic-sounding name hints at a complicated past before anyone rolls a history check.

Age category is gravitas

Dragons in most systems grow through age bands, from wyrmling to ancient, and a name can carry that weight. A useful convention: the older the dragon, the longer the name and the more formal its use. A wyrmling might be Kess. As a young adult she styles herself Kessarine. By the time she is ancient, the region knows her as Kessarinoth, the Silent Snowfall, and only fools use the short form to her face. Running one dragon across a long campaign, this gives you a built-in way to show time passing. Introducing an ancient wyrm cold, skip straight to the long form plus epithet; the syllable count alone tells the party what tier of trouble they are in.

Epithets do table work

An epithet is the most efficient piece of dragon lore you can write, because it is the part the commoners actually use. Villagers do not say Tharkuzul; they say the Hearthbreaker, and the players learn the dragon's habits from the nickname alone. Good epithets name a deed (the Skysplitter), a territory (the Old Terror of the Passes), or an unsettling quality (the Quiet Between Stars). They also solve the pronunciation problem in play: if the table mangles the true name, the epithet carries the scene. Write both, introduce the epithet first through rumours, and hold the true name back for the lair. Naming the moment a dragon's real name is first spoken is a free dramatic beat.

The read-aloud test

Every dragon name must pass one test before it enters your notes: say it out loud three times, fast, in your game-master voice. If you stumble, the players will too, and a name that gets abbreviated to "the dragon" by session two has failed. Watch for three traps. First, ambiguous spellings: players will see the name written on a handout eventually, and Xarvenoth invites three different first syllables, so decide the pronunciation and note it. Second, rhymes and near-misses with real words: a dread wyrm named Morgash survives contact with the table, but one named Borgash will be a burger joke within minutes. Third, collisions with player characters: a dragon named Kellan in a party with a Callan will derail every scene it appears in. When in doubt, shorter and harder to mangle beats longer and grander.

Stay consistent with your setting

A dragon's name should sound like it comes from somewhere in your world. If your campaign region draws on Norse-flavoured naming, a dragon called Vrogmaeth fits and one called Aurelianos sounds like a tourist. There are two clean ways to get consistency. Either the dragon's name comes from the local human tongue, in which case build it from the same sounds as your towns and NPCs, or it comes from the dragon's own ancient language, in which case it should sound like nothing else in the region, and every dragon in your world should share that alien sound palette. Both choices are right; mixing them at random is the only wrong one. Our guide to draconic phonetics covers how to build that shared sound palette so your dragons feel related.

Worked examples

Here is the whole method run end to end, three times. A campaign villain: red-scaled, ancient, lairs in a burned watchtower. Chromatic tone, maximum gravitas, deed-based epithet: Kragvarax, the Hearthbreaker, pronounced KRAG-var-ax, introduced for six sessions only as the Hearthbreaker. A recurring ally: bronze-scaled adult who trades information for stories. Metallic tone, middle-length name, no epithet needed because the party will coin their own: Thessamir, whom the players will call Tess within a session, and that is a feature. A rescued wyrmling adopted by the party bard: companion register, one bouncy syllable, room to grow: Piplet now, Piplessarine in the epilogue if the campaign runs long enough.

If you want raw material to run through this process, the dragon name generator produces batches in every register, epithets included, as fast as you can press the button. Roll ten, read them aloud, and keep the one your table voice already knows how to say.