How to build dragon names that feel believable
A good draconic name feels ancient in the mouth. Tolkien set the pattern with Smaug, Glaurung and Ancalagon: guttural consonants, long vowels and suffixes suggesting historical weight. If your dragon is millennia old, avoid names that sound modern or too cute. Syllables like kr, thr, vr and gh deliver instant ferocity.
Apply the three-component rule: a hard root (Drak, Vrog), a body vowel (a, o, u feel weightier than e, i) and a closing with a sonorant consonant (-th, -or, -ax). This yields Drakothar, Vrogondir, Mornakax. For more subtle or elven dragons, soften with liquids: Aelyndras, Sylariax.
Add a descriptive epithet. Ancalagon the Black works because the adjective rounds out the image. Your dragon can be the World-Devourer, Stormbreath or the Bone-Crowned. For D&D campaigns, tie the epithet to the dragon's domain: an aquatic dragon deserves of the Black Tides, not of the Hollow Volcano.
Styles by subspecies and fantasy tradition
Western dragons in the Tolkien vein use names with Norse or Celtic roots: endings in -ung, -or, -ir. Glaurung, Scatha, Fafnir. For D&D campaigns, chromatic dragons (red, blue, green, white, black) tend to have more aggressive names: Klauth, Iymrith. Metallic dragons (gold, silver, bronze) lean toward nobler, more musical sounds: Aurinax, Bahamut.
Eastern dragons (Chinese long, Japanese ryū) follow different phonetics: names with clear syllables and poetic meanings. Shenlong, Ryūjin, Mizuchi. If your worldbuilding blends traditions, decide which fictional culture inspires each draconic race before generating names. Mixing Tolkien with Chinese phonetics in the same dragon breaks immersion.
Ancestral wyrms (wingless, serpentine) deserve more archaic, hissing names: Ssyrith, Nymesh, Vassyr. Wyverns are less majestic and tend to bear shorter, tribal names: Krag, Thrak, Vorn. For drakes (young or small dragons), think of pet names given by humans: Pyrro, Embra, Cinder.
Common mistakes when naming dragons in your worldbuilding
The first mistake is apostrophe overload. Dr'a'koth or Vr'a'gon'a'th doesn't sound more ancient, it sounds like a bad fantasy parody. Use apostrophes only if your linguistic system has clear rules (like glottal stops or click consonants). Otherwise a continuous word always reads better: Drakoth.
The second mistake is unpronounceable names. A dragon called Xqthrnyx is impossible for your gaming table or readers. Try saying the name aloud three times. If you stumble, simplify. Xanthar keeps the strength without frustrating the reader.
The third mistake is copying real names. Calling your dragon Smaug, Drogon or Toothless kills originality. Generate variations: if you like the sound of Smaug, start from the structure (consonant-vowel-hard final consonant) and build Skraug, Vraug, Throg. The fourth mistake is not assigning internal meaning. In the dragons' tongue, what does the name mean? Tolkien always knew. Document a small fictional etymology and you enrich every mention.
Practical applications in novels, games and roleplay
In D&D 5e, names from the Monster Manual follow a consistent pattern by color. If your DM is using it as a base, stay faithful: red dragon with strong consonantal name, gold dragon with noble melodic name. For one-shot sessions, generate three options and pick the one your table can pronounce without stumbling.
In novels, introduce the dragon's name with ceremonial weight. Don't drop it in a casual description. 'His true name, never spoken by mortals, was Vraketh the Shadowless' hits harder than 'Vraketh appeared flying'. Save the full name for key revelation moments.
In video games and MMOs, names must be short for boss titles and health bars: 12-15 characters max. Drakothar fits; Drakothar the World-Devourer of the Hollow Volcano doesn't. Save the full name for dialogue and lore. If you're doing solo worldbuilding for a future project, generate 30 names and group them by age: young ones with simple names, ancients with long epithets. That gives you a draconic hierarchy ready to use.