Pre-upload checklist
Check these before you upload. Reviewers use the same list, and when they reject a game your dashboard says which item it was.
"Required" items are refused at upload or checked by a reviewer. "Recommended" items keep players around longer, and are never the only reason for a rejection.
Size and start time
- Required A zip may be up to 20MB and 1000 files. No single file may be over 8MB, and everything unpacked may not be over 50MB. A larger upload is refused.
- Recommended Keep what loads before the first screen under 20MB, and have the game start within 10 seconds on a mid-range phone. This goes for linked games too.
- Recommended Load music and large images when they are needed, not all at the start.
Start straight into the game
- Recommended Start the game right away, without a logo screen, title screen or menu. One tap to start is plenty.
- Required A reviewer plays the game. A game that does not start, or stops working while played, is rejected.
Controls and phone support
- Required Pick at least one way to play (keyboard, mouse, touch) when you upload. A reviewer checks it against the game and corrects it before it goes public.
- Recommended Pick touch only after trying the game on a phone. Only games with touch show up under "Works on phones".
Saving progress
- Required A game played from uploaded files runs in an isolated frame and cannot use browser storage (localStorage, IndexedDB, cookies). Reaching for storage throws an error, so wrap it in try/catch so the game keeps running.
- Required If the game has progress to come back to, such as levels or unlocks, tick "This game doesn't save your progress". The game page then tells players.
Browser features that are off
- Required alert(), confirm() and prompt() windows never open. Draw messages and questions inside the game.
- Required Pointer lock (capturing the mouse) is not available. Design controls that work without it.
- Required Opening new windows, submitting forms, downloading files and navigating to another page are blocked too.
- Required Requests to other sites or servers are blocked. A game can still read the files it ships with (JSON, text, images, sound, fonts) through fetch() or XMLHttpRequest, with a relative address such as "levels/1.json".
Sending scores
- Required A game that goes public must have <script src="/sdk/v1.js"></script> on its entry page (index.html). The path is the same for a public game, a private game and the review preview. At review the hub looks for this line in the uploaded files, and without it the game goes public only when a moderator accepts an exception. A full address starting with https://, or a copy of the SDK, does not count. A private game opens without the SDK and is checked when it asks to go public.
- Required Send the lifecycle events: JonGem.ready() when the game is ready, JonGem.start() when a round starts, and JonGem.end() when it ends. Send scores with JonGem.score(board, score) before the end. They then show under the game as "This play's score", and rankings will use them.
- Required Declare 1 to 5 scoreboards when you upload. The board ids your game sends scores to must be the ones you declared. A score sent to a board you did not declare never reaches a ranking.
- Required Give each board the lowest and highest values a play can really reach. A score outside that range is refused, or kept off the ranking until it is checked.
- Recommended Even a game where a score means nothing, like a toy or a story, can often use a board such as "time to finish" (a time, lower is better). Consider that first.
- Required If the game really has no score, tick "This game has no score" when you upload. Put in the SDK with ready, start and end anyway. A moderator checks that the game has no score and decides whether to accept the exception.
- Recommended After you upload, the "SDK test" under the preview on your creator page shows the events and scores your game sends as they arrive, and points out a board you did not declare.
- Recommended A board name starts with a lowercase letter and has lowercase letters, digits and underscores, up to 32 characters (such as best_score). A score is a whole number from 0 up, and a round reports on 5 boards at most. Send values during a round with JonGem.progress(board, value).
- Required On a board marked replayable, the server checks a top record by replaying the game with the same seed and inputs. The game announces itself with JonGem.ready({ start: yourStartFunction }), begins a round inside JonGem.start(function () { ... }), and on every fixed step passes its input as a whole number from 0 to 16777215 (such as key bits) to JonGem.tick(input) and uses only the value it returns. Randomness comes only from JonGem.random(), nothing moves before the round begins, and neither the clock (Date, performance) nor screen pixels may change the score. Break any of these and top records are held as "the replay gave other values".
- Recommended A copy opened from your own computer has no SDK. Call it only when window.JonGem is there, as below, and the game keeps running.
<script src="/sdk/v1.js"></script>
<script>
const jongem = window.JonGem;
jongem?.ready();
function startRound() {
jongem?.start();
}
function endRound(score) {
jongem?.score('best_score', score);
jongem?.end();
}
</script>
Cover, screenshots and description
- Required A cover image is required: a still PNG, JPG or WebP, 16:9 or 16:10, at least 1280×720, up to 2MB.
- Recommended You can add up to 4 screenshots of the real game, 2MB each. One or two already help players choose.
- Required The cover, screenshots, title and description must match the game. Dressing it up as another game gets it rejected.
- Required Use only tags that fit the game. Piling on unrelated tags gets it rejected.
- Recommended If you made it with AI tools, name them in "AI tool used" (for example Claude, Cursor). The game page shows it.
Your own game
- Required Copies of another game, and bought assets or templates uploaded with little of your own added (asset flips), are not accepted.
- Required Do not upload the same game more than once. Upload a fixed build as a new version from your creator dashboard.
- Required Where the images, music and code came from, and your right to use them, must be clear. If they cannot be confirmed, the game is rejected.
Content rules
- Required Games must be fit for every age. Adult or sexual content, excessive violence or hate, and gambling simulations are not accepted. The terms have the details.
- Required A fan game built on another work's characters or world must be marked as one, naming the original and its rights holder. Using the original's own images, music or code is not accepted.