Vibe Coded Games in Browser: How to Put Yours Online

A browser game is the easiest kind of vibe coded game to share, because a single link is all a player needs. Most of them still need a few fixes before they work on a phone, so make those before you publish.

The example here is an invented game where you tap to peg washing on a line before the rain arrives.

Where can my game live?

Home	Best for	What to know
itch.io	Being found by people who look for games	Upload a ZIP with an index.html inside. Its docs, as quoted by users, allow 1,000 files, at most 200 MB each and 500 MB altogether. It asks whether you used generative AI
GitHub Pages	A plain free home	Sites to 1 GB, about 100 GB of monthly traffic as a soft cap. Not for a business
Cloudflare Pages	Games made of many files	On the free plan, 20,000 files of up to 25 MiB each
Your builder's own hosting	Quick sharing	Often comes with the tool's branding on free plans

If you are not sure, start with itch.io. A game page gives you a place for a description and comments, and people there are used to small games.

What breaks when a game goes online?

Your game ran fine on your computer. Here is what tends to go wrong next.

1. There is no sound until the first tap. Browsers generally block audio until the player has interacted with the page, as the MDN guide explains. The washing game's rain sound stays silent. The fix is a start screen with one big button.

2. Phones have no keyboard. If your game uses arrow keys, a phone player cannot do anything. Decide on the touch controls now.

3. Screens differ. The washing line that fits your laptop runs off the side of a phone. Ask for the game to scale to any screen, and decide what happens if the phone is turned.

4. Fingers cover things. Whatever sits under a thumb cannot be seen. Keep the important parts above the bottom third of the screen.

5. A link is not the same as a file on your desktop. Some things only break once the game is on the internet, so always try the real link.

6. Anything in the game can be read. A browser game is sent to the player's computer, so a secret key inside it is no longer secret. If your game calls a paid service, ask a programmer how to do this safely, and never put your key in the game.

Once it runs, tell people what they are looking at. One sentence on the page and a screenshot help more than a long story. If you used AI art or sound, answer the disclosure question truthfully, and see what stores ask.

Paste this to your AI

I want to publish my browser game so that it also works on phones.

First draw a Mermaid diagram of what happens from the moment someone opens the link: loading, the start screen, the first tap, playing, losing, playing again. Add what happens if they turn the phone, or leave for another app and come back. Mark any moment where the player is stuck or nothing responds.

Then compare the game with that diagram. Tell me what is missing and what you would change, naming the place in the project for each one.

If you cannot try something on a real phone, say so and tell me exactly what I should try instead. Never tell me it works on phones unless you can show how you know.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP

How to check it worked

• Open the real link on a phone with sound on. Does the first tap start the sound?
• Turn the phone sideways in the middle of a game. Does the game survive?
• Leave for another app and come back. Is your game still there?
• Send the link to a friend. Does it open with no login and no explanation?
• Close the browser and come back tomorrow. If you saved a high score, is it still there?