Publishing A Scene

← Home · Solarxy Web · Runtime and playback

Publishing a scene

File > Export web bundle... writes a zip that runs your scene on any static host. No install, no account, no Solarxy needed at the other end.

The bundle carries the engine, not a recording. Anything driven by an expression, an attribute wrangle or the clock keeps computing in the published page exactly as it does in the editor, because it is the same engine cooking the same document.

Exporting

Open File > Export web bundle... and choose how the page behaves:

Option
Allow autoplay	Lets the page start playing. It can only ever turn the scene's own autoplay off; a scene that did not ask to play is never started by an export setting
Show playback controls	A small play / stop strip for the visitor. Off by default, since most published scenes are meant to be watched rather than driven
Turntable	Spins the camera. A view effect, so it works whether or not the scene animates
Page background	The colour behind the canvas

Save the zip, unzip it, and upload the folder.

Serving it

The bundle must be served over HTTP. Opening index.html straight from your disk will not work, and the page will tell you so if you try. This is a browser rule rather than a Solarxy limitation: the page loads an ES module and fetches the engine by URL, and browsers refuse both from a file:// address.

To check it locally, from inside the unzipped folder:

python3 -m http.server 8000

then open http://localhost:8000.

To publish it, upload the whole folder anywhere that serves static files — GitHub Pages, Netlify, S3, nginx, a directory on your own server. There is no build step and nothing to configure.

What is in the folder

index.html               the page
assets/                  the player and the Solarxy engine (wasm)
scene.slxy               your scene, exactly as the editor saved it
solarxy-player.json      playback and appearance settings
README.txt               the short version of this page

scene.slxy is a normal Solarxy scene file. You can open it back up in the editor, which makes the bundle a reasonable way to hand work to somebody who might want to edit it later as well as look at it.

solarxy-player.json is plain JSON, and editing it changes how the page behaves without re-exporting. Turn the playbar on, change the background, stop it autoplaying.

Size

Expect roughly 1.6 MB compressed, most of it the engine. Scene files themselves are small; the geometry is cooked in the browser rather than shipped.

That is the cost of the bundle being self-contained. It is the same engine the editor runs, deliberately: a stripped-down player would be a second thing to keep working, and the two would drift.

Requirements for the visitor

A browser with WebGPU — current Chrome or Edge, or Safari 26 and later. The page says so plainly if WebGPU is missing, rather than showing a blank canvas.

What the published page does not have

No node canvas, no parameter panel, no gizmos, no selection, and no review markers. It is the viewport and, optionally, the playbar. Review notes in particular stay behind: they are an authoring conversation, not part of what you published.

See also

• Runtime and playback
• Solarxy Web