The browser app now, desktop apps next

Star Trail Stacker runs in your browser today with nothing to install. Desktop apps for macOS, Windows and Linux are in development, and no build can be downloaded yet.

Ready now

In your browser

Browsers
Chrome, Edge, Firefox and Safari
Computers
macOS, Windows, Linux and ChromeOS
Install
nothing; your frames are read in the tab and never uploaded
Memory
a stated budget per browser, checked before a run starts

Open the app Which browser to use

In development

macOS

Planned for
Apple Silicon and Intel Macs
Build
none yet
Signing
signed and notarised before it is offered

In development

Windows

Planned for
Windows 10 and 11 on x64
Build
none yet
Signing
signed before it is offered

In development

Linux

Planned for
x64, as an AppImage and a .deb
Build
none yet
Signing
checksums published with every build

What the desktop apps are for

The same engine, with the machine's resources instead of a browser tab's. A browser gives a page a slice of memory, a capped number of worker threads and only the files you pick or drop; the desktop apps are meant to size a run from your computer's own memory, use every core, and read a folder where it lies.

The browser today, and what the desktop apps are planned to change
 Browser, todayDesktop, planned
Memory for a runthe tab's stated budgetsized from your computer's memory
Worker threadswhat the browser allows a pageone per core
Filesfiles you pick or drop; a whole folder in Chrome and Edgefolders read in place
Speednot claimed until it is measured on a named machine with the same frames and the same recipe

The desktop apps are not a different product: the modes, the recipes and the files they write are the same as in the browser. See star trail stacking on a Mac for how the browser app compares with the desktop stackers people use today.