Build a game for TipTap
Your agent builds it, or you upload it yourself. Either way it runs sandboxed, a human reviews it, and then it is in the feed.
- Agent or manual
- Free to publish
- One HTML file
What TipTap is, for a creator
TipTap Games is a swipeable feed of browser games that play instantly — no install, no download, and no account needed to play one. For you that means the distance between finishing a game and someone playing it is a review queue, not an app store.
A TipTap game is one self-contained HTML file. Everything it needs is inside it, because it runs in a locked-down sandbox that cannot make network calls. The platform gives you the rest — scores, leaderboards, achievements, the loading screen — through a small SDK that is already injected when your game starts. Publishing costs nothing: there are no credits, no build minutes, and no paid tier gating any of it.
Connect, build, review
Three steps, and the middle one is the only one that takes any real time.
Point the agent you already use — Claude, Replit, Cursor, anything that speaks MCP — at TipTap once. Or skip this entirely and bring your own HTML file.
Connect your agent →Describe the game you want and your agent writes it — one self-contained HTML file against the TipTap SDK — or build it yourself. Either way it's a single file with no build step.
Build your first game →You submit when you're happy with it. A human moderator approves it, and it goes live in the feed where players swipe into it.
How review works →Two ways in
Both routes end in the same place: the same validator, the same review queue, the same feed. Pick whichever suits the way you work.
Connect once and your agent builds, validates and submits games straight to your account. You watch the build happen on your sessions page and keep full ownership of what it makes. The connection is scoped to your account and revocable in one click.
Set up your agent →Wrote it by hand, or your tool has no MCP support? Drop the single self-contained HTML file at /create/upload and you get the same validator errors in the browser. If an agent wrote the file, point it at the agent spec first so it builds against the real constraints.
Upload a game →A second way to build, in development
Everything above, and everything else in these docs, describes the tier you can ship on today: one self-contained HTML file using the TipTap SDK, validated, reviewed, and in the feed. That is the whole platform as it stands and it is the right answer for almost every game.
A second tier is being built for real-time multiplayer. Instead of an HTML file you write one TypeScript file, compiled to WebAssembly and run as a deterministic simulation on every player’s device, so all of them compute the same world from the same inputs. It is a different way to build, not a replacement for the one above.
Status: in development. It compiles and runs, but it is not yet reachable from the Creator Studio — you cannot publish a game with it today.
Read about creator logic →Every game runs sandboxed. Every game is reviewed.
- Sandboxed — games run in an isolated frame with no network access and no same-origin access. A game cannot reach your data or anyone else's.
- Human-reviewed — a moderator approves every game before it goes live, including the ones an agent submitted.
- Reportable — players can flag anything in one tap, and a flagged game comes back to the queue.
The same rules apply to you as a creator: the sandbox is why a game has to be one file with no outbound calls, and human review is why a submission is not instantly live. The security model has the full picture, and the content policy is what a moderator judges your game against.
Where to go next
Pointing an agent at the docs? Give it https://tiptapgames.com/llms-full.txt. It is every page on this site composed into one plain-text document — the platform constraints, all 24 tools, the build workflow, the validation error codes, the SDK spec and the whole cookbook — written for a model to read rather than a person.