arcade.fun
The creator handbook
A great arcade can hold a ten-second obsession or a world worth exploring for years. Build deep systems, memorable worlds and games players can keep discovering. Bring a complete browser build, or start with our voice and camera SDK.
Build in Creator Studio Upload a gameAvailable today
Creator Studio lets you brief Claude Opus 5.5, generate a modular game, play it immediately, edit files, restore versions and keep expanding the same project. Activation costs 0.25 SOL and includes 2,000,000 AI credits (1 per input token, 5 per output token). The balance and source stay with your signed-in wallet. Submit finished versions for review and update the same game after launch. Studio projects support up to 128 source files and 2 MB per version; complete engine exports use the upload flow below.
The one-file starter is a starting point. Upload a complete web build with multiple scripts, maps, art, audio and data. Browser exports from Unity, Godot, GameMaker, Construct, Defold, PlayCanvas, RPG Maker, Phaser, three.js and other engines are welcome.
Independent web build
Use keyboard, mouse, touch, gamepad or your own browser controls. Your game runs on the games origin in a frame, or in its own tab when it needs threads. You can use your own backend; uploading a game hosts its browser files, not a server.
Independent builds do not automatically receive SDK input, recording or wallet integration. Declare external services and permissions for review.
Arcade SDK build
The arcade owns the microphone, camera and wallet UI. Your sandboxed game receives readings, reports a score and integrates with the arcade lifecycle. Bundle libraries and assets locally; this mode cannot call external services.
SDK builds can also have multiple files. The upload server injects the SDK when it detects its calls. The in-page test bench is for one self-contained HTML file.
index.html at its root and zip it. Whole-project zips with an existing dist, build, out or www folder are also detected; the platform does not compile your source.Current default limits: 250 MB uploaded, 600 MB unpacked, 8,000 files. These are caps, not recommended initial downloads. The single-file test bench has a separate 1 MB limit. Threaded exports use their own tab; plan them as independent web builds because the embedded SDK bridge needs the arcade parent.
A small interface, room for big ideas
arcade.on('start', () => {
/* reset and begin */
arcade.score(0);
});
arcade.on('frame', ({ voice, hands, face }) => {
if (!arcade.running) return;
// Map readings to your own input actions.
});
arcade.on('pause', () => { /* freeze simulation */ });
arcade.on('resume', () => { /* resume safely */ });
arcade.ready({ mic: true, hands: false, face: false });
// When the score changes: arcade.score(currentScore);
// When the run ends: arcade.gameOver(finalScore);Register handlers before calling ready. Read loudness and pitch from voice, fingertips and gestures from hands, and expressions from face. The SDK sends readings, never raw microphone audio or camera images. video: true can show the arcade camera behind a transparent game.
Token integration is optional: arcade.token, arcade.wallet, connectWallet(), pay(amount, note) and buyToken(). Handle a missing token or wallet, declined payments and repeat sessions. Keep a complete free play path.
Purchases and stakes have different flows. arcade.pay() sends an in-game purchase to the creator. It provides no matchmaking, escrow, refunds, winner payout or burn. A client score cannot authorize a token prize.
Phenomenal. Deep. Massive. Expansive.
Build mechanics that change one another: movement and terrain, equipment and enemy behavior, resource choices and exploration. Give players viable strategies, counters and surprising discoveries. Add progression that opens decisions.
Describe levels, quests, items, enemies and dialogue as data. Build an editor or validation script once, then let designers expand the game. Keep a stable content schema and room for new modes, biomes and campaigns.
Separate simulation, rendering, input, UI, audio, assets and saves. Load a small first session; load later regions on demand. Pool busy objects, budget textures and audio, and profile the exported build on real target devices.
Version saves, plan migrations, provide export/import where practical and keep old saves playable. Test readability, touch controls, reduced motion, remapping and sound alternatives. Playtest the first minute and the twentieth hour.
Browser storage is not a platform cloud-save guarantee. Treat it as best effort, handle denied storage and avoid putting secrets there. Account saves, persistent worlds and authoritative multiplayer need backend services; the arcade does not provision those today.
For a larger game, use the creator brief and project prompt. Specify a complete playable slice, interacting systems, content tools, performance budgets and an expansion plan. Then iterate from real play.
Proposed platform capability · not live
A player chooses how many of the game's tokens to stake. Matchmaking finds another human who accepts the same stake and rules. Both fund a match escrow. The verified winner receives 95% of the combined pool; the remaining 5% is permanently burned.
Example: 100 tokens each → 200-token pool → 10 burned → 190 paid to the winner. The winner gains 90 tokens after recovering their stake. A draw or void returns both stakes with no burn. Network fees and account rent are separate.
Before play, an expired funding or ready deadline returns deposited stakes in full. During play, reconnect grace and a server-proven forfeit follow the accepted rules. Platform failure or an unverifiable result gives a void/refund. An unresolved on-chain deadline must allow refunds without the arcade server.
Keep game rules independent of wallet code. Define fixed-step state, validated inputs, snapshots and a reproducible result. Voice and camera readings can be fabricated by a modified browser, so sensor-only games need additional review before real stakes.
Online matchmaking, authoritative rooms and Solana match escrow still need implementation and review. The old Base escrow prototype has no 5% burn and is not used here. Proposed APIs and manifests do not enable real-token play.
Working creator tool · quote only
Each player contributes the amount below. The burn is 5% of both stakes together. On a draw or void, each gets their deposited stake back and the burn is zero.
Example uses a 6-decimal token. No wallet or real tokens are involved.
The helper uses integer base units and rejects rounding. Stakes must be divisible by 10 base units for an exact 5% burn; for this example the smallest step is 0.00001 tokens. It checks the combined pool against the u64 token amount limit. A real implementation must independently enforce these rules in escrow.
Download the reusable quote helper · How Solana token burns reduce supply
Take these into your project
| Tool | Use it for | Status |
|---|---|---|
| Creator Studio | Brief Opus 5.5, build and play modular games, edit code, inspect errors, restore versions and submit updates. | Available · 0.25 SOL activation |
| Upload & test bench | Publish browser builds; simulate voice, hands, face and token purchases for a single-file SDK game. | Available |
| Sky Lift starter | A complete voice game to adapt in the test bench. | Available |
| Creator brief & AI prompt | Plan systems, content tools, milestones, budgets and expansion. | Available |
| Exact stake math | Quote the pool, burn, payout and net gain without float rounding. | Available; quote only |
| Multiplayer contract | Prepare an authoritative adapter, queue rules, recovery and acceptance tests. | Specification |
| Match configuration | Write down rules, stake tiers and deadlines for review. | Draft; not loaded by platform |
What the platform should provide next
These are development priorities, not available services or delivery promises. The current arcade hosts reviewed browser files on one server; it does not yet host arbitrary game backends or persistent worlds.
The platform should carry the shared infrastructure. Creators should have the tools to build games with depth, scale, personality and years of room to grow.