AI Battlemap Generator for Foundry VTT

Finish this map: walls, doors and lights from the picture

A generated map is a picture. One click makes it a room.

• Under every map Familiar generates sits a Finish this map button. It is opt-in per map and never runs on its own.
• Press it and the AI reads the rendered image, then places walls, doors, windows and lights with the same tools you would use by hand.
• It checks its own work: darkness up, a screenshot, a look at where the light stops, and the walls the light gives away are corrected before the map comes back.
• Windows are real windows, light passes and sight does not. Doors are real Foundry doors: open one and the light follows.

Strongest on interiors with straight walls, a tavern, a barracks, a dungeon of rooms and corridors. Still experimental on organic caves, where a tunnel bend can land a wall a few dozen pixels off.

From a sentence to a playable scene

Type what the encounter needs and where it is. The result is a Foundry scene, not a download.

• Size in table words: small for a tavern brawl, medium for a typical fight, large for a battlefield, screen for a map that fits one monitor, huge for a whole harbour quarter. Or give the squares yourself.
• Ask for four candidates and pick the one you like; only the chosen map is applied.
• The scene dimensions come from the grid you asked for, and on providers that accept exact sizes the image is requested at exactly that shape, so the art lines up with the squares your tokens move on. Diffusion models cannot count squares, so none is asked to draw a grid; Foundry overlays its own.
• When a provider can only return a shape that does not fit, Familiar applies it anyway and tells you the stretch percentage instead of hiding it.
• Create scene turns any image into a scene: under a generated illustration or on an Art Library card, it prefills a name and a best-guess grid you can overtype, warns live when the squares would stretch the picture, and can activate the scene and pull the players in one go.

Tokens and portraits from the sheet

Maps are half the prep. The same chat draws the people who stand on them.

• Ask for a token and the art comes back with a transparent background, goes onto the actor, and drops into Foundry's dynamic token ring. Tokens already on the map that carried the old art follow the new one.
• Ask for a portrait and it lands on the sheet, for a player character or the NPC they are three minutes from meeting.
• Nothing to type: on an actor sheet, the Familiar entry in the header menu opens the chat with the ask already written.

Not every provider can return a transparent background. Familiar checks yours can before it bills anything, and when a token comes back opaque it says so in the result instead of applying it silently.

Icons for items, spells and features

Ask for item art and the icon appears on the item: loot sitting in the world, a spell, or a class feature on a sheet.

• The item sheet has the same Familiar entry in its header menu as the actor sheet, so a bare inventory gets icons one line at a time without leaving Foundry.
• The icon lands on the item sheet and in the chat, with its cost printed under it.

Change art you already have

Every stored image Familiar made carries an Edit button, and anything else you can name in the chat. Say what should change.

• Take the ruins map and ask for it at night. Put the same NPC in plate armour for the second act.
• Optional: click two corners on the thumbnail to point at the part that should change.
• Edits come back one at a time and land beside the original, never over it; the Art Library files each as an edit with a link back to its source, and a Try again button gives you another take. The multi-candidate picker is for fresh maps.
• Hand back a character image on a later call and the same face comes back with it, which is how a recurring NPC stays recognisable across sessions.
• The reference can be anything Foundry already stores: an earlier generation, an actor portrait, an item icon, a scene background. Up to eight of them in a single ask.

The region is a hint, not a mask. The whole image is regenerated from your instruction, so nearby details can still move. Editing belongs to the provider, so it follows the one you brought. fal.ai and OpenAI's GPT Image models both do it. On OpenRouter it depends on the model you pick, and Familiar checks before it spends anything. Leonardo and NanoGPT cannot edit, and say so. On the same provider an edit costs more than a fresh image, so it is the wrong tool for a map you could simply ask for again.

Everything you generate has a home

Nothing you generate is lost in a folder.

• Every image is filed as a page in a Familiar Art journal for its kind: Battle Maps, Scene Backgrounds, Portraits and Tokens, Items, Other Art. The page carries the prompt that made it, the provider, and what it cost.
• The Art Library window, opened from the journal sidebar or the token controls, shows the same art as a gallery: tabs per kind, a search box that matches your prompt text and not only the name, and thumbnails that load as you scroll.
• Under each card sit the actions the art supports: share it to the table, send a prop to the canvas as a tile, turn a map into a scene, edit it, or remove it from the library.
• Cards drag onto the canvas. A portrait or token drops as that actor's token, exactly as dragging the actor from the sidebar would. A prop, item or handout drops as a tile centred where you let go, snapped to the grid unless you hold Shift. Battle Maps do not drag; a map wants to be a scene, so its card offers Create scene instead.
• Players cannot see the library until you share something from it.

Show the table

You see every result first. Nothing reaches the players until you click.

• A Share button under each generated image posts it to the Foundry chat, where your connected players see it immediately.
• For handouts that should outlive the chat log, the same image can go straight into a journal as an image page.