PrusaSlicer 3.0 Preview Is Not a Production Build
PrusaSlicer 3.0’s first public preview is unfinished and not for production. Run it beside 2.9.6; opening 3.x projects in 2.x discards 3.x settings.
PrusaSlicer 3.0 is an unfinished public alpha, not a production build and not feature-complete beside 2.9.6. Run it from its separate profile directory with copied projects: opening a 3.x project in 2.x keeps geometry but discards 3.x settings. The preview adds projects, multi-bed work, offline operation, and experimental Lua plugins.
The public preview changes the workflow, but Prusa still calls it unfinished
The preview is not feature-complete beside 2.9.6, so it should not replace a working production setup.
Prusa says the preview supports multiple printers, parallel slicing and more than the former nine-bed limit.
Geometry remains, but Prusa says the newer settings are discarded; separate profile directories allow side-by-side use.
ReportPrusa Research
PrusaSlicer 3.0 should stay beside 2.9.6 while the alpha develops
Prusa’s first public 3.0 preview rebuilds the slicer around projects and tabs, adds local project backups, supports true multi-bed work with multiple printers and parallel slicing, introduces layered profiles, and exposes an experimental Lua plugin system. Prusa also says the application can run fully offline because its network libraries are not loaded in that mode.
Prusa calls this an unfinished alpha, not a production build, and says it is not feature-complete beside 2.9.6. Opening a 3.x project in 2.x keeps geometry but discards the 3.x settings. Separate profile directories make side-by-side use possible, but that separation does not remove the need to protect working projects. The Crafty Catsman has not installed or tested this preview. The safest useful path is to run the preview beside stable 2.9.6 in its separate profile directory and use copied projects.
The new workflow is useful only if the production fallback remains intact
The preview introduces project tabs, local backups, multiple build plates without the earlier nine-bed limit, multiple printers in one project, parallel slicing, layered profiles and an experimental sandboxed Lua plugin API. Prusa says a marketplace will come later. Offline mode prevents the network libraries from loading. A 2.x 3MF file can bring settings into 3.x, while reopening a 3.x project in 2.x retains geometry but discards 3.x settings.
This is a test track, not the stable slicer handoff: Prusa is exposing the architecture early so users and plugin developers can test it, but 2.9.6 remains the complete production reference. The preview does not establish print-quality gains, plugin safety, migration reliability, or a final stable-release date.
- Which 2.9.6 features will return before Prusa considers the 3.0 line feature-complete?
- When will the plugin marketplace open, and how will plugin review and updates be handled?
- What additional project-compatibility warnings will later previews add?
Keep production on 2.9.6 when continuity matters:Keep production work on 2.9.6 if profile migration, project compatibility, or plugin behavior is unclear.
Evaluate the preview in a protected lane:Run the preview beside stable 2.9.6 in its separate profile directory and use copied projects.
PrusaSlicer 3.0 preview — official status record
| Decision field | Prusa Research PrusaSlicer 3.0 preview |
|---|---|
| Release state | Unfinished public alpha; not a production build |
| Stable comparison | Not feature-complete beside 2.9.6 |
| Side-by-side profiles | Separate directories |
| 3.x project opened in 2.x | Geometry retained; 3.x settings discarded |
| Plugin system | Experimental sandboxed Lua API |
| Independent testing here | Not established |
Sources: Official preview announcement
Evaluate beside the stable slicer, not in place of it
Keep 2.9.6 installed, duplicate important projects, and verify one workflow at a time before trusting 3.0 with production work.
Stay on 2.9.6 when settings round-trips, profile migration, missing features, or experimental plugins could interrupt paid or time-sensitive jobs.
Prusa publishes the first public PrusaSlicer 3.0 preview
The announcement introduces the rebuilt interface, projects, multi-bed workflows, layered profiles, offline operation and an experimental Lua plugin path while retaining the unfinished-alpha warning.
Primary pages and records used for this report.
Frequently Asked Questions
Is PrusaSlicer 3.0 ready to replace 2.9.6?▼
No. Prusa calls the current public preview an unfinished alpha, not a production build, and says it is not yet feature-complete beside 2.9.6.
Can PrusaSlicer 3.0 run beside PrusaSlicer 2.9.6?▼
Yes. Prusa says the 3.0 preview uses a separate profile directory, which allows side-by-side evaluation without replacing the stable installation.
What happens if a PrusaSlicer 3.x project is opened in 2.x?▼
Prusa says the geometry remains, but settings created by 3.x are discarded. Use copied projects when testing a round trip between versions.
Have a launch, correction, or test opportunity?
Brands, product teams, and knowledgeable sources can send relevant details, approved media, or corrections. Coverage is selected independently.
Choose the useful next step.
Use the official preview records for the software decision, then continue into the workflow and change-log guides for production planning.
Get the next useful Prusa software update.
When a source-backed change affects what to buy, update, test, or ignore, we send a short decision brief with the evidence, the workshop consequence, and what remains unknown.
Know what changed. Know what it means at the bench. Decide whether to act, wait, update, test, or ignore.
Scanned daily. Sent only when the signal changes a workshop decision, with a rare alert when waiting would matter.
See how The Workshop Signal works