D&D 5e Pantheon Guide - Build a Pantheon and Its Gods

What a 5e Pantheon Needs

A pantheon is a cast, not a list. Most working pantheons in D&D, from the SRD's Greek and Norse gods to homebrew settings, cover the same ten roles. Fill each role with one god (or let one god hold two) and the pantheon will answer every question a cleric, paladin, or worldbuilder asks of it. The domains column uses the cleric domains a player will actually pick from.

Six to twelve gods is the comfortable size: enough to cover the table, few enough that players remember names. For a full pantheon in one click, the D&D Pantheon Generator builds eight linked gods with domains, symbols, tenets, and the oaths and rivalries between them (any size from one to twelve); the Deity Generator is the same engine for a single god or a small cult.

Why Gods Matter

Religion is not a side dressing in D&D; it is one of the primary engines of the setting. A cleric's spells come from their god. A paladin's oath is sworn to a divine ideal. A warlock's patron may be a minor deity in all but name. Even characters with no faith live in a world where temples are landmarks, festivals mark the calendar, and people swear oaths to beings they believe are listening.

Designing a pantheon is worldbuilding leverage. One strong pantheon gives you calendar holidays, moral factions, NPC motivations, quest hooks, and a reason for every major ruin in the world. Skimp on this at your peril.

Borrow, Remix, or Build

You have three options for pantheon design. First, borrow an existing one: the 5e SRD includes fantasy versions of the Celtic, Greek, Egyptian, and Norse pantheons under a Creative Commons license, and real-world mythologies are public domain. (Setting pantheons like the Forgotten Realms and Greyhawk gods appear in the Player's Handbook but are not part of the SRD.) Second, remix: take the Greek pantheon and file off the serial numbers, or combine the structure of the Norse gods with your own names and domains. Third, build from scratch: start with your setting's themes and generate gods whose domains support them.

Borrowing gets you to the table faster. Remixing gives you familiarity plus customization. Building from scratch is the most work but produces pantheons that feel load-bearing to your story. All three are valid; the right choice depends on how central religion is to your campaign. If you build, the D&D Deity Generator rolls a full pantheon with domains, tenets, and rivalries you can edit into shape.

Designing a Single Deity

Each deity needs: a name, an alignment, one to three domains, a portfolio (what they are the god of), a holy symbol, and a one-line tenet their followers repeat. That is the minimum. Go deeper if the god is central to your campaign; keep it short if they are one of twelve in a backdrop pantheon.

• Name: short, memorable, pronounceable. Avoid apostrophes unless you want players fumbling every reference.
• Alignment: sets the feel, not a rule. Expect some followers to bend it.
• Domains: map to the cleric subclasses your players might pick. Multiple domains make the deity more playable.
• Portfolio: a concrete list ("war, courage, the harvest moon"). Specific beats abstract.
• Holy symbol: a single image that could be carved on a shield. The players will describe it more than any other detail.
• Tenet: one sentence. "Break what deserves breaking." "Keep the promises your ancestors made."

Pantheons as Factions

A pantheon is not a list of gods; it is a political map. Which gods cooperate? Which hate each other? Are there wars between mortal followers that echo divine grudges? A pantheon of fifteen gods who all get along is boring. A pantheon where the Sun god and the Shadow god have been at war for an age drives campaigns.

Group your gods into two or three factions plus some lone operators. Give each faction a shared agenda and a point of conflict with at least one other faction. This lets you design quest hooks where any religious NPC already has a stake in the outcome.

Clergy, Temples, and Observance

Gods need mortal infrastructure. Each major deity should have clergy with titles (priests, celebrants, inquisitors), at least one temple city or sacred site, a holy day or festival, and daily observances the party will see NPCs perform. Minor gods may have only shrines and lay practitioners; that is fine. Not every god runs a bureaucracy.

Temples are location gold. A war god's temple is an armory-adjacent community center. A death god's temple is the local undertaker plus an archive of lineages. Let the temples do double duty as setting infrastructure; your players will visit them for reasons other than worship. The D&D Religion Generator fills in commandments, clergy hierarchy, and worship practices for any god you have sketched.

Using Gods in Play

Divine intervention is rare by design in 5e: the RAW rules let a cleric pray for help with a d100 roll against their level. Lean into the rarity. A god who answers every prayer is a power source; a god who answers one prayer per campaign is a plot device. Save the divine hand for moments that matter.

Small-signs are more useful than miracles. A raven that always appears at a war god's omens, a chill that runs through a death cult when the grave god is displeased, a warm breeze on a specific hillside sacred to a harvest goddess. Players pay attention to small signs the way they would not to booming voices from the sky.