Guides
How to Create a Homebrew D&D Campaign
Learn how to create a homebrew D&D campaign as a first-time GM: a simple build order, what to settle before session one, and what to improvise during play.
By Mythical AtlasLast updated
Most first-time GMs who decide to create a homebrew D&D campaign make the same mistake: they try to build the whole world before anyone rolls a die. Months of maps, pantheons and kingdom histories later, session one still hasn't happened, and most of that work never reaches the table.
The fix is to build in milestones. Write a one-paragraph pitch, build one small starting area, plan a first story arc of three to five sessions, then expand only where play takes you. This guide walks through that build order, gives you a checklist of what to settle before session one and what you can safely improvise, and works for D&D 5e, Pathfinder or any other system.
Why a homebrew campaign should start small
A homebrew campaign doesn't need a finished world. It needs enough to run the first few sessions well, and a way to grow from there. Players will ignore some of your favorite ideas and latch onto a throwaway NPC you invented on the spot. Building small means you spend your prep time on the parts they actually care about.
It also helps to know that homebrew doesn't have to mean "everything original." Plenty of experienced GMs invent the setting, the villains and the story, then borrow monsters, maps and dungeons from published material. Make the parts that make your campaign yours, and reuse the rest.
Milestone 1: write the campaign pitch
Before you build anything, write a pitch of one short paragraph. It should answer four questions:
- What's the tone? Heroic, grim, comic, mysterious, political?
- What's the premise? The big situation the characters are stepping into, such as a plague spreading through river towns, or a border fort about to fall.
- Who or what is the main threat? A villain, a faction, a curse or a force of nature. You don't need their full plan yet, only what they want.
- Why are the characters involved? The hook that pulls the party in and keeps them together.
Here's an example: "The river towns of the Grey Reach are emptying, one village at a time, and nobody who goes upstream comes back. The characters are hired guards on the last supply barge heading north. A low-magic mystery with some horror, and a lot of travel."
That paragraph is enough to share with your players. It also becomes your filter for later decisions: if an idea doesn't fit the pitch, save it for another campaign.
Milestone 2: build the starting area
Your starting area is the only place you need in real detail before play. Keep it to one town, village or outpost and the land a day or two around it. For that area, prepare:
- The town itself: a name, what it's known for, and two or three places the party will visit, such as an inn, a temple and a market.
- Five or six NPCs: each with a name, a want and one memorable detail. Include at least one person who can give the party work.
- Two or three nearby locations: a ruin, a cave, a haunted mill. One of them should tie into the main threat.
- A few rumors: short hooks the party can hear in town, some true and some not.
Then sketch the wider world in a sentence or two per region: "the empire is to the south," "the northern mountains belong to the giants." That gives players a sense of the world beyond the map without you having to build it. Everything past the starting area can stay blank until the party heads that way.
Milestone 3: plan the first story arc
Instead of plotting the whole campaign, plan one arc of roughly three to five sessions. A simple arc has:
- An opening situation that hits in the first session, so the party has something to do right away.
- Two or three leads the party can follow in any order, each pointing toward the same answer.
- A climax: a confrontation, a discovery or a choice that ends the arc.
- A loose thread: something left unresolved that points toward the next arc.
Write the arc as situations rather than a script. "The miller is hiding his son, who has been infected" is better prep than "the party will go to the mill in session two." Situations survive whatever the players decide; scripts don't.
You also don't need the ending of the whole campaign. Knowing what the main threat wants is enough. The ending will be better once you've seen what your players do.
Milestone 4: expand as play needs it
After each session, look at where the party is heading and build just that. If they've decided to travel to the capital, the capital gets a page. If they keep asking about the old war, write two paragraphs of history. This "just in time" approach keeps your world consistent with what's actually happened at the table, and it keeps prep manageable.
A useful habit: keep a running list of every name and fact you improvise during a session, and add the keepers to your campaign notes afterward. Improvised details become canon the moment players hear them, so write them down.
Homebrew D&D campaign checklist: settle now vs improvise later
Not everything needs an answer before the first session. Use this split as a guide.
| Settle before session one | Improvise or leave blank |
|---|---|
| The pitch: tone, premise, main threat, hook | The campaign's ending |
| The starting area and its key NPCs | Distant regions and kingdoms |
| The first arc's opening situation and leads | Most of the world's history |
| Which rules and options you're using | Names for minor NPCs and shops |
| Any setting changes that affect character creation | Exact loot after the first arc |
| How the characters know each other | Gods, factions and lore nobody has asked about |
The table-level agreements such as safety tools, scheduling and how lethal the game will be belong in a session zero. Our session zero checklist covers those in detail, so you don't need to plan them here. Bring your pitch to that session and let players help shape the parts they care about.
Where to keep your homebrew campaign
A homebrew setting grows fast, and once players start asking questions you'll want to find answers quickly. The key is splitting what players can see from what only you should know. If you don't, spoilers end up in the same document as the town guide.
If you run your game in Mythical Atlas, the milestones map onto the app like this:
- Create the campaign. A GM creates a campaign with a name and an optional description, then shares the invite code. Players request to join, the GM approves them, and players use the app for free. See the Campaigns guide.
- Put the pitch and setting on the Info page. Info entries sit under categories such as Setting, World Lore, Character Creation, Locations, History and Religion, with Markdown, a table of contents and search. Players can read every Info entry, so keep it to what the characters would know. See the Info guide.
- Write house rules and setting changes on the Rules page. Rules use categories you name yourself, such as "Magic" or "Character Options," so a homebrew rule like "no resurrection magic in the Grey Reach" is easy to find. See the Rules guide.
- Catalog NPCs and places in the Glossary. Glossary entries can be creatures, items, spells, rules, locations or other entries such as factions, each with tags and a Markdown description. Mark an entry as private and only the GM can see it, which makes it the right place for the villain's real identity or the dungeon the party hasn't found yet. When the party discovers it, turn privacy off. See the Glossary guide.
As the campaign grows, our guide on how to organize a D&D campaign covers keeping quests, recaps and NPCs tidy from session to session. If you'd like to try the setup before inviting your group, Sandbox Mode is a free, private practice campaign limited to 5 entries per category.
Start with one town and one problem
You don't need a world to run a homebrew campaign. You need a pitch, a starting area, a first arc and the habit of writing down what happens. Run the first session, see what your players care about, and build the next piece from there.
