Start here

Getting started

This is the full path from a web build on your computer to a game players can open on Smaz Games.

1. Create a developer account

Create a developer account, or sign in and complete your studio profile. To upload you need:

  • An account for someone aged 18 or over.
  • A verified email address. We send a six-digit code when you sign up.
  • A studio profile. The studio name is shown on your game pages; your legal name and contact details are not.
  • Acceptance of the current Developer agreement.

2. Check your build

Smaz Games accepts static HTML5 builds: HTML, JavaScript, WebAssembly and assets, with index.html at the root of the ZIP. Most engines that export to the web work, including Unity WebGL, Godot, Phaser, Construct, PlayCanvas, Three.js, Babylon.js, Defold, GDevelop and plain JavaScript.

Games run in a sandboxed frame with their own origin. They can use localStorage and IndexedDB, but not cookies, pop-up windows or alert(). Read Game requirements before you export, because some engines need a setting changed.

3. Add the SDK (optional, recommended)

The Smaz Games SDK is one JavaScript file. Without it your game still runs and can save in the player's browser, but it cannot save to the player's account, respond to the site's pause and mute buttons, or offer rewarded ads. Browser storage stays on one device, so games with progress should use SDK saves, which follow a signed-in player to any device.

<script src="./arcade-sdk.js"></script>
<script>
  OpenArcade.init().then(() => OpenArcade.gameplayStart());
</script>

4. Prepare media

You need one landscape cover at exactly 16:9, at least 1280×720. A square icon, portrait cover, up to five screenshots and a gameplay video of up to 20 seconds are optional. See Media specifications.

5. Create a draft and upload

Open the developer dashboard, choose New game and enter a title. Then choose Add build & media and fill in:

  • Title, short description, description and controls.
  • Category and up to 6 tags.
  • Supported devices (desktop, mobile, tablet) and orientation.
  • The build ZIP and your media.
  • Outside addresses: servers your game connects to and sites it links to, if any.
  • Content declarations, such as violence or chat.

The upload is checked straight away. If something is wrong you see the reason and nothing is saved.

6. Preview

Each version has a Private preview link on the dashboard. It opens the exact uploaded build in the same player frame players use. The link lasts 15 minutes; open a new one from the dashboard when it expires. Saves made in a preview stay separate from live progress.

Open the Quality report to see the automatic checks. A build with a failed check cannot be submitted.

7. Submit for review

Choose Submit for review. A reviewer plays the exact build and approves it, asks for changes or rejects it, with written feedback. You get a notification when the decision is made. See Review process.

8. After approval

The approved version goes live on its game page. Its address ends in a short code, such as /game/your-game-x7k, and stays the same for the life of the game. To change anything, upload a new version: the live version stays in place until the new one is approved. See Versions and updates.