Linux / Not specified in filename
SuperSlicer-ubuntu_20.04-2.5.59.13.AppImage
Community-tuned PrusaSlicer fork
101 releases in the GitHub release archive
Official project ↗Official files
6 downloadable files for this selection.
SuperSlicer-ubuntu_20.04-2.5.59.13.AppImage
SuperSlicer-ubuntu_20.04-gtk2-2.5.59.13.AppImage
SuperSlicer_2.5.59.13_linux64_240701.tar.zip
SuperSlicer_2.5.59.13_macos_240701.dmg
SuperSlicer_2.5.59.13_macos_arm_240701.dmg
SuperSlicer_2.5.59.13_win64_240701.zip
Platform and processor labels come from the published filenames. Unspecified processors are shown as unspecified; check the official release before choosing.
Excerpts are taken from the linked official release notes and can remain in the publisher’s original language.
First beta for 2.7.62 Many many changes. I started working on 2.7.63, with a new wipetower that allows multiple nozzle size & variable layer height.
Read full release notes →Some more little bug fixes for 2.7.61 (same known issues as 2.7.61.4) First alpha of 2.7.62 is out. Feature-wise, it's 80% finished. I also started a big rework for later (wipetower with multiple nozzle size, more wipe, better min time, more sequential…
Read full release notes →Keep the prior application build and a reference project; the publisher says the Linux and macOS builds were not author-tested.
Open official preservation source ↗Re-slice a model with a critical seam, wipe tower or support interface and compare Preview with known-good G-code.
Open official validation source ↗SuperSlicer is a PrusaSlicer-derived tool for users who want granular FFF and mSLA controls, calibration patterns, configurable G-code and post-processing. It targets modern RepRap-style ecosystems including Marlin, Prusa and Klipper firmware.
Sources reviewed:Its niche is deep process tuning on open printer platforms, particularly when custom macros, output naming, calibration and post-processing matter more than a simplified interface.
Use a tagged GitHub release for repeatable work. The maintainer notes that Linux and macOS builds are compiled but not personally tested; nightly artifacts are better treated as temporary test builds than in-place upgrades.
Inspect the generated geometry or toolpath before sending it to a printer.
Open official instructions ↗The documented controls and behaviour are tied to a release; check your installed version.
Open official instructions ↗Development artifacts can change between runs; keep a stable build available.
Open official instructions ↗The project targets modern RepRap-style machines using firmware such as Marlin, Prusa or Klipper. A suitable machine profile is still required because firmware compatibility alone does not define the printer's geometry and limits.
Check the source ↗It supports a command-line interface, output-name variables, custom G-code macros and post-processing scripts. Those pieces let a repeatable slice feed a larger local production pipeline.
Check the source ↗No. The maintainer explicitly says the Linux and macOS builds are compiled but not personally tested and asks users to report platform-specific problems.
Check the source ↗The project publishes nightly artifacts through GitHub Actions for Windows, Linux and macOS. They reflect recent development and should be isolated from a dependable stable setup.
Check the source ↗101 releases in the GitHub release archive
382 public application files
Counts cover attached application packages across all indexed releases. The same package type may recur in several versions; platform and format are classified from the publisher filename.
Save your tuned profiles. Use the same calibration model to compare the old and new version.
Project documentation ↗A .3mf file holds model or project data. Opening it does not install the slicer. After opening a project, check the printer, nozzle and material settings.
Files are hosted by the developers. Before installing, check their system requirements and release notes. A file labelled for your platform does not establish the minimum OS version.
Before you update →