Publishing & export

Choose a destination according to what you want to keep or share. A playable download, a private restart record and a public game link carry different information and permissions.

Download a playable game

Use the creator's download action to export the playable build and source. Extract the ZIP and open play.html, then test controls, scoring, win/loss and restart. Retain an unmodified copy before making independent changes.

Supported browser exports package their runtime and included assets. A separate template or source edition can have its own build process, dependencies and external-service requirements. Follow that project's instructions; downloading a kit does not provision its backend.

For project decisions, journal and retained references, also export a private restart record from Memory & docs. Ordinary playable downloads do not contain that complete private record. See projects and recovery.

Publish a public game link

1. Open the creator's publishing controls and sign in if requested.
2. Review the source-sharing notice and confirm that the project contains no private information and that you have the rights to publish its contents.
3. Complete the required checks and publication action shown for the current project.
4. Copy the public play link and test it while signed out, including on your intended screen sizes.

Publishing makes the game source public. Check asset licenses as well as secrets. Public-link publication and inclusion in the discovery catalog are separate steps; discovery requires its own opt-in and review. The interface reports applicable account limits and errors.

Remix, update and unpublish

A public game can offer a remix into a new editable project. Treat that copy according to its source and asset terms. Updating a published game requires the current project's authorized publishing flow.

Unpublishing removes the hosted link, but cannot recall copies already downloaded or remixed. Keep your own backups independently of the public link.

Host or distribute elsewhere

Export through your own hosting account when you need a custom domain or backend. Configure server secrets with that host, then test the deployed result. Exporting alone does not set up a domain, synchronize a repository in both directions or move external credentials.

A browser-source ZIP is not an app-store binary. Native distribution needs a suitable build/wrapper, platform testing and signing. See store publishing for release kits and the separate assisted-publishing request process.

Your original contributions remain yours. Dependencies and imported assets retain their licenses. Licensed Studio editions may permit compiled game distribution while restricting source redistribution, so do not publish covered private source through a public play link without the necessary rights. Review the Studio Source Code License when an edition is involved.