Skip to main content
Summer Engine, the game engine built for AI, exports games that play in the browser. This page covers what is different about a web build and how to ask your agent for one. For file formats and limits, see Export your game.

How a web build works

A web build is a .zip with index.html at its root. The browser downloads it and runs your game as WebAssembly. The web template is not always installed. Your agent can check and install it with summer_export_templates. See Export templates. Threads. Keep thread support off. On summer.games, a build without threads plays in a frame on the game page. A build with threads opens in its own tab.

Ask your agent

Write browser code

Put code that only runs in the browser behind OS.has_feature("web"). Then the same script works in the editor and on desktop.
Saves. Files you write to user:// in a web build live in the browser’s storage on that device. They are lost when the player clears site data. To keep progress across devices, save it with Summer. See Save player progress. Audio. Browsers block sound until the player clicks or presses a key. Start music after the first input, for example on a “Click to play” screen.

Keep it small

Players wait for the download before the game starts.
  • Use textures at the size the game shows them.
  • Use Ogg Vorbis for music and long sounds.
  • Remove assets the game does not use.
Ask your agent: “List the 20 largest files in my export and how to make each one smaller.”

Publish it

Export your game

Build kinds, limits and export templates

Make a web game

Quickstart from idea to a browser game