It tells you the map has a large pixel canvas, but that number alone does not determine tabletop quality. For VTT play, pixels per grid square and total file size matter more than DPI. For print, the physical print size and resulting DPI matter. A 4096 × 4096 map on a 30 × 30 grid gives you about 136 pixels per square, which is a strong high-resolution VTT export. The same 4096-pixel file printed 30 inches wide lands at about 136 DPI. Always evaluate the pixel dimensions, grid count, and intended use together.
You download a battle map, drop it into Roll20, zoom in to position a token, and the stonework turns into smeared blocks. Tree edges dissolve. Fine terrain detail disappears. The map looked fine in the marketplace preview because the preview was small. At session scale, the source file does not have enough information to hold up.
High-resolution battle maps solve that problem, but “4K” gets used loosely in the TTRPG map market. Sometimes it means 4096 pixels on one side. Sometimes it means something close to UHD display dimensions. Sometimes it is simply marketing language attached to a file that never states its actual size.
The numbers that matter are straightforward once they are separated: total pixel dimensions, pixels per grid square, physical print size, and file weight. This guide explains how each one affects Roll20, Foundry, TV tables, and print.
What does 4K mean for a battle map?
In consumer displays, 4K UHD normally refers to 3840 × 2160 pixels. Battle maps do not have one official “4K map” specification. Square maps are commonly sold at dimensions around 4096 × 4096, while rectangular maps may use very different dimensions and still be marketed as 4K.
That is why the grid count has to be part of the conversation. A 4096 × 4096 file divided across 30 squares gives you roughly 136 pixels per square. The exact same 4096 × 4096 file divided across 60 squares gives you only about 68 pixels per square. Both files are technically the same total resolution, but the 30 × 30 version carries twice as many pixels into each tactical square.
Foundry's current documentation explicitly notes that common map grids include 70, 100, 140, and 200 pixels per square. There is no universal requirement that every VTT map use 140. What matters is that the map has enough density for the way it will be viewed and that the grid size is documented so the scene can be configured correctly.
That calculation is more useful for VTT quality than the word “4K.” If the seller gives you the pixel dimensions and grid count, you can immediately see how much detail each tactical square contains.
Why does resolution matter so much for battle maps?
Battle maps are not viewed at one fixed size. Players zoom. DMs zoom farther. Tokens are positioned against small terrain features. Doorways, ledges, stairs, rubble, and cover all need to remain understandable after the scene has been enlarged beyond its initial fit-to-screen view.
That makes a battle map different from a normal web image. A small image can look perfectly sharp in a 400-pixel marketplace card because the display is shrinking it. Once the file is expanded to thousands of pixels of tabletop space, there is nowhere for missing detail to come from.
Zoom exposes pixel density. A map that looks clean from a full-scene view may become soft around token scale if the source does not contain enough pixels per square.
Large physical dimensions spread the same pixel count across more inches. The wider you print, the lower the resulting DPI unless the source image is correspondingly larger.
How is resolution different for VTT play and print?
| Factor | VTT Play | Print Play |
|---|---|---|
| Primary quality metric | Pixels per grid square | DPI at intended physical size |
| DPI metadata | Generally irrelevant to the VTT renderer | Relevant when converting pixels to physical inches |
| Where weakness shows | Zoomed terrain, thin edges, small props | Soft grid lines, blurred textures, blocky detail |
| Useful format | JPG for opaque maps, PNG where lossless detail or transparency matters | High-quality PNG, TIFF, or print-ready file requested by the printer |
| Grid choice | Gridless is flexible because the VTT can overlay its own grid | Gridded is convenient for miniatures and direct measurement |
| File-weight concern | Important for upload caps, bandwidth, and scene load time | Less important once the file reaches the printer |
What does the print math look like?
For a standard 30 × 30 map printed at one inch per square, the finished map is 30 inches wide. Divide the source width by 30 inches and you get the resulting print DPI.
For a close-viewed art print, 300 DPI is a familiar target. Battle maps are different because players normally view the full table from farther away and because the finished print may be extremely large. A map does not automatically need 9000 pixels per side simply because a 30-inch print at 300 DPI would mathematically require it. The right target depends on art style, viewing distance, printer, and how much fine detail matters.
How do you set up a high-resolution map in Roll20?
A high-resolution source can still look wrong if the map is stretched to the wrong number of cells. In Roll20, size the map according to its intended grid count rather than preserving its full source pixel dimensions as tabletop dimensions.
If the map is 30 × 30, the image should occupy 30 × 30 Roll20 cells. The source might be 4096 pixels wide, but that does not mean the Roll20 display needs 4096 tabletop pixels.
Let Roll20 provide the overlay grid when you want the easiest alignment. If you use a baked-in grid, use Align to Grid and fine-tune the image position instead of forcing a mismatched scale.
Roll20 currently gives Free accounts 100 MB of total storage and allows image uploads up to 20 MB per asset. High-resolution maps often benefit from JPG compression when transparency is not needed.
Do not judge the map from a thumbnail. Zoom to the distance players actually use and verify that terrain edges, doors, hazards, and cover remain readable.
How do you set up the same map in Foundry VTT?
Foundry separates image dimensions from grid size. When the map's intended grid density is known, set the scene background normally, then configure the grid to match the pixels per square used by the source file.
A 4200 × 4200 map built for a 30 × 30 grid uses 140 pixels per square, so the Foundry grid can be set to 140. A 4096 × 4096 map on the same 30 × 30 grid works out to roughly 136.5 pixels per square, which creates an awkward non-integer grid size. In that case, it is often cleaner to scale the scene or use the grid configuration tools rather than pretending the source is exactly 140.
Foundry supports common grid sizes including 70, 100, 140, and 200 pixels per square, with a minimum grid size of 50 pixels. It also recommends deciding on the grid before building walls, lights, and other scene elements so later rescaling does not force rework.
What about TV and projector tables?
For a horizontal TV or projected map, the most important setting is physical scale. If standard miniatures will sit directly on the display, one map square should measure about one physical inch. The map file's pixels per square and the screen's pixels per inch are separate measurements.
Load the map, place a ruler on the physical display, and adjust the software zoom until one grid square measures correctly. A high-resolution source gives you more visual headroom while you make that adjustment, but “4K” by itself does not guarantee a one-inch physical grid.
What should you look for when buying high-resolution battle maps?
“High resolution” and “4K quality” are vague. Look for 4096 × 4096, 4200 × 4200, or another stated number.
The same 4K file can be excellent at 30 × 30 and much less detailed at 60 × 60. You need both numbers.
Gridless is flexible for VTT overlays. Gridded is ready for physical play or DMs who prefer the lines baked in.
PNG is lossless and useful where transparency or exact edges matter. JPG is often more efficient for large opaque map art and is Roll20's preferred image format.
A beauty crop can hide weak spatial readability. Look for full-map previews where walls, doors, paths, and hazards are still clear.
Resolution is only the technical floor. Lighting, palette, scale, terrain language, and regional continuity determine whether a pack feels like one place.
Resolution is a requirement, not a quality guarantee. A large file can still have weak terrain design, confusing scale, poor composition, or excessive visual noise.
Why do DMs underestimate resolution until it is too late?
Frequently Asked Questions
What resolution should a battle map use for VTT play?
There is no single universal VTT standard. Common grid densities include 70, 100, 140, and 200 pixels per square. Higher values provide more zoom detail but create larger files. A 30 × 30 map at 140 pixels per square is 4200 × 4200 pixels. A 4096 × 4096 version of the same grid is about 136 pixels per square and is similarly high resolution.
Do I need a different file for print and VTT use?
Not always, but separate exports can make setup easier. Gridless files are flexible in VTTs because the software can apply its own overlay. Gridded files are convenient for print because the measurement system is already baked into the map. Print quality also depends on the physical output size, so a dedicated print file may be useful for very large formats.
What is the difference between a 4K and an HD battle map?
The difference is total pixel count, but the tactical impact depends on grid size. A roughly 4K square map gives a 30 × 30 encounter much more pixel density per square than a 1920-pixel source. As the grid count increases, the per-square advantage decreases, which is why total resolution and square count should always be read together.
Why can a high-resolution battle map still look bad?
Resolution only prevents one class of problem. Poor composition, blurry source textures, aggressive JPEG compression, inconsistent scale, unreadable terrain, repeated texture tiles, and weak lighting can all survive inside a very large file. Pixel count is the technical floor, not the full quality standard.
How do I know if a battle map pack is actually high resolution?
Look for stated pixel dimensions and the grid count. Divide the image width by the number of grid columns to calculate pixels per square. If a listing only says “4K quality” or “high resolution” without giving dimensions, you do not have enough information to verify what that label means.
Can I print a 4K battle map on a home printer?
Yes, but a 30 × 30 map at one-inch squares is physically 30 × 30 inches, which is much larger than letter or A4 paper. You can tile the map across multiple pages or send it to a large-format print service. Check the resulting DPI at the final physical size before printing.
What grid size is standard for battle maps?
There is no single standard map dimension. General encounter maps often fall around 20 × 20 to 30 × 30 squares, while large outdoor or boss encounters may use 40 × 40 or more. In D&D tactical play, one square commonly represents five feet. Always judge resolution against the actual grid count rather than the file size alone.
High-resolution digital map packs with documented dimensions, gridded and gridless options, and terrain designed to stay readable when the session zooms in.
Shop Battle Maps →Sources
| Foundry VTT | Scenes and Grid Configuration |
| Foundry VTT | Content Creation Style Guide |
| Roll20 | Best Practices for Files on Roll20 |
| Roll20 | Sizing and Aligning Maps |
| Black Lantern Forge | Battle Map Collection |
