To publish an HTML5 game, you export a production build with an index.html entry point, zip it, and upload it to a site that hosts and lists web games. On Mayavoo you do that from the creator studio or through the creator API, add a cover, screenshots and instructions, and the team plays the game before it goes live.
The rest of this guide walks through each step, from the build folder to the moment your game page is public.
Step 1: prepare a clean build
Most engines and bundlers can export a web build. What you upload should be the finished output, not the project.
- Put
index.htmlat the root of the ZIP, or inside a singledist/folder. - Keep the HTML, CSS and JavaScript files plus an
assets/folder for images, sound, fonts and data. - Use relative asset paths, so the game loads from wherever it is served.
- Leave out source files,
node_modules, source maps, config files and assets the game never loads.
Mayavoo minifies code during processing, but bundling and pruning before you zip still gives you a smaller, faster upload.
Step 2: write the listing
A game page is what players see before they press play, so treat it as part of the release. Mayavoo asks for:
| Field | What to write |
|---|---|
| Title | The game's name |
| Short description | One line that says what the player does |
| Description | The longer pitch: genre, goal, what makes it different |
| Instructions | Controls and how to win |
| Category | The genre players will browse |
| Devices | Desktop, mobile, tablet, or a mix |
| Cover and screenshots | One cover and at least one screenshot |
If you list mobile or tablet, test on a small screen. The player's menu button sits in the bottom-right corner there, so keep your own buttons out of that spot. You can also lock the game to wide or tall screens, or let it run either way.
Step 3: upload and submit
In the browser, sign in with Google or GitHub, complete your creator profile and upload from the creator studio.
If you would rather script it, the Mayavoo creator API covers the same flow. Create a read-and-write key in your account, then:
- Create a draft game with a title.
- Reserve uploads for the cover, screenshots and build ZIP, and send each file to the signed URL you get back.
- Fill in the listing with a PATCH request.
- Submit the build key as a new version and poll its status.
Each write takes an idempotency key, so a retried request does not create a second game. Mayavoo also offers a Node.js upload script, an example manifest, an OpenAPI schema and a plain-text guide you can hand to an AI coding agent.
Step 4: review and go live
A submitted version moves from queued to processing to in review, then to approved or rejected. Processing checks the files; a person then plays the game and looks at its network behavior. Nothing goes live on its own, and a new build never replaces the live one until it passes review.
Once approved, the game gets its own page and shows on your creator profile. Players open it in the browser, with no download and no account needed. Edits to the text and images update the live page right away; a new ZIP starts a fresh review.
When another route fits better
If you want to sell the game or offer a paid download next to the web version, a store like itch.io is built for that. Mayavoo is the pick when you want a free, reviewed home where players can just press play. You keep ownership of everything you upload.