Export & deploy
Export overview
Choose a standalone web export or the built-in Android APK build workflow.
#Available export targets
| Target | Availability | What it creates |
|---|---|---|
| HTML5 | Available | A standalone static game package with index.html and the required runtime/assets. |
| PWA | Available | The HTML5 game package plus a web manifest and service worker for installable/offline behavior. |
| Android APK | Available through the configured build service | A debug-signed APK generated remotely from the same standalone web package. |
| Desktop (Windows/Mac/Linux) | Coming soon / disabled | Not currently generated by the Export window. |
Open File → Export… or the toolbar's Export button. See Export window reference for the controls and Android APK for the service workflow.
#Standalone game package
The browser builds a standalone ZIP with index.html at its root, a game entry script, runtime files and referenced assets. It does not include the editor or Hub. The Android build flow consumes this same standalone export package rather than reconstructing a game from editor-only project data.
#Run a web export
Serve the exported folder through HTTP(S) or upload it to a static host. Do not double-click index.html from the file system: browser module and asset requests can fail under file://.