An AI asset generator inside the Godot editor
Godot is the open-source engine a large share of indie and jam teams ship 2D games with. Its scene system turns art into nodes in a few clicks, which means the slow part of a 2D project is rarely the engine: it is the art. Sprites, animation frames, tiles, buttons and panels all have to exist before a level feels like anything. Layer generates them, and the Layer AI plugin puts that generation inside the Godot editor, working on the scene you already have open.
The plugin is a dock in the editor. It holds your account, your workspace and the Layer session your project is bound to, the tools Layer offers for images, and the files the session holds. Everything it makes arrives as the node Godot expects: an image as a Sprite2D, a sprite sheet as an AnimatedSprite2D, a 9-slice element as a NinePatchRect, tiles as a TileSet painted into a TileMapLayer. Nothing is downloaded, sliced and imported by hand.
Every clip and screenshot on this page is the plugin at work in Generic Fantasy RPG, an internal pixel-art Godot 4.7 project of ours, with real Layer generations. For indie game developers working solo or in small teams, that is the point: production-ready 2D assets without leaving the project you are building.
AI sprite generator: images placed as Sprite2D
Image to Sprite2D generates an image from a description and places it as a Sprite2D at the center of the 2D view with one click. Placing is one undo step, so trying an asset in the scene costs nothing.
The model picker lists every model that can run the tool, with its price and Layer's recommendation first, and remembers your pick per workspace on this machine, never in the project. Every run is priced before it is sent.

Edit sprites in place: remove backgrounds, upscale, pixelate
The dock's image tools work on what is already in the project. Select an image in the FileSystem dock, or a node that shows one, and pick an edit: prompt edit, upscale, remove background, reframe, relight, restyle, pixelate, inpaint with a mask and more. The original is never touched. The result is saved beside it as a new version of the original's name, and an edit of a node is placed over it as a copy showing the result, with the original hidden, in one undo step.
That makes background removal and quick variations part of the scene work. Generate a prop on a plain background, remove the background on the placed node, and the cutout takes its place at the same size.

Sprite sheets, tilesets and 9-slice UI as Godot nodes
Sprite sheets to AnimatedSprite2D
Sprite sheet generates the frames of an animation in a grid. Give the grid its columns and rows in the dock and the plugin builds a SpriteFrames beside the image; Place adds an AnimatedSprite2D playing it. A sheet the agent or the web app made with its frames and animations arrives ready to place. For more on making them, see sprite generation.
9-slice UI as NinePatchRect
9-slice UI element generates a button, frame or panel that stretches. Layer finds its insets, the plugin builds a StyleBoxTexture from them, and Place adds a NinePatchRect with them as its patch margins, so a dialogue box or an inventory panel stretches to any size without smearing its corners. For whole menus and HUDs, see game UI kits.
AI tilesets for TileMapLayer
Game tiles made in Layer, by the agent or the web app, arrive with their grid. Each grid gets one TileSet, and Place paints a tile into the cell under the view center: into the selected TileMapLayer when it uses that grid, or into a new one with Y Sort on. For isometric and hex sets that snap together, see game tilesets.
Pixel art for 2D games
The village on this page is pixel art, and every asset in it was generated to match. Describe the style in the prompt and pick a model that draws it, or run Pixelate on any image in the project to turn it into pixel art beside the original. For palettes, eras and sprite-scale guidance, see pixel art.
Generated files in your Godot project and Git repository
Everything the plugin makes is filed under a Layer session, the same sessions you see at layer.ai, so work started in Godot can be reviewed in the browser and the other way round. The dock lists every file in the session, from Godot, the web app or a teammate, with a preview; previews stay in memory, and nothing lands in the project until you Download or Place it.

Files land in res://layer/ under the session, with a sidecar beside each image that records its metadata and never its prompt, and the TileSets, StyleBoxTextures and SpriteFrames built from them. Which session the project uses is a small file you commit, so a teammate who pulls works in the same one. Logins stay in Godot's per-user data folder, never in the project, and the plugin's JSON files are left out of exported games.
For studios that also build in Unity or Unreal Engine, or model in Blender, one Layer workspace, one catalog of models and one pool of Creative Units cover all of them. For batch pipelines, the Layer API runs the same generations headless.







