Every dungeon master hits the same wall: the party is one room away from a big encounter, and you have no map that fits the scene. You could draw one, but that's an hour of graph paper and ruler work. You could buy a map pack, but then you're adapting your story to someone else's art. Or you can type a description into an AI image generator and get a usable map in under a minute. Tabletop maps are one of the best uses of AI image tools around, mostly because players only need the map to be clear, not museum-quality. Here's how to generate dungeon and battle maps that actually work at the table.
Decide what the map has to do first
A map for a one-shot dungeon and a map for a sandbox region serve completely different jobs, and the prompt should change with the job. Battle maps are small, one-screen scenes: a ruined temple chamber, a bridge over a ravine, a tavern's back room. They need to read fast so players can plan a fight in seconds. Region maps are bigger, looser things — a wilderness hex crawl, a city district, an island chain — where the art can be more decorative because nobody is counting squares. Decide which kind you're making before you write anything. Most generators are better at battle maps, by the way, because a contained scene is easier to describe than a whole landscape.
A prompt skeleton that reads like a map
Generic prompts like "fantasy dungeon" give you pretty but useless results — no clear rooms, no obvious entrances, weird corridors that don't connect. What works is describing the map like a floor plan with style attached. A reliable skeleton: "top-down battle map of a [location], [size] grid, [terrain features], [materials], [lighting], [style], hand-drawn fantasy map texture." A filled-in example: "top-down battle map of a flooded crypt, 15 by 15 grid, stone floor with standing water, broken columns, moss on the walls, torchlight from the corners, detailed fantasy map style." Say "top-down" or "overhead view" explicitly — generators love producing dramatic angled views that are useless for tokens. And mention the grid by name; "with grid lines" usually gets you something close enough to play on, though you may want to add your own grid over it anyway.
Keep the grid readable
Here's the thing nobody warns you about: a gorgeous map with unreadable grid lines is a liability at the table. If the room boundaries blur into the floor texture, your players will argue about line of sight and movement for five minutes before every encounter. A few habits fix this. First, ask for "clear room boundaries" or "distinct wall outlines" in the prompt — that phrase does more than any style keyword. Second, generate at high resolution so the walls stay crisp when you zoom in. Third, if the generator's grid is inconsistent, don't fight it: generate the map without a grid and lay your own grid down in any image editor, or print it and draw the grid with a ruler. A clean overlay beats a baked-in grid that's slightly wrong every time.
Tileable maps and the reroll habit
If you run games with a virtual tabletop, you'll quickly want tileable map sections — corridors, rooms, and intersections that repeat seamlessly so you can build a dungeon on the fly. Some generators can do seamless tiles if you ask, but even without that, you can fake it: generate a corridor, crop it to a clean section, and reuse it. The reroll habit matters more than any single prompt. The first result is almost never the keeper. Generate four or five variations, pick the one where the entrances line up and the scale looks right, and only then start polishing. Map-making is the one AI art task where consistency beats beauty — a plain map your players can read beats a stunning one they have to squint at.
Scale and doors: the details players notice
Two details separate a playable map from a pretty one. Scale first: if a five-foot square in your map is the size of a coin on screen, the whole scene feels off. State a grid size in the prompt ("15 by 15 grid" or "20 by 20") and check the result at the size you'll actually display it. Doors second: players will ask about every single doorway, so make them visible. Ask for "open doorways" or "door openings on the walls" rather than leaving the generator to guess. If the tool gives you a map with no clear way in or out, that's the fastest way to know the map failed its only job — a dungeon you can't enter is just a picture.
Remix one map into a full session
The real trick of AI maps is that one good result becomes many. Take the flooded crypt you liked and rerun the prompt with small changes — "larger main chamber," "add an altar at the north end," "dried bones scattered in the corridor" — and you have a whole dungeon in ten minutes instead of an evening. Keep the same style and lighting keywords in every variation so the set looks like it belongs together; players notice when room one looks like a watercolor and room three looks like a 1980s module scan. Build the variations around your session plan: the entrance room first, then the encounter room with the most open space, then the boss room with the least. That order means the maps get more dramatic exactly when the stakes do.
You don't need to be an artist to run a good-looking table anymore. A few prompt habits — top-down view, clear walls, a stated grid, consistent style across variations — turn an AI image generator into the fastest map-making tool in your kit. Next session, when the party opens a door you didn't plan for, you'll have a map for it before the dice stop rolling.