Start here
Publishing a game made with AI tools
You can publish a web game you made with AI coding tools on Smaz Games, such as Claude Code, Codex, Cursor, GitHub Copilot, Lovable, Bolt, Replit or v0, or a game written in a chat with ChatGPT, Claude or Gemini. It goes through the same review as any other game, and publishing is free.
What you need
- A static web build: HTML, JavaScript and assets that run in a browser without a server. A single
index.htmlfile is enough for a small game. - An account for someone aged 18 or over, and a developer account.
- A landscape cover image at 16:9, at least 1280×720. See Media specifications.
- The rights to everything in the game, including AI-generated art, music and text. Check the terms of the tools you used.
1. Get a build
- One HTML file (common from chat tools): save it as
index.html. - A Vite, React, Vue or Svelte project (common from Lovable, Bolt, Cursor or Claude Code): run
npm run build. The build is indist/(sometimesbuild/). Set the base path to relative first; in Vite that isbase: './'invite.config. - Phaser, Three.js or PixiJS: build it the same way, so every library is bundled into the build.
- A game engine (Unity, Godot, GameMaker, Construct): use its web export. See Game requirements.
Open the build from a local web server (for example npx serve dist) and play it once before you upload.
2. Check these before you upload
AI-written code often breaks in a few predictable ways:
- Absolute paths.
/assets/hero.pngfails on Smaz Games; useassets/hero.pngor./assets/hero.png. - Files from other sites. Libraries, fonts and images loaded from a CDN are blocked. Put them in the ZIP.
- API keys. Never leave an API key in the game, including keys for AI services. Anyone can read a game's code. The upload check flags anything that looks like a key, and a flagged build can't be submitted.
- Calls to AI services while playing. A game that calls an AI API from the browser would expose your key, so it is not accepted. Generate content before you build, or run your own server and declare its address (see Outside addresses).
- Pop-ups and
alert(). These are blocked in the player. Show messages inside the game. - Saving.
localStorageandIndexedDBwork. To save to the player's account across devices, add the SDK.
3. Zip and upload
Put the contents of the build folder in a ZIP, with index.html at the top level, not inside another folder. Then follow Getting started from step 5: create a draft, upload the ZIP and cover, add a description and controls, and submit it for review.
Optional extras
- Leaderboards: high scores and fastest times without your own server.
- Saves and cloud data: progress that follows the player between devices.
- Playtests: watch recordings of real players before release.
Review
AI-made games follow the same Review and rejection policy as any other game. Common reasons a game is sent back are a blank screen from a broken path, controls that don't work on the devices you selected, and missing rights to assets.