AutoStakkert! vs Eise.app - Which Planetary Stacker Should You Use?

AutoStakkert! (by Emil Kraaikamp) has been the industry-standard planetary stacker for over a decade. Eise.app is a newer browser-based alternative built for people who want to stack a video without installing anything. This page compares the two honestly so you can pick the right tool for your workflow.

Short version: AutoStakkert! is the more mature and battle-tested tool if you're on Windows and comfortable installing native software. Eise.app is the more approachable choice if you're new to planetary imaging, want stacking and post-processing bundled together, work on macOS or Linux without Wine, or want an open-source tool that will keep evolving.

Feature-by-Feature Comparison

FeatureAutoStakkert!Eise.app
Install requiredYes (Windows binary)No - runs in browser
Native platformWindowsAny (browser)
Mac / Linux supportWine / VM onlyNative (browser)
Mobile / tabletNoYes (limited)
PriceFreeFree
Uploads your dataNo (local)No (local, in-browser)
Input formatsSER, AVI, MOV, MP4SER, AVI, MOV, MP4, image sequences
Alignment pointsYes, mature implementationYes
Drizzle stackingYes (1.5x, 3x)Yes (1.5x bicubic and pixfrac beta)
Integrated post-processingNo (pair with Registax / ImPPG / AstroSurface)Yes (wavelets, RGB alignment, color)
GPU accelerationLimitedWebGPU (when available)
Community / documentationLarge, decade-plus historyNew (2026)
Open sourceNo (closed source)Yes (MIT-style, on GitHub)
Development paceSlowed (last public blog activity ~2020)Active (weekly changes)
Beginner-friendlyPowerful, but many settings to learnYes - sensible defaults, guided flow
MaturityBattle-tested since 2012Beta - active development

When AutoStakkert! is the better choice

  • You're on Windows and stacking is your main workflow. AutoStakkert! is fast, mature, and integrates well with the wider Windows astrophotography ecosystem (SharpCap, FireCapture, Registax).
  • You already know it. Every tutorial, every YouTube video, every forum thread about planetary stacking references AutoStakkert!. If you have muscle memory for the workflow, there's no urgent reason to switch.
  • You need very large drizzle or very heavy stacks. A native binary with a full desktop CPU/RAM budget can crunch through frame counts that a browser sandbox will struggle with.
  • You want the most refined alignment-point implementation available. Emil has spent over a decade tuning AS!, and it shows in edge cases.

When Eise.app is the better choice

  • You're new to planetary stacking. Eise.app was designed to work well with defaults. Frame ranking, cropping, alignment, and sensible sharpening are all set up out of the box - you can get to a decent result without knowing what "AP size" or "double stack reference" means yet. Compare to AutoStakkert!, which is powerful but has more settings to learn upfront.
  • You're on macOS or Linux. No Wine, no CrossOver, no VM. Eise.app runs natively in the browser on Apple Silicon and Linux.
  • You want to try stacking without committing to an install. Open the page, drop a file, see a result in seconds.
  • You want stacking and post-processing in one tool. Wavelet sharpening, RGB alignment, deconvolution, and color adjustments are built in - no need to save a TIFF and open Registax or ImPPG afterwards.
  • You want long-term insurance against a tool going stale. Eise.app is open-source under active development. If maintenance ever slows, the code is on GitHub and forkable. AutoStakkert! is closed-source and its blog has been quiet since around 2020 - the app still works well, but if you rely on it heavily and it ever stops running on a future OS update, you'd be stuck.
  • You're stacking on a shared or work computer. Nothing to install, no admin rights needed.
  • You want to try stacking on mobile. It's slower and RAM-constrained, but it does work on a modern phone or tablet.

Technical Differences

Architecture. AutoStakkert! is a native Windows application. It has direct access to the file system, full CPU threading, and OS-level memory. Eise.app runs in a browser sandbox: file access is user-initiated, memory is limited (~2-4 GB per tab depending on browser), and processing uses WebGPU compute shaders and WebAssembly. That trade-off buys cross-platform portability at some cost in peak throughput.

Alignment. Both tools use alignment-point-based local warping to compensate for atmospheric seeing across the frame. AutoStakkert!'s implementation is the more refined - years of tuning show up in edge cases (very low light, extreme seeing, dense AP grids). Eise.app implements the same core approach with WebGPU-accelerated template matching.

Post-processing. AutoStakkert! deliberately doesn't do post-processing - the assumption is you'll pass the stacked output to Registax (wavelets), ImPPG (deconvolution), or AstroSurface for sharpening. Eise.app bundles wavelet sharpening, deconvolution, and RGB alignment into the same session.

Privacy. Both tools process your data locally. AutoStakkert! runs on your machine. Eise.app runs in your browser - nothing is uploaded to a server.

Try Eise.app

The fastest way to compare the two is to run the same SER or AVI through both.

Try Eise.app in your browser →

See also