# Web game maker guide, what a web build needs and where Summer stands > Here is what it takes to ship a game that plays in a browser, and where Summer Engine stands. Summer builds real games on the desktop and exports Windows and macOS builds, plus web builds for GDScript projects. - URL: https://www.summerengine.com/web-game-maker - Keyword: web game maker - Related: https://www.summerengine.com/ai-game-maker A browser game has to load fast, read keyboard, mouse, and touch, and run from a page with nothing to install. Summer builds a real 2D or 3D game from a description on your desktop and exports it as a Windows or macOS download. A GDScript project also exports a web build that you publish on Summer Games, where people play it in the browser. One distinction is worth knowing up front. Browser-only makers run the editor inside a tab, which keeps your project on their server and caps what you can build. Summer Engine is a desktop app for macOS and Windows, so the AI and the full engine run on your machine without a tab freezing or a session timing out. The game you ship is a build you control, as a desktop download or as a web build on Summer Games. So this page does two jobs. It explains what any web build needs, so you can judge a browser game maker on facts, and it shows the path Summer offers today. Make a 2D arcade game or a 3D scene, playtest it on your machine, then publish a web build on Summer Games or upload a Windows or macOS build to itch.io or Steam. ## Build on the desktop, ship a web or desktop build You install Summer Engine once, describe the game you want, and it builds the scenes, scripts, and assets into a real project. When the game plays the way you like, export a Windows or macOS build and share it as a download. For a web link, export a web build of a GDScript project, a .zip with index.html at the root, and publish it on Summer Games. The heavy lifting happens on your machine. C# projects cannot export to the web, so keep a web-first game in GDScript. ## What a web build needs to work Most web games today are built with an engine that compiles to WebAssembly and draws through WebGL. Summer's own web template draws through WebGPU, and Summer Games also accepts Godot's standard Web export. For Godot 4.3 and later, a single-threaded web export needs no special server headers, and the COOP and COEP headers only matter if you turn on thread support. Hosts set their own limits too. itch.io caps an HTML5 upload at 500 MB in total, 200 MB per file, and 1,000 files, so a small download is not only good for load time, it is the difference between an upload that works and one that fails. ## Input, size, and load time A good browser game handles keyboard, mouse, and touch together, because the same link gets opened on a laptop and a phone. It keeps textures and audio compressed so the first frame shows up quickly, and it scales its canvas to whatever window it lands in. 3D is possible in a browser, but it costs more download and more GPU than 2D, so web-first projects usually keep scenes light. These are the questions to ask any browser game maker before you commit a project to it. ## Keep editing in plain language until it ships Building the game is a conversation, not a one-shot generation. Ask for a new level, tighter controls, a different art style, a title screen, or a score system, and the change applies to the same project. You see it running on your machine, then export a fresh desktop build when you want testers to try it. Because you own the project files, you can also open the scripts and scenes directly at any point, since Summer Engine is compatible with Godot 4. ## Your game, your hosting, your revenue A build you make belongs to you with no lock-in. Publish it on Summer Games, upload it to Steam or itch.io, sell it from your own site, or share it with testers. There are no royalties and no revenue share, and your game is not tied to a maker's server that could change terms or shut down. The project is standard files on your machine, so it stays yours whatever platforms you target later. ## FAQ ### Is this a browser-based game maker I use in a tab? No. The editor is a desktop app for macOS and Windows, which is what lets the full engine and the AI run on your machine without a tab timing out. Summer Studio at summerengine.com/studio works in the browser, but it generates assets such as images, video, audio, and 3D models, not games. You build and playtest games on the desktop. ### Can players play my game in a browser with no download? Yes, if the project uses GDScript. Summer exports a web build, and you publish it on Summer Games, where people play it in the browser. C# projects cannot export to the web, so those players download a Windows or macOS build. ### Where can I publish the game I make? Publish a web build on Summer Games. Steam and itch.io both take the Windows and macOS builds Summer exports, and you can also offer the download from your own site. You control the files, so you are not locked to one host. ### Can I make both 2D and 3D games? Yes. The maker builds 2D platformers and top-down games as well as full 3D scenes with cameras, lighting, and physics, and both export as Windows and macOS builds. A GDScript project also exports a web build. ### Is Summer Engine free to start? Yes. Summer Engine is a free download and the core engine is open source, so you can build a game and export a desktop build without paying. You only pay for advanced AI usage at higher volume, not to install the app, start a project, or export your first game. ### Do I need to code to make a game? No. You can build and refine the whole game through conversation, then export a desktop build. If you want to go deeper, the project uses standard scripts and scenes you can edit directly, since Summer Engine is compatible with Godot 4. [Build your game](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