Stable vs pre-release slicer versions

Release channels help you decide how much change and testing you want to accept. Keep your current setup recoverable whichever channel you choose.

1. Stable is the regular release channel.

Stable releases are not marked as previews by the publisher. They are generally the best starting point for everyday use, while still requiring you to check known issues and system requirements.

2. Pre-releases expose upcoming changes.

Alpha, beta and release-candidate builds can provide new features or fixes earlier. They can also change file formats, profiles or behaviour before the final release.

3. Nightly builds need extra care.

Nightly or development builds can change frequently and may receive less testing. Use them when a project explicitly asks you to test a fix, and keep them separate from a dependable setup.

4. Make the switch reversible.

Export changed presets, keep original project files and record the working version. Test a copied project before relying on a new release for an important print.