OBSERVABILITY Signal 124
PrusaSlicer 3.0 preview rewrites UI, adds multi-bed projects and continuous local backup
↗
PrusaSlicer 3.0's first public preview replaces the entire UI, introduces a project system where each bed is independently configurable, and continuously backs up open projects locally for crash recovery.
The continuous local backup of open projects into a dedicated folder gives operators a recovery path after crashes that previous versions lacked. The shift from .ini to .yaml profiles and the layered multi-tool profile system change how print configurations are structured and maintained. Old 2.x 3MF projects still load, but the profile format and data structure are entirely new, so anyone managing custom profiles will need to understand the migration.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Each bed in a project can now hold its own configuration, profile, and even printer type, with the previous 9-bed limit removed and beds sliced in parallel.
Open projects are continuously backed up to a local backup_projects folder, enabling recovery after application crashes.
Profile format moved from .ini to .yaml with a new layered data structure designed around multi-tool printers, while old 2.x 3MF projects load with automatic configuration transformation.
THE READ
What the cluster adds up to.
PrusaSlicer 3.0 is described as the biggest upgrade in the software's history, driven by a complete UI rewrite and a restructured project and profile system. The preview is positioned not around any single feature but around the architectural foundation it creates for future updates. The release date is noted as exactly 15 years after the first Slic3r commit.
The project system now treats beds as real, independently configurable parts of a project rather than the minimal implementation introduced in 2.9.0. Each bed can use different profiles, materials, or even different printer models within the same project window, and the previous 9-bed limit is removed. Beds are processed in parallel during slicing, which the material frames as a time saver for both multi-printer and single-printer workflows.
From an operational standpoint, the most relevant change for reliability is continuous local backup of open projects. The material states that backups are stored in a backup_projects folder within the PrusaSlicer data directory, and that work can be recovered if the application crashes. This is the closest the release comes to observability: there is no mention of logging, telemetry, or diagnostic dashboards, only a crash-recovery mechanism for unsaved work.
The profile system has been rebuilt from the ground up to describe multi-tool hardware directly. The old system could not represent a printer like the Prusa XL with different nozzles on different tools without requiring separate printer profiles and manual switching. The new layered format lets users assign different print or printer profiles to individual tools. The profile format itself moved from .ini to .yaml, and the preset updater was rewritten to manage both online and local sources from one place.
Migration appears partially handled: old 3MF projects from PrusaSlicer 2.x load correctly, with configurations transformed and matched to system profiles automatically. However, the material does not specify whether custom .ini profiles from 2.x are automatically converted or require manual recreation in the new .yaml format. The material also does not detail what the new UI looks like beyond stating it was written from scratch, so the practical impact on existing workflows cannot be fully assessed from this preview announcement alone.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER