D&D World Building: A Practical Guide That Survives Session 1 (2026)

You sat down to plan your D&D world on a Sunday afternoon. It is now Tuesday night. You have 42 pages of lore, three pantheons, a calendar system based on twin moons, and an extremely strong opinion about how trade routes work in your continent's southern empire.

Your players arrive on Saturday. You have not written a single NPC they will meet.

I have done this exact thing. The first homebrew world I ever tried to run had a 60-page setting bible and a cosmology that referenced four planes of existence. My players spent the first session asking the innkeeper for directions. They never learned the name of the empire. They never met a single god. By session 4 the campaign was dead, and not because the world was bad. Because I had built the wrong thing.

This guide is everything I wish I had read before that campaign. D&D world building is not novel writing. It is a play-support discipline, and once you treat it that way, you stop drowning in prep and start running games that feel alive.

Why most D&D world building advice is wrong

If you Google "how to build a D&D world," you will mostly find advice borrowed from fantasy novelists. Start with geography. Define your magic system. Develop your pantheons. Map your trade networks. Build your languages.

That is excellent advice if you are writing a book. It is terrible advice if you are running a Saturday game.

Tabletop worlds are made of two ingredients: what your players touch, and what the table believes is true. Everything else is wallpaper. The most beautifully detailed creation myth in your binder does not exist in the world unless your party finds out about it. The trade routes you mapped do not matter until a player asks how the merchant got from the coast to the capital.

The fix is simple but uncomfortable. Build only what the table will touch in the next two sessions. Let the world expand outward from there.

This is the same principle behind the lazy DM approach to session prep and the reason most published starter adventures work so well for first campaigns. They give you exactly enough to run the next three nights of play, then trust you to grow the world from there.

The eight steps in order

Before we get into details, here is the whole flow on one page. If you do these eight things, you will have a world that survives session 1 and keeps surviving.

Step	What you build	Time
1	The one promise of your world	15 minutes
2	A small starting region (3 to 5 locations)	30 minutes
3	Three factions in tension	20 minutes
4	Five NPCs your party will meet first	30 minutes
5	Magic and tech baseline (one paragraph each)	10 minutes
6	The active threat that opens the campaign	15 minutes
7	Where the world lives (your wiki)	15 minutes
8	Session 1, run with the table	One game night

Total prep time: about two hours. Anything longer is usually procrastination dressed up as worldbuilding.

Step 1: Pick the one promise of your world

Before you draw a map, pick one sentence. "This is a world where..." or "In this setting, stories are about..."

A few real examples from games I have run or played:

• "This is a world where every dragon has been killed, and the people who killed them are running the empire."
• "This is a coastal city where the sea is sentient and slowly waking up."
• "This is a world where magic is a recent invention and nobody has figured out the rules yet."

The promise is not a plot. It is a tonal contract. It tells you what kind of sessions you are running. A world where dragons are gone but the dragonslayers rule is a political world about legacy and corruption. A world where the sea is waking up is a horror world about scale. You can run a dungeon crawl in either, but the dungeon will feel different.

If you cannot finish the sentence, you do not have a world yet. You have a vibe. Sit with it longer.

Step 2: Draw a small starting region

Not a continent. Not a kingdom. A region the party can cross in three or four sessions of travel.

Three to five locations is plenty. A capital town. A nearby dungeon or ruin. A second settlement with a different culture. Maybe a wilderness area between them. That is enough surface for a dozen sessions.

I sketch these by hand on a single sheet of paper. Crude is fine. The map exists so you can answer "how far is it from here to there" without lying about it later. If you want a polished map for the table, you can make one once the campaign survives session 6.

For inspiration on what a region needs to feel alive, the worldbuilding section of the r/DMAcademy subreddit is one of the better free resources. The recurring theme: small worlds with conflict feel bigger than large worlds with none.

Step 3: Name three factions in tension

Factions are the engine of your campaign. They give NPCs goals, give locations stakes, and give players reasons to care about the people they meet.

Three is the magic number. Two creates a binary. Four becomes hard to track. Three gives you a triangle of conflict where every party choice picks sides.

For each faction, write two sentences:

• What they want. Power, faith, money, vengeance, survival, knowledge.
• What they fear. What outcome would make this faction fall apart.

A merchant guild that wants trade dominance and fears the rise of a populist movement. A church that wants conversions and fears heresy. A criminal network that wants protection and fears exposure. Those three groups can drive 30 sessions of play and you have not yet named a single NPC.

Once you write the factions, every NPC you make later has a relationship to one of them. The innkeeper is not just an innkeeper. She is also paying the criminal network for protection, which puts her at odds with the church next door.

Step 4: Write five NPCs your party will meet first

Five is the right number for session 1 and 2. Any more and you will forget half of them yourself.

For each, write:

• A name (just say it out loud first to check it does not sound silly).
• A job (innkeeper, guard captain, retired adventurer, town drunk, child).
• A goal (what they want this week, not in their life).
• A quirk (one observable thing: a missing finger, a nervous laugh, never makes eye contact).

That is the whole NPC entry. A paragraph. If they become important, you can write more later. Most will not, and the ones who do will gain depth through play in ways you cannot predict.

If you want a deeper take on making NPCs that stick in your players' memory, I wrote a whole piece on curing NPC amnesia that pairs well with this step.

Step 5: Magic and tech baseline (one paragraph each)

You do not need a magic system. You need a magic baseline.

Two questions. How common is magic? What does it cost? Write a paragraph. That paragraph tells your players what to expect when they cast spells, what NPCs treat as normal, and what makes them gasp.

Same for technology. Are we at medieval baseline, or has someone invented gunpowder, printing, clockwork? One paragraph. Done.

You can sweat the deeper rules later. For session 1, players just need to know if a fireball in a tavern is shocking or a Tuesday. That answer changes everything about how they roleplay.

Step 6: The active threat

This is the step new DMs skip and pay for later.

Your world needs a current problem. Something the party can run into in session 2 at the latest. A village being raided. A noble who has gone missing. A cult buying up land. A plague that is changing people.

Without an active threat, you have a setting. Settings are fine. But you cannot run a setting. You run a campaign, and a campaign needs forward motion. The active threat is what turns "you arrive in town" into "you arrive in town, and the militia is gathering at the gates because something is wrong."

If your three factions are well chosen, the active threat will usually come straight from one of their conflicts. The cult buying land? That is the criminal network expanding under cover of religion, and the church has noticed. The party walks into a powder keg.

Step 7: Decide where your world lives

This is the step most worldbuilding guides leave out, and it is the one that decides whether your world survives past session 8.

If your locations, NPCs, factions, and lore are scattered across a notebook, three Google Docs, the back of a Doritos receipt, and your memory, they will fall apart. Not because you are disorganized. Because the volume grows every session and human memory does not.

You need one place where everything in the world lives, and you need it before session 1. The right tool depends on how you like to work:

• Notion or Google Docs if you enjoy organizing manually and have the patience for it.
• A dedicated worldbuilding platform if you build a lot of lore before you play and want detailed templates for cultures, religions, and so on. World Anvil is best for that style.
• An auto wiki tool if you would rather just play and let your notes organize themselves. Saga20 records your sessions and builds the campaign wiki for you, so the locations, NPCs, and factions you invent at the table show up in your world reference without you typing them in.

Whichever you pick, pick it before session 1 and commit. Switching tools mid-campaign is how you lose the first ten sessions of your world's history.

Step 8: Run session 1 and let the table change everything

This is the part new DMs find hardest.

Your players will invalidate parts of your prep. They will ignore your most carefully designed location. They will fall in love with an innkeeper you invented on the fly. They will name your unnamed villain. They will decide your church is corrupt before you had decided that.

Let them. That is the entire point of tabletop worldbuilding. The world that emerges from play is always better than the world you wrote alone, because it has been stress-tested by five other imaginations. Your job from session 2 onward is to listen for what the table cares about and build outward from there.

Pointy Hat made a strong video on exactly this principle. Worth watching if you have 30 minutes.

Five worldbuilding mistakes that kill first campaigns

These are the patterns I see in nearly every dead campaign I have heard postmortems for. Avoid them on purpose.

1. Writing the cosmology first. Players almost never care about your creation myth in session 1. They care about the tavern. Build the tavern.

2. Treating worldbuilding as homework. If a session of prep does not produce something you will use in the next two sessions, it is a hobby, not prep. Hobbies are fine. Just be honest about what you are doing.

3. Refusing to use real-world inspiration. Every great fantasy setting is a remix of real history and culture. You do not need to invent feudalism from scratch. Start with something that exists, change three things, and call it yours.

4. Locking in canon too early. If you write that the empire fell exactly 312 years ago, you cannot adjust later when the campaign needs a different timeline. Leave room. Soft canon survives play. Hard canon breaks.

5. Building alone the whole time. Talk to your players in session zero about the kind of world they want to play in. Their backstories will give you hooks you would never have invented. The best worldbuilders I know treat the table as co-authors from day one.

Where to put your world: the wiki step matters more than you think

I want to come back to step 7 because it is the most underrated decision in this whole guide.

Your world is not the document you wrote on Sunday. Your world is the entity that grows every session: new NPCs invented at the table, locations the party named on the spot, factions that emerged from play, plot threads that were not in your notes until your rogue made them real.

If you do not have a system for capturing all of that, your world dies in your head by session 12. You will sit down to plan session 13 and not remember what the party promised the church or whether Gorrin the innkeeper is still alive.

A campaign wiki fixes this. It is the difference between running a campaign and running a story you remember as you go. We wrote a longer piece on what a campaign wiki is and why every DM needs one, and the short version is this: a wiki organizes your world by entity (NPCs, locations, factions) rather than chronologically (session notes). When a player asks who the blacksmith was, you find the page, not the session.

Some DMs build wikis by hand. Some use a D&D world builder that writes the pages for them by listening to the session. Either approach works. Skipping the wiki step entirely is what does not.

If you want the tool version of this guide rather than the craft version, our world builder keeps every NPC, location and faction on its own page and adds a new history entry after each game, so the world you actually played stays ahead of the one you planned.

If you want the players to do the exploring for you, the same small-region approach is the foundation of a West Marches campaign, where the map only gets filled in once someone walks that way.

A note on published settings versus homebrew

For a first campaign, a published setting is genuinely easier. The Forgotten Realms gives you a continent of factions, religions, and locations to drop in. Eberron gives you a noir-flavored magitech world with built-in political tension. Ravenloft gives you horror with structure.

The worldbuilding rules from this guide still apply. You still pick a region within the setting. You still write the five NPCs and the three factions. You still pick an active threat. You are just borrowing the wallpaper instead of painting it yourself.

Homebrew is best when you have a specific premise that no published setting captures. If your one-sentence promise is unusual enough, homebrew is the only way to honor it.

If you are still deciding whether to homebrew at all, the Wistedt step-by-step homebrew guide is one of the more honest resources online. It assumes you actually want to run the world, not just write it.

Final thought

A great D&D world is not the one with the most lore. It is the one that survives contact with the table, gets richer every session, and stays organized enough that you can still find Gorrin the innkeeper by session 30.

Pick a one-sentence promise. Build small. Write your three factions. Write your five NPCs. Pick the active threat. Set up a wiki. Then play.

The world will build itself from there. You just have to let it.