Web game maker: why this one is a download instead

By Eduardo Orellana · Updated

Two different things get called a web game maker: one that runs in your browser, and one that makes games for browsers. Flockbay is neither. It is a download, and the reason is what happens to a game once the browser is out of the way. Flockbay is free, AI included: free hosted AI every day, or your own Claude, ChatGPT, agent or API key. It runs on Windows 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 Windows

Flockbay is a download, and the game is not a link

You searched for a web game maker. Flockbay is a desktop application for Windows and Linux that you download and install, and the game it produces runs locally on the copy of Godot bundled inside it. There is no browser editor, no browser preview, and no hosted link to send to a friend.

If the deliverable has to be a game that loads in a tab — an entry for a browser-only jam, something embedded on a site, something a school laptop can open without installing anything — this is the wrong tool. Web-native engines and frameworks exist and they are good at exactly that. Use one.

The rest of this page is for the person who searched for a browser tool out of habit rather than requirement, because that is most people. If nobody actually requires a tab, the trade is worth understanding before you make it.

More on this: Online 3D game makers, and why this one installs

A browser puts a ceiling on how much world a game can hold

The tab is a sandbox with a memory ceiling, a download budget before anything appears on screen, and a graphics path that is a layer removed from the hardware. Every one of those is a good decision for the web and a real constraint on a game.

This is why browser tools quietly steer you toward small, tightly bounded scenes. Not because the people making them lack ambition, but because a world with real terrain, weather, water and a few hundred moving characters is not something a tab handles gracefully. The tool has to protect you from its own platform, and it does that by keeping the ceiling low enough that you do not hit it.

Notice which word is doing the work there. It is "small", not "flat". Browsers are perfectly good at 2D and a great deal of excellent 2D lives in them, so the ceiling is on how much world, not on how many dimensions. It is not our word for a compromise either: a 2D game here is its own kind of game, with its own world tools, rather than the cautious end of the 3D range.

Run the same game locally and those limits mostly go away. Your machine's memory, your machine's framerate, no download before the first frame. That is the entire case for a desktop tool, and it only matters if the game you want is bigger than a tab.

More on this: You searched for an online game builder. This one is a download.

Browser tools are genuinely better at three things

Distribution. A link is the best distribution mechanism ever invented for a small game. No install, no trust decision, no platform. If you want strangers to try your game on impulse, nothing beats it and this tool does not compete.

Access. A locked-down machine, a school computer, a work laptop, a school Chromebook. If you cannot install software, a browser tool is not a preference, it is the only option available to you.

Speed to first thing on screen. Opening a tab is faster than downloading an application, and for an idea you want to test in twenty minutes that difference is real.

More on this: Make a game with AI and no coding, without a closed toolbox

If you take the trade, the AI builds and you judge

It starts with a brief. Flockbay asks questions one round at a time, each with a recommendation, and writes down what gets built first, what comes after and what is not in this version. Nothing is built until you approve it.

Then it builds the world. In 3D that is terrain, water, sky, weather, plants, the player controller, characters and props. In 2D it is tile ground, where the tiles, the edges and the collision all follow from which cells are ground, plus a band of scenery behind it and sprites at an exact position, rotation and scale. It writes the GDScript inside your project, which is a real Godot project on your disk, then runs the game, sends input events and reads the debugger to check its own work.

Then you press Play, the game runs locally, and you say whether it is right. You are not asked to read the code. You are asked to have an opinion about the game, which is a different and more important job. When the opinion is pure taste, like exactly where a hill sits, the same world tools are buttons around the Godot editor's 3D and 2D view, so you can make that one change by hand and Godot's undo takes it back.

Building needs an internet connection, since the chat, asset generation and world data all come over the network. Playing what you built does not. Flockbay is free, AI included: free hosted AI every day, or your Claude or ChatGPT plan, your own agent, or an API key.

More on this: Flockbay vs Rosebud

Where your players are decides the tool

If your players will click a link, use a web tool. If your players will download a build, the ceiling on what you can make goes up a long way and you should take that.

If you genuinely do not know yet, note which decision is easier to reverse. The kind of game that suits a tab is generally small enough to remake elsewhere. A world you spent three months building does not fit into a tab afterwards, so pick the platform before the world, not after it.

Questions

Can Flockbay export a browser game?
No. Its Export makes a native Windows build, and games run locally on the copy of Godot bundled with the app. A web build is not what this tool produces. The project is an ordinary Godot project, so Godot's own export can make one from it, the tab's ceiling included.
Is there a browser version of the editor?
No. It is a desktop app that you install. There is no online editor and no cloud workspace.
What if I cannot install software on my machine?
Then this is not usable for you, and a browser-based tool is the right choice rather than a compromise.
Why not just support both?
Because the tool is shaped around worlds that need to run locally to be worth building. Supporting a tab would mean designing for the tab's ceiling, which is the constraint we are avoiding.
Does building work offline then, since it is local?
No. The chat, asset generation and world data come over the network, so building is online. Playing the finished game is not.
Do I need to code?
No. Flockbay builds the world and writes the GDScript. You judge the result by playing it.