Publishing
What to send, how a game moves from draft to live, how a new build reaches players, and how to upload from a script.
The build
A build is a ZIP of static files that runs in the browser; nothing is executed on our side. The uploader checks these rules and refuses a build that breaks one:
index.htmlsits at the archive root, spelled exactly that way. Zip the contents of your folder, not the folder. A zero-byteindex.htmlcounts as missing.- The filename ends in
.zip, in lower case. - Limits: 30MB compressed, 200MB extracted and 2000 files.
- No entry's path contains
..or starts with/. - Internal references (images, stylesheets, scripts) are relative. See Runtime.
- Nothing your game loads or calls comes from outside the build. See Runtime.
- A file's content type comes from its extension. These are recognised:
.avif, .bmp, .css, .flac, .gif, .glb, .gltf, .htm, .html, .ico, .jpeg, .jpg, .js, .json, .m4a, .map, .mjs, .mp3, .mp4, .ogg, .opus, .otf, .png, .svg, .ttf, .txt, .wasm, .wav, .webm, .webmanifest, .webp, .woff, .woff2, .xml. Anything else is served asapplication/octet-stream, which a browser downloads instead of running, so a module script or stylesheet with another extension fails to load. Do not ship pre-compressed files (.br,.gz,.unityweb): they are served as stored and will not load. - Zero-byte files are dropped when the ZIP is extracted. A game that fetches one gets a 404.
Artwork and screenshots
| Slot | Required | Shape | Minimum | Formats | Max file |
|---|---|---|---|---|---|
| Icon | Yes | 1:1 | 512 × 512 px | JPEG, PNG, WebP | 5MB |
| Thumb | Yes | 16:9 | 640 × 360 px | JPEG, PNG, WebP | 5MB |
| Hero | No | 16:9 | 1920 × 1080 px | JPEG, PNG, WebP | 10MB |
| Screenshots | No, 0 to 5 | Any | 1280 × 720 px | JPEG, PNG, GIF, WebP | 5MB each |
| Achievement badge | One per achievement | 1:1 | 256 × 256 px | JPEG, PNG, WebP | 2MB |
- The minimum applies to each side, not to the pixel count. A 1080 × 1920 px portrait image is refused for the hero, because its width is under 1920 px.
- An achievement badge must already be square.
- The thumb is your listing image in browse and search, so it has to read at small sizes. The hero heads your game page and is the share image, falling back to the thumb, then the icon.
Rating, the content floor, and demos
Pick the PEGI band that matches your content. A game whose content does not match its band is sent back.
- PEGI 3: no violence or mature themes.
- PEGI 7: mild fantasy violence, or mildly scary content.
- PEGI 12: moderate violence, mild language or suggestive themes.
- PEGI 16: realistic violence, strong language or mature situations.
- PEGI 18: explicit adult content. It is accepted, behind an age gate.
The content floor applies at every rating, including PEGI 18: no sexual content, no real-money gambling, no hate speech, nothing illegal. It covers what your game links to as well as what it contains.
Demos are welcome. A demo is a game whose free part ends and points players elsewhere to continue. Four things must hold: the free part reaches a real ending (a finished round or a completion screen, not "you are out of lives, buy more"); the prompt appears only at that ending, never mid-session and never blocking a retry; the title and description say it is a demo; and the link goes to a purchase page, not to an ad network, a mailing list or a download. A demo is labelled as one in the catalogue, and a demo whose full version is sold off Gamemoor is never featured.
Money
Games are free to play. The one money path is tips: a Stripe Checkout on your game page that pays your own Stripe account. There is no in-game purchase, and no checkout your game can open.
- You pick the country you are paid in before Stripe sets up your account, and it cannot be changed afterwards. Payouts go to the United States, the United Kingdom, the EEA, Canada and Switzerland. From anywhere else you can publish, but tips are not available.
- The tip button appears only once Stripe reports that your account can take charges and receive payouts. Finish the Stripe onboarding: tips can read as switched on in the portal while no button shows.
Player feedback
Signed-in players can send you a private message from your game's page, once you switch feedback on for the game. It takes effect at once, with no review.
- A message carries its category, the date and the build the player was on. You see the player's username only if they chose to show it, and never their email address. There is no way to reply.
- A script can read the inbox with a token. See Reading feedback from a script.
- Links in a message are shown as plain text. Report is for abuse, not for feedback you disagree with.
Submitting, and what happens next
- Submitting moves the game to
review. You are emailed the decision, either way. - You can withdraw a submission while it is in
review. The game goes back todraft. Uploading a build does the same. - A rejection returns the game to
draftwith the reviewer's reason, which is emailed to you and shown on My games. Fix it and submit again. - Your release date is set once, on the first approval. Unpublishing and coming back does not put you at the top of New releases again.
- Your game's address is fixed once it has been live. Renaming the game afterwards changes the title and leaves the address and the links to it alone.
The lifecycle
| Status | Public | Listing edits | Build uploads | How it moves on |
|---|---|---|---|---|
draft | No | Saved directly. | The new build serves at once. | → In review: you submit it. |
review | No | Not editable. | Allowed. The upload withdraws the game to draft. | → Live: Gamemoor approves it. → Scheduled: Gamemoor approves it for a release date. → Draft: Gamemoor rejects it with a reason, or you withdraw it or upload a build. → Suspended: Gamemoor takes it down. |
scheduled | No. It goes public at its release time. | Not editable. | Allowed. The upload drops the release date and withdraws the game to draft. | → Live: its release time arrives, or Gamemoor releases it early. → In review: Gamemoor sends it back. The release date is dropped. → Draft: Gamemoor rejects it with a reason, or you upload a build. The release date is dropped. |
live | Yes | Staged as a pending edit for review. The game stays live. | Staged. Players keep the approved build until Gamemoor promotes the new one. | → In review: Gamemoor moves it there. No developer action does. → Suspended: Gamemoor takes it down. → Unpublished: you unpublish it. |
archived | No | Saved directly. | Refused. | → In review: you re-submit it, and it goes through review again. |
suspended | No | Saved directly. | Refused. | → Live: Gamemoor reinstates it. You cannot. |
- Only
livegames have a public page. One exception: Moor's Club members can play ascheduledgame 48 hours before its release date. Have your build ready by then. - A release date is optional. With none, your game goes live as soon as it passes review. A date has to be at least 3 business days after you submit. You can change it while the game is in
review; once the game isscheduled, only Gamemoor can, and you are emailed. If the date has passed by the time the game is approved, it goes live at once.
Builds
Each upload on the Builds tab is kept as its own version. What an upload does depends on the game's status (see the table above).
- On a
livegame the upload is staged: players keep loading the approved build until Gamemoor promotes the new one. Promotion sends no email, so check the tab. Open this build plays a staged build in your owner-only preview before it ships. - In
review, an upload withdraws the game todraft, so the build that is reviewed is the one that was submitted. No email is sent: checkwithdrawnFromReviewin the upload response, and hold uploads while a review is open. A withdrawal is not a rejection. - Rolling back is yours; promoting is ours. On a
draftgame, any build that was active before has Roll back to this build. On alivegame, any build that was live before has it, and players load it on their next request. A build that was never live cannot be rolled back to: upload it again and it goes through review. Rolling back is not offered inrevieworscheduled. - Only the newest 3 builds keep their files, staged builds included. An older build stays in the history without its files and cannot be activated or rolled back to. The build that is serving, and the newest build that was live before it, are always kept.
- Treat every build you upload as public. Do not upload anything embargoed, confidential or licensed elsewhere before you are ready to publish it.
Scripts and CI
A developer access token lets a script do without a browser what you do in the portal up to review: create a game, fill in its listing and artwork, upload a build, and submit it. It can also read your players' feedback. Review, approval and release are the same as for a game you submit by hand. Create a token under Access tokens in the portal. It starts with gmd_ and is shown once: a lost token is revoked and replaced, never recovered.
| Scope | Allows |
|---|---|
builds:write | Uploads a build. |
listing:read | Reads the two export documents and the achievement list. |
games:write | Creates a draft and edits it, edits a listing, uploads artwork and screenshots, and adds achievements. |
games:submit | Sends a draft, or an unpublished game, to review. |
feedback:read | Reads the feedback players sent about your games, as your inbox shows it. |
- Only the endpoints in the table below take a token. Everything else needs a browser session: deleting a draft, withdrawing from review, unpublishing, release dates, rolling back builds, editing or retiring an achievement, switching, marking or reporting feedback, money, your profile, and tokens themselves.
- Send it in an
Authorization: Bearerheader and nowhere else: never a query string, cookie or form field. Revoking is immediate. - A token expires after 90 days unless you tick Never expires. You can hold at most 5 active tokens; revoked and expired ones do not count.
- Each token is limited to 10 requests a minute, counted per token and not per IP address, so a shared runner does not share it. Pace your loop.
gameIdis the 26-character id in your game's portal URL,/developer/games/<id>, or the onedrafts/createanswers. A game that is not yours answers404with codeNOT_FOUND, the same as an id that names no game.- A token without the scope an endpoint needs is answered
403with codeFORBIDDENand the scope named. - A JSON body that is not JSON is answered
422with codeINVALID_JSON. One that breaks a rule is answered422with codeVALIDATION_ERROR: the first problem inerrorasfield: message, every problem indetails.
Endpoints a token reaches
Every answer is { success, data } or { success: false, error, code }, except the three exports, which answer a bare document when they succeed. Multipart uploads need no Origin header.
| Method | Path | Body | Scope |
|---|---|---|---|
| POST | /api/developer/drafts/create | JSON: the details below. Answers { gameId, slug }. | games:write |
| POST | /api/developer/drafts/{gameId}/update | JSON: the details below, all sent again. A draft only. | games:write |
| POST | /api/developer/upload-icon?gameId={gameId} | Multipart: file. The same for upload-thumb and upload-hero. Answers { url }. | games:write |
| POST | /api/developer/upload-screenshot | Multipart: file, pendingGameId, index (0 to 4). Answers { url }. | games:write |
| POST | /api/developer/drafts/{gameId}/screenshots | JSON: { screenshots: [urls to keep] }. Removes the others; adds nothing. | games:write |
| POST | /api/developer/games/{gameId}/upload-achievement-icon | Multipart: file. Answers { url } for icon_url below. | games:write |
| POST | /api/developer/games/{gameId}/achievements | JSON: { title, description, icon_url, trigger_type, trigger_value, slug? }. Creates a draft achievement. | games:write |
| GET | /api/developer/games/{gameId}/achievements | None. Lists the game’s achievements. | listing:read or games:write |
| POST | /api/developer/games/{gameId}/update | JSON: the details below, plus optional screenshots (a JSON array as a string) and icon_url, thumb_url, hero_url from an upload. For a game past draft; on a live game the edit goes to review. | games:write |
| POST | /api/developer/upload-game?gameId={gameId} | Multipart: file (the ZIP). | builds:write |
| POST | /api/developer/drafts/{gameId}/submit | JSON: {}, or { release_at?, early_access? }. Answers { status: "review" }. | games:submit |
| POST | /api/developer/games/resubmit | JSON: { gameId }. An unpublished game only. | games:submit |
| GET | /api/developer/games/{gameId}/export/listing and /export/achievements | None. | listing:read |
| GET | /api/developer/games/{gameId}/export/feedback | None. Optional ?since= or ?cursor=. Answers one page of player feedback. | feedback:read |
- The details:
title(up to 100 characters),genre(one of action, adventure, arcade, board, cards, casino, casual, creative, music, puzzle, racing, rpg, sim, sports, strategy, trivia, word),pegi_rating(3, 7, 12, 16 or 18),tags(a string, comma-separated or a JSON array of strings, at most 5),short_description(up to 160 characters),description(150 to 2000 characters) andmobile_support(full,limitedordisabled). A draft may be saved incomplete; submitting checks it. - Submitting needs complete details, a build, an icon and a thumbnail. Otherwise it answers
422with the missing steps indetails.missing. Screenshots and achievements are optional. - On a draft, an upload is saved to the game as it lands. On a live game it is held until you send the listing through
games/{gameId}/updatewith the returned URL, and it goes to review with that edit. trigger_typeismanual,score_thresholdorplay_count. See Achievements.
{
"title": "Lantern",
"genre": "puzzle",
"pegi_rating": 7,
"tags": "cozy, light",
"short_description": "Light every room.",
"description": "At least 150 characters…",
"mobile_support": "full"
}# Create a game, fill it in and submit it for review.
# The token needs games:write, builds:write and games:submit.
AUTH="Authorization: Bearer $GAMEMOOR_TOKEN"
API="https://gamemoor.com/api/developer"
# 1. The draft. Keep the gameId.
GAME_ID=$(curl --fail-with-body -s -X POST -H "$AUTH" \
-H "Content-Type: application/json" \
-d @details.json "$API/drafts/create" | jq -r .data.gameId)
# 2. Artwork: icon and thumbnail are required, the hero is not.
curl --fail-with-body -X POST -H "$AUTH" -F "file=@icon.png" "$API/upload-icon?gameId=$GAME_ID"
curl --fail-with-body -X POST -H "$AUTH" -F "file=@thumb.png" "$API/upload-thumb?gameId=$GAME_ID"
curl --fail-with-body -X POST -H "$AUTH" \
-F "file=@shot-1.png" -F "pendingGameId=$GAME_ID" -F "index=0" "$API/upload-screenshot"
# 3. The build.
curl --fail-with-body -X POST -H "$AUTH" -F "file=@build.zip" "$API/upload-game?gameId=$GAME_ID"
# 4. Submit. A 422 lists what is still missing in details.missing.
curl --fail-with-body -X POST -H "$AUTH" \
-H "Content-Type: application/json" -d '{}' "$API/drafts/$GAME_ID/submit"# Upload a build from CI.
curl --fail-with-body -X POST \
-H "Authorization: Bearer $GAMEMOOR_TOKEN" \
-F "file=@build.zip" \
"https://gamemoor.com/api/developer/upload-game?gameId=$GAMEMOOR_GAME_ID"
# {"success":true,"data":{"buildId":"01J…","activated":false,
# "withdrawnFromReview":false,"releaseDateDropped":false,
# "fileCount":42,"sizeBytes":1048576}}activatedistruewhen the build is serving (adraft) andfalseon a live game, where it is staged.withdrawnFromReview: truemeans the upload took the game out of review.releaseDateDropped: truemeans it also dropped an approved release date.- A failed upload is answered with a status and a code. See Troubleshooting.
# Your published listing and your achievement definitions, as JSON.
# Both answer a bare document, not the { success, data } envelope.
curl -H "Authorization: Bearer $GAMEMOOR_TOKEN" \
"https://gamemoor.com/api/developer/games/$GAMEMOOR_GAME_ID/export/listing" \
-o listing.json
curl -H "Authorization: Bearer $GAMEMOOR_TOKEN" \
"https://gamemoor.com/api/developer/games/$GAMEMOOR_GAME_ID/export/achievements" \
-o achievements.jsonBoth exports are stable documents to commit next to your game: no timestamps and no generated ids, so an unchanged listing gives an identical file. The achievements export holds every achievement with its state, drafts and retired ones included. It holds definitions only, never who earned what. There is no import.
Reading feedback from a script
# Player feedback sent after the newest message you already hold.
curl --fail-with-body -H "Authorization: Bearer $GAMEMOOR_TOKEN" \
"https://gamemoor.com/api/developer/games/$GAMEMOOR_GAME_ID/export/feedback?since=2026-10-14T09:00:00Z"
# {"format":1,"game":{"id":"01J…","slug":"lantern"},
# "messages":[{"id":"01J…","category":"bug","created_at":"2026-10-15T08:12:40.511Z",
# "build_id":"01J…","body":"The jump does nothing on level two.","username":null}],
# "has_more":false,"next":null}- The feedback export holds the messages your inbox shows, archived ones included, oldest first. A message you reported, or one Gamemoor hid, is not in it. Reading does not mark a message read.
- Each message has its
id, which never changes,category(bug,ideaorother),created_at,build_id(the build that was serving when it was sent, ornull),bodyandusername. The username is there only when the player chose to show it, otherwisenull. Nothing else about the player is. sinceis optional: an ISO-8601 time with its zone (2026-10-14T09:00:00Z) or a date (2026-10-14, midnight UTC). Only messages created after it are answered. Pass the newestcreated_atyou hold to fetch what is new.- One call answers at most 100 messages. When
has_moreistrue, call again with?cursor=and thenextvalue, withoutsince, until it isfalse. A badsinceorcursoris answered422with codeVALIDATION_ERROR. - Reading is all a token can do with feedback. Marking, archiving and reporting stay in the portal.
The store listing
- Editing a live listing does not take your game down. The edit is staged as a pending revision for review. The game stays live on its current listing until the edit is approved, and a rejection leaves that listing as it was. You are emailed either way, and a second save replaces the pending edit.
- New art and screenshots on a live game go to review with the edit. Players keep seeing the current ones until it is approved.
- Limits: short description at most 160 characters, long description 150 to 2000 characters, at most 5 tags.
Unpublishing and suspension
- Unpublishing is yours, from My games, and only from
live. The game becomesarchived(shown as Unpublished) and leaves public listings. Play history, scores and achievements are kept, and you can still edit the listing. Re-submitting puts it back intoreviewfor a full review, with its original release date. - You can delete only a
draft. Deleting removes the game, its builds, its achievements and its files. Once a game has plays, scores or tips it cannot be deleted, and your account cannot be deleted while you own a game. - Suspension is the one status you cannot leave. You are emailed with the reason. You can still edit the listing; you cannot upload a build, unpublish or re-submit. Only Gamemoor can restore the game. Reply to the email to appeal or to ask.