About this mount name generator
A warhorse with a name is a character. Roland had Veillantif, the Cid had Babieca, and every paladin who casts find steed is really asking the universe for a companion, not a vehicle. A mount carries its rider into the worst moment of their life and is expected to stand there while it happens, so the good ones earn names the way knights earn them. This mount name generator is built to give a steed that kind of weight: a name, a bond, and a reason the rider would die before letting it fall.
It rotates across nine traditions, so a stable holds more than warhorses. You get the paladin's find-steed mount, summoned and spell-bonded; the ranger's animal companion, a wolf or eagle or bear that chose its person; the druid's wild-shape kin, more ally than property; the named warhorse of the chivalric tradition, in the line of Roland's Veillantif; the prized horses of the Mongol and Arabian warrior cultures, bred and loved across generations; and the stranger mounts of D&D's far corners, a Spelljammer beast bonded to a helmsman, a planar traveller's steed that walks between worlds, a githyanki's red dragon, and a Theros phoenix blessed by the sun-god Heliod. Each result names the mount, names its rider, and gives you something happening between them now.
What kinds of mount names you'll see
The horse registers give you names a knight or a horse-lord would actually use, proud and a little grand. The companion registers, ranger and druid, lean wilder and plainer, names that sound earned in the field rather than bestowed at a ceremony. The exotic registers go for awe: a dragon's name is a threat in itself, a phoenix's name burns, a planar mount's name sounds like nowhere on the map. Each tradition shapes the name, the bond between mount and rider, and how rare such a creature is.
Why the bond and the rider matter
A mount name with no rider behind it is just a pet's name. The questions that make a mount usable are who rides it, how the two came together, what the creature can do, and how much it would cost to replace, because a paladin's summoned steed plays nothing like a dragon a githyanki knight has flown into battle for decades, and neither plays like a phoenix that will rise from its own ashes when it falls. Each result builds the mount out of those parts: its rider, its bonding history, its abilities, and its rarity. That gives you a creature the party can ride, fight beside, mourn, or covet.
How to use it at the table
Take what you need. Give a recurring knight a named warhorse so the party feels it when the horse goes down. Hand a player's paladin a find-steed mount with a personality instead of a stat line. Use a dragon-mount or a phoenix as the centrepiece of an encounter the party will remember. The hooks stay small and personal (a wounded companion, a bond under strain, a steed whose loyalty is being tested) so they deepen a scene without hijacking the campaign. The schema reuses the same fields as every generator here: backstory, personality, and a plot hook.
What you get
Every roll returns a mount name, a pronunciation note, an etymology that fixes the mount's type and rider, a backstory (how it was bonded, who rides it, what it can do, how rare it is), a personality built from how it behaves and what it shares with its rider, and a current situation for play. Most mount generators give you a horse-name and stop. This one gives you a companion the rider would grieve.