Choose resolution from the map's grid, not from a single universal canvas size. A practical target is roughly 100 to 150 pixels per grid square. That makes a 30 × 30 map about 3,000 × 3,000 to 4,500 × 4,500 pixels, while a 50 × 30 map needs a wider canvas. Use dimensions that divide cleanly by the grid count whenever possible, then balance image quality against your VTT's upload limits and your players' connection speeds.
A battle map can look beautifully detailed in a store preview and still become soft, slow, or difficult to align once it reaches your virtual tabletop. The usual problem is not that the image lacks a fashionable “4K” label. It is that the file dimensions, grid dimensions, and intended display were never considered together.
This guide explains the numbers that actually matter. You will learn how to calculate pixels per square, prevent alignment drift, choose a file format, prepare a map for a tabletop TV, and decide whether a listing gives you enough technical information before you buy.
Is 4096 × 4096 the standard battle map resolution?
It is a common high-resolution canvas size, but it is not a universal standard. A square 4096-pixel image can work well for many encounter maps, especially on large displays, yet the best dimensions depend on the map's shape and number of grid cells. A 40 × 25 tavern, a 30 × 30 cave, and a 60 × 40 dungeon should not automatically use the same canvas.
The phrase “4K map” can also be misleading. Consumer 4K televisions are usually 3840 × 2160 pixels with a 16:9 aspect ratio. A 4096 × 4096 square map cannot fill that screen without being scaled, cropped, or surrounded by unused space. That does not make the map unsuitable. It simply means canvas dimensions and display resolution describe different things.
Start with grid columns and rows. Multiply each by your chosen pixels per square. This produces a canvas that fits the encounter instead of forcing every encounter into the same square image.
How many pixels should each grid square use?
For most digital battle maps, 100 to 150 pixels per square is a strong working range. Around 100 pixels per square keeps files manageable while retaining enough detail for tokens and terrain. Moving toward 140 or 150 pixels provides more zoom headroom, but the file becomes larger. Lower values can still work when the map is large, the artwork is simple, or fast loading matters more than close inspection.
| Grid | 100 px per square | 140 px per square | Best fit |
|---|---|---|---|
| 30 × 30 | 3000 × 3000 | 4200 × 4200 | Focused encounter |
| 40 × 30 | 4000 × 3000 | 5600 × 4200 | Large room or complex |
| 50 × 40 | 5000 × 4000 | 7000 × 5600 | Exploration map |
Illustrative calculation: assume a map has 36 columns and 24 rows at 120 pixels per square. Multiply 36 × 120 for a width of 4320 pixels, then 24 × 120 for a height of 2880 pixels. The final 4320 × 2880 canvas divides evenly into the grid and is naturally suited to a widescreen display.
Why does clean grid math prevent alignment drift?
Grid drift happens when a VTT grid looks aligned near one corner but gradually separates from the map's printed lines. One common cause is a mismatch between the image dimensions and the grid count. For example, 4096 divided by 30 equals about 136.53, not exactly 136. Rounding that value and treating every cell as 136 pixels leaves a growing discrepancy across the image.
If you create a map from scratch, use a canvas that divides evenly by its columns and rows. If you import an existing map, enter its stated grid dimensions rather than relying on an estimated pixels-per-square value. Owlbear Rodeo supports known grid dimensions and visual alignment rulers, while Roll20 provides page sizing and alignment controls. Gridless versions are especially useful because the VTT can draw one clean grid after alignment, avoiding doubled lines.
How should you choose a battle map resolution?
Build the file around the way it will be played
1 Count the playable cells. Record the exact columns and rows, including any intentional border cells.
2 Choose a detail target. Use about 100 pixels per square for efficient VTT play or move toward 140 to 150 when close zoom and large displays matter.
3 Calculate the canvas. Multiply columns and rows by the same pixels-per-square value so every cell remains square.
4 Check the destination. Confirm the VTT's supported formats, account-level upload limit, storage allowance, browser performance, and player bandwidth.
5 Test at play scale. Open the final export on the actual monitor, TV, projector, or VTT before session night. Check text, doors, hazards, tokens, grid alignment, and loading speed.
Is PNG, JPEG, or WebP better for battle maps?
There is no single correct format for every map. PNG uses lossless compression and is excellent for sharp grids, transparency, text, flat colors, and artwork that must survive repeated editing. Its disadvantage is file size. A highly textured forest or cave can become much larger as a PNG than as a well-exported JPEG or WebP.
JPEG is widely compatible and often efficient for painterly maps without transparency. At sensible quality settings, it may look nearly identical during play while loading faster. WebP can offer a strong quality-to-size balance, but you should confirm that your chosen platform and workflow support it. Keep a lossless master file, then export the play copy in the format that fits the destination.
| Format | Best for | Main tradeoff |
|---|---|---|
| PNG | Sharp grids, text, transparency, archival exports | Larger files on textured art |
| JPEG | Painterly scenes and broad compatibility | Lossy compression and no transparency |
| WebP | Smaller modern web exports | Compatibility should be checked first |
What changes when you use a tabletop TV or print the map?
For a tabletop TV, judge the map at the size players will actually see it. A square map shown on a widescreen panel will normally occupy only part of the display unless the software crops or stretches it. The map does not need to match the television's pixel dimensions exactly, but it should retain enough source detail at the chosen zoom. Also test whether one-inch physical squares on the screen match your miniatures.
For printing, PPI finally matters. Divide the pixel dimension by the intended print dimension in inches. A 4200-pixel-wide image printed 28 inches wide produces 150 PPI. Printed at 14 inches wide, it produces 300 PPI. Around 150 PPI can be suitable for a tabletop map viewed at normal distance, while 300 PPI provides finer close-up output. Your printer, paper, viewing distance, and artwork all affect the result.
PPI describes print density. Pixel dimensions and on-screen scaling determine how a digital map looks.
What should you check before buying a battle map pack?
A useful product listing should tell you more than “high resolution.” Look for exact pixel dimensions, grid columns and rows, file formats, gridded and gridless options, number of maps, and approximate download size. These details tell you whether the pack will align cleanly and fit your setup.
- Exact dimensions: Width and height in pixels, not only HD, 4K, or print-ready.
- Grid dimensions: Columns × rows so the VTT can be configured without guessing.
- Grid options: A gridless version gives you more control inside the VTT.
- Format: Confirm that the included files work with your platform and editing workflow.
- Readable scale: Doors, passages, furniture, and hazards should make sense at token size.
A connected collection of tavern interiors, hidden rooms, underground passages, and encounter spaces supplied for digital tabletop play.
View the Map Pack →Frequently Asked Questions
The best resolution depends on grid size and intended use. A practical target is about 100 to 150 pixels per square, which produces clear VTT maps without automatically creating oversized files. Calculate width and height separately from the map's columns and rows.
Yes, it can be a strong high-resolution size for square encounters, but it is not ideal for every grid. Because 4096 does not divide evenly by 30, a 30 × 30 printed grid may require careful alignment or a slightly different canvas size.
About 100 to 150 pixels per square works well for many modern digital maps. Lower values reduce file size, while higher values preserve more detail during zoom. The VTT and the scale at which players view the map should guide the final choice.
Drift usually means the map scale, grid count, offset, or border was entered incorrectly. Use the creator's exact column and row count when available, align from a known cell corner, and verify the opposite edges before finishing.
PNG is excellent for sharp grids, text, transparency, and lossless masters. JPEG can be much smaller for painterly maps and may load faster with little visible difference at play scale. Choose according to the artwork and platform rather than treating either format as universally superior.
The PPI metadata does not control normal on-screen quality. Pixel dimensions, browser scaling, zoom, and display resolution do. PPI becomes useful when calculating how large the same image can be printed at a chosen density.
Usually not for a single encounter. Very large dungeons, regional maps, close zoom, or oversized prints may benefit from more pixels, but an 8K file can increase loading and storage costs. Use the smallest resolution that stays clear in your real setup.
Explore Cubold Gaming battle map packs built for atmospheric encounters and straightforward digital tabletop setup.
Browse Battle Maps →Sources
- Roll20: Best Practices for Files on Roll20
- Roll20: Sizing and Aligning Maps
- Owlbear Rodeo: Aligning a Map
