Invited publishers should prepare a browser build before using the Puls CLI.
The One Requirement#
Your build folder must contain an index.html file at the root. This is the file that launches your game.
my-game-build/
├── index.html ← required
├── game.js
├── game.wasm
└── assets/
├── sprites.png
└── music.mp3Supported Engines#
Browser exports from these engines are common starting points. Test your build in a browser before publishing it:
| Engine | Notes |
|---|---|
| Unity (WebGL) | Use the WebGL export — make sure index.html is at the root |
| Godot (HTML5) | Use the HTML5 export preset |
| Phaser / PixiJS | Export a web build with an index.html entry point |
| PlayCanvas | Download build from the editor |
| Three.js | Bundle with your preferred tool, ensure index.html at root |
| Construct | Export as HTML5 |
| Any other | Export a self-contained browser build and test it |
Size Limit#
Your game build can be up to 500 MB.
The CLI packages supported files before uploading. Keep the build as small as practical for faster loading.
Recommendations#
- Check asset paths — relative paths such as
./assets/image.pngare a portable choice - Bundle everything — don’t rely on external CDNs or servers
- Test locally — serve the build with a local web server and check it in a browser before deploying
Next: Enable Hosting