
How Do You Build a Fantasy Pantheon in 5e?
Build gods that function as a divine system—not a collection of unrelated names and domains.
by Jackson Dean Chase
Founder and Lead Designer, MageGate Games
Why trust this guide?
MageGate Games founder and lead designer Jackson Dean Chase is a USA Today bestselling author, veteran Game Master with more than 40 years of gaming experience, and the author of dozens of 5e-compatible sourcebooks and GM resources.
MageGate Games was founded to create practical tools that help Game Masters prepare faster, make stronger decisions at the table, and build more memorable campaigns.
MageGate has published extensive 5e material dealing with fantasy religion, divine rites, cults, temples, rituals, omens, prophecies, and supernatural traditions—including the Game Master’s Guide to Rites and Rituals. This guide applies that same practical, campaign-first approach specifically to designing pantheons that feel coherent and usable in play.
If you'd like to learn more about building better religions and cults in 5e, check out our full guides:
Choose a Pantheon Structure
To build a strong fantasy pantheon in 5e, design the gods as a connected system.
Do not begin by inventing twenty unrelated deities and assigning each one a domain.
Start with the structure of the pantheon itself:
A pantheon becomes memorable when its gods make sense in relation to one another.
Before creating individual gods, decide what kind of divine order exists.
Common pantheon structures include:
You can combine these. A pantheon might have an ancient creator, several powerful descendants, younger ascended gods, and conquered foreign deities whose worship was incorporated later. That immediately gives the divine order history.
Establish the Divine Hierarchy
Not every pantheon needs a king or queen of the gods.
But it helps to know whether the gods regard one another as equals.
Ask:
Hierarchy creates pressure.
A god who rules the pantheon may fear a successor.
A younger god may resent an elder deity whose importance has faded.
A dead god’s followers may believe the divine throne belongs to them.
These are not just myths. They are sources of conflict.
Give Each God a Primary Identity
A god should be describable in one clear sentence.
“The goddess of storms, sailors, and dangerous journeys” is easier to grasp than a deity with eight unrelated portfolios.
Give each major god:
For example:
Korath, the Iron King
God of conquest, rulership, military obedience, and oaths of service.
His portfolios reinforce one another.
You immediately know what kinds of rulers, soldiers, and institutions might invoke him.
Let Divine Portfolios Overlap
Do not divide existence into perfectly separate departments.
Two gods can both care about war.
One represents disciplined soldiers, defense, and duty.
Another represents conquest, personal glory, and domination.
A third might govern strategy, fortifications, or victory.
The overlap creates something useful:
religious disagreement.
Followers can argue about which god deserves credit for a victory, which deity should receive sacrifices before battle, or whether a particular war is honorable.
Overlap produces theology.
Theology produces factions.
Factions produce adventures.
Use Inherited, Stolen, and Contested Domains
Divine portfolios do not have to remain fixed forever.
A god can:
This makes the pantheon feel historical rather than designed all at once.
Suppose the god of death was destroyed.
One deity claims authority over the honorable dead.
Another governs restless spirits.
A third controls judgment.
The old priesthood might reject all three.
Now a single mythic event has created:
That is far more useful than simply replacing “God of Death A” with “God of Death B.”
Give the Gods Relationships
Pantheons become easier to understand when gods have personal relationships.
They might be:
These relationships create mythology almost automatically.
Suppose the goddess of civilization stole fire from the god of the wild.
Now you have more than two divine portfolios.
You have an explanation for why their followers distrust one another, why frontier settlements might honor both gods, why old myths disagree over whether the theft was heroic or criminal, and why some priests might still seek reconciliation.
The relationship creates consequences.
Build at Least One Pantheon-Level Conflict
A pantheon without conflict can feel static.
Give the divine order at least one unresolved problem.
Examples:
You do not need to build the campaign around this conflict.
Its existence simply gives the pantheon history, tension, and direction.
Turn Divine Structure Into Mortal Consequences
Pantheon design matters because divine relationships eventually affect the world below.
If two gods are rivals, their institutions may also compete.
If one god conquered another, different cultures may interpret that event very differently.
If several gods share authority over death, their followers may disagree over funerary law.
If one deity rules the others, kings may invoke that divine hierarchy to justify earthly monarchy.
You do not need to fully design those religions here.
The important step is identifying what the pantheon structure makes possible.
Once divine relationships begin producing temples, cults, churches, rites, festivals, and competing religious organizations, Game Master’s Guide to Rites and Rituals can help turn that structure into active campaign material. The book includes tools and random tables for generating temples, festivals, rites, cults, and organizations rather than leaving religion as background lore.
Allow Myths to Contradict One Another
A pantheon does not need one perfectly consistent history.
Different cultures or priesthoods can tell different versions of the same divine event.
One kingdom may claim the sun god created humanity.
Another says humanity awakened the sun god through worship.
One faith teaches that two gods are brothers.
Another insists they are the same being wearing different faces.
Those contradictions can represent:
Contradiction makes a pantheon feel like something cultures have interpreted over centuries rather than something created from a spreadsheet.
Use a Pantheon Architecture Template
You can build a functional pantheon quickly by answering a few structural questions.
For the pantheon as a whole:
For each important god:
That is enough structure to begin.
You can add more only when the campaign needs it.
Example: A Four-God Pantheon
You do not need twelve gods to create complexity.
Consider four.
Aurel, Keeper of the Flame
God of civilization, hearths, law, and protected settlements.
Mara, Lady of Roots
Goddess of wilderness, birth, death, seasons, and things that grow beyond human control.
Veyr, Lord of Roads
God of travelers, merchants, thieves, messengers, and fortunate accidents.
Korath, the Iron King
God of warfare, rulership, ambition, conquest, and oaths of service.
Now connect them.
Aurel and Mara are ancient rivals because civilization continually expands into wilderness.
Veyr moves between their domains and is welcomed fully by neither.
Korath claims civilization survives only because rulers possess the strength to defend it, placing him in constant tension with Aurel over whether law or power creates order.
Mara considers both arguments irrelevant. Forests eventually reclaim kingdoms.
Four gods now create:
The structure matters more than the number of gods.
How MageGate Approaches Pantheon Design
A useful pantheon should produce consequences.
Do not ask only:
“What is this god the god of?”
Ask:
Build outward from consequences.
A pantheon is successful when the relationships between its gods give you material you can actually use.
Fantasy Pantheon Checklist
Before calling the structure finished, check the following.
Divine structure:
Relationships:
History:
Conflict:
If the answer is yes, the pantheon is probably developed enough to begin using.
Frequently Asked Questions
How many gods should a fantasy pantheon have?
Enough to support the setting without becoming difficult to distinguish. A small pantheon of four to eight strongly connected gods can create considerable complexity. Add more when they introduce a meaningful divine role, cultural distinction, or conflict.
Should every god have a unique domain?
No. Overlapping divine responsibilities often make a pantheon more believable and create useful theological disagreements. Two gods can both represent war, death, magic, nature, or rulership while representing different aspects of those concepts.
Does a pantheon need a supreme god?
No. A pantheon can be hierarchical, democratic, divided into factions, organized around divine families, or largely decentralized. What matters is understanding how authority works among the gods.
Can gods gain or lose domains?
Yes, if that fits your setting. Inherited, stolen, surrendered, or contested portfolios give the pantheon history and create natural religious conflicts.
Do I need to know whether the gods are objectively real?
Not necessarily. You need enough information to run the campaign consistently. Whether mortal theology perfectly reflects divine reality can remain uncertain.
Build Gods That Belong Together
The strongest fantasy pantheons do not feel like lists.
They feel like systems.
Start with structure.
Give the gods clear identities.
Let responsibilities overlap.
Connect them through alliances, rivalries, family, betrayal, inheritance, and conflict.
Then ask what those divine relationships change.
If every god exists in isolation, you have a deity list.
If the gods affect one another, you have a pantheon.
Put the Pantheon Into Play
Once your divine structure is established, the next challenge is turning it into religion players can actually encounter.
Game Master’s Guide to Rites and Rituals helps transform temples, cults, churches, festivals, omens, prophecies, and divine ceremonies from background lore into active gameplay systems.
It includes tools and random tables for creating religions, rites, festivals, temples, cults, organizations, arcane and divine rituals, supernatural predictions, and related campaign material.
The majority of the book is system neutral, while its rules material is designed for the 2014 5e and 2024 5.5e rules and is readily adaptable to OSR and other fantasy TTRPGs.
Continue with:
Discover More Resources for Serious Game Masters
MageGate Games publishes practical 5e resources designed to help Game Masters create stronger encounters, memorable villains, distinctive magic items, dangerous environments, deeper fantasy religions, and more useful campaign material without unnecessary prep.
Explore MageGate Games' 5e GM Resources
Explore MageGate Games’ growing library of encounter design tools, boss lairs, monster customization systems, and Game Master resources built for serious 5e campaigns.
Are You a TTRPG Creator, Influencer, or FLGS Looking to Earn More?
Whether you’re a TTRPG creator, influencer, or friendly local game store (FLGS), here’s how you can earn more from the audience or customer community you’ve already built.
About MageGate Games
MageGate Games creates practical 5e tools for Game Masters who want faster prep and more memorable campaigns. Our books focus on reusable systems for boss fights, encounters, traps, terrain, magic items, and long-term campaign support—helping busy GMs spend less time preparing and more time playing.
Discover the MageGate Games design philosophy for building faster, lower-prep, more memorable campaigns.