Submission walkthrough
Submission walkthrough
This page follows the developer console from an empty account to a submitted game, then explains what happens in review.
1. Create your studio#
Go to /developer/onboarding. You need a ZokoGames account first. The form asks for:
- Studio name and a studio URL name (2 to 40 lowercase letters, numbers and single hyphens; it cannot be changed later).
- A support email that players and the review team can reach, and an optional website.
- A payout profile: legal name, country, payout currency (USD or EUR) and method (bank wire, PayPal or ACH). Bank details are never entered here; a payout provider collects them later.
- Acceptance of the developer terms.
You become the studio's owner. Owners and admins can invite members on the Team page.
2. Create the game and fill in the steps#
Create a game with a name (2 to 60 characters), a URL name and a category. The submission wizard has five steps and autosaves.
| Step | What you provide |
|---|---|
| Basics | Short description (20 to 160 characters), description (at least 80 characters of text), controls (at least 5 characters), tags (up to 10; one is recommended), optional FAQ, and the two confirmations: English text and the age rating. |
| Technical | Engine, orientation (landscape, portrait or both), mobile / iOS / Safari friendliness, how progress is saved, whether the game is multiplayer (with minimum and maximum lobby size), whether it has a leaderboard or uses the data module, whether it needs popups, and hosting. |
| Build | Upload a zip, see the validation report. See below. |
| Artwork | Three covers (required) and two preview videos (needed for full launch). See covers and videos. |
| Review and submit | A checklist of what is missing, an optional note for the reviewer, and the Submit for review button. |
Hosting is either hosted by ZokoGames (you upload a zip, recommended) or on your own server (an https address that allows being framed from zokogames.com). Games on your own host only earn when they use the SDK.
Use the note for the reviewer to say how to reach a specific level, which button opens the leaderboard, or how to start a multiplayer room. Reviewers have a few minutes per game; the note saves them hunting.
3. Upload and validate the build#
Drop a zip with index.html at its root (or inside a single top-level folder). Large uploads are sent in parts and can be resumed. The validator then checks, without trusting the archive:
- At most 1,500 files and 250 MB unpacked.
- An estimated initial download of at most 50 MB (a warning above 20 MB, the mobile target).
- No absolute or traversing paths, backslashes, symbolic links, encrypted entries or duplicate paths.
- No executable or server-side files (
.php,.exe,.sh,.jar,.pyand similar). - No suspicious compression ratios.
- It also detects your engine, whether the SDK script is referenced, and warns about case collisions and ignored system files such as
__MACOSX.
A build that fails shows each problem with the offending path. A build that passes is published and, before launch, becomes the active build at once so you can preview it. See the technical requirements for details.
4. Preview#
Open Preview on the game in the console to run the exact build in the portal frame with ads on, and tick through the checklist. See testing.
5. Submit#
The Submit for review button enables when every required checklist item is done. Optional items (tags, preview videos) show as advisory; videos are needed for full launch. Once submitted, the game is locked for editing and builds cannot change. You can withdraw the submission at any time to edit again.
What reviewers check#
A reviewer plays the game and works through a checklist that adapts to your game's settings. It covers:
- Technical. Loads in the portal frame without blocking console errors; initial load reasonable on a mid-range phone (about 10 seconds on 4G); within the size budget; fullscreen and resize work with no layout break at 360 px wide; touch controls on mobile; no unapproved external requests, popups or redirects; audio starts only after interaction and can be muted.
- Gameplay. A new player can start playing within 30 seconds; controls match the description and are explained in game; no soft-locks in the first 10 minutes; the game pauses when focus is lost and during ad breaks.
- Ads (when ads apply). Ad breaks use the SDK and never block gameplay start; rewarded ads grant the reward only after a finished ad; banners use approved sizes and do not cover controls; no third-party ad code.
- Accounts and saves (when the data module or a leaderboard is used). Playable as a guest; progress saves and restores through the data module; leaderboard scores submit and display.
- Multiplayer (when enabled). Lobby, invites and join links work; a player leaving does not freeze the room; minimum and maximum lobby size match the listing.
- Quality and presentation. Original work or properly licensed; content suitable for the declared audience; covers and videos meet the specs; title, descriptions and controls are accurate and free of spam; overall quality competitive for its category.
The full matrix is on the requirements checklist.
The decision#
You get an email and a console notification with one of three outcomes:
- Approved. The game moves to basic launch.
- Changes requested. The reasons are listed (for example: game does not run, performance, ad integration, external links, unclear controls, quality, artwork, listing information, audience flag). Fix them, upload a new build if needed and submit again.
- Rejected. Some reasons are fixable; others are final: copyright or brand misuse, a copy of another game, inappropriate content, or unsafe code. If the reasons can be fixed, you can edit the game and submit again.
The Review history on the submit step shows every decision with its notes.
After approval#
During basic launch updates go live right away. In full launch an update waits for a reviewer before it replaces the live version. To change artwork on a live game, stage the new files and submit them as one artwork review, or compare them first with an artwork experiment.