# Multiplatform game engine with AI, and what each platform takes > Describe your game and Summer Engine builds one project that exports Windows and macOS builds today. Here is what every other platform really takes, from mobile toolchains to console approval. - URL: https://www.summerengine.com/multiplatform-game-maker - Keyword: multiplatform game engine ai - Related: https://www.summerengine.com/ai-game-maker If you need to ship on more than one platform, the engine choice matters more than the prompt. Summer Engine is an AI game engine where you describe a game once and get a single standard project. Today that project exports desktop builds for Windows and macOS, which is what Steam and itch.io take, and this page covers what the other platforms need. Many AI game tools lock the result inside a browser tab on their own site. Summer Engine is a full desktop engine that is compatible with Godot 4, so the project it builds is standard scenes and scripts on your machine, not a hosted demo. A GDScript project also exports a web build that you publish on Summer Games, where people play it in the browser. You keep working in plain language the whole time. Add gamepad support, a settings menu, a touch control scheme, or a Steam achievement, and the engine applies it to the one project, so the work carries over to whichever platform you take it to next. ## One project, and what each target really takes You build the game once as a standard project. Desktop is the supported release path today, with Windows and macOS builds when the export templates are installed. iOS and Android builds need that platform's toolchain and signing (the Android SDK and a keystore, or a Mac with Xcode for iOS) and a pass on touch input. A GDScript project also exports a web build for Summer Games, and C# projects cannot export to the web. Console versions need platform holder approval and certification, and are usually handled with a licensed porting partner. Summer has no console export of its own. ## Built for Steam and the desktop stores Steam is the destination most serious projects aim for, and Steam takes desktop builds. Because the underlying project is a real, compiled game rather than a hosted web demo, it runs as a native Windows or macOS build that Steam and itch.io accept. Ask for a settings menu, gamepad support, or a pause screen and the engine adds it to the project, so the desktop release feels like a finished product, not a wrapped webpage. ## Mobile, browser, and consoles, one at a time Reaching phones usually means reworking input, scaling the UI, and a separate build toolchain. You can ask for touch controls and a portrait layout in the same project, and the phone build then goes through that platform's own toolchain and signing. For the browser, a GDScript project exports a web build that you publish on Summer Games. Consoles go through the platform holders, with developer approval, NDA SDKs, dev kits, and certification, and indie versions are usually handled with a licensed porting partner. ## You own the project and every build it produces The output is a standard project with no lock-in, no royalties, and no revenue share. Every build you make is yours. Publish the desktop build on Steam or itch.io and pay Summer no royalties on what you earn, and if you later take the game to another platform, the source files are yours to bring. Nothing you ship lives on someone else's server unless you choose to put it there. ## FAQ ### What is a multiplatform game engine with AI? It is a game engine that lets you build one project through AI and take it to more than one platform without rewriting the game. Summer Engine reads your prompt, builds a single standard project, and exports Windows and macOS builds today. Mobile needs each platform's toolchain and signing, and consoles need platform holder approval. ### Which platforms can I export to? Windows and macOS desktop builds, which Steam and itch.io accept, and web builds of GDScript projects, which you publish on Summer Games. iOS and Android builds need that platform's toolchain and signing (the Android SDK and a keystore, or a Mac with Xcode for iOS) and a pass on touch input. There is no console export of Summer's own. ### Do I have to rebuild the game for each platform? No. You build and describe the game once, and the scenes, scripts, and assets stay in one standard project compatible with Godot 4. Each platform you add brings its own build requirements, but you are not maintaining a separate codebase per store. ### Can I make and export games for free? Yes to start. The Summer Engine desktop app is a free download and the core engine is open source, so you can build a game and export desktop builds on the free tier. You only pay for advanced AI usage at higher volume, not to install the engine or export a build. Stores like Steam charge their own separate fees. ### Can I publish to Steam with this? Yes. The project compiles to a native desktop build that Steam accepts, and you can add the menus, input, and settings a store release expects by asking in plain language. You own the build and keep your revenue with no royalties to Summer Engine. ### Does it make both 2D and 3D multiplatform games? Yes. Because Summer Engine is a complete game engine, it builds 2D and 3D games, and both export as Windows and macOS builds, so the style of game you describe does not limit where the desktop release can go. [Build your game once](https://www.summerengine.com/download) --- ## Machine-readable resources - Site index for agents: https://www.summerengine.com/llms.txt - Full inlined content: https://www.summerengine.com/llms-full.txt - Porting catalog: https://www.summerengine.com/llms-porting.txt - Structured catalog: https://www.summerengine.com/agent-catalog.json - Sitemap: https://www.summerengine.com/sitemap.xml - Developer resources: https://www.summerengine.com/docs