> ## Documentation Index > Fetch the complete documentation index at: https://docs.summerengine.com/llms.txt > Use this file to discover all available pages before exploring further. # Export your game for Summer Games > Which file the Summer Games store takes for iPhone, Android, Mac, Windows and the web; how summer_export_game makes it; export templates from the Summer CDN; file names, icons and signing. The Summer Games store takes two kinds of build. Which one you need depends on where players run your game. | Kind | Players run it | Platforms | Made by | | - | - | - | - | | **Store bundle** | inside the Summer Games apps | iPhone, Android, Mac, Windows | `summer_export_game` (default) | | **Web build or download** | in the browser on summer.games, or as a file they download | web, Mac, Windows | `summer_export_game` with `format: "download"` | Three kinds of build. A store bundle zip runs in the Summer Games apps on iPhone, Android, and for multiplayer games Mac and Windows. A web build zip with index.html plays on summer.games in the browser. A download is a Mac or Windows app that players download. Three kinds of build. A store bundle zip runs in the Summer Games apps on iPhone, Android, and for multiplayer games Mac and Windows. A web build zip with index.html plays on summer.games in the browser. A download is a Mac or Windows app that players download. ## Which one do I need? | Target | Build | Store platform | Rule | | - | - | - | - | | iPhone | store bundle | `ios` | any game | | Android | store bundle | `android` | any game; needs Summer Engine 0.7.1 or later | | Mac app | store bundle | `macos` | multiplayer games (with a server) only | | Windows app | store bundle | `windows` | multiplayer games (with a server) only | | Web (play in the browser) | web build | `web` | Forward+ projects; not the Compatibility renderer | | Mac download | download | `macos-universal` | any game | | Windows download | download | `windows-x64` | any game | `summer_publish_build` uploads every kind. See [Upload and submit](/publishing/upload-and-submit). A game **without a server** can use the store bundle only for iPhone and Android. For Mac and Windows it uses a download. One store bundle serves every platform it lists, so it carries every texture format those platforms need: ETC2/ASTC for iPhone, Android and Mac, S3TC/BPTC for Windows. In **Project Settings → Rendering → Textures**, turn on the formats your platforms need. ## Export with your agent The local summer-engine MCP runs Summer Engine on your computer without a window. You do not need to open the editor. ```json title="Store bundle for iPhone and Android" theme={null} { "tool": "summer_export_game", "targets": ["ios", "android"] } ``` ```json title="Web build" theme={null} { "tool": "summer_export_game", "targets": ["web"] } ``` ```json title="Mac download" theme={null} { "tool": "summer_export_game", "targets": ["macos"], "format": "download" } ``` ```json title="Windows download" theme={null} { "tool": "summer_export_game", "targets": ["windows"], "format": "download" } ``` | Input | Meaning | | - | - | | `project` | Folder with `project.godot`. Defaults to the open project, then the working folder. | | `targets` | Bundle: any of `macos`, `windows`, `ios`, `android` (omit for every platform the project declares). Download: exactly one of `web`, `macos`, `windows`. | | `format` | `bundle` (default) or `download`. `["web"]` means `download`. | | `out` | Output path. Defaults to `/.summer/exports/`. | | `debug` | `true` for a debug build. | | `timeoutSeconds` | Default 900. The first export imports every asset, so it is slow. | It returns the file path, its SHA-256, its size, and for a bundle the manifest: main scene, platforms and whether it has a server. For a download it also returns the store platform to upload it as. For a store bundle the MCP writes a named preset `summer.games ` into `export_presets.cfg`. It only changes that preset's platform options. ## Export in the editor Open **Project → Export**, pick the **summer.games** preset and click **Export Project**. You get one `.zip`. See [Publish your game](/build/publish). ## What is in each file A `.zip` in the `summer.bundle.v1` format: | Entry | What it is | | - | - | | `summer-bundle.json` | The manifest: Summer version, engine, main scene, platforms, file hashes. | | `client.pck` | Your game for players. | | `server.pck` | Multiplayer games: the server. | | `config/` | Multiplayer games: Summer settings. | At most 16 entries and 40 GiB. The platforms in the manifest must match the platforms you upload it for. Summer runs `client.pck` on its own engine in the Summer Games apps, so you need no export template. A `.zip` with `index.html` at its root. At most 500 MiB, 2,000 files and 200 MiB per file. Threads off. summer.games plays it in a frame. It uses Summer's **WebGPU Forward+** web template (`web_summer_jspi_release.zip`). Projects on the Compatibility renderer are refused. * **Mac:** a `.app` in a `.zip`, named `-macos-universal.zip`. Ad hoc signed by the MCP. * **Windows:** an `.exe` with the game pack inside, zipped as `-windows-x64.zip`. At most 20 GiB. Players download it from your game page. ## Export templates Only web builds and downloads need export templates. Store bundles do not. **What you already have:** the Mac app of Summer Engine comes with the Mac template, the Windows app with the Windows templates. Both can come with the web template pair. Linux and cloud editors have none. **Get the missing ones** from Summer's CDN with your agent: ```json title="List what you have and what is published" theme={null} { "tool": "summer_export_templates", "action": "list" } ``` ```json title="Install the web template" theme={null} { "tool": "summer_export_templates", "action": "install", "platforms": ["web"] } ``` | Input | Meaning | | - | - | | `action` | `list` or `install`. | | `platforms` | `web`, `macos`, `windows`, `linux`, `ios`, `android`. Default `["web"]`. | | `includeDebug` | Also install debug templates. | | `summerVersion` | Your Summer Engine version (Help → About, for example `0.7.1`). Read for you on Mac; needed on Windows and Linux. | The MCP checks each file's SHA-256 before it installs it. Do not use the editor's own template download: it fetches stock templates, not Summer's. **Where templates go.** The engine looks in its own folder first, then in your user folder: | System | Folder | | - | - | | Mac | `Summer.app/Contents/Resources/export_templates//`, then `~/Library/Application Support/Godot/export_templates//` | | Windows | `\export_templates\\`, then `%APPDATA%\Godot\export_templates\\` | | Linux | `~/.local/share/godot/export_templates//` | `` is the engine's full version, for example `4.7.2.stable` (or `4.7.2.stable.mono`) for Summer Engine 0.7.x. The CDN address is `https://downloads.summer.games/engine-templates//manifest.json`. Templates are on the CDN from Summer Engine 0.7.1. For 0.7.0, `summer_export_templates` answers `templates_not_published`: update Summer Engine, or use the templates that came with it. ## File names and versions * Give every upload a new version: `vMAJOR.MINOR.PATCH`, for example `v1.0.0`, then `v1.0.1`. * Download files are named `-macos-universal.zip` and `-windows-x64.zip`. * The default output folder `/.summer/exports/` is ignored by the editor and by git. ## Icons * **Store icon:** the icon on your store page comes from your store art, never from the build. See [Store art](/publishing/store-art). * **Download icon:** Mac and Windows downloads use your project icon (**Project Settings → Application → Config → Icon**). ## Signing You do not need to sign anything for the Summer Games store. * **Summer Games apps** (iPhone, Android, Mac, Windows): Summer signs the apps that run your game. No App Store account, no keystore. * **Mac download:** the MCP signs it ad hoc. It is not notarized. * **Windows download:** no signing needed. Selling your game in other stores needs their own signing. That is outside this guide. ## Ask your agent Export my Summer game for Summer Games. Use the Summer Engine MCP and follow [https://docs.summerengine.com/publishing/export.md](https://docs.summerengine.com/publishing/export.md). * My platforms: \[PLATFORMS, for example "iPhone, Android and the web"]. If I didn't say, read them from my project. * Pick the right build for each: the store bundle for the Summer Games apps, a web build for the browser, a download for Mac or Windows if my game has no server. * Install any export template that is missing with summer\_export\_templates. * Export with summer\_export\_game and tell me each file, its platforms and its size. Don't upload anything yet. ## Next [Upload and submit](/publishing/upload-and-submit). *** Does this not help you? [Reach out on Discord!](https://discord.gg/summerengine) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.