How to Measure Distance and Areas on a Virtual Tabletop Battle Map

Check whether the scene uses a square grid, hex grid, or no grid, and confirm what one space represents in your game. In Foundry, the scene settings distinguish these grid types and let a GM set the grid size; if a map already has grid lines in its image, those lines need to align with the virtual grid. If alignment is off, a ruler may display a precise number that is wrong for the map. Foundry VTT: Scenes

Use a known map feature or a stated map scale to check the setup. For an image with an existing square grid but no scale, Foundry suggests estimating the pixel size of a space by dividing the image’s pixel dimensions by the number of spaces across and down. In play, compare the virtual grid to a visible map square at high zoom; if its lines drift, pause and ask the GM to fix alignment before relying on range or templates.

Select the distance ruler, place its start point, and drag to the destination. In Foundry V13, the distance ruler can be activated with the R key by default or the Measure Distance control; key bindings may be changed. Waypoints let you measure a route with bends or account for elevation changes. Foundry VTT: Measurement and Templates

For a quick check, measure from the relevant point on one token’s space to the relevant point on the other, then compare the displayed distance with the ability’s range. Token size and the game’s range rule matter: the ruler’s endpoint-to-endpoint number can differ from a rule that counts occupied grid spaces. On the D&D 5.2 square grid, each square is 5 feet; for range between creatures or objects, the SRD says to count from a square adjacent to one and stop in the other’s space, following the shortest route. D&D 5.2 System Reference Document

A route’s geometric distance and the movement it consumes are related, but they are not always identical. In Foundry, the distance ruler reports distance; token-drag measurement reports movement cost. The software documentation specifically notes that difficult terrain and scene behaviors that modify movement cost can make the two totals differ. Foundry VTT: Measurement and Templates

To check a planned move, drag the token along the intended path and add waypoints around corners or terrain changes. Compare the movement-cost display with the character’s remaining speed and the game’s terrain rules. In D&D 5.2, entering an adjacent square normally costs one square of movement, difficult terrain costs two, and diagonal movement cannot pass through the corner of a wall or similar feature. Don’t assume that a simple ruler line accounts for these rules. D&D 5.2 System Reference Document

For an area effect, use a template with the effect’s listed shape and size. Foundry’s measured templates include common area shapes and are intended to show which spaces a shape covers; the template can be repositioned or adjusted after placement. Foundry VTT: Measurement and Templates

Before placing it, read the effect description for both size and point of origin. A radius is measured outward from its origin; a cone extends in a chosen direction and widens as it extends. Under the D&D 5.2 SRD, the origin’s inclusion varies by shape: for example, a sphere includes its point of origin, while a cone’s origin is excluded unless its creator decides otherwise. The rules also say that total cover can block parts of an area effect. The template displays geometry, but it cannot settle every game-specific targeting or cover question by itself. D&D 5.2 System Reference Document

Zoom in enough to see where the template edge falls relative to grid lines and token spaces. Check each potentially affected creature against the rules for that effect and your system’s method for handling partial squares. Don’t quietly substitute the platform’s drawn boundary for a table rule about whether a space is included.

Then inspect walls and other obstructions. The D&D 5.2 SRD excludes a location from an area effect if every straight line from the origin to that location is blocked by total cover. That means a circular or cone-shaped overlay is not necessarily the final affected area behind a solid wall. Confirm uncertain edge cases with the GM before resolving the effect. D&D 5.2 System Reference Document

When a result seems surprising, run this short sequence:

1. Confirm the scene’s grid type and scale. 2. Identify whether you need distance, movement cost, or an area shape. 3. Place the ruler or template at the rules-defined origin. 4. Account for route bends, difficult terrain, token spaces, and elevation where relevant. 5. Check walls, corners, and borderline spaces against the game’s rules. 6. State the result in game units and resolve any ambiguity consistently with the GM.

This sequence helps diagnose common errors: a misaligned grid, measuring a straight path when movement follows a bend, using distance where movement cost is needed, or assuming that a template alone determines targeting. For systems with different grid conventions—or gridless maps—use that system’s rules and the scene’s configured scale rather than importing the D&D square-grid example.

Use a distance ruler to ask how far apart two points are, a token drag ruler to check what a route costs, and a measured template to visualize an effect’s shape. Then apply the game’s rules for movement, range, cover, and affected spaces. Keeping those steps distinct makes a virtual map easier to read and makes contested measurements easier to explain at the table.

• Foundry Virtual Tabletop, “Measurement and Templates”: https://foundryvtt.com/article/measurement/
• Foundry Virtual Tabletop, “Scenes”: https://foundryvtt.com/article/scenes/
• D&D 5.2 System Reference Document 5.2.1: https://media.dndbeyond.com/compendium-images/srd/5.2/SRD_CC_v5.2.1.pdf