
The improvised session
The party ignored the plot hook and went to the abandoned mill instead. A dnd map of the mill in two minutes is the difference between running the scene and hand-waving it.
One sentence · Top-down · Grid you can move minis on
Session starts in forty minutes and the party has gone somewhere you did not prep. Describe the place in a sentence and get a top-down battle map with rooms, corridors and a grid you can count squares on.
Both generated on this page's engine, from a sentence each. They are shown side by side rather than as a before and after because a dnd map has no before — the point is the range between an underground crawl and a settlement. Every output is AI-generated, so yours will differ.

Asked for a flooded ritual chamber with side rooms off it. What came back has the things that make a room playable rather than decorative: the water reads as a distinct surface you can rule on, the rubble gives cover positions, the braziers explain the light level without anyone writing it down, and the spiral stair in the corner is a second exit. Count the squares across the flooded chamber and you can price a dash across it before the session starts.
Put them in the flooded chamber
The harder of the two, because a settlement map has to show inside and outside at once. The roof is cut away over the common room so the bar, hearth, tables and stair are all placeable, while the stable, well and cart outside stay roofed. That cut is what makes a tavern brawl runnable — the party can go through the window, and everyone can see where the window is.
Give them a tavern to wreckThe bar is not beauty. It is whether four players can agree where everyone is standing without arguing about it.
Search for dungeon art and you get a thousand gorgeous images shot from a heroic low angle, none of which you can play on. A battle map is a different object with a different job: it is a shared coordinate system that happens to be pretty. So the constraints this dnd map generator works under are unusually specific — the camera sits directly overhead and never tilts, walls read as walls at a glance, and a corridor is visually distinct from a room.
Two honest limits: what comes back is a flat image, not a virtual tabletop module, and there is no separate wall layer, no dynamic lighting and no fog-of-war data. Everything a dnd map has to do for a table — show cover, show distance, show where a door is — has to survive being looked at from four feet away across a coffee table, which is a harsher test than any piece of dungeon art ever faces.
Creative engine
Describe the location, choose a shape, and check the corridors before you commit to it.

A flooded ritual chamber produces a better map than a big room, because function implies furniture, wear, and where the entrances would sensibly be. Purpose is the single most productive word in the prompt.

Two doors and a stair means the party can be flanked. Say how many ways in and out you want and the plan holds together around them; leave it unsaid and you get a beautiful room with one door and no tactics in it.
A prompt for a battle map is a spec, not a mood board. These are the four things worth spelling out.
"A smugglers' cellar under a fishmonger" beats "a cellar". Function fills the room with the right clutter — crates, a winch, a hatch — and clutter is what gives players something to hide behind.

Three chambers off a central hall behaves very differently from three chambers in a line. Connection topology is the encounter design; state it rather than letting the model decide it for you.

Say you want a faint square grid across the whole map. Without it you get an illustration, and aligning a virtual tabletop grid to art that was not drawn for one is where most of the evening disappears.

Open the result full size and look at the narrow parts. If a passage is one square wide where you wanted two, that is a five-second reroll now and an argument mid-combat later.

Four situations, and all of them are about time rather than art.

The party ignored the plot hook and went to the abandoned mill instead. A dnd map of the mill in two minutes is the difference between running the scene and hand-waving it.

Published adventures ship with maps; the world you invented does not. Every location you write is a map you have to make, and that is the recurring cost that quietly stops people homebrewing.

A remote game has no theatre of the mind fallback that works for combat — everyone needs the same picture. Drop the image in as a scene background and align the grid once.

A map the party finds in-world is a different object from the one you run combat on — smudged, partial, drawn by a character. Ask for that look and it becomes prop rather than tool, the same way a stylised portrait turns a photo into an artefact.
What DMs check before dropping a generated map on the table.
The grid is drawn as an even square overlay, and the art underneath is composed to sit sensibly against it, but nothing is measured to a standard the way a hand-built virtual tabletop scene is. Treat the squares as the scale — a door is one square, a corridor one or two — and align your VTT grid to the image once when you import it.
Outputs are yours to use, including commercially. The caveat is a practical one rather than a licensing one: a map with generated art in a published product invites the same questions any AI asset does, so decide that on your own terms before you build a Kickstarter around one.
Because generated lettering is unreliable, and a room labelled with a misspelled word is worse than a room with no label. Every dnd map here is drawn deliberately without text so you can add your own numbers in whatever tool you prep in.
Not closely. Each run invents a plan from your description, so two runs of the same sentence give you two different buildings. If continuity matters, describe the layout you already established — room count, shape, where the stair is — and expect to reroll until it lines up.
Yes, just leave the grid out of your description. A gridless top-down map is the right choice for a hex-crawl overview or a handout, and for anything you plan to use in a VTT that draws its own grid on top.
Both work, and the tavern above is the mixed case — an interior cut away inside an exterior yard. Forests, roads, riverbanks and camps all render fine from directly overhead; the thing to watch is that large outdoor spaces need landmarks, or the map becomes an undifferentiated green field nobody can navigate.
Credits are shared across everything Kavel runs. You see the cost before each run, and a failed job is never charged.
What's included
Secure checkout by Stripe. Card details never touch our servers.
What's included
Secure checkout by Stripe. Card details never touch our servers.
What's included
Secure checkout by Stripe. Card details never touch our servers.
What's included
Secure checkout by Stripe. Card details never touch our servers.
Charges appear as “KAVEL AI” on your card statement. You can cancel any time from Settings → Billing; cancellation takes effect at the end of the period you already paid for. Operator details, the full model list, and the refund window are on the about page.
Describe the place, check the corridors are the width you meant, and take it to the table — or design what lives in it first.