The four export formats
Export from the Studio menu → Export, or Settings → Exports. Builds run in the
background, and you can have a link emailed to you when they’re ready. Most exports take
seconds; a first desktop build takes a few minutes. Download links stay valid for 7 days —
build again any time for a fresh link.
Availability
- Any paid plan unlocks all four formats. Free-plan games show the export options locked.
- Source code export is limited to original games — copies, earlier remixes, and template-derived projects can export playable builds but not source. See Make a copy.
Self-hosting the web export
The web export is a plain static site — no backend needed:- Unzip and upload the folder to any static host (nginx, S3+CloudFront, Cloudflare Pages, Netlify, GitHub Pages, itch.io…), keeping the files together.
- Serve it over HTTP(S) — opening
index.htmlstraight from disk won’t work in most browsers. For local testing, runpython3 -m http.serverin the folder.
Running the source project
The source export is a standard Vite + TypeScript project using Three.js (3D) or Phaser (2D). It includes a README with everything below. With Node.js installed:src/main.tsis the entry point; all game code lives undersrc/.- Every image, model, and sound is under
assets/. - Open the folder in any code editor (VS Code, Cursor, WebStorm…) and develop it further — it’s yours.
Desktop builds
The macOS and Windows exports wrap your game as a native desktop app.- macOS: the app is unsigned, so macOS warns that it can’t verify it the first time. Right-click the app, choose Open, then Open again.
- Windows: SmartScreen may show a warning. Choose More info, then Run anyway.