Dungeons And Dragons Map Tiles

The Real Problem With Digital Map Tiles

Most people treat map tiles like they're just pretty pictures you drag around. That's not how they work, and if you treat them that way you'll waste a lot of time fighting your VTT later. A tile is a rectangular coordinate block. That's it. Everything else is your workflow around those blocks. I've been running games with digital grids since the early 2000s. Started with printed squares on acetate, moved to virtual tabletops, then to my own custom tile sets. The medium changed. The problems didn't.

Understanding Dungeons And Dragons Map Tiles

Dungeons And Dragons Map Tiles are individual rectangular grid sections that snap together to form larger battle maps. Each tile is typically 1 by 1 foot, or whatever your tabletop scale uses. On a virtual tabletop they render as an image within a coordinate grid, and that's where most people run into trouble. Here's what people miss: the snap grid on your VTT doesn't automatically know where the tile boundaries are unless your tile has the right metadata or your layer is configured correctly. I learned this the hard way during a campaign when a player's spell effect snapped to the wrong tile because two adjacent maps weren't aligned on the same coordinate origin. The whole fight was already resolved before I realized something was off. We had to redo that encounter.

How To Actually Build A Working Tile Set

Start with your source resolution. Most people download or generate tiles at 512 by 512 pixels. That's fine for desktop use but looks terrible on a tablet or phone. I switched to 1024 by 1024 and haven't looked back. The file size doubles, but you can always downscale. You can't upscale a blurry mess. Every tile needs a border or seam that matches its neighbors. This sounds obvious but most free tile packs ignore it. If your stone floor tile has a dark grout line on the right edge and the next tile also has a dark grout line on the left edge, you'll get a thick double-width seam that breaks immersion and confuses distance counting. Always check the edge alignment before downloading a pack. Look at adjacent tiles at full zoom. If it looks wrong, skip that pack. Name your files consistently. "dungeon_01_floors," "dungeon_02_walls," "tavern_interior." Don't name anything "untitled_final_v3." You will spend hours looking for the one tile you need three sessions from now.

Setting Up Your Virtual Tabletop

On Roll20, use the Tile Layer. Not the VFX layer, not the Art layer. The Tile Layer. It supports true snap-to-grid behavior and can block vision the way a wall should. Put your terrain on the Background Layer and your walls and obstacles on the Tile Layer. This separation matters when you're using the Fog of War. On Foundry VTT, you're working with Scenes. Each scene is a collection of tiles. Your tile size setting in the scene must match your actual tile dimensions. If you set it to 70 pixels per unit but your tiles are 100 pixels wide, everything will be misaligned and your walls won't line up. I've seen this happen more than once when someone imports a community tile set without checking the configuration. For vision and lighting, make sure your wall tiles have the proper Wall Layer data. Some people draw walls as plain images and then try to add walls manually. That works for a single room. It does not work for a dungeon with fifty rooms and dynamic light sources. Learn the wall creation tool for your VTT. It takes an afternoon to learn and saves you weeks of grief.

Creating Your Own Tiles

You don't need to be an artist. You need to be systematic. I use a simple workflow in Aseprite or Photoshop: Create a new canvas at your chosen resolution. Fill it with a base color. Add your texture at low opacity. The key is keeping the texture edges soft so they blend into the next tile. Hard edges repeat visibly. I use a noise overlay at 5 to 10 percent opacity across every tile. It breaks up the repetition without looking artificial. For modular dungeons, create a base set of twelve to sixteen tiles that cover your most common room types. Corridor intersections, straight corridors, room corners, doorways, stairs. Once you have that base, any layout becomes a rearrangement problem instead of a creation problem. My current campaign uses about forty unique tiles arranged into sixty-plus rooms. I built the whole thing from those base twelve plus a few variations.

If you want professional quality without drawing everything yourself, the Unity Asset Store and the Unreal Marketplace both have dungeon tile sets. But read the license. Some are single-game use only. Some require attribution. I learned that after accidentally using a pack in a published module and getting a takedown notice. That was a Tuesday.

Common Pitfalls And How To Avoid Them

Tiling repetition is the biggest visual problem. Humans are surprisingly good at spotting repeating patterns. If your corridor tile appears three times in a row without variation, players will notice. Rotate your tiles. Flip them horizontally and vertically. Even a 2 by 2 checkerboard pattern of rotated variants makes a space feel significantly more natural. Scale drift is another one. When you add new tiles to an existing dungeon, make sure the wall thickness, door width, and floor texture scale match the originals. I once merged two tile sets from different artists and spent two sessions playing with misaligned doors because one set used 70-pixel walls and the other used 80-pixel walls. The difference was subtle until you tried to walk a character through a doorway. Performance matters more than people think. A single scene with hundreds of high-resolution tiles on the Tile Layer will slow down your VTT, especially on shared hosts or lower-end machines. I keep my tile counts per scene under three hundred. If a map needs more, I split it into connected scenes with transition zones. The loading delay is worth it for smooth combat rounds.

Where To Get Tiles

Free options exist. Kenzer and Company used to have a solid free tile set. DMs Guild has a free section that's worth browsing. The Roll20 Wiki community maintains a tile set database. For paid options, Mythic Cartography and Procore are reliable. Each tile costs more but the quality consistency is noticeable. My personal recommendation is to mix sources. Use a paid pack for your core interior tiles because those are seen most often. Use free outdoor tiles for wilderness encounters. You'll rarely notice the difference when players are looking at a forest for three rounds, but you'll notice it when they're staring at a tavern interior for forty-five minutes of combat.

One Technique That Changes Everything

Use a heightmap. Most people treat their tiles as flat images. Adding a simple grayscale heightmap lets your VTT compute visibility and lighting properly. Dark areas become walls. Light areas become open floor. It turns your tiles from decorative backgrounds into functional game pieces. Foundry handles this well with its layered wall system. Roll20 requires the Token Modification or Vision Master macros to approximate it. It adds maybe twenty minutes of work per tile set. It saves hours of manual wall placement. I stopped building tiles without heightmaps about two years ago. There's no going back once your players see dynamic light blocking work correctly.