Sizing Maps for Fantasy Grounds
- FG Academy
- 7 minutes ago
- 2 min read
Official Image formatting and sizing guidelines.
FANTASY GROUNDS MAP DIMENSIONS: (100 PPI STANDARD)
To ensure your maps align perfectly without "grid drift," use these specific pixel dimensions. These are optimized to be as close to 2K/4K as possible while remaining perfectly divisible by 100.
HORIZONTAL (16:9)
* Near 2K: 2500 x 1400 pixels (25 x 14 Squares)
* Near 4K: 3800 x 2100 pixels (38 x 21 Squares)
VERTICAL (9:16)
* Near 2K: 1400 x 2500 pixels (14 x 25 Squares)
* Near 4K: 2100 x 3800 pixels (21 x 38 Squares)
SQUARE (1:1)
* 2K High Quality: 2000 x 2000 pixels (20 x 20 Squares)
* 4K Ultra Quality: 4000 x 4000 pixels (40 x 40 Squares)
QUICK RULES FOR SUCCESS
The 100 PPI Standard: This is the "sweet spot" for modern Fantasy Grounds Unity. It balances high-zoom detail with manageable file sizes for players.
Legacy/Performance: For massive overland maps, use 50 PPI (Half the pixels, much faster loading).
Cross-Platform: If you need Roll20 compatibility, use 70 or 140 PPI. Note: Use a width of 2520px or 3850px to keep those grids even.
⚠️ CRITICAL WARNING: THE "SOURCE MAP" TRAP...
When sourcing maps for Fantasy Grounds Academy, be extremely cautious with "found" images or low quality or bootlegged scans:
Non-Square Grids: Maps from book scans or PDFs are often stretched during the printing process. A grid that aligns in the top-left will often be several pixels off by the bottom-right.
The Double-Grid Nightmare: Avoid maps with baked-in grids. Digital grids laid over "ghost" grids cause visual distortion and distracting Moire patterns.
Reputable Sources: Always prioritize GRIDLESS maps from reputable digital cartographers. It is always easier to add a perfect 100px grid to a clean map than it is to fix a broken one.
And, finally, for those whom absolutely must use an uneven, stretched or distorted map, you can try and fiddle about with the Map Align application, hosted on the official Fantasy Grounds forums. (No Mac/Linux support)
Link:

.png)



Comments