About ArcadeLab

ArcadeLab is the shortest path from "I made something" to "anyone can play with it." Paste a single HTML file. Get a shareable URL. No signup, no build tools, no friction.

It started as a game host. It still is — most of what gets published is games. But a single self-contained HTML file is a remarkably flexible shape: physics simulations, interactive explainers, data viz, generative art, anything you can fit in one document works the same way. The double-slit experiment demo is one example.

Why does ArcadeLab exist?

The founder's 7-year-old uses Claude on an iPad to build real, playable browser games — meteor shooters, zombie chases, the kind of thing a kid wants to share with friends. The kid could make. The kid could not share. Every existing platform required accounts, emails, app installs, or developer knowledge. ArcadeLab removes all of that. One paste, one click, the thing is live.

Who is ArcadeLab for?

Anyone who built something and wants someone else to play with it. In practice:

• Indie developers and hobbyists shipping small games with AI assistants
• Science communicators making interactive visualizations and physics demos
• Educators publishing interactive lessons and explorables
• Parents helping kids share games they made
• Anyone building one-file experiments with Claude, ChatGPT, Cursor, Bolt, v0, or by hand

How does ArcadeLab work?

1. You (or your AI) make a single-file HTML document
2. You paste it at arcadelab.ai/publish
3. ArcadeLab assigns you a Creator Code (the first time), e.g., ROCKET-WOLF-COMET-73
4. Your thing gets a public URL like arcadelab.ai/play/your-title
5. You share the URL. People play with it.

What makes ArcadeLab different?

• AI assistants are first-class visitors. The /for-ai page is a living briefing — current themes, recent games, publishing instructions — so any AI a creator chats with can act as an ArcadeLab guide.
• Every piece is a single HTML file. No bundlers, no build tools. Inspectable, remixable, the way the web was meant to work.
• Identity without accounts. Creator Codes, not emails. Low stakes by design.
• Security through sandboxing. Sandboxed iframes on a separate origin with connect-src 'none'. Games cannot make network requests.

Who built ArcadeLab?

Michael LaPeter, Founder. Michael built ArcadeLab after watching his 7-year-old son use Claude on an iPad to make real, playable browser games — meteor shooters, zombie chases, you name it. The kid could build, but the existing platforms to share required accounts, emails, app installs, or developer knowledge. ArcadeLab removes all of that. One paste, one click, the thing is live.

You can find Michael on GitHub.

Is ArcadeLab open source?

Yes. The code is MIT licensed and lives at github.com/mlapeter/arcadelab.

How do I contact ArcadeLab?

Open an issue on the GitHub repo.