"Sounds like a dragon" is doing a lot of unexamined work. Ask someone to describe the sound and you'll get harsh, long vowels, lots of R and G — which is a description of one tradition, borrowed from another tradition, filtered through a third. The actual naming systems behind the famous dragons have almost nothing in common with each other, and knowing which one you're aiming at is the difference between a name with a culture behind it and a name that's just consonants.
Norse: the name is a personal name because he used to be a person
Fáfnir is the one everybody half-knows, usually as "the dragon Sigurd kills." But in the Völsunga saga he starts as one of three brothers — sons of Hreiðmarr, alongside Reginn and Ótr — and becomes a dragon through greed for the cursed gold of Andvari. He lies on the hoard until he turns into the thing that lies on hoards.
That changes what the name is. Fáfnir is not a monster's name; it's the name he had before, still attached to him afterwards. Same for Níðhǫggr, the corpse-gnawer at the root of Yggdrasil, whose name is a compound description that reads as a title. Norse dragon names are ordinary Norse names or ordinary Norse compounds — nothing about them is phonetically marked as reptilian.
The rule: a Norse dragon name should be indistinguishable from a Norse person's name. If your generator is adding extra growl to it, it's already off-tradition.
Tolkien: real Germanic verbs, conjugated
Tolkien named Smaug with a joke he expected roughly nobody to get. Writing to the Observer in early 1938, he explained that the name is the past tense of the primitive Germanic verb smugan, "to squeeze through a hole" — and called it, in his own words, a low philological jest. Smaug is named for the thing he does at the start of the story: get into a mountain he shouldn't fit into.
His other dragons follow the same method in different languages. Glaurung and Ancalagon are Elvish constructions — Ancalagon parses in Sindarin roughly as "rushing jaws." Scatha is Old English sceaða, an injurer or enemy. Every one of them is a real word doing real morphological work in a real (or fully-built) language.
This is why Tolkien's dragon names sound so much better than their imitations. They aren't assembled from dragon-flavoured syllables; they're words. The Tolkien Estate's own material on The Hobbit is fairly direct about how much of the book grew out of language rather than plot.
The rule: pick a verb or a noun in a real old Germanic language, describe what the dragon does, and use that. It works far better than it has any right to, and it gives you an answer when a reader asks what the name means.
Chinese: dragons hold offices
Ao Guang is not a dragon's name the way Smaug is. He's the Dragon King of the East Sea — 東海龍王 — and the interesting half of that is the second half. In the Journey to the West and Fengshen Yanyi tradition, the four Dragon Kings are a bureaucracy: one per sea, each with a domain, a court, a rank in the celestial administration, and a set of duties around rainfall.
Chinese dragons are civil servants with weather portfolios. The name that matters is the post, and treating "Dragon King of the East Sea" as a title rather than an epithet is the whole difference. It's also why 龍 (lóng) appears constantly in the naming: it's a category marker, like writing "Judge" before a surname.
The rule: build a title — rank plus domain — and hang a short personal name off it, not the other way round. A Western-style single evocative name flattens a system that was never about individuals.
D&D: the name is a taxonomy entry
Tabletop went somewhere else entirely. The chromatic/metallic split — red, blue, green, black, white against gold, silver, bronze, copper, brass — means a dragon's type is public information encoded in a colour word, and the personal name sits on top of a species label that already told you the alignment and the breath weapon.
Tiamat, the five-headed chromatic queen, is a straight borrowing from the Babylonian Enūma Eliš, where she's a primordial saltwater goddess and not a dragon in the scaly-lizard sense at all. Bahamut comes from Arabic cosmology, where Bahamūt is a colossal fish. Both were pulled in as impressive-sounding proper nouns and given jobs that have nothing to do with their sources.
The rule: the name is allowed to be grandiose and borrowed, because the system around it is doing the classification work. This is the tradition most generators are actually imitating, whether or not they know it.
Side by side
| Tradition | Name is | Sound profile | Gets it wrong by |
|---|---|---|---|
| Norse | a person's name | ordinary Norse | adding menace to the phonology |
| Tolkien | a real word, translated | Germanic or Elvish morphology | inventing syllables with no meaning |
| Chinese | a rank plus a domain | title-first | treating the title as a surname |
| D&D | a proper noun on a species label | borrowed, grand | forgetting the colour already said everything |
So which one are you generating?
The practical failure mode isn't picking the wrong tradition — it's picking none, and getting a name that averages all four. Long vowels, a hard G, an X somewhere, three syllables, no meaning. It reads as dragon and as nothing else, and it's forgettable the moment a second one shows up.
Decide first, then generate. If you want the Norse register, keep the name plain and let the story do the work. If you want the Tolkien register, start from a verb. If you're running a tabletop game where six dragons need to be told apart at the table, the D&D convention exists precisely because it solves that problem, and there's no shame in using it as designed.
A dragon name generator is at its most useful when you've already made that call and you're looking for twenty candidates inside one convention — not when you're hoping it'll make the decision for you.
Cover photo via Pexels.