How do I make an HTML game in 30 minutes with AI?

Half an hour is enough time to build and publish a real browser game — as long as the game is small and the steps are clear. Here is a path that fits, broken into the minutes it actually takes.

What kind of game fits in 30 minutes?

One mechanic, one screen, one ending. A dodging game, a one-button jumper, a memory match, a falling-blocks puzzle. No level select, no save files, no menus. If you cannot describe the game in two sentences, it is too big for the time box — cut it down until you can.

Minutes 0-5 — Pick the idea and write the prompt

Choose the idea, then write a prompt that names the format and the constraints: a single self-contained HTML file, all code inline, canvas that resizes to the window, no external files, no network calls. Spending five honest minutes on the prompt saves more than five minutes of debugging later.

Minutes 5-20 — Build and iterate

Send the prompt, then treat the first reply as a draft. Run it and change one thing at a time: speed, colors, the lose condition, the feel of the controls. Small, specific follow-ups keep a working game working. This is the longest stretch — and the most fun.

Minutes 20-25 — Test the game

Save the file and open it directly in a browser. Play for a minute, watch the developer console for errors, resize the window, and check it at a phone-sized width. Fix anything that breaks now — not after publishing.

Minutes 25-30 — Publish it

Open arcadelab.ai/publish, paste the whole file, and click publish. You get a permanent URL with no signup and no email. Send the link to whoever you made the game for — that moment is the entire point of the exercise.

What if it is not done at 30 minutes?

Publish what you have. A simple game that someone can play beats a complicated one stuck in a chat window. You can edit it later with your Creator Code. If you want ideas scoped to fit this time box, see game ideas you can build in one evening.

Finished early? Publish the game at arcadelab.ai/publish.