OrcaSlicer: an AGPL G-code generator with built-in calibration, belt and IDEX modes, and a phishing problem

One slicer aimed at many printer families, from Bambu Lab to VzBot

OrcaSlicer is a G-code generator for 3D printers, written in C++ and released under AGPL-3.0. Its own description names Bambu, Prusa, Voron, VzBot, RatRig and Creality as target machines, and the feature list adds broad compatibility with Bambu Lab, Prusa, Creality, Voron and more. It ships pre-made profiles for popular printers and a drag-and-drop interface.

For printers that sit on a network, OrcaSlicer can talk to Klipper, PrusaLink and OctoPrint for remote control, so a sliced job does not have to travel by SD card.

The limit is in the wording. Compatibility is promised at the brand level, and profiles are promised for popular printers. If you own a less common model, or a heavily modified machine, there may be no ready profile, and you will be building printer and filament settings yourself. Check the printer list inside the application for your exact model before you commit a print farm to it.

Calibration prints are part of the slicer, and the wiki is the manual

OrcaSlicer bundles calibration tools rather than leaving them to downloaded test models. The calibration set covers temperature towers, flow rate and retraction, among others, and the calibration guide on the project wiki at orcaslicer.com/wiki/calibration_guide walks through them.

The wiki is where the depth lives. Its stated aim is to give a detailed explanation of each slicer setting, how to get the most from it, and how to calibrate and set up a printer. Process settings, support settings, quality settings for overhangs, seams and precision, and printer settings such as adaptive bed mesh each have their own pages. The wiki also takes contributions, with a how_to_wiki page explaining the process.

The consequence for new users is that the interface alone will not explain what a setting does. If you change flow or retraction values without reading the matching wiki page and running the matching calibration print, you are tuning blind, and the calibration tools only help if you carry their results back into your settings.

Wall, seam and hole controls aimed at dimensional accuracy

Several of OrcaSlicer's settings target the shape of the printed part rather than speed. Precise Wall adjusts the spacing of the outer wall. Seam control adds scarf seams. Sandwich mode prints walls in an inner, outer, inner order. Polyholes target accurate hole shapes, and sandwich mode can be combined with varied infill patterns.

Overhang settings can modify geometry so that overhangs become printable, and support optimisation places supports more precisely. Mouse ear brims add automatic brims, and adaptive bed mesh calibration is offered alongside them, both aimed at consistent bed adhesion. Granular controls cover print speed, layer height, pressure and temperature.

Each of these is a setting you have to switch on and tune. None of them fixes an uncalibrated printer, and the README links each one to its own wiki page because the right values depend on your machine and material.

Belt printers and IDEX/IQEX machines get their own slicing modes

Two features address less common hardware. Belt printer support slices for belt or conveyor printers with an effectively infinite Z axis, adds belt-aware supports and shows a tilted-bed preview. It was contributed by Joseph Robertson (@HarrierPigeon), and the belt_printing wiki page covers it.

IDEX/IQEX parallel printing lets every carriage on an IDEX or IQEX printer print a copy or a mirror image of a part at the same time. The mode is chosen per plate, and nozzle clearance zones are shown on the bed. Clifford (@cgarwood82) contributed it, and it has its own idex_iqex_parallel_printing wiki page.

Both are community contributions rather than vendor features. If you own one of these machines, read the wiki page for your mode first, check the clearance zones on every plate before you send the job, and report problems with the specific feature name so they reach the right people.

Lookalike domains are serving fake OrcaSlicer downloads

The most important line on the project's front page is a warning. Several clickbait and malicious websites pretend to be the official OrcaSlicer site, and the project names two of them: orca-slicer[.]com and orcaslicer[.]net. These sites may redirect visitors to dangerous downloads or contain misleading information. The only official website is www.orcaslicer.com.

This matters because people searching for a slicer download click the first result. An installer from an impostor site is not the OrcaSlicer build, whatever its file name says.

The safe routes are the official website, the GitHub releases page of OrcaSlicer/OrcaSlicer, the Microsoft Store listing and winget. If you run into one of the fake sites in search results, the project asks you to report it as unsafe or phishing through Google Safe Browsing, Microsoft Security Intelligence or IPThreat.

2.5.0 is at release candidate, and nightlies hang off a single tag

OrcaSlicer publishes through three channels on GitHub. The stable release sits behind the releases/latest link and is the one recommended for most users; Windows binaries in it are code signed. The 2.5.0 cycle is in progress: OrcaSlicer V2.5.0 Beta was tagged v2.5.0-beta on 2026-10-27, and OrcaSlicer V2.5.0 RC followed as v2.5.0-rc on 2026-11-01. The last push to the repository was on 2026-11-02, so work on the code is continuing.

Nightly builds use a different arrangement. There is one release named OrcaSlicer Nightly Builds under the nightly-builds tag, dated 2024-11-21, and the README points to that tag for the latest nightly. The project asks for feedback on these builds.

The consequence: the release date on the nightly entry does not tell you how fresh the build is, so look at the asset dates. And a beta, an RC and a nightly all sit on the same releases page as the stable build. If you want predictable output for production prints, take the release behind releases/latest and leave the pre-releases for a spare machine.

Windows has five install routes and two runtimes you may be missing

Windows users can choose between an installer exe, published for both x64 and arm64 CPUs, a portable build, a Microsoft Store package, and the Windows Package Manager:

winget install --id=SoftFever.OrcaSlicer -e

The Store package is the one to use if Windows 11 Smart App Control blocks the installer, because it is Store-signed. On Mac, the download is a universal DMG that runs on both Apple Silicon and Intel machines.

If a Windows build will not start, two runtimes are the first suspects: the Microsoft Edge WebView2 runtime and the Visual C++ 2019 x64 redistributable. The project mirrors both installers on its own release v1.0.10-sf2 and also gives Microsoft-hosted download links. The redistributable may already be present if Visual Studio is installed, under %VCINSTALLDIR%Redist\MSVC\v142.

Pick the installer that matches your CPU. An arm64 Windows laptop needs the arm64 build, and installing the wrong architecture is an avoidable first failure.

Building from source means a script per platform and AGPL obligations

The repository is organised for building on all three desktop platforms. CMakeLists.txt sits at the root with a cmake/ directory, and each platform has its own entry script: build_win.bat for Windows, build_release_macos.sh for macOS, build_linux.sh for Linux and build_flatpak.sh for a Flatpak package. Third-party dependencies are split across deps/ and deps_src/, translations live in localization/, and there are tests/, tools/, scripts/ and a .devcontainer/ directory for a containerised development setup. A version.inc file sits at the root as well.

Contributors should read CONTRIBUTING.md, and security reports have their own SECURITY.md. AGENTS.md, CLAUDE.md and a .claude/ directory also sit at the root. The winget package ID still carries the SoftFever name, as does the SoftFever_doc/ directory.

The license is the part to read before you fork. OrcaSlicer is AGPL-3.0, so if you distribute a modified build, or offer it to users over a network, you must make your modified source available under the same license. Vendors planning a rebranded slicer need to plan for that from the start.

Editorial conclusion

OrcaSlicer suits people who want calibration routines, seam and wall controls, and network printing through Klipper, PrusaLink or OctoPrint in one slicer, and it is the obvious candidate for owners of belt printers or IDEX/IQEX machines who need those dedicated modes. It is the wrong pick for anyone who wants a frozen tool right now, since 2.5.0 is at release candidate stage and nightly builds sit one click away from stable ones. Before installing, confirm you are on www.orcaslicer.com or the GitHub releases page, pick the stable release rather than the RC or nightly, and check that a profile exists for your exact printer model.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes