How to export your Godot game for the web

What you need

• Godot 4.7, the current stable release, with the Web export template installed (Editor > Manage Export Templates).
• A GDScript project. Godot 4's web export currently does not support C# projects at all, so a C# game needs Godot 3 or a native export instead.
• No special setup for age gating: your build plays inside an iframe on naughty.games, behind the site's own age gate.

Godot 4 can only target WebGL 2.0 on the web, through its Compatibility rendering method; Forward+ and Mobile are not available in a browser. Most current desktop and Android browsers support WebGL 2.0 fine, but Safari has had more issues with it than Chromium-based browsers or Firefox, so it is worth testing your build in more than one browser before you publish, not just the one you develop in.

Export for the web

1. Open Project > Export, click Add... and choose Web to create an export preset.
2. Leave Thread Support unchecked. This has been the default since Godot 4.3, and it is also the setting the Godot docs call out as the most compatible with hosts like itch.io, Poki and CrazyGames.
3. Leave Progressive Web App > Enable unchecked too. See the box below for why.
4. Set the export path to a new folder and name the output file index.html, since that is the name a plain web server loads by default.
5. Click Export Project. Godot writes index.html, a .pck file (your game's data), a .wasm file (the engine itself), a .js start-up file, and a .png boot splash image into that folder.

Why single-threaded, and why no Progressive Web App

A threaded Godot web export uses SharedArrayBuffer, which only works on a page that is cross-origin isolated. That requires the server to send both a Cross-Origin-Opener-Policy: same-origin header and a Cross-Origin-Embedder-Policy: require-corp header on every response. naughty.games does not send both of those together, and neither do most general-purpose hosts, so a threaded build simply will not start there. Godot's own docs describe single-threaded export, the default since 4.3, as the fix for exactly this problem, with the added benefit of working better on macOS and iOS too.

Godot's Progressive Web App option offers a workaround for hosts that cannot set those headers: it installs a service worker that simulates cross-origin isolation and also caches the game for offline play. naughty.games does not allow hosted builds to register service workers at all, so this workaround will not work here and should stay off.

Test it locally

Opening index.html directly from your file system will not work. The browser blocks the requests Godot's loader makes for the .wasm and .pck files when the page is loaded over file://, so the game gets stuck loading or never appears.

Serve the export folder over HTTP instead. From inside the folder, run:

python -m http.server 8000

Then open http://localhost:8000 and play through the build before uploading it anywhere.

Zip it for upload

• Zip the contents of the export folder, not the folder itself, so index.html ends up at the top level of the zip.
• Stay under 250 MB unpacked and 2,000 files. A Godot web export is usually just the five files listed above, so this rarely becomes an issue unless your game streams a lot of video.
• Do not manually gzip or brotli the .pck or .wasm file before uploading. naughty.games serves whichever exact filename you upload, and Godot's generated index.html and .js request the plain file names (for example game.pck), so a renamed game.pck.gz simply will not be found. Upload the files exactly as Godot exported them.

Common problems

1. Blank page or stuck on loading. You opened the export over file://. Serve it from a local server, or upload it and preview it on naughty.games directly.
2. The game refuses to start and the browser console mentions SharedArrayBuffer. Thread Support was left on during export. Re-export with it off.
3. Progress does not save between visits. Godot's user:// file system persists through the browser's IndexedDB. Check the player is not in a private/incognito window and is not blocking third-party storage for the naughty.games iframe.
4. A C# project will not export to Web. Godot 4's web export only supports GDScript; a C# project needs a different export target.
5. No sound until the player clicks or taps. Browsers block autoplaying audio until a user gesture. This is expected, not a bug in your game.
6. The game seems to freeze when a player switches tabs. Godot pauses _process() and _physics_process() while a browser tab is inactive. This is a browser limitation, not something to fix in your project.

Publish it

Once the export runs cleanly from a local server, zip it with index.html at the top level (up to 250 MB unpacked and 2,000 files) and upload it to naughty.games, or send us an https URL if you would rather embed it. Review is usually about 2 working days, listing is free and non-exclusive, and any Patreon, Ko-fi, Steam or itch links inside the game earn you 100% of what they bring in. Head to /submit when you are ready.