Fifteen years to the day after the first line of Slic3r was committed, Prusa Research pushed PrusaSlicer 3.0 into public preview — and it is not a normal point release. Josef Přůša calls it the biggest set of changes in the software's history, and for once that is not marketing. The interface was rebuilt from scratch, the profile system was re-architected, and the slicer now accepts plugins.
The headline change for hobby printers is the new project system. Print beds are no longer just copies of one machine's settings. Each bed is an independent part of a single project with its own configuration, so you can combine different printers and profiles inside one file, move models from bed to bed, and slice several beds in parallel. The old nine-bed ceiling is gone, multiple projects can sit open in separate tabs, and the application quietly keeps local backups of whatever you have open. Multi-tool machines like the Prusa XL can finally assign a different nozzle size and print profile to each tool head.
The rest of the rebuild is about getting out of your way. Tools now run along the top of the screen, a collapsible scene browser sits on the left, and the right-hand panel changes depending on whether you have a bed, an object or a tool selected. There is a View Cube for camera control, a light theme at last, and navigation presets that match Tinkercad, Blender, SolidWorks or Fusion so your muscle memory carries over. You can star individual settings as favourites and they appear directly in that contextual panel. Underneath it all sits a sandboxed Lua plugin system: plugins run with no disk, project or network access by default, two calibration-tower generators ship bundled, and a reviewed community marketplace is on the way.
Installing it is low-risk, which is the whole point of a preview. PrusaSlicer 3.x installs alongside 2.x using a separate profile directory, so nothing you already rely on gets touched. Your existing 3MF projects open and have their settings mapped across automatically, though profiles themselves have moved from .ini to .yaml. Two caveats: third-party 3MF files from Bambu Studio or OrcaSlicer import as geometry only, with no settings attached, and the preview is not yet feature-complete against 2.9.6 — some functionality is not due back until 3.1.0. There is also a proper offline mode if you would rather the slicer never phoned home.
Try it on your printer. Download the preview, open a model you have already printed successfully, and slice the same job in both 2.x and 3.x. Compare the time and filament estimates, then skim the G-code preview layer by layer. It is the fastest way to build trust in a new slicer without burning a single gram of filament. Keep 2.9.6 as your production slicer for now, and send anything odd to Prusa's GitHub or community forum, because preview builds only improve when people report. Stocking up on filament to test with? Browse the range at flarelab.com.
Frequently asked questions
Is PrusaSlicer 3.0 safe to install over my current version?
It does not overwrite anything. PrusaSlicer 3.x installs alongside 2.x and uses its own separate profile directory, so your existing setup stays intact. Keep 2.9.6 as your production slicer while the preview matures.
Will my old projects and profiles still open?
Yes. 3MF projects created in PrusaSlicer 2.x load in 3.x and have their settings matched to the new system automatically. Profile files themselves have moved from the .ini format to .yaml.
Can I open Bambu Studio or OrcaSlicer files in it?
Partly. Third-party 3MF files import as geometry only, so the models come through but the print settings do not. You will need to reapply your own profile after importing.
What do the new plugins actually do?
The initial Lua plugins generate parametric objects, and two calibration towers for flow rate and temperature are included by default. Plugins run sandboxed with no disk, project or network access unless granted, and a reviewed community marketplace with ratings is planned.
Reporting based on coverage by 3D Printing Industry. Written and rewritten for beginners by the Flarelab team.
Originally published at flarelab.com.
Top comments (0)