Get it, or just open it.
The browser version is the same application, not a preview of it. It installs nothing, uploads nothing and does the geometry in your tab. Start there; download when you want real files on disk and saves that survive a crash properly.
Desktop builds
Every build is produced by the same automated job from the same commit, and each release carries checksums. Read the state column before you spend an evening on one.
| Platform | Format | State | What to expect |
|---|---|---|---|
| Linux | AppImage and .deb | Run and verified | Run on this project’s own machine: opening, saving, autosave and recovery all watched working. |
| Windows | Installer | Never launched | Builds and is published automatically. Nobody has ever launched it. Expect a SmartScreen warning, because it is not signed. |
| macOS, Apple silicon | Disk image | Never launched | Builds and is published. Never launched. Not notarized, so Gatekeeper will object — and double-clicking a model file will not open it, because that path is not wired on macOS yet. |
| macOS, Intel | Disk image | Never launched | As above. |
Nothing is signed yet.
Windows will warn you that the publisher is unknown; macOS will refuse until you allow it explicitly. Certificates are being sorted out and will land before a stable release. Until then, verify the checksum against the release page and know that the source that produced the binary is public.
There is also no automatic updater. A new version means downloading it, which is worth knowing before you build a habit around this.
Hosting the browser version yourself
It is a static bundle and needs no backend, but the server has to send two headers — COOP and COEP — because long operations are cancelled through shared memory, and browsers only allow that on a cross-origin isolated page.
Without them the app still loads and still works; what stops working is cancelling an import halfway. The docs page has the exact header values.