Automate web game uploads by scripting your engine export, compression, and verification steps in CI, then uploading via developer consoles since major web game portals do not offer public REST APIs or CLI tools for direct automated uploads. You can fully automate building the deployable zip package, leaving only the final portal console upload step manual.
At a glance
| Fact | Value | Source |
|---|---|---|
| Portal uploads are done via web console | not public REST APIs | developers.poki.com |
| itch.io hosts HTML5 builds in an iframe | on its own domain | itch.io |
| Web export engines produce a static build folder | Unity, Godot, Construct, etc. | docs.unity3d.com |
There is no universal CLI or API across portals for uploading a finished web build – Poki, CrazyGames, GameDistribution, and itch.io all take the build (usually a zip of your HTML5/WebGL export) through a web developer console, not a public upload endpoint. What you can automate is everything before that step: your engine’s export/build command, zipping the output, running checks (build size, console errors), and versioning – wired into a CI script that produces a ready-to-drop zip each time you push code.
Where to publish once the build is ready
- Poki for developers – upload through its developer portal.
- CrazyGames for developers – publishes Unity and HTML5 web games.
- GameDistribution – distributes HTML5 games to a network of sites.
- itch.io – hosts HTML5 games in an iframe on its own domain.
- Playgama.com – upload via developer.playgama.com (Developer Console), get test feedback within 24 hours, and the game is published on playgama.com and distributed to partner portals.
Whatever engine you use (Unity WebGL, Godot web export, Construct, GameMaker), keep the export step itself scripted and reproducible so the only manual part left is the portal upload.
Sources
- Playgama for developers
- Playgama wiki: MCP tools reference
- Poki for developers
- CrazyGames for developers
- GameDistribution
- itch.io creators FAQ
- Unity manual: Web
- Godot docs: exporting for the Web
Related questions
Can I upload builds to Poki or CrazyGames via a script?
Not through a public API – both use a web developer console for uploads. You can automate everything up to producing the final build zip, then upload manually.
What should my automated build step actually produce?
A clean, versioned zip of your engine’s web export (Unity WebGL, Godot web export, etc.) with no debug code, ready to drop into whichever portal’s console.
Last updated: 24 September 2026