Skip to main content
Publishing on Summer Games is free. You make a store page in Studio, upload your build and click Publish. Your game goes live on summer.games as soon as Summer’s automatic checks pass. There is no review to wait for. Start at summerengine.com/studio/upload, or click Publish a game in Grow. This is the one place to upload a game; the Upload button on summer.games brings you here too. You can fill in the first step before you sign in; Studio keeps your draft and asks you to sign in when you save. Your saved games are in Your games at summerengine.com/studio/store. See How do I publish my game on Summer? for the whole path, with or without your agent.
Want your AI agent to do every step? It fills the store page, makes the art, uploads the build and asks you before it goes live. See Agent permissions. See Create and publish your game.

The steps

Studio walks you through one step at a time. You can go back to any step.
1

How you earn

Free to play + Sparks (anyone plays for free; you earn from the Sparks players spend in your game) or a Paid game (players buy it once). This decides what the Get paid step asks for. What Summer takes is on What does it cost to publish?.
2

Game and targets

Give your game a title (up to 60 characters) and choose its targets: Web, macOS, Windows, Linux, iPhone and Android. Targets decide which store pages you fill next:
  • Web, macOS, Windows or Linux open the Desktop store: summer.games and the Summer Games desktop app.
  • iPhone or Android open the Mobile store: the Summer Games apps for iPhone and Android.
A build is optional here; your builds, one per platform, go in Check and publish. If a jam is open, you can enter it here: see Summer Games Jam. Click Save and continue. This makes a private draft of your store page. It does not submit anything.
3

Desktop store

The text and art for summer.games and the desktop app, with a live preview next to the form: a tagline (up to 80 characters), a description (120-300 characters), 3-8 tags, key art, 4-8 screenshots and an icon. A trailer and capsule art are optional. See Store page text and Store art.
4

Mobile store

The same for the phone apps, with a phone preview: a shorter description (120-170 characters), key art, 3-8 screenshots and an icon. Same as desktop copies your desktop text once; Use desktop icon reuses the icon.
5

Get paid

For a paid game: set your price, then connect Stripe so players can buy it. For a free game with Sparks, this step is Join the Creator Program and shows what the program pays and when; you do not need it to publish. See Earnings & payouts.
6

Check and publish

Add a build for each platform (see Your build below). The Before launch checklist shows what is still needed to go live and what makes the page shine. Each row links to its fix. When nothing required is left, click Publish: your game goes live as soon as the automatic checks pass. Or click Schedule… to pick a time with Go live at.
7

Live

Where your game is on its way to players, and what each platform gets now.
The full dashboard of a game (Full dashboard on its page, in Your games) has every field in tabs: Store page, Audience (platforms, content classification, languages, system requirements, release date), Builds and Sales.

Your build: browser play or downloads

In Check and publish, Studio asks What are you uploading?: A Summer Engine export (one file with every platform, made with Summer) or A zip for each platform (Web, Windows, macOS and Linux, each in its own box).
  • A Summer Engine export asks for a version, such as v1.0.0.
  • A lone .exe or .dmg (up to 40 GB) is kept privately. It is not offered as a download.
  • Studio does not take iPhone and Android app files (.ipa, .apk) or macOS installers (.pkg). Phone players get a Summer Engine export.
  • Without a web export, players download your game instead of playing it in the browser.
  • Games that use C# (.NET) need a download per platform; they do not run in the browser or the Summer Games apps.
Large uploads resume if they stop. Keep the tab open until the upload finishes.

Web exports

summer.games plays any web export with index.html at the root of its .zip:
  • Godot’s standard Web export uses the Compatibility renderer (WebGL 2). Export to Web, zip the contents of the export folder, and upload it.
  • Summer’s web export (summer_export_game, format download, target web) runs Forward+ or Mobile projects on WebGPU. See Export your game.
  • Thread support off plays on the game page. A build with threads opens in its own tab.
  • Other engines’ web builds work the same way.

Going live

There is no human review before your game goes live. A live store page and a released version are two things:
  • A web export and downloads go to players as soon as the page is live.
  • A Summer export goes out when you pick it under Versions and click Promote to production. Uploading a new version never replaces the live one by itself.
Editing a live page starts a new draft. Players see it when you publish it.
Share a preview. On the store page, Share preview makes a private link that expires in 1 hour, 1 day or 7 days. Anyone with the link sees your saved page before it is on Summer Games.

With your agent

In Studio, ask the assistant “publish my game”. It opens Publish a game, fills the title and targets, and walks the store page with you. It never presses Publish unless you ask for exactly that. See Use the agent. From Claude Code, Codex, Cursor, or Claude and ChatGPT with the full Summer MCP (https://mcp.summerengine.com/mcp), your agent does every step. It asks you before the game goes live, and the game is live as soon as the automatic checks pass. If Publish is off in your Agent permissions, it gives you an approval link instead. The version of Summer made for the ChatGPT app directory does not publish. See Approvals.
Does this not help you? Reach out on Discord!