5e Battle Map Size Guide: Squares, Pixels, and Print Dimensions

How big should a battle map be? Every Game Master runs into the battle map size question from three directions at once: the encounter designer in you thinks in squares, Roll20 wants an answer in pixels, and the print shop only speaks inches. Get one of the three wrong and you end up with a skirmish lost on a football field, a map that blurs the moment a player zooms in, or a printed goblin the size of a thumbtack.

In this guide, we will settle all three questions in one place. You will get encounter sizing in squares, the exact pixel math for Roll20 and other virtual tabletops, print dimensions for physical play, and a single lookup table you can keep open during prep.

The short answer

One square on a D&D battle map equals 5 feet. A tight interior skirmish plays well at about 20 x 20 squares, a roomy standard encounter at about 30 x 30, and roads, ships, and set pieces at about 40 x 30. On Roll20, multiply squares by 70 pixels for the default scale or by 140 for crisp zooming. For print, one square becomes one physical inch, and you want roughly 300 pixels per square for sharp results. The rest of this guide unpacks why those numbers work and when to break them.

How many squares should a battle map be?

Encounter sizing starts with movement. A typical character moves 30 feet per turn, which is six squares, so map size directly controls how many turns it takes for the two sides to meet and how much room anyone has to reposition once they do.

Around 20 x 20 squares suits a tight interior skirmish: a cellar brawl, a guardroom breach, a shrine with a single choke point at the door. Fighting starts almost immediately, cover matters more than mobility, and every square of the map sees use.

Around 30 x 30 squares is the roomy standard for most encounters. There is space for flanking lanes, a second rank of archers, and a retreat that takes more than one turn, without so much emptiness that ranged characters spend the fight plinking across a void. If you are unsure what size to make a map, this is the answer.

Around 40 x 30 squares serves roads, riverbanks, ship decks, and set pieces, where the shape of the space is the encounter itself. Go bigger only with a clear reason: every ten extra squares of empty ground is another round of the party simply walking, and oversized maps are the quiet killer of session pacing.

Roll20 pixel math for battle maps

Roll20 pages default to 70 pixels per square, so converting a map from squares to pixels is one multiplication. A 30 x 20 square map is 2,100 x 1,400 pixels at the default scale. Set the page to 30 by 20 units, upload the image to the map layer, stretch it to fill the page, and every square lines up.

Map artists commonly deliver at 140 pixels per square, exactly double the default, so the art stays crisp when players zoom in on their tokens. That same 30 x 20 map at 140 pixels per square is 4,200 x 2,800 pixels. Roll20 scales it down to fit the page without complaint, and the extra resolution is pure headroom. Our Roll20 battle map generator walkthrough covers the import process step by step, and if your table plays elsewhere, our guide to using AI maps in a VTT covers Foundry and Owlbear Rodeo, which handle scale through pixels per square in much the same way. You can also generate Roll20-ready maps directly with our Roll20 map generator.

Print dimensions for physical battle maps

Physical play adds one hard constraint: miniature bases assume a one-inch grid, so a printed map must come out at exactly one inch per square. A 30 x 20 square map printed to scale is 30 x 20 inches, which is poster territory, and a 40 x 30 set piece is a serious piece of paper.

Print sharpness is measured in dots per inch, and roughly 300 DPI is where a print stops looking soft at reading distance. Since one square is one inch, that translates to a simple target: around 300 pixels per square in your source image. This is where screen-sized exports betray you. A 1,000-pixel-wide image spread across 30 inches of paper works out to about 33 pixels per inch, and the mush is visible from across the room. High-resolution generation is not a luxury for print work: a 2K or 4K export is the difference between a battle map and a blur.

Battle map size lookup table

Encounter type	Squares	Roll20 pixels (70 px per square)	Print size (1 inch per square)
Tight interior skirmish	20 x 20	1,400 x 1,400	20 x 20 in
Standard encounter	30 x 30	2,100 x 2,100	30 x 30 in
Wide scene (roads, rivers)	30 x 20	2,100 x 1,400	30 x 20 in
Set piece (ships, bridges)	40 x 30	2,800 x 2,100	40 x 30 in

Double the pixel figures if you want the crisp 140-pixels-per-square delivery, and remember that the print column assumes the full one-inch grid scale.

Matching resolution tiers to the job

Text to Tabletop generates maps at three resolution tiers, and they map cleanly onto the three unit systems above. The 1K tier (1 token) covers standard VTT play at Roll20's default 70 pixels per square. The 2K tier (2 tokens) gives large maps and 140-pixel crisp-zoom delivery room to breathe. The 4K tier (3 tokens) exists for print and oversized set pieces, where pixels per square decide everything.

There is one more sizing advantage worth knowing: generated maps come out at a strict top-down angle with no baked-in grid, so the squares you planned are the squares your VTT draws. You set the grid scale at import instead of nudging an image around to match lines drawn into the art. You can try all three tiers in our AI battle map generator, and new accounts start with 3 free tokens.

Size the map before you prompt

The best time to answer the size question is before the map exists. Decide the encounter type, read the numbers off the table above, and generate to match: a 30 x 30 warehouse brawl, a 40 x 30 ship deck, a 20 x 20 crypt. Your pacing improves, your grid aligns on the first try, and your prints come out sharp. When you are ready to put the numbers to work, sign up for the Text to Tabletop app and generate a map at exactly the size your next encounter needs.