Quick picks
| If you want… | Publish on |
|---|
| A free page in minutes, a community and optional tips | itch.io (HTML5 games take donations; you choose itch.io's cut) |
| Your agent to publish it and hand back a playable link | Playgama via its MCP server (Bridge SDK required) |
| Your agent to build and publish into a feed of players | Astrocade via its hosted MCP server (games are made on Astrocade's own platform) |
| Ad revenue from a big web-portal audience | Playgama, CrazyGames or Poki (each needs its own SDK; Poki wants web exclusivity) |
| To make a game with no code and share a link | Google Playground (U.S., 18+) or Rosebud AI |
| Your own site and domain, keeping every player | Cloudflare Pages, Netlify or GitHub Pages (free tiers) |
Step 1: make a build that runs from a zip
Every platform below takes the same thing: a folder of HTML, JavaScript, CSS and assets with an index.html entry point, uploaded as a ZIP. Most “it works on my machine” failures come from the same few mistakes, so fix them before you upload:
- index.html at the root of the zip. Zip the contents of your build folder, not the folder itself. itch.io and Playgama both require
index.html in the archive (Playgama: at the archive root). macOS/Linux: cd build && zip -r ../mygame.zip . Windows PowerShell: Compress-Archive -Path build\* -DestinationPath mygame.zip. - Relative paths only. itch.io serves your game from a subdirectory, so
/assets/hero.png breaks while assets/hero.png works. CrazyGames gives the same rule. - Match filename case exactly. itch.io's servers are case-sensitive (Windows and macOS usually aren't), so
Hero.png referenced as hero.png fails with a 403. Playgama also requires Latin-only file and folder names. - Bundle everything. Poki blocks external requests by default, and Playgama's checklist says to load no external resources except its Bridge SDK. Put fonts, libraries and assets in the build instead of loading them from a CDN, and drop Google Analytics (Playgama says those requests may be blocked; use the platform's analytics instead).
- Test over a local web server, not by double-clicking. For example, run
python3 -m http.server in the build folder and open the address it prints. Then test on a phone. - Keep it small. Poki's engine guide says a good web game's initial download shouldn't exceed 5 MB, and 8 MB in total. CrazyGames requires an initial download of 50 MB or less (20 MB or less for its mobile homepage).
Ask your agent to do it. A prompt that works with Claude Code, OpenAI Codex or Cursor: “Make this game a static web build in build/ with index.html at the root, relative paths only, no external CDN or analytics requests, filenames in lowercase Latin characters. Then zip the contents of build/ as mygame.zip and list any file over 5 MB.”
Engine notes. Godot: the docs suggest exporting with index.html as the file name, and since Godot 4.3 the single-threaded Web export is the default; the Godot docs call it more compatible with itch.io, Poki and CrazyGames, because threaded exports need cross-origin isolation headers. The full Godot walkthrough (templates, threads, file size vs Poki's budget, audio, C#) is in Godot 4 web export for itch.io and Poki. Unity: itch.io serves pre-compressed .br (Brotli) files with the right headers, which itch.io notes is common in Unity 2020 WebGL exports. Unreal: there's a new Experimental web target in the 5.9 Preview; see Unreal Engine games on the web below. Made it in Google Playground? Its Creation Studio has an Export (Download Zip) button that gives you the game's HTML, JavaScript, CSS and generated assets.
Step 2: pick where to publish
The free options, side by side. “Audience” figures are the platforms' own claims.
| How you earn | Audience | Build requirements | Size limits | SDK / ads |
|---|
| itch.io | Open revenue sharing: you set itch.io's cut from 0% to 100% (default 10%), plus payment fees. HTML5 games only take donations; to sell access, make the game downloadable | itch.io's own community and browse pages | ZIP with index.html, or one self-contained HTML file. ZIP only (no .rar/.7z) | Up to 1,000 files, 500 MB extracted, 200 MB per file, 240-character paths (can be raised on request) | No SDK. itch.io says it never puts ads on your pages |
| Playgama | No upfront cost. You get 70% of net revenue up to $1,000; $700 + 80% from $1,000 to $3,000; $2,300 + 90% above $3,000 (ads and in-app purchases) | Playgama says 450M+ players across YouTube Playables, MSN and 100+ partner platforms | ZIP with index.html at the root, Latin file names, no external resources or analytics, no external sign-in to play | 300 MB per archive | Playgama Bridge SDK required for every game, sandbox included; at least one interstitial or rewarded ad, ads only through Bridge |
| CrazyGames | Revenue share only after Full Launch; CrazyGames calculates it monthly from your game's traffic and ad performance (no fixed % published). Optional +50% for 2 months of exclusivity | CrazyGames says 50M+ monthly players | Relative paths; must run in Chrome and Edge; mouse, keyboard and touch if mobile | 250 MB and 1,500 files total; initial download 50 MB or less (20 MB for the mobile homepage) | SDK optional in Basic Launch (no ads there); required for Full Launch |
| Poki | 100% of revenue from players who come directly (search, bookmarks, social, your community); 50/50 on players Poki brings | Poki says 100 million monthly players | Desktop, mobile and tablet; 16:9 scaling; works in incognito; no external requests, branding or third-party ads | No hard cap given; Poki's guide recommends 5 MB initial and 8 MB total | Poki SDK required. Standard deal is web-exclusive (5 years by default, “indicative”), including Discord and YouTube Playables |
| Google Playground | Google can monetize Your Games on Playground (including ads) after asking your permission; no creator payout is described | Players browse a public catalog; anyone 18+ in the U.S. can play | Games are made in Playground's Creation Studio from prompts (you can upload PNG/JPG images, not a build) | None stated | None; free tier gives a weekly token allowance, Google One AI plans raise it |
| Cloudflare Pages (Free) | Whatever you set up yourself (your own ads, tips, a paid download elsewhere) | None built in: bring your own players | Any static folder; dashboard drag-and-drop accepts a zip or a folder | 20,000 files (1,000 via drag-and-drop), 25 MiB per file | None |
| Netlify (Free) | Same: you monetize yourself | None built in | Any static folder; deploy from Git, API or AI tools | Free plan is 300 credits a month as a hard limit: a production deploy costs 15 credits and bandwidth 20 credits per GB, and when credits run out every project pauses until the next cycle | None |
| GitHub Pages | Same, but GitHub's terms say Pages isn't for running an online business or e-commerce site | None built in | Static files from a repo or Actions | Published site up to 1 GB, soft 100 GB/month bandwidth | None |
Example from Netlify's credit table: 10 production deploys in a month use 150 of the 300 free credits, which leaves about 7.5 GB of bandwidth before the site pauses. Cloudflare's Pages limits page for the Free plan lists file, build and project limits but no bandwidth allowance.
Step 3: don't trip over exclusivity
- Poki asks for web exclusivity: you can't publish the same game on other web portals or aggregators, and that includes Discord and YouTube Playables. Steam, mobile app stores and consoles stay yours. For games already live elsewhere, Poki may offer a one-time flat license fee instead of a revenue share.
- Playgama distributes your game to its partner portals (YouTube Playables, MSN and others), and you can exclude specific platforms when you submit. That clashes with a Poki exclusive.
- CrazyGames pays 50% more for two months if the game is only on CrazyGames among browser game sites (it must be hosted by CrazyGames). Steam and the app stores don't count.
- itch.io and your own site don't ask for exclusivity. A common order: put a playable build on itch.io and your own domain first to collect feedback, then decide whether to go exclusive with Poki or wide with Playgama and CrazyGames.
Publishing straight from your agent with Playgama MCP
Playgama runs an MCP server for agent-built games. Add https://developer.playgama.com/api/mcp to your MCP client (Codex, Claude Code and others), sign in to Playgama in the browser window it opens, then ask your agent to upload the game. Playgama's suggested prompt: “Upload this game to Playgama and give me a public playable link. If the game does not have the Playgama Bridge SDK yet, integrate it first.” The agent integrates the Bridge SDK, uploads, and returns a public sandbox link. Getting into the main catalog is a separate submission. Playgama says ads switch on once a game clears a session threshold, and that advertising is in beta and rolling out to published games. For the main catalog, moderation usually takes 3 to 5 business days, and partner platforms can take up to 2 weeks.
Building and publishing on Astrocade from your agent
Astrocade launched a hosted MCP server on October 12, 2026. There's nothing to install: add https://mcp.astrocade.com/mcp to your agent (Claude Code: claude mcp add --transport http --scope user astrocade https://mcp.astrocade.com/mcp, then /mcp and Authenticate; Codex: codex mcp add astrocade --url https://mcp.astrocade.com/mcp), sign in to Astrocade and click Allow. Astrocade lists Cursor, ChatGPT on the web, Claude and Gemini CLI too, and any agent that supports remote MCP servers.
It works differently from Playgama. Playgama takes a build you already made and uploads it; Astrocade games are built on Astrocade's own platform and follow its game guidelines (made for phones and mobile connections), and the MCP lets your agent create, change and save them back to your account, including games you started in Astrocade's app. Publishing is one command; after review the game shows up in Astrocade's feed with plays, comments, followers and analytics. Astrocade says it's free to create and publish, and that it pays creators based on plays (the payout terms are behind a sign-in, so we haven't checked the rates).
What we checked: on November 2, 2026 the endpoint answered an unauthenticated request with HTTP 401 and OAuth metadata (authorization server astrocade.com, scope creator), which matches the sign-in flow above. We haven't built or published a game with it yet. Pick Astrocade if you want an audience inside its app; pick Playgama, itch.io or your own hosting if you want to keep your own HTML5 build portable.
Whatever the platform, save progress the way it asks: Playgama's checklist says to use Bridge storage rather than localStorage directly, and Poki requires that your game still works in incognito, where localStorage is restricted (wrap it in try/catch).
Unreal Engine games on the web: the 5.9 Wasm target vs Strata
Unreal dropped its HTML5 export years ago, so until now the only ways to put an Unreal game in a browser were cloud streaming or a third-party build service. That changed on November 9, 2026: Epic's Unreal Engine 5.9 MegaJam Preview adds an Experimental web platform called Wasm that compiles your project to WebAssembly and renders with WebGPU. Epic says agents wrote the platform code, starting from UE4's retired HTML5 platform, with engineers directing, reviewing and testing the work.
What Epic says it does today (announcement and the Web Platform roadmap card, read November 11, 2026):
- Wasm shows up alongside the other target platforms in the editor, with a page template for hosting the build and deployment tools for publishing it.
- It uses the mobile renderer, in two tiers: “mobile deferred” for desktop browsers and “mobile forward” for phones. Full desktop deferred rendering is still being investigated, so don't expect Lumen-style lighting.
- Mouse and keyboard, controllers and touch are supported, and you can build for web on Windows, Mac and Linux.
- Limits for now: you need a code (C++) project, Chrome gives the best experience, and Epic warns of longer cook times and occasional performance problems. The announcement said a source build was required, but Epic's November 10 tutorial says the Launcher (installed) build works too, from Preview 1 on. It's a Preview, so test on a copy of your project.
Publishing the result: the packaged build is a folder of web files with an index.html, so Step 1 above still applies. The difference is size: an Unreal web build can be far bigger than a small vibe-coded canvas game, so check the folder against the limits in the table above (itch.io: 500 MB extracted, 200 MB per file, 1,000 files; CrazyGames: 250 MB and a 50 MB initial download; Poki recommends 5 MB initial) before you pick a portal. itch.io is the realistic first stop. Self-hosting on Cloudflare Pages works only if no single file (a big .wasm or .pak, say) is over its 25 MiB per-file limit. Run it from a local web server and in Chrome before you upload.
Packaging a UE 5.9 web build, step by step
This is a summary of Epic's Getting started with UE 5.9 on the web (Wasm) tutorial (Epic Education and Training, November 10, 2026, read November 11). Windows is the host Epic documents. We haven't run these steps ourselves.
- Get the prerequisites. Unreal Engine 5.9 (Launcher build from Preview 1 on, or a source build), Visual Studio with the C++ workload, and a C++ project. A Blueprint-only project needs one C++ class added (Tools > New C++ Class) before it can be packaged. For a fresh test, use File > New Project > Games > Third Person with C++; don't copy a template folder by hand.
- Install Emscripten 6.0.10 exactly. No other version is accepted. Clone emsdk to a short path (
git clone https://github.com/emscripten-core/emsdk C:\emsdk), then run emsdk install 6.0.10 and emsdk activate 6.0.10 --permanent. The --permanent flag saves the EMSDK variable the engine reads. Restart the editor and any command prompts afterward. - Check the SDK. Platforms > Wasm in the editor shows its status, or run
Engine\Build\BatchFiles\RunUAT.bat Turnkey -command=VerifySdk -platform=Wasm. If validation fails because an older emsdk from another project is still active, set WASM_EMSDK_ROOT to the 6.0.10 folder (it wins over EMSDK). This is the fix for the “editor doesn't see my web SDK” problem in early forum posts. - Set the web options in Project Settings > Platforms > Wasm: Page Title, Start Mode (Click lets sound start, since browsers only play audio after a click or key press), Mobile Devices (Warn, Block or Allow), and Target Mobile Deferred Tier (turn it off for a smaller, forward-only cook). Also set Maps & Modes > Game Default Map, because Shipping builds always start there.
- Package a Shipping build. Platforms > Wasm > Package Project, or Platforms > Wasm > Local Browser to build, cook, serve and open it in one step. Use Shipping for anything you share: it's much smaller, and the deploy tools refuse Development builds. The first build and the link step take a while and a lot of memory. (The tutorial also gives the full
RunUAT BuildCookRun -platform=Wasm command line.) - Know the output.
<Output>/Wasm is the whole website (index.html, scripts, .wasm, data files and .br copies). Wasm-Debug holds the symbol map: keep it for crash call stacks and never upload it. - Run it locally. Double-clicking
index.html won't work. Double-click Play_<Project>.bat in the output folder (needs Python 3.8+), which serves the folder with the right headers. In the console (F12), UE_RUN READY means it started. Add ?compat=1 to the URL for a browser and GPU compatibility report, ?debug=1 for a frame-rate and memory overlay, and ?sw=0 to skip the download cache.
Hosting on your own site. Upload the contents of the Wasm folder as-is, over HTTPS. The server has to send Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp on index.html and sw.js, and Cross-Origin-Resource-Policy: same-origin on every file, or the page stops with “not cross-origin isolated”. It also needs correct MIME types (application/wasm for .wasm), plain 206 responses to byte-range requests with no on-the-fly compression, and Cache-Control: no-cache. Epic ships ready-made configs for nginx, Apache, IIS, Netlify and Cloudflare-style _headers hosts in Engine/Platforms/Wasm/Build/Tools/deploy/templates, plus check_stage.py (before upload) and webdoctor.py (after). For GitHub Pages, which can't set headers, turn on Inject Isolation Headers. Upload each update to a new folder instead of overwriting the live build.
Hosting on itch.io. Create an HTML project with Embed in page, Fullscreen button, Click to play and SharedArrayBuffer support on. Save, then reopen Edit game and check that SharedArrayBuffer is still on; Epic says the new-project form has dropped it before, and without it the game won't start (the _headers file doesn't help inside itch.io's frame). Upload a zip with index.html at the top, or butler push <Output>\Wasm <user>/<game>:html. If you're over the size limit, delete .br files that have a plain copy next to them. Keep test builds in Draft and share the secret URL.
Phones and multiplayer. Phones get the mobile forward renderer, and most can't use the default BC textures; to support them, cook a second ASTC texture set and add it with -WasmAddTextureSet (the page picks the right set at start). There are no raw sockets in a browser, so multiplayer goes through a WebSocket relay to a native server, and a browser can't host a game.
| UE 5.9 Wasm target (Epic) | Strata (SimplyStream) |
|---|
| Engine versions | 5.9 Preview only | 5.8 (the 6.0 line on paid plans for now) |
| Engine install | Launcher or source build, C++ project, Emscripten 6.0.10 | No editor install needed: one prompt to your agent or the strata CLI |
| Who builds it | You, on your machine (longer cooks) | Strata's build agent, checked on a cloud GPU |
| What you get | Web files you host yourself | A play link |
| Cost | Free | Free plan with $10 of trial credits and two runs a day |
| Status | Experimental Preview; full 5.9 release due next year | Launched October 2026 |
If you're on 5.8 today or don't want to set up Emscripten and a C++ build, Strata is the shortcut; if you want to own the build and host it yourself, the 5.9 target is the one to watch. More on the 5.9 Preview's other features (in-editor agents, Unreal Canvas, Semantic Search) is in AI tools for Unreal Engine. We haven't packaged a 5.9 web build ourselves (no Unreal Editor on our Linux test machine).
What 116 MegaJam teams shipped with the UE 5.9 web target (our data)
The Epic AI MegaJam (November 12-15, 2026) was the first big test of Unreal's new web platform, so we looked at what teams actually uploaded. On November 16 we took the jam's itch.io entry list, kept the 145 entries tagged as playable in the browser (now listed with their pitches and load sizes), and opened each one's hosted page and build files (no logins, nothing played or rated). 116 of the 145 (80%) were Unreal Engine 5.9 Wasm builds, recognizable by Epic's staged page template and its wasm-manifest.json. The rest: 16 plain JavaScript or other web builds, 4 three.js, 1 Godot, 1 Unity, 1 PixiJS, and 6 whose embedded build we couldn't find.
- Content files are big. The files listed in each build's
wasm-manifest.json (cooked content and engine data, not counting the engine's .wasm binary) came to a median of 90 MB; the middle half ranged from 55 to 191 MB, the smallest was 24 MB and the largest about 450 MB. 28 builds listed more than 200 MB. The largest builds split their content across several .ucas files of up to about 176 MB each, which keeps every file under itch.io's 200 MB per-file cap. - The engine binary alone is around 140 MB. We downloaded the Shipping
.wasm from 10 builds picked at random: 79 to 167 MB uncompressed (8 of the 10 between 139 and 146 MB). itch.io serves it gzip-compressed, which brought the transfer to 24 to 44 MB. So before any of your content loads, players download roughly 40 MB of engine, far over CrazyGames' 50 MB initial-download budget once content is added and nowhere near Poki's 5 MB guideline. - Renderer: 97 builds shipped the WebGPU mobile deferred shader cache (
SP_WEBGPU_ES3_1_DEFERRED), one of them alongside the experimental desktop SM5 cache; the other 19 listed no global shader cache file. - Template settings teams kept or changed (the
ue-* meta tags in the staged index.html): 114 of 116 kept threading on for desktop, which is why itch.io's SharedArrayBuffer option has to be on; 74 used click-to-start (ue-start = click) and 42 started automatically (Epic's template comment notes sound only starts after the player's first click or key press either way); 108 left phones at “warn”, 4 blocked them and 4 allowed them; 113 kept the template's 8 GB minimum-memory check; and 26 added their own shell script for things like custom loading screens, menus or input remapping.
What that means for your own UE web build: plan for a cold download in the tens of megabytes even for a small game, so keep the template's loading cover and make the first scene light; check each file against itch.io's 200 MB cap and the whole folder against its 500 MB extracted limit before you zip; leave SharedArrayBuffer on for threaded builds; and keep click-to-start if your game has sound. If you need a small initial download for Poki or CrazyGames, Unreal's web target isn't there yet, and a lighter engine (see our Godot 4 web export guide) is the practical route.
AI disclosure outside Steam
itch.io added a “Generative AI disclosure” field to project edit pages in November 2024. Answer yes and you pick the types (Graphics, Sound, Text & Dialog, Code) and get the AI Generated tags; answer no and you get the No AI tag. It's mandatory for asset pages and, since November 2026, for soundtrack, book, comic and physical game pages too, so a separate soundtrack page for your game needs it before you can save. It's still optional for the game itself, but itch.io's search now has a No AI filter that only shows pages whose creator answered no. itch.io's founder also said code an LLM generated that you put into your project counts (details in our itch.io AI disclosure section). If you'll also launch on Steam, see Steam AI disclosure: what to write, and keep a per-asset log with our free AI asset log template (CSV). Taking the game to Steam later? Steam's rules don't allow advertising-based business models, so plan a version without portal ad SDKs and read the Steam launch checklist. Steam also needs a desktop app, not a web page: how to put an HTML5 game on Steam covers Electron vs Tauri wrappers, Steamworks achievements and Steam Deck.
Pre-upload checklist
index.html at the zip root; relative paths; filenames match case- No external CDN, font or analytics requests (or only the ones the platform allows)
- Runs from a local web server and on a phone; keyboard, mouse and touch work (for touch, see touch controls for HTML5 games; plus controllers, if you support them: see Gamepad API controller support)
- Scales to the portal's frame sizes without blur, stretching or big black bars (see responsive canvas scaling for web games)
- Pauses audio when the tab is hidden; mute button if there's sound
- Initial download as small as you can get it (aim for Poki's 5 MB guide)
- Every AI asset made on a plan that allows commercial use, if you'll earn money from it
- Cover art and screenshots ready (Playgama and itch.io pages both use them)
Before you upload, playtest it with real people: see AI tools for game playtesting and QA. Still building it? Start with how to vibe code a game, or compare the no-code makers that host and publish for you in Rosebud vs Google Playground vs Higgsfield Playable vs Astrocade.
Know a free platform we should add? Get the VibeStack Weekly digest: new AI game tools and publishing options for solo devs, every Monday.
Sources (checked October 28, 2026): itch.io creator docs (Uploading HTML5 games, Accepting Payments, Creator FAQ) and itch.io's “Generative AI Disclosure tagging” announcement (November 20, 2024); playgama.com/developers, playgama.com/mcp and the Playgama wiki (Submitting a game, MCP game checklist, Game Moderation FAQ); CrazyGames docs (overview, technical requirements, FAQ) and CrazyGames Developer Terms (August 18, 2025); Poki for Developers (Working with Poki, deals, Requirements, Choosing your web game engine); Google Playground Help Center and Terms; Cloudflare Pages docs (Limits, Direct Upload); Netlify pricing and “How credits work”; GitHub Pages limits; Godot docs (Exporting for the Web). Audience figures are each platform's own claims. Platforms change terms often, so read the current page before you sign anything.
Get the Starter Stack ($12) Get the free weekly digest