Skip to main content
After the store page is filled and the game is exported, your agent uploads the build and submits. In Studio you do the same under Check and submit; see Publish your game. Your export is uploaded in resumable 64 MiB parts. Summer checks it on iPhone, Android, Mac and Windows. Submit sends the page, the build and a proposed price, and publishes nothing. The owner gets an approval link. Your export is uploaded in resumable 64 MiB parts. Summer checks it on iPhone, Android, Mac and Windows. Submit sends the page, the build and a proposed price, and publishes nothing. The owner gets an approval link.

​
1. Upload the build

summer_publish_build uploads the file from your disk: a store bundle, a web build or a download. The first call shows what it will upload; the second, with confirm: true, uploads it.
1. Preview
It returns the exact game, file, SHA-256, size and version. Your agent shows you this and asks.
2. Upload
Store bundles upload in 64 MiB parts, web builds in 16 MiB parts. If the connection drops, call it again with the same file and version: it continues the same upload and skips the parts already stored. Web builds and downloads are store versions, one per platform. A web .zip is checked before upload: index.html at its root, at most 2,000 files and 500 MiB.
On a game that is already live, a finished web build or download goes live at once. So on a live game only the owner can finish one, in Studio.
Without the npm MCP (a hosted agent that has the file elsewhere), use the hosted steps. Store bundle: summer_build_begin_upload, summer_build_sign_parts, PUT each part with every returned header, summer_build_complete_upload until ready or failed. Web build or download: summer_store_version_begin_upload, summer_store_version_sign_parts, PUT each part, summer_store_version_complete. See the tools reference.

​
2. Wait for the checks

summer_build_status shows each store bundle’s state: uploading, processing, checking, ready or failed. summer_store_version_status does the same for web builds and downloads: awaiting_upload, processing, ready or rejected. Summer checks a bundle on every platform it lists. A failed build says what to fix; see Troubleshooting.

​
3. Look at it first (optional)

A private link to the saved page on summer.games. It is hidden from search, and Buy and Play do nothing. It expires after 1h, 1d or 7d.

​
4. Check what is missing

summer_store_get_listing returns the publish checklist for each store. Fix everything it lists before you submit. Read it again after each change.

​
5. Submit

It checks the publish checklist first. Then it returns awaiting_owner_approval and an approvalUrl. Nothing is published. Give the owner the link. To withdraw it: summer_store_cancel_submission with the approvalId.

​
What happens next

  1. The owner opens the link and clicks Approve publishing. See Approve publishing.
  2. Summer staff review the page.
  3. When the review passes, the game goes live. No second click.

​
Updates

Export again with a new version, upload it the same way, and submit again. Players keep the current version until the new one is live.

​
Ask your agent

Upload my build and submit it. Your agent uploads, waits for the checks, submits, and gives you the approval link.

Does this not help you? Reach out on Discord!