Your web game,live on a link.
Publish and host your HTML5, WebGL, or Three.js game. Point the CLI at the folder you already have.
Free to publish. Works with any account.
Ensure Node.js (>= 18) is installed. Install the Sandscape skill globally: npx -y @sandscape/cli@latest skill install Then use it to connect this game folder to Sandscape and stage it for publishing.
Three commands from folder to link.
No build config, no Docker, no bucket to provision. The CLI has zero runtime dependencies and needs Node 18 or newer.
sandscape init ./my-gameConnect the folder
Point it at a game you already built. It reads your .gitignore and .sandscapeignore, so nothing you keep out of git gets uploaded.
sandscape pushSync the changes
Builds a local manifest, diffs it against the last push, and streams only what changed. Every file is SHA-256 verified on both ends.
sandscape publish --prepareStage the release
Stages the metadata, uploads your footage, and hands back a review URL. You press Publish. The server keeps the first 20 seconds of gameplay video and drops the audio, so lead with your best moment.
It hosts what you already wrote.
Sandscape serves the index.html you give it. If it runs in a browser today, it runs here. For a bundled project, connect the build output rather than the source folder.
- Three.js
- WebGL
- JavaScript
- TypeScript
- WebAssembly
- Vite
- per file
- 50 MiB
- per push
- 500 MiB
- files per push
- 5,000
Published means people can actually play it.
Your game lands in the Sandscape catalogue on a shareable link, running on phone, tablet, and desktop with nothing to install.
- Cover art generated from your staged draft and gameplay footage
- A play link that works on phone, tablet, and desktop
- Pull the project back down with sandscape clone at any time
Or let your coding agent run the whole thing.
The CLI ships an Agent Skill. Install it once and Claude Code, Codex, Cursor, or OpenCode can drive the connect, sync, and publish flow for you.
Sync this project with Sandscape and stage it for publishing.
Questions about hosting and publishing.
Install the Sandscape CLI, run sandscape init in your game folder, then sandscape push. Sandscape serves your index.html and assets on a public play link. There is no server to configure.
Yes. Publishing a game to Sandscape is open to every account and costs nothing. Cover-art generation is free for the first three runs per project, within a daily cap of six per account.
That is the point. sandscape init connects any existing web game folder. Bring a Three.js, WebGL, or plain HTML5 build and push it as it is. Sandscape serves static files, so if your project uses Vite or another bundler, run your production build first and connect that output directory.
Yes. push and pull keep your local folder and the hosted project in sync in both directions. If the hosted version moved ahead, push refuses and tells you to pull first, so nothing gets clobbered.
In ~/.sandscape/credentials.json with 0600 permissions. It is never printed, and authenticated requests refuse to follow redirects so the token is never replayed to another host.
Stop sitting onan unplayed build.
Create an account, install the CLI, and put your game on a link people can open.