Upload and publish a build

A build is one upload of your game. Players always see the build that is live, and each new build replaces it.

What goes in the zip

Export your game for the web (HTML5) and zip the result.

• Put an index.html at the top of the zip. A zip that contains a single folder works too.
• Use relative links, such as game.js, not /game.js, so the game works from any address.
• Only files a browser game needs are allowed: pages, scripts, styles, images, sound, video, fonts, WebAssembly and common engine data files. Anything else makes the upload fail and names the file.
• Limits: up to 100 MB zipped, 300 MB unpacked, 500 files, and 100 MB for any one file. A zip that unpacks to far more than its own size is refused.
• A game can have up to 5 builds. Delete an old one to add another.
• Games run in a sandbox. Depending on how the site is set up, they may or may not keep saves in the browser, so keep progress in memory or on your own server. The upload page says which applies.
• Games cannot reach the internet. Requests to other sites are blocked, so a game cannot load things from other servers or send data out. Put everything the game needs in the zip. The one thing a game can do is count its own events, such as levels finished: see Send game events from Godot or Defold.

Upload

On the game's edit page, choose the zip and give the build a version name, such as "1.1 Fixed saves". Big games upload straight to storage with a progress bar, and then take a minute or two to unpack. The page updates by itself, and you can keep working.

Try it privately

A new build starts as a draft. Use Preview to play it before anyone else can. The preview link works for a limited time and nobody else has it.

Publish

Tick that the build follows the content policy and that you have the rights to everything in it, then choose Publish this build (or Send for review).

1. We run automatic checks on the build: a first opinion on whether it needs a person to look at it, and a scan for crypto-mining code. We send the game's title, tagline, description, tags, age label, file names, the start of its main page, and its pictures to an AI model for this. We do not send your name or email.
2. If nothing looks wrong and automatic approval is on, the build goes live right away and replaces the old one.
3. If the checks flag something, or automatic approval is off, a moderator plays it first and you get an email: approved, or sent back with what to change. You can fix it, upload a new build or send the same one again.

Moderators can still hide a game later, for example after a report. See Moderation and appeals.

Take a build offline or delete it

• Take offline removes the live build. The game disappears from the site until you publish a build again. The build keeps its files, so you can publish it again.
• Delete this build removes it and its files for good. You cannot delete the build that is live: take it offline first, or get a newer build approved.

Versions and reviews

Each build has its own reviews. See Reviews and ratings. Followers of your game are not emailed for a new build, only for devlog posts. See Devlog and news.