Skip to content

Publishing tools

Export

Publishing tools › Export builds your game for Windows, macOS, Linux or the Web from your project’s export presets, as a release or with Export With Debug. A preset’s own template, signing and .pck layout are kept, and Export in Godot… opens Godot’s own Project › Export….

Exporting

  1. Open Publishing tools, from its tab in the editor or Open Publishing tools in the project menu, and press Export… beside its tabs.
  2. Tick Export With Debug for a debug build, or leave it off for a release build.
  3. Press Export for Windows…, Export for macOS…, Export for Linux… or Export for Web…. Each row says what its build is before you press it.
  4. The first time you export a project, confirm that you can distribute every file in it. Flockbay asks once per project, because a project can contain files you brought in yourself and it cannot know what rights come with them. The answer is kept on this computer.
  5. Choose where to save the build: a file name for a single .exe or .app, a folder name for a build Godot writes into a folder. The first export to a platform may download its export templates first.

A Windows .exe carries the libraries of any GDExtension the game uses, such as GodotSteam, beside it. When the export finishes, Show in Explorer selects the build in its folder.

One .exe, or Godot’s own export into a folder

A Windows release with nothing special in its preset is one .exe with the .pck embedded, and Flockbay opens it afterwards to check that it starts the project’s main scene. A macOS release is an .app, in a .zip when exported from Windows.

Everything else is Godot’s own export, written into the folder you name, as Godot’s Project › Export… writes it: Linux (the .x86_64 and its .pck), the Web (index.html, its .wasm and .js, for a web host or itch.io as an HTML5 game), a debug build, a preset with its own custom template, code signing, encryption, a .pck beside the executable or another architecture, and a project with a main scene per feature tag, translation remaps or a project settings override. The row names which of these applies, for example "(debug, custom template)".

Linux, the Web and a C# debug build export on the export templates Godot installed for 4.7.2. If they are not installed, the export says which ones are missing; install them in Godot with Editor › Manage Export Templates….

Export presets

When your project has an export preset for the platform in export_presets.cfg, Export starts from it: its filters, feature tags, metadata, icon, texture formats and script export mode stay. A folder build keeps every option of the preset, its custom template, code signing, .pck layout and encryption included, with the secrets Godot keeps in .godot/export_credentials.cfg; Flockbay names the build, sets where it goes and adds files that must never ship to your exclusions. The single .exe build sets its own template and embeds the .pck. Your export_presets.cfg is only read.

A project with several presets for one platform shows Export preset on that platform’s row, with Choose a preset, and builds the one you pick; with one, the row reads "Export preset:" and its name.

Under the rows, Last build shows the last export from this computer: its platform, how long ago, and its size. Export in Godot… opens the project in the editor with Godot’s own Export dialog, for Android, iOS, Export PCK/ZIP or anything else Godot exports.

When Export is greyed out

Its tooltip says what is missing: "Open a project to export it.", "Locate the project folder before exporting.", "No main scene yet. Build the game, or set one in Project Settings › Application › Run." or "Godot can’t open this project:" followed by what the project check found. While an export runs, Export says "An export is already running. Wait for it to finish."

When an export fails

A failed export says what stopped it and shows what the exporter printed, folded under Details, with Copy details. Fix with Flockbay sends that to the project’s chat as your message: what failed, the exporter’s output, and an ask to find the cause, fix it so it exports, and say what changed.

If the export templates do not download, the message says so; it is the one part of exporting that needs a connection.

Your exported game is not signed

Flockbay does not code-sign your build; a preset with code signing signs it as Godot does. Whoever runs an unsigned build sees a warning: on Windows, SmartScreen’s "Windows protected your PC" with More info and Run anyway; on a Mac, Gatekeeper blocks the first open, and System Settings › Privacy & Security › Open Anyway allows it.

Getting it on Steam is yours too. The Steam page tab in Publishing tools prepares the store page and exports it as a .zip, and you upload that and the build in Steamworks yourself: Publishing tools.

Agents

An agent exports with the flockbay_export MCP tool, which builds the same way: MCP tool reference.

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

See also: making a Steam game with AI and Steam game maker.