A standard 30x30 D&D battle map represents a 150-by-150-foot encounter area when each square equals 5 feet. That means a character with 30 feet of Speed can move 6 squares per turn, a character with 40 feet can move 8 squares, and a 30-foot character using Dash can cover up to 12 normal squares. Difficult terrain usually costs twice the normal movement to enter, while standard fifth-edition diagonal movement still costs one square per adjacent square. The image's pixel dimensions do not determine its D&D scale. What matters is that the VTT or physical display treats the map as exactly 30 squares wide and 30 squares tall.
You download a 30x30 dungeon map, drop it into your virtual tabletop, and start placing tokens. The fighter has 30 feet of movement, so they should be able to cross six squares. Instead, the ruler says 42 feet. The wizard's 60-foot spell range reaches farther than expected. A Large monster only occupies one square. Suddenly every tactical distance on the map feels slightly wrong.
The art is not the problem. The scale is. A 30x30 map only behaves correctly for D&D combat when the software, grid, and tokens all agree on what those 30 squares mean. Once you set each square to 5 feet, everything else becomes predictable: movement, spell ranges, creature sizes, difficult terrain, Dash distances, and encounter spacing.
This guide breaks down the exact math and shows how to make a 30x30 map behave correctly whether you are using Roll20, Owlbear Rodeo, another VTT, or a television built into your gaming table.
What does a 30x30 D&D map actually represent?
Under the standard D&D fifth-edition grid rules, one square represents 5 feet. The math for a 30x30 map is therefore straightforward.
30 squares × 5 feet per square = 150 feet across each side of the battlefield.
The total map contains 900 individual grid squares. If you think about the entire rectangular footprint, a 150-by-150-foot area represents 22,500 square feet of battlefield. That does not mean every encounter should use the entire space, but it gives you a useful sense of scale.
A typical 30-foot-speed character can cross 30 percent of the map's width in a single Dash turn if the route is clear. A creature with a 60-foot flying Speed can cover 12 normal squares without Dashing. A 120-foot spell range can span 24 squares, which is most of the map.
That is why a 30x30 layout works so well for many combat encounters. It is large enough for meaningful ranged positioning and movement without creating the enormous empty spaces that can make every melee character spend several rounds simply trying to reach the fight.
How many squares can a D&D character move each turn?
Take the creature's Speed in feet and divide it by 5. The result is the number of standard squares available for movement.
| Speed | Normal Movement | With Dash | Map Width Covered Normally |
|---|---|---|---|
| 25 ft. | 5 squares | 10 squares | 16.7% |
| 30 ft. | 6 squares | 12 squares | 20% |
| 35 ft. | 7 squares | 14 squares | 23.3% |
| 40 ft. | 8 squares | 16 squares | 26.7% |
| 60 ft. | 12 squares | 24 squares | 40% |
The important part is that the map itself does not change when different creatures move at different speeds. The grid remains 5 feet per square. Speed simply determines how many of those squares each creature can enter.
D&D also allows characters to break up their movement. A character with 30 feet of Speed could move two squares, attack, move another three squares, interact with something, and then move their final square if the circumstances allow it.
Does diagonal movement change the scale?
Not under the standard fifth-edition square-grid rules. Moving into an adjacent diagonal square costs the same amount of movement as entering a horizontally or vertically adjacent square.
That means a character with 30 feet of movement can move six diagonal squares just as easily as they can move six squares in a straight horizontal line. This is intentionally simpler than measuring the real geometric distance between the centers of those squares.
For standard 5e grid play, count spaces. Do not turn every diagonal move into a geometry problem.
Some tables prefer alternate diagonal rules where every second diagonal costs additional movement. That can create more realistic distances, but it is not the standard fifth-edition grid method. If your group uses an alternate method, configure your VTT ruler to use the same system or players will constantly get conflicting answers from the grid and measurement tool.
How does difficult terrain work on a 30x30 map?
Difficult terrain does not change the physical size of a square. It changes what that square costs to enter.
A normal adjacent square costs one square of movement. A difficult-terrain square typically costs two squares of movement to enter. In feet, every foot traveled through difficult terrain costs one additional foot of movement.
For a character with 30 feet of Speed, six normal squares use the entire movement allowance. If every square along the route is difficult terrain, that same character can generally cover only three squares before using the same 30-foot movement budget.
A creature with 30 feet of Speed can normally move six 5-foot squares. If the entire route is difficult terrain, those six squares of movement pay for only three difficult-terrain spaces.
This is where map design starts affecting tactics. A 30x30 swamp, ruined city, mountain pass, or collapsed dungeon can feel dramatically larger than an open 30x30 courtyard because the usable movement budget changes even though the map dimensions remain identical.
How large should creature tokens be on a 5-foot grid?
Token scale should follow the creature's combat space, not the visual size of the artwork. A towering character illustration might nearly fill its token image, but a Medium creature still occupies one 5-foot square during normal combat.
| Creature Size | Combat Space | Grid Footprint |
|---|---|---|
| Tiny | 2.5 × 2.5 ft. | Up to four Tiny creatures per square |
| Small / Medium | 5 × 5 ft. | 1 × 1 square |
| Large | 10 × 10 ft. | 2 × 2 squares |
| Huge | 15 × 15 ft. | 3 × 3 squares |
| Gargantuan | 20 × 20 ft. | 4 × 4 squares |
This becomes especially important on 30x30 boss maps. A Huge creature occupies nine squares. A Gargantuan creature occupies sixteen. A dragon, giant construct, or massive monster therefore changes the usable geometry of a room even before you consider reach, difficult terrain, or surrounding enemies.
Do the pixel dimensions of a 30x30 map matter?
Pixel dimensions determine image resolution. They do not determine the rules scale.
A 30x30 battle map could be exported at 2,100 by 2,100 pixels, 3,000 by 3,000 pixels, 4,096 by 4,096 pixels, or another resolution entirely. It can still represent exactly the same 150-by-150-foot encounter.
What matters is that the software understands that the image contains 30 columns and 30 rows.
| Export Resolution | Approx. Pixels Per Cell | D&D Scale |
|---|---|---|
| 2100 × 2100 | 70 px | 5 ft. per square |
| 3000 × 3000 | 100 px | 5 ft. per square |
| 4096 × 4096 | About 136.5 px | 5 ft. per square |
The third example is intentionally awkward. A 4,096-pixel image does not divide evenly into 30 cells. That is completely manageable in modern VTT software. The software can rescale the image to fit exactly 30 grid units. You do not need to redesign the map around a particular pixel count just to preserve D&D movement.
If the map has a baked-in grid, alignment matters more because the VTT grid must land on the artwork's existing lines. Our Roll20 and Owlbear Rodeo grid alignment guide covers that process in detail.
How should you set up a 30x30 map in Roll20?
For standard D&D combat, the important settings are a 30-by-30-square map, a page scale of 5 feet per grid cell, and a D&D-compatible diagonal measurement setting.
Roll20 uses 70 pixels as its baseline grid-cell measurement at default settings. That means a 30x30 page at the baseline works out to 2,100 pixels by 2,100 pixels. Your uploaded map does not have to use that resolution. Roll20 can resize higher-resolution artwork while preserving the same 30-square tactical area.
Recommended Roll20 setup
Canvas: 30 cells wide by 30 cells tall.
Page Scale: 5 feet per cell.
Grid: Square.
Diagonal Measurement: D&D 5E/4E Compatible for standard fifth-edition movement.
Map: Sized so the full playable grid covers exactly 30 by 30 Roll20 cells.
Roll20's D&D-compatible measurement treats a diagonal grid move as one unit, matching the standard fifth-edition square-grid method.
How should you set up a 30x30 map in Owlbear Rodeo?
Owlbear Rodeo is particularly straightforward when you already know the grid dimensions. Enter 30 columns and 30 rows when aligning the map, then set the scene's grid scale to 5 feet.
Owlbear Rodeo's Chessboard measurement option is designed for standard fifth-edition D&D movement. Each adjacent grid cell counts as one square, including diagonals. Two grid cells on a scene with a 5-foot scale therefore measure 10 feet.
Recommended Owlbear Rodeo setup
Map Dimensions: 30 columns by 30 rows.
Grid Size: 5 ft.
Grid Type: Square.
Measurement: Chessboard for standard 5e movement.
Snapping: Enabled when you want tokens centered cleanly within the tactical grid.
You can even include 30x30 in the map filename. Owlbear Rodeo can recognize grid dimensions from filenames during import, making maps with documented dimensions especially easy to set up.
Why do DMs accidentally break the scale of 30x30 maps?
The most common mistake is assuming pixels equal feet. They do not. A 4,096-pixel-wide image does not represent 4,096 feet, and changing its image resolution does not change the fictional dimensions of the encounter.
The second mistake is setting the page to 30x30 but leaving the measurement scale at something other than 5 feet. The grid may look perfect while the ruler reports incorrect ranges.
The third mistake is resizing tokens by eye. A Large monster should occupy a 2x2 footprint regardless of whether its artwork looks better when squeezed into one square.
The fourth mistake is mixing diagonal systems. If the DM counts diagonals as one square but the VTT measures them using Euclidean distance or an alternating diagonal rule, players receive two different answers for the same movement.
The solution is to pick one system and make every part of the table follow it.
How do you test a 30x30 map before the session?
A properly scaled map should survive a few quick tests before you start placing enemies and fog.
| Test | Correct Result |
|---|---|
| Measure one square | 5 feet |
| Measure six squares | 30 feet |
| Move diagonally six spaces | 30 feet under standard 5e grid movement |
| Place a Large token | 2 × 2 squares |
| Measure map edge to edge | 150 feet |
If all five tests pass, your map is scaled correctly for standard fifth-edition combat. From there, you can add difficult terrain, monsters, spell effects, elevation notes, hazards, and whatever else the encounter needs without worrying that the basic geometry is working against you.
If you want encounter-ready maps already built around consistent tactical dimensions, browse our Black Lantern Forge battle map collection.
Frequently Asked Questions
How big is a 30x30 D&D battle map in feet?
A standard 30x30 D&D battle map represents an area 150 feet wide by 150 feet tall. Each of the 30 squares represents 5 feet, so 30 multiplied by 5 equals 150 feet.
How many squares can a character with 30 feet of movement move?
A character with 30 feet of Speed can normally move six 5-foot squares. Taking the Dash action gives that character additional movement equal to their Speed, allowing up to 12 normal squares if no other effects reduce the available movement.
Does moving diagonally cost more movement in D&D 5e?
Not under the standard fifth-edition square-grid rules. Entering a diagonally adjacent square normally costs one square of movement, just like moving horizontally or vertically. Some groups use alternate diagonal measurement systems, but those should be configured consistently across the table and VTT.
What resolution should a 30x30 battle map be?
There is no single required resolution. A 30x30 map can be 2,100 pixels, 3,000 pixels, 4,096 pixels, or another size depending on the desired image quality. The VTT needs to treat the playable area as 30 by 30 cells regardless of the image's pixel dimensions.
What size should a Large creature be on a 30x30 map?
A Large creature normally controls a 10-by-10-foot space, which equals a 2x2-square footprint on a standard 5-foot grid. Huge creatures use 3x3 squares, while Gargantuan creatures use 4x4 squares under the current creature-space table.
What scale should I use for a 30x30 map in Roll20?
For standard D&D combat, use a 30-by-30-cell page with each cell representing 5 feet. Roll20's default 70-pixel grid size can remain in place because the uploaded artwork can be resized to fit the 30x30 grid.
What settings should I use for a 30x30 map in Owlbear Rodeo?
Set the map to 30 columns by 30 rows, use a grid size of 5 feet, and select Chessboard measurement for standard fifth-edition diagonal movement. If the file name includes "30x30," Owlbear Rodeo can also use that information when importing and aligning the map.
Browse encounter-ready battle maps designed for clean VTT setup, physical miniatures, and the kind of fights where every five feet matters.
Browse Battle Map Packs →Sources
| D&D Beyond | 2024 Basic Rules: Playing the Game |
| D&D Beyond | 2014 Basic Rules: Combat |
| Roll20 | Page Settings |
| Roll20 | Measure Tool |
| Owlbear Rodeo | Aligning a Map |
| Owlbear Rodeo | Measure |
