Across a long campaign, most fights happen on the same handful of map types: a roadside ambush, a tavern that turns violent, a defensible chokepoint, a crypt, a cave, a city street, a sewer, a boss arena, a raided camp, and a throne room. These ten battle map encounters recur because they map to tactical roles, not story specifics. Stock them ahead of time and you stop scrambling for art at 6 p.m. on game night. This guide breaks down all ten, what makes each one work at the table, and how to tell when a map is earning its place.
It is forty minutes before your session. The party went off-script, ignored the dungeon you prepped, and decided to chase a smuggler through the docks instead. You have no map for the docks. You open three browser tabs, find nothing that fits, and end up sketching a rough grid in the chat while four players wait and the momentum drains out of the night.
Every long-running campaign eventually runs into this. Not because the GM failed to prep, but because players generate combat in predictable kinds of places even when the specifics surprise you. The fix is to stop prepping maps for plots and start stocking maps for situations. In our experience building map packs for tabletop tables, roughly the same ten encounter types account for the large majority of fights that ever need a grid. Stock those ten and you are covered for almost anything the party throws at you.
Why do campaigns keep needing the same ten maps?
Because encounters cluster by tactical function, not by story. A fight on a bridge and a fight in a doorway are the same encounter wearing different costumes: one narrow crossing, open flanks, a decision about who holds the line. The plot reason changes from campaign to campaign, but the spatial problem repeats. Once you start seeing fights as problems to solve rather than scenes to illustrate, the list of maps you actually need gets short and stable.
This is why a map library organized by encounter role outperforms one organized by adventure. Your players will not remember that the ambush happened on the King's Road in session twelve. They will remember that the rogue used the rock cluster for cover and the wizard got cut off on the far side. The terrain carried the memory. The job of a battle map is to create those decisions, and a small set of archetypes covers nearly all of them.
Prep maps for situations, not plots. The party will skip your plot. They will never skip needing somewhere to stand.
In our packs and playtests, roughly four out of five mapped combats fall into fewer than a dozen recurring encounter types. The story around them is infinite; the terrain underneath them is not.
What are the 10 battle map encounters every campaign will eventually need?
Here is the full set, each paired with the tactical role it fills and the single map feature that makes it work. If your library covers these ten, you can improvise almost any fight a session throws at you.
| Encounter | Tactical Role | Feature That Makes It Work |
|---|---|---|
| 1. Roadside Ambush | Travel and surprise | Cover clusters flanking an open road |
| 2. Tavern That Turns | Social into chaos | Tight furniture, multiple exits, a second floor |
| 3. Chokepoint Hold | Defense and control | One narrow crossing with exposed flanks |
| 4. Crypt Crawl | Dungeon delve | Branching corridors, broken sightlines |
| 5. Cave Descent | Verticality and dark | Elevation changes and drop-offs |
| 6. City Street Chase | Pursuit and crowd | Long lanes, alleys, rooftops, obstacles |
| 7. Sewer Run | Confined and hazardous | Water channels and narrow ledges |
| 8. Boss Arena | Climactic set piece | Open center with usable hazards |
| 9. Night Camp Raid | Rest interrupted | Open ground, low cover, a fire to anchor |
| 10. Throne Room Audience | Negotiation gone wrong | Long approach, raised dais, columns |
1. The Roadside Ambush
Sooner or later the party travels, and something is waiting. The ambush map lives or dies on its cover: clumps of rock, trees, or stalled wagons set just off a clear road, so attackers have somewhere to spring from and the party has something to break line of sight behind. Keep the road readable and the flanks busy. A flat green field with nothing on it produces a boring fight every single time.
2. The Tavern That Turns
The tavern is where your campaign socializes, and eventually a chair gets thrown. A good tavern map packs tables and stools tightly enough to create improvised cover and movement penalties, gives you at least two exits, and ideally a second floor or back room for someone to flee toward. Our Shadows Beneath the Tavern map pack was built around exactly this: a friendly room that becomes a tactical one the moment initiative is rolled.
3. The Chokepoint Hold
A bridge, a gate, a collapsed corridor: the chokepoint is the same encounter in different clothing. One narrow crossing forces the party to decide who holds the line, while the open flanks tempt anything with a ranged attack or a fly speed. This is the map that makes front-line characters feel essential, so every campaign should keep one ready to drop.
4. The Crypt Crawl
Undead, tombs, and old money. The crypt rewards branching layouts and broken sightlines: short corridors, alcoves, and a central chamber, so the party cannot simply see the whole fight at once. Tight quarters favor enemies that swarm, which is why crypts are the natural home of the first real horror beat in most campaigns. If that beat leans cosmic, our guide to running eldritch encounters pairs naturally with the map.
5. The Cave Descent
Caves bring the one thing flat dungeons lack: verticality. Ledges, drops, and uneven floors turn positioning into a puzzle, and limited light rewards enemies that ambush from the dark. Build in at least one elevation change the party has to commit to, and the fight stops being a slugfest on a checkerboard.
6. The City Street Chase
Cities generate combat constantly, and the street is where it spills out. The best urban maps give you long lanes for line of sight, alleys for escape, stalls and crates for cover, and ideally rooftops for anyone who climbs. Pursuit is half the encounter, so the map needs to reward movement, not just standing and trading blows.
7. The Sewer Run
Every city has an underside, and the party will end up in it. Sewers combine confined corridors with hazard terrain: water channels that slow movement, narrow ledges, and grates that open or block paths. The claustrophobia is the point, so keep the walkable space tight and the water doing real tactical work.
8. The Boss Arena
The climactic fight needs room to breathe. A boss arena should give the party space to spread out and reposition, a few terrain hazards or features the encounter can exploit, and an open center so the showdown reads clearly at the table. We design our boss arena maps with deliberate negative space, because cramped final fights collapse into a scrum and lose all their drama.
9. The Night Camp Raid
The party rests, and something finds them. The camp map is mostly open ground with low cover and a campfire as the natural anchor, since most of the tension comes from characters being scattered, half-armored, and caught flat. Keep it simple and let the surprise do the heavy lifting.
10. The Throne Room Audience
Negotiations go wrong. The throne room, audience hall, or council chamber starts as a conversation and becomes a fight, so the map needs a long approach, a raised dais for whoever holds power, and columns or furniture to break the open floor. Range and elevation favor the defender, which is exactly the disadvantage the party should feel the moment the talking stops.
Why do most tables keep reusing the same three maps?
Three failure modes show up again and again. The first is prepping maps tied to specific plot beats. You build a gorgeous map for the cult ritual chamber, the party burns the cult's contact instead and never goes, and the art dies in a folder. The second is the opposite extreme: hoarding one generic grass field and one generic stone room and forcing every fight onto them, which flattens tactics until combat feels like the same encounter on repeat. The third is the unsorted dump, a folder of three hundred unlabeled maps that is impossible to search at game time, so you give up and grab whatever loads first.
High performers do the boring thing that works. They keep a small, labeled library organized by encounter role rather than by story, so the right map is one search away when the party improvises. They cover the ten archetypes above with a couple of variants each, leaning on broad role-spanning sets like our Dark Encounter Battle Maps Pack, and they stop there. A map library you can actually navigate under pressure beats one that is technically enormous and functionally useless.
How many battle maps does a single campaign actually burn through?
Treat the following as illustrative, not a benchmark. Assume a level 1 to 20 campaign runs about 50 sessions. Assume one to two combats per session need a grid, call it 1.5, which works out to roughly 75 mapped fights across the campaign. Even if half of those reuse a map you already own, that still leaves somewhere around 35 to 40 distinct map needs over the life of one campaign. Both the session count and the combat rate vary widely by table and play style, but the direction is unmistakable: a single campaign consumes far more maps than any one prep session can produce.
A simple line chart across a 50-session campaign: a flat line near 1.5 mapped fights per session, and a steadily climbing cumulative line that crosses 35 to 40 distinct maps by the finale. The gap between the two is the case for a stocked library instead of one-off prep.
How do you know a battle map is pulling its weight at the table?
A map is a tool, and tools can be measured. After a session, run the map through five signals. If it fails most of them, retire it or replace it.
- Movement. Did players actually reposition, or did everyone plant and swing? A working map gives them reasons to move.
- Turn speed. Could players read the terrain at a glance? If turns slowed down while people decoded the art, the map is too busy.
- Terrain use. Did anyone use the cover, elevation, or hazards? If the features got ignored all fight, they were decoration, not design.
- Drop-in time. Could you load it and align the grid in under five minutes? Prep cost is part of a map's real value, not a separate problem.
- Zoom legibility. Did it still read at the zoom level players actually use? A map that only looks good at full resolution fails in play.
Drop-in time and legibility are where production specs matter most. We ship our battle maps at 4096 by 4096 resolution on a 30 by 30 grid, with both gridded and gridless versions, so the file aligns cleanly in Roll20, Foundry, or Owlbear and stays sharp when players zoom in to count squares. The faster a map gets onto the screen, the more the table feels like play and less like setup.
Frequently Asked Questions
Most campaigns eventually need ten recurring types: a roadside ambush, a tavern that turns violent, a chokepoint, a crypt, a cave, a city street, a sewer, a boss arena, a night camp raid, and a throne room. They repeat because they fill tactical roles rather than tell one specific story. Cover those ten and you can improvise almost any fight.
As an illustrative estimate, a 50-session campaign with about 1.5 mapped combats per session generates roughly 75 mapped fights, or 35 to 40 distinct maps after accounting for reuse. The exact numbers vary by table, but the point holds: you need far more maps than one prep session can make, which is why a stocked library beats one-off creation.
Make custom maps for signature locations the party will see repeatedly, and buy packs for the recurring archetypes you can predict. Building every map yourself does not scale across a campaign, and most one-off DIY maps get used once. A pack of broad encounter types is usually the better value per session, and for a signature location the party keeps returning to, our custom map commissions cover the one-off you cannot buy off the shelf.
Good combat maps create decisions: cover to break line of sight, elevation or chokepoints that reward positioning, and hazards players can use or avoid. They also stay readable, so turns move quickly instead of stalling while players decode cluttered art. Tactical interest plus legibility is the whole job.
A common standard is 4096 by 4096 resolution on a 30 by 30 grid, which aligns cleanly in Roll20, Foundry, and Owlbear and stays sharp when players zoom in. Having both gridded and gridless versions lets you match the VTT's own grid or use the baked-in one. High resolution matters most for legibility at table zoom.
Start with the tavern and the roadside ambush. Nearly every campaign opens with a social hub and a journey, and both reliably produce the first combat. A chokepoint and a small dungeon or crypt are the natural next two, since they cover the first real defensive fight and the first delve.
Yes. The same ten encounter archetypes apply regardless of format. For in-person play, gridded high-resolution maps can be printed or shown on a TV table, and gridless versions suit custom scaling. Even at theater-of-the-mind tables, the maps work as a GM reference for terrain and positioning. If you are weighing the two styles, our breakdown of theater of the mind versus battle maps goes deeper.
Browse VTT-ready battle maps built around the encounters your campaign will actually run. High resolution, gridded and gridless, instant download.
Browse the Map Library →Sources
| Wizards of the Coast | Dungeon Master's Guide: Building Combat Encounters |
| Roll20 | Orr Group State of the Industry Report |
| Sly Flourish | The Return of the Lazy Dungeon Master |
| The Alexandrian | Thinking About Encounter and Scene Design |
| Foundry VTT | Scene and Grid Configuration Documentation |
