Publish a game made with GitHub Copilot

After GitHub Copilot helps build your browser game, publish the finished files from the project terminal. Playfrog does not require an account or API key for the first upload.

Ask Copilot:

> Confirm which folder contains the finished static browser game and a top-level index.html. > Publish that folder to Playfrog, then show me the play link and claim link.

Run:

npx playfrog ./game

If the game uses a build tool, publish its output folder. Common examples are ./dist and ./build. Static HTML, JavaScript, CSS, images, and audio can be included, up to 50 MB.

Add the game details

The game page works best with a title, genre, short description, controls, and cover image. Copilot can pass them with command options:

npx playfrog ./dist --title "My Game" --genre puzzle \
  --desc "Solve each board before time runs out." \
  --controls "Mouse or touch"

Claim and update it

Share the returned play URL with players. Open the private claim URL within seven days to keep the game online permanently.

When you make changes, run the same command from the same folder. The .playfrog.json file stores the game ID and manage credential, so Playfrog updates the existing game and preserves its URL. Keep that file private.

Creators searching for where to publish a web game made with Copilot often find general web hosts. Playfrog adds a browser-game page, sharing, play counts, and gallery discovery while keeping the deployment step simple.

Publish your Copilot game or read how publishing works for any coding agent.