How to publish a web game
Publish a static HTML5 web game from any coding agent. Get a playable link without an account, then claim, share, and update the game.
If you are wondering where to publish your web game, Playfrog is built for static HTML5 games made with coding agents. Your agent can publish the game directly from the project folder. You do not need to create an account, configure a hosting service, or change the game code first.
Tell your agent:
> Publish this game to Playfrog.
Playfrog returns a public play page, a link for claiming the game, and credentials your agent can use for later updates. Publishing and updates are free. Players open the game in their browser and can share its Playfrog page. The agent chooses the supported method available in its environment: CLI, remote MCP, or HTTP. Browser upload is also available.
Publish a static HTML5 web game from any coding agent. Get a playable link without an account, then claim, share, and update the game.
Ask Claude Code to publish your HTML5 browser game to Playfrog, return the play and claim links, and update the same game later.
Use Codex to publish a static browser game to Playfrog, check the correct build folder, return a play link, and ship later updates.
Tell Cursor to publish an HTML5 game to Playfrog using a supported method available in the workspace. Get a shareable page and update it without changing the URL.
Publish a static web game from Windsurf by command or MCP. Receive a playable link, claim the game, and update it later at the same URL.
Publish a static HTML5 game built with GitHub Copilot. Get a public play page without an account and update it from the same project later.
Ask Gemini CLI to publish an HTML5 browser game to Playfrog, return a shareable play page, and update the same game after later changes.
Use the Playfrog MCP connector to publish a small browser game from ChatGPT or Claude, receive a play link, and update it later.
Update game files, metadata, controls, cover art, and release notes on Playfrog while keeping the same public play URL.
The game must be static browser content with an index.html at the top level. HTML, JavaScript, CSS, images, audio, and other browser assets can be included. If a framework creates a dist or build folder, publish that folder rather than the source directory.
CLI and browser uploads can contain up to 50 MB. Connector uploads carry files inline and are limited to 8 MB.
Share the returned play_url with players. Open the claim_url within seven days to keep the game online permanently and add it to the public gallery. Keep the manage credential private. Your agent can use it to update the same game without changing its public URL.
Publish your browser game or read the complete Playfrog documentation.