How to Build a Homebrew Campaign Setting (Without Drowning in Lore)

Start at the table, not the beginning of time

The instinct is to build a setting from the bottom up: cosmology, then history, then geography, then finally, exhausted, the town where the game starts. Reverse it. The first thing you build is the thing the players touch first — the starting settlement, the people in it, the problem that gets them moving — and you build it in real detail because it's the only part guaranteed to see play. Everything else waits.

This feels backwards to anyone who loves worldbuilding, because the cosmology is the fun part. But the players don't enter through your creation myth; they enter through a door in a specific town, and that town needs a name, a mood, a few NPCs with wants, and a reason for the party to care. Get that right and you can run session one. Get the pantheon right and you can run nothing yet. Build in the order the game is played.

Build enough rules to improvise from

A homebrew setting's job is to answer questions you didn't foresee, and it can only do that if it runs on rules rather than a pile of specific facts. Decide the load-bearing systems early — how magic works and what it costs, who holds power and how, what the map's geography implies about trade and travel — because those are what let you rule consistently on the situations the players invent. A world with a real magic system can answer the spell nobody planned; a world with a spell list can only shrug.

You don't need every system finished before session one, but you need the ones that will come up. If magic is central, build the system before you build the fifth kingdom — see how to create a magic system. If travel and territory matter, get the map's logic right early, because a coherent map answers 'what's out there' on demand: how to make a fantasy map. Rules are the part of a setting that keeps paying off; specific facts are the part you'll spend a session inventing anyway.

Leave room on purpose

The richest homebrew settings are mostly negative space: named regions never visited, eras gestured at but not detailed, factions with a one-line agenda and nothing more. This isn't a gap to apologize for — it's where the campaign grows. When the players turn toward a region you left blank, you fill it in with detail tuned to what's actually happening, which is always better than the detail you'd have guessed at cold months earlier.

The trick is to make the blank spaces feel intentional rather than empty. A name, a sentence of intent, and a note on what it implies is enough to make a region feel real from a distance and give you a firm hook when the players arrive. Keep those sketches somewhere you can promote to full detail without rewriting anything — the goal is a setting that expands cleanly toward the players instead of one you have to retrofit. Building just ahead of the table is the whole rhythm of running a homebrew world, and it starts with sketching wide and cheap.

Write it down so you can run it, not just read it

A homebrew setting only helps at the table if you can find things in it fast. The failure mode is a beautiful linear document — the kind that reads like a novel and searches like a haystack — where every mid-session lookup means scrolling past lore you don't need. Structure the setting as discrete, connected pieces instead: this place, this faction, this NPC, each findable on its own, linked to the others it touches.

Many game masters lay the whole thing out spatially, as a board of connected cards, precisely because a setting you can navigate by location is one you can run without stalling — you find the baron by remembering where he lives on the canvas, not by searching text. That's the case we make for any world bible in why a world bible belongs on a canvas, and it's what turns a homebrew document you admire into one you actually run from. From there, the week-to-week rhythm of pulling exactly what a session needs is session prep for game masters.

Frequently asked questions

Where should I start building a homebrew setting?

Start at the table, not the cosmology. Build the place the players will begin — the starting settlement, the people there, the immediate problem — and the few world rules that will come up in the first sessions. Then work outward only as far as the campaign is likely to reach soon. Starting with creation myths and continents is the most common way homebrew settings become elaborate documents that never get played. Build what the first three sessions need, run it, and grow from there.

How much homebrew is too much?

When you're building faster than you're playing, and building parts of the world no plausible campaign will reach. A setting is a tool for running a game, not a novel you write instead of running one. If you have a thousand years of history and haven't sketched the town square the players start in, you've over-built. Keep the ratio honest: depth where the players are, sketches everywhere else, and new detail added just ahead of where the table is heading.

Should I use an existing setting or build my own?

Use an existing one until building your own earns its cost. A published setting is thousands of hours of consistency you get for free; homebrew is worth it when you want a world tuned to your table's specific campaign, or the control to change anything without contradicting a canon you didn't write. Many game masters do both — a homebrew region grafted onto a published world — which gets you a consistent backdrop plus the parts you actually want to own.