Godot web export hosting — HTML5 build to a play link
A Godot web (HTML5) export hosts free on The Gaming Nest and becomes a link that plays instantly in the browser. Export into an empty folder, zip every file the export produced — the .html, .wasm, .pck and their siblings — and upload it. Each account gets 300 MB, builds are CDN-served, and 10 versions are kept so you can roll back without re-uploading. The one setting that decides whether your build runs at all is thread support; that is covered below.
Turn thread support off before you export
Godot's web export can be built with thread support, which relies on SharedArrayBuffer. A browser only exposes SharedArrayBuffer to a cross-origin-isolated page, which requires specific COOP and COEP response headers. We serve builds from a separate storage origin without those headers, so a thread-enabled Godot export will load and then fail. Export with thread support disabled and it runs. This is the single most common reason a Godot build works locally and not once hosted — anywhere, not just here.
Naming the entry point
Godot names the main HTML file after your export preset, so it often comes out as something like game.html rather than index.html. Either rename it on export, or type the real filename into the "Entry point" field when you upload — the field exists precisely for this. Do not rename it after export without checking: the surrounding files reference it.
Ship every exported file, and nothing else
A Godot web export is not one file. The .pck holds your game data and the .wasm holds the engine; drop either and the build loads to a blank page. Zip the whole export folder together. Do not add your project directory: executables (.exe, .bat, .cmd, .sh …) are rejected at upload, and the extracted archive is capped at 1,000 files.
Frequently asked questions
Can I host a Godot HTML5 game for free?
Yes. Export your Godot project for Web, zip the exported folder, and upload it — every account gets 300 MB free with CDN delivery and 10 retained versions per project.
Why doesn't my Godot web export run after uploading?
The usual cause is thread support. It relies on SharedArrayBuffer, which browsers only expose to cross-origin-isolated pages, and builds are served from a storage origin without those headers. Re-export with thread support disabled. The other common causes are a missing .pck or .wasm file in the zip, or an entry point whose real filename wasn't declared at upload.
Which Godot version does this work with?
Any version whose web export produces a static folder with an HTML entry point — that covers both the Godot 3 and Godot 4 lines. We host the files your export produced and do not modify them, so anything that runs on a plain static file server runs here.