Skip to content

AI sprite generator, and the part it leaves you holding

By Eduardo Orellana · Updated

Most sprite generators hand you a PNG and wish you luck. Flockbay has a library of 55,073 sprites, and its AI places them in the scene you describe and writes the game around them. You can move, swap or resize any sprite yourself in the Godot editor. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building. It runs on Windows, macOS and Linux, on the official Godot engine.

AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.

Intel or AMD Chromebook, with Linux turned on.

Download for macOSDownload for WindowsDownload for Linux

The problem is not making one sprite

Generating a single good sprite is close to a solved problem. There are plenty of sites that will do it, and some of them are excellent at it. If that is all you need, use one of those; there is no reason to install a game engine to get one image.

The problem starts at sprite number two. You need it to match the first: same palette, same weight of outline, same light direction, same apparent scale. Then you need the walk cycle to match the idle, and the enemy to look like it lives in the same world as the player.

Consistency is what actually decides whether a game looks made or assembled, and it is the thing that a series of one-off generations in a browser tab tends not to produce.

Most of the sprites you need already exist

The library holds 60,648 objects, and 55,073 of them are sprites. You search it by name and see a picture of each result, which is the only kind of search that works for art. That is the honest first answer to where the sprites come from, and it beats generating them for a reason nobody enjoys admitting: a library drawn as a library already matches itself.

Flockbay places them from the brief you approved, each at an exact position, rotation and scale, and Godot's 2D view does the same when you want to move one yourself. Set a sprite's offset so its origin is at the feet, turn on Y-sort, and a lamp post stands on the ground instead of floating by however much transparent margin the file carries, and the thing lower down the screen draws in front. Those two settings are the difference between placing art and arguing with it.

You can bring your own too. It is a normal Godot project, so anything Godot imports works, and drawing your own is still the route that produces a game only you could have made.

More on this: Steam image sizes: every capsule, library and event asset, with templates

What generation does here, and what it will not do

Flockbay generates a single flat picture on request, and it arrives inside the project, next to the assets you already have, in a scene you can look at it in. You see the mismatch straight away rather than three exports later.

It will not generate an animated one. No frames, no sprite sheet, no walk cycle for a character you invented. If your protagonist has to move through drawn poses, those frames come from you, from an artist, or from a library, and Godot's own animation tools in the editor put them in motion. This is a real gap rather than something we are being careful about the wording of, and it is better read here than discovered on the day you need it.

Pixel art is a style with strong conventions and an audience that reads them closely. The tile grid suits it, which is an observation and not a recommendation — your style is yours. Whether a generated picture passes as pixel art rather than as a picture of pixel art is a call you are qualified to make, and we would rather say that plainly than promise a finished sprite sheet.

More on this: Card game maker: the rules engine is the hard part

The errand does not end at the image

In a standalone generator, getting the picture is the short half. Then you import it, set it up, hook it to a controller and write the code that makes it do something. That tail is longer than the generation and no generator advertises it.

Here a sprite lands in a game. A new project starts blank, and its first build is the one in the brief you approved. Ground is painted rather than assembled: Flockbay lays the cells in a TileMapLayer, and its TileSet's terrains give the edges and the collision, so a sprite it places has something to stand on. Godot's TileMap panel lets you paint cells in or out yourself.

The behaviour is a sentence. Flockbay writes the GDScript into your project: what the enemy does when it loses sight of you, what the pickup does, what happens to the save when somebody quits mid-level. You play it and say what is wrong, which is the normal loop rather than a sign of failure.

More on this: Where assets come from in Flockbay

The app around it

Flockbay is a desktop application for Windows, macOS and Linux. You download and install it, and Godot ships inside it so your game runs locally on your machine.

Building needs an internet connection, since Flockbay and generation come over the network. Playing the game you built does not.

The download is free, and so is the app, with your own art or the library's. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building. Flockbay builds from a library of ready-made objects, or with Godot's own shapes.

More on this: A visual novel is a 2D game with the walking taken out

A workable order of operations

Settle the main character first and treat it as the reference for everything else. Every later asset gets compared to it: same light direction, same palette, same level of detail. Deciding that once, at the start, saves you from a library of pieces that individually look fine and collectively look like a pile.

Then get it moving in the game before you add anything more. An asset that looks good in isolation and reads badly at actual size, in motion, against your background is a very common outcome, and you want to discover it on asset one rather than asset thirty.

After that the rest is production and it goes quickly, because searching a library that already matches itself is faster than asking twice for consistency and comparing the answers.

Questions

Can I use it just as a sprite generator?
Not really, and we would rather say so. It is a game maker with 55,073 sprites in its library. If you only want images and no game, a dedicated web tool is the lighter choice.
Where do the sprites come from, then?
The library, which is 55,073 sprites out of 60,648 objects and searchable by name with a picture of each; the web; your own hand; or a single flat picture generated on request.
Does it generate animation frames?
No. A single flat picture can be generated; an animated character cannot. Sprite sheets and frame animation are art you bring, and Godot's own animation tools are in the editor.
Can I edit what it generates?
Yes. The output lands in a normal Godot project, so you can take it into any editor you like and bring it back.
Does it work offline?
No. Flockbay and generation come over the network, so building requires a connection. The finished game runs locally without one.
What does it cost?
Free to download, and working with your own art costs nothing. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building. Flockbay builds from a library of ready-made objects, or with Godot's own shapes.

Free for Windows, macOS and Linux. 55,073 sprites, and an AI that builds the game around them.

Download Flockbay free