Publishing
Review and rejection policy
This page lists every reason a version can be refused, sent back or rejected, and how to fix it. It applies the Developer agreement and the Acceptable use policy; if they differ from this page, they apply.
There are three outcomes when something is wrong:
- Refused at upload: an automatic check failed. Nothing is saved. The message says why.
- Changes requested: the version can be published once the problem is fixed.
- Rejected: this version will not be published. Some reasons, marked Not allowed below, mean the game cannot be published in any version.
Feedback always says which rule applies and, where it can, where in the game the problem is.
Refused at upload
| Reason | Fix |
|---|---|
No index.html at the root of the ZIP | Zip the contents of the build folder, not the folder |
| ZIP over 100MB, expanded build over 250MB, a file over 64MB, or more than 1,500 entries | Compress textures and audio, remove unused assets, load large content later |
Unsafe paths, hidden files (including __MACOSX), symbolic links, encrypted entries or duplicate paths | Re-zip without them. See ZIP structure |
| Executables, server scripts, keys or nested archives | Remove them. Upload only the web build |
| A file with a compression ratio over 200:1 | Remove padding or generated filler data |
| Media of the wrong ratio, size, format or length | Follow Media specifications |
| Missing title, description, controls, devices or orientation, or a version label already used | Complete the form. Use a new version label |
| Rights not confirmed | Tick the rights confirmation |
Quality report failures
A version with a failed quality check is saved as a draft but cannot be submitted.
| Reason | Fix |
|---|---|
| A private key, cloud access key, live payment key or access token in a text file | Remove it from the build and revoke it: anything in a web build is public |
| Missing media files | Upload a new version with complete media |
| Files, metadata or media changed after upload | Upload a new version |
Broken or unfinished builds
Usually Changes requested.
- Does not load, shows a blank or black screen, or never leaves the loading screen.
- Crashes, freezes or becomes unplayable during normal play.
- Missing files, often because a path's upper and lower case do not match the file name.
- Relies on features the sandbox blocks, such as cookies, pop-ups,
alert()or files from sites that are not declared, so it fails or loses progress. See The browser sandbox. - Placeholder art or text, debug menus, test levels, cheat keys left on, or developer console output shown to players.
- Too little to play: a game that ends after a minute or two, or a demo that sends players elsewhere for the rest.
- Takes much longer than the performance targets to become playable, or runs far below them on the declared devices.
Controls, devices and orientation
Usually Changes requested.
- Controls do not match How to play, or the game cannot be started or finished with the declared input.
- Mobile or tablet declared, but parts of the game need a keyboard or mouse, touch targets are too small, or the page scrolls or zooms during play.
- The wrong orientation is declared, or UI is cut off at common frame sizes or in fullscreen.
- Keys used by the game scroll the page or trigger browser shortcuts.
Saves
Usually Changes requested.
- Progress is lost on reload when the listing says the game saves.
- One player's progress appears for another player or account, for example because account progress is kept only in browser storage.
- Newer progress is overwritten, or a failed save is shown as saved.
- The SDK box is ticked but the build does not use the SDK, or the game claims account saves it does not have.
Sound and pause
Usually Changes requested.
- The site's mute does not silence all audio, or the site's pause does not stop gameplay.
- Sound or gameplay continues while the tab is hidden or an ad is playing.
- Without the SDK, the game has no sound or pause controls of its own.
- Loud sound plays before the player has interacted.
Content
See Content rules.
| Reason | Decision |
|---|---|
| Content that is not declared, such as violence, horror, mature language, simulated gambling or chat | Changes requested: declare it |
| Content unsuitable for players aged 13 and over | Rejected |
| Pornography or sexual content; any sexual content involving minors | Not allowed |
| Real-money gambling, or betting with anything that can be bought or cashed out | Not allowed |
| Hate, harassment, or content that glorifies violence against protected groups; shock content | Not allowed |
| Promotion of illegal goods, drugs, weapons sales, self-harm or dangerous challenges | Not allowed |
| Political campaigning or advertising inside the game | Rejected |
Rights and originality
| Reason | Decision |
|---|---|
| Characters, music, art, fonts, brands or code you have no licence for, or assets whose licence forbids redistribution in a web game | Rejected until you show permission or replace them |
| A copy or misleading clone of someone else's game, or a game uploaded by someone who did not make it or license it | Not allowed |
| A title, cover or description that uses another game's or company's name to attract players | Changes requested |
| Open-source or asset-store licence terms not met, such as missing credits where required | Changes requested |
| Many near-identical versions of the same game as separate listings | Rejected |
We may ask for evidence of your rights at any time, as the developer agreement says.
Listing and metadata
Usually Changes requested.
- The title, description, screenshots or video show features, modes or art the game does not have.
- Claims of awards, ratings, reviews or player numbers that are not true.
- Fake badges, "free" labels, play buttons or system-style warnings on the cover.
- Tags or a category that do not describe the game, or lists of unrelated keywords.
- Media from another game, or a video that is only a logo or text.
Outside services, links and data
| Reason | Decision |
|---|---|
| The game contacts an address that is not declared under Outside addresses | Changes requested |
| Links to stores, payment pages, donation pages, other game websites or app downloads | Changes requested: remove them |
Opening links without the SDK's openExternalLink, or redirecting the player away from the game | Changes requested |
| Asking for email addresses, phone numbers, real names or locations | Changes requested |
| Its own login form that asks for Smaz Games details or imitates the site | Not allowed |
| Tracking players across games or sites, device fingerprinting, or undeclared personal data collection | Not allowed |
| Personal data stored on your servers without a privacy policy that covers it | Changes requested |
Ads, analytics and payments
See the Monetization policy.
| Reason | Decision |
|---|---|
| Ad networks, ad SDKs, other game sites' SDKs or ad tags in the build | Changes requested: remove them |
Google Analytics (gtag.js), Tag Manager, pixels or other tracking scripts | Changes requested: remove them, use SDK events |
| In-game purchases, real-money payments, subscriptions, ad-removal purchases, cryptocurrency or NFTs | Changes requested: remove them |
| A rewarded ad that is not chosen by the player, is required to progress, or does not grant its reward | Changes requested |
| Buttons that imitate ads, or ads that imitate game controls | Changes requested |
Multiplayer and chat
- Free-text chat available to guests or players under 18, or no profanity filter on player text, including names.
- No way to mute or report another player.
- Private messages between players who are not both adults, voice chat, or links in chat.
- Online modes that do not work during review because servers are down or unreachable, with no message to the player.
Usually Changes requested.
Security and device use
| Reason | Decision |
|---|---|
| Malware, cryptocurrency mining, or hidden work unrelated to the game | Not allowed |
| Code that hides what it does or where it connects. Normal minification is fine | Rejected until explained |
| Excessive CPU, memory or battery use when idle or paused | Changes requested |
| Attempts to escape the sandbox, read other games' data or interfere with the site | Not allowed |
After publication
Approval covers only the build you submitted. We may unlist or remove a live game, with notice where practical, if a problem is found later, if a player report is confirmed, or if your outside services change what the game does. A game that is harmful, illegal or infringes someone's rights can be disabled immediately. An earlier approved version may be restored while you fix an update.
Fix and resubmit
- Read the feedback on the version in your dashboard.
- Fix the problem and upload a new version with a new label, such as
1.0.1. Builds cannot be edited after upload. - Test it in the private preview, then submit it.
- If something in your fix needs explaining, contact developer support and mention the version.
After Changes requested you may resubmit the same version if the feedback concerned something outside the build, such as your outside servers being offline. Each game can have up to 20 versions. If you reach the limit, contact developer support.
Appeals
If you think a decision is wrong, email [email protected] within 30 days. Include the game, the version and why you disagree. Someone who did not make the original decision will look at it where possible, and we reply with the outcome and reason. A rejected version does not by itself mean your account is restricted. Serious or repeated breaches of the developer agreement can lead to suspension of a developer account.