For VTT battle maps, the embedded DPI number is far less important than the actual pixel dimensions of the image and the number of pixels available for each grid square. On a 30×30 map, 72 pixels per square produces a 2160×2160 image, 150 pixels per square produces 4500×4500, and a 4096×4096 map gives you about 136.5 pixels per square. For most VTT play, roughly 100 to 150 pixels per square provides an excellent balance of detail and performance. A 4K-class source is especially useful when players zoom in or when the same map will also be displayed on a tabletop TV.
You download a beautiful dungeon map, drag it into your VTT, and immediately notice two problems. The file takes longer to load than expected, but when a player zooms into the room where combat is happening, the floor textures still look softer than they did in the preview.
Then you check the image properties and see "72 DPI." Another map advertises "150 DPI." A third simply says "4K." Which one is actually better?
The answer is more technical than the marketing labels make it sound, but it is also easier once you know what matters. Virtual tabletops do not judge a battle map the way a printer does. They care about pixels, grid scale, file size, browser or GPU limits, and how aggressively players are going to zoom into the image.
If you understand those five things, you can choose the right battle map resolution without making your VTT carry millions of unnecessary pixels.
Does DPI Actually Matter for a Digital Battle Map?
Not in the way most people think.
DPI means dots per inch and is fundamentally a printing measurement. Digital images are better described by their pixel dimensions, such as 3000×3000 or 4096×4096 pixels.
A file can be tagged as 72 DPI or 300 DPI without changing a single pixel in the image. If both files are 4096×4096 pixels, they contain the same number of pixels. Changing only the DPI metadata does not magically create more texture detail for Roll20, Foundry VTT, or a browser.
Image width in pixels ÷ number of grid columns = pixels available per grid square. That number tells you far more about VTT sharpness than the DPI metadata embedded in the file.
There is one source of confusion worth knowing. Some VTT tools use the label "DPI" to describe the pixel size of a grid cell. Owlbear Rodeo, for example, uses DPI as the resolution assigned to a grid cell. In practical VTT conversation, someone saying "150 DPI map" may actually mean approximately 150 pixels per grid square.
That is the interpretation that matters for this guide.
What Does 72 DPI Mean for a VTT Battle Map?
If we treat 72 DPI as 72 pixels per grid square, a 30×30 battle map needs 2,160 pixels on each side.
Illustrative 30×30 map at 72 pixels per grid cell: 30 cells × 72 pixels = 2,160 pixels per side.
That is already enough resolution for basic online play. Tokens remain readable, rooms are clear, and the map does not require an enormous texture.
There is also a practical reason this range feels familiar. Roll20's default square grid is 70 pixels per cell, which is very close to the old 72-pixel convention many digital maps used.
The weakness appears when players zoom in. A map that looks perfectly acceptable when the entire dungeon is visible can begin to look soft when one 5-foot square occupies a large section of a laptop or 4K monitor.
For simple maps, older computers, slow internet connections, and groups that rarely zoom deeply, approximately 70 to 72 pixels per square can still work. It is a performance-first choice, not a detail-first choice.
What Changes When You Move Up to 150 DPI?
At 150 pixels per grid square, the same 30×30 encounter becomes a 4500×4500-pixel image.
That is more than four times as many total pixels as a 2160×2160 image. The extra resolution gives the VTT much more detail to preserve during zooming, but it also creates more image data to download, decode, and render.
| 30×30 Map | Pixel Dimensions | Total Pixels | Best Fit |
|---|---|---|---|
| 72 px/cell | 2160×2160 | 4.67 million | Lightweight VTT play |
| 100 px/cell | 3000×3000 | 9 million | Strong general-purpose balance |
| 4K-class BLF source | 4096×4096 | 16.78 million | High detail and tabletop display |
| 150 px/cell | 4500×4500 | 20.25 million | High-resolution VTT scenes |
This is why "double the resolution" can be misleading. Going from 75 pixels per square to 150 pixels per square doubles the width and height, but roughly quadruples the number of pixels in the image.
That does not mean 150 pixels per square is excessive. Foundry's own content guidance recommends at least a 100-pixel grid when possible for strong grid snapping, and higher-resolution content can look excellent during close zoom. It simply means the extra quality has a real performance cost.
Where Does a 4096×4096 4K Battle Map Fit?
A 4096×4096 map sits in a useful middle ground for a 30×30 encounter.
Divide 4096 pixels by 30 squares and you get approximately 136.5 pixels per square. That places the source above a common 100-pixel VTT standard while remaining slightly below a full 150-pixel-per-cell export.
Assume the map represents exactly 30 columns and 30 rows. The VTT can scale that image to 30 grid units even though 4096 does not divide evenly by 30.
That last point is important. A map does not have to divide into a perfectly round number of pixels per square to work. Modern VTTs can rescale the image to the intended grid dimensions.
Black Lantern Forge maps use a 4096×4096 source on a 30×30 layout because it preserves substantial terrain detail while remaining practical for modern VTTs and 4K tabletop displays. You can see the same sizing logic in our guide to scaling 30×30 battle maps for D&D movement.
It also gives the file enough source resolution to look good when used outside a browser. A tabletop television changes the equation because the map may be physically stretched across a 40-inch or larger display. In that setup, a higher-resolution source becomes much easier to appreciate.
Does a Higher-Resolution Map Always Look Better?
Only until the extra pixels stop solving a visible problem.
A 12,000×12,000 map is technically more detailed than a 4000×4000 version, but that does not automatically make it a better VTT asset. Players may never zoom far enough to see the difference, while their browsers and GPUs still have to process the larger texture.
Foundry specifically warns that extremely large image dimensions can exceed hardware texture limits. Its troubleshooting guidance notes that older systems may run into problems around 8,000 pixels in a dimension, while newer hardware can often handle larger textures.
The real target is therefore not "maximum resolution." It is enough source resolution for your intended viewing scale without wasting resources.
A battle map is optimized when adding more pixels would no longer change what your players can actually see.
What Actually Causes VTT Performance Problems?
Resolution is only one part of the problem. File format, compression, scene complexity, lighting, animated assets, browser memory, GPU capability, and player internet speeds can all matter.
1. Pixel Dimensions
More pixels mean a larger texture for the VTT to render. This becomes especially relevant when you start using enormous regional maps rather than normal encounter maps.
2. Compressed File Size
The number of megabytes determines how much data needs to move from the host or server to each player's device. Two images with identical dimensions can have dramatically different file sizes depending on their format and compression.
3. File Format
Foundry recommends WebP for many image assets because it offers a strong quality-to-size ratio. JPEG can also be efficient for large static backgrounds that do not require transparency. PNG preserves quality extremely well but can produce substantially larger files depending on the artwork.
4. Everything Else in the Scene
Dynamic lighting, walls, tokens, effects, animations, modules, audio, and browser tabs all compete for resources. If one player's laptop struggles with a scene, shrinking the map may help, but the map is not automatically the only culprit.
Which Resolution Should You Use for Roll20, Foundry, and Owlbear Rodeo?
There is no single number that every platform requires, but there are sensible ranges.
| Use Case | Practical Target | Why |
|---|---|---|
| Roll20, performance first | 70 to 100 px/cell | Matches lightweight browser play and Roll20's familiar grid scale. |
| Foundry VTT | 100 to 150 px/cell | Good snapping, detail, and zoom quality on capable hardware. |
| Owlbear Rodeo | 70 to 150 px/cell | Flexible depending on desired grid DPI and image size. |
| Tabletop 4K TV | 4K-class source | Preserves terrain detail across a physically large display. |
These are practical targets, not hard compatibility rules. A 4096×4096 map can be used in Roll20 even if the displayed grid is smaller than the source grid. Likewise, Foundry can use a lower-resolution scene when bandwidth or hardware is more important than close-up detail.
For platform-specific setup, use our Roll20 battle map setup guide or our Foundry VTT import guide.
Why Do DMs Get Battle Map Resolution Wrong?
The most common mistake is comparing DPI labels without checking the actual pixel dimensions.
A map advertised at 300 DPI can still be tiny. A map tagged at 72 DPI can contain thousands of pixels and look excellent on screen. The label by itself tells you almost nothing about VTT quality.
The second mistake is assuming bigger is always safer. It feels logical to download the largest version available because the VTT can always scale it down. The problem is that your players still need to receive and render that source asset.
The third mistake is ignoring grid count. A 4096×4096 image used as a 20×20 map gives you about 205 pixels per square. Use the same file as a 60×60 map and you get only about 68 pixels per square. Same image dimensions, completely different close-up detail.
High-performing VTT preparation starts with the encounter size, determines the grid dimensions, then chooses the pixel resolution needed to support it.
What Should You Check Before Your Session?
You do not need benchmark software. Test the map the way your players will actually use it.
- Load time: Does the scene appear quickly for remote players?
- Zoom quality: Can players zoom to token level without obvious pixelation?
- Grid alignment: Does the VTT grid remain aligned across the entire image?
- Pan performance: Does moving around the scene remain smooth?
- Lighting performance: Does the scene remain responsive after walls and dynamic lighting are enabled?
- Player hardware: Does the least powerful device at the table still handle the encounter?
That final test matters more than chasing a theoretically perfect export setting. The best battle map resolution is the highest useful resolution that your actual group can run smoothly.
Frequently Asked Questions
If 72 DPI means roughly 72 pixels per grid square, it can be enough for normal VTT play, especially when performance and smaller files are priorities. It will look softer than a 100 to 150 pixel-per-square map when players zoom in heavily.
A 150-pixel-per-square source contains substantially more detail, but Roll20 does not require that resolution. A lighter image around 70 to 100 pixels per square may load faster while still looking good for typical browser-based play.
At 100 pixels per square, a 30×30 map is 3000×3000 pixels. At 150 pixels per square, it is 4500×4500. A 4096×4096 map gives you approximately 136.5 pixels per square, which is a strong high-resolution middle ground.
Not if you only change the metadata. A 4096×4096 image remains 4096×4096 pixels whether its embedded resolution field says 72 DPI or 300 DPI. You need additional real pixel data to increase digital detail.
They can be excellent for Foundry because they preserve strong detail during zooming, particularly on medium-sized encounter maps. Extremely large pixel dimensions can still create performance or hardware problems, so 4K is useful without assuming that bigger is always better.
PNG offers excellent image fidelity and broad compatibility, while WebP can often deliver similar visual quality at a smaller file size. Foundry specifically recommends WebP as a strong quality-to-size option for many image assets.
A 4K-class source is strongly preferable when the display itself is 4K, especially on large tabletop screens where players are physically close to the image. Lower-resolution maps can be upscaled by the display, but fine terrain details will not be as sharp.
Black Lantern Forge battle maps are delivered at 4096×4096 pixels with 30×30 tactical layouts, giving you sharp terrain for VTT sessions and tabletop displays without guessing at the source resolution.
Browse 4K Battle Maps →Sources
