How Gnome Names Actually Work in D&D
Gnome names in D&D follow a specific naming convention that varies by subrace. Forest gnomes tend toward playful, whimsical names like Bunnie, Carambole, and Tilly. Rock gnomes lean slightly more practical with names like Burdro, Gimble, and Warryn. The names aren't random - they're drawn directly from the Player's Handbook and have been consistent since 3.5 edition. Here's what most people miss when creating gnome characters. The PHB lists about two dozen male and female first names per subrace, but it doesn't explain surname generation, which is where most players botch it up. Gnome surnames are typically occupational or descriptor-based - Thingsong, Bonaduce, Greenwise, Witterstick. They sound made up because they're deliberately meant to sound like folk etymology. You're not supposed to take them literally. Pick a trait about your character and attach "stick," "foot," "worth," or "wise" to it. That's it. No need to overthink it. I ran into a problem last year where a player wanted a gnome character whose name had to fit a specific cultural backstory I'd built for my campaign setting. He tried combining three random name generators online, and the result was something like "Zizzypip Quillsworth the Third." It completely undermined the immersion of his character's family lineage. What I had him do instead was pick one PHB gnome name, add a descriptor surname based on his character's trade (he was a tinker, so "Fitzwright"), and give him a childhood nickname his family used. "Caddinwick 'Caddy' Fitzwright." Done. Takes thirty seconds.
The deeper issue with gnome names in D&D is that players often treat them as a joke rather than a character design choice. This isn't wrong per se - gnomes in the lore are curious and mischievous by nature. But the name you pick affects how NPCs react to your character from session one. A gnome named "Nutmeg Fluffbottom" is going to get treated differently than "Roderick Bonaduce." The former gets laughed at or patronized. The latter gets taken more seriously, especially by other gnomes who might see the name as trying too hard. If your gnome is supposed to be an outcast or someone who doesn't fit in, a overly silly name reinforces that. If you want your gnome to be respected in gnome society, go with something steadier. There's also a mechanical consideration most players overlook. In some editions and homebrew settings, a gnome's name can affect social skill checks. The Dungeon Master's Guide doesn't codify this for names specifically, but several campaign settings like Dragonlance and Forgotten Realms have established naming conventions that carry weight. In Dragonlance, for instance, gnomes have clan names that matter enormously. If you're playing in a setting like that, picking a name without checking the source material can put your character at a social disadvantage before you've even rolled for initiative. For actual gameplay purposes, here's a practical method I use when helping players create gnome names. Start with the subrace. Check the PHB table. Write down three first names that sound plausible alongside your character concept. Then create a surname by combining a root word with a common gnome suffix. Common gnome suffixes include: -wick, -worth, -foot, -stick, -wick, -son, -worth. Common roots come from trades, animals, terrain features, or personality traits. Combine them. Say the whole name out loud. If it makes you cringe, pick different components. If it rolls off your tongue, you've got a functional gnome name.
One more thing. If you're running a level 1 gnome character in a formal setting like a noble gnome household, having a proper clan designation matters. These aren't in the PHB - they come from sourcebooks like Races of Stone or Eberron. The difference between "Tavin Thingsong" and "Tavin Thingsong of House Glimmerlight" is the difference between a nobody and someone with connections. If your campaign involves gnome politics, spend ten minutes looking up established gnome houses before you finalize the name. It'll save you from having to explain away the omission later.
Get the Full Details
