Prusa Research has published the first public alpha of PrusaSlicer 3.0.0-alpha11 on GitHub, and the release notes describe something closer to a new application wearing the old one's name than a version bump. The changelog opens by billing the release as coming with "completely redesigned internal architecture," and by the time you reach the end of it — a sandboxed plugin runtime, a rebuilt profile system, and a toggle that lets the whole program run with no network calls at all — it's clear Prusa means it literally.
PrusaSlicer has run on essentially the same architectural bones, inherited from Slic3r, since the project began. That lineage gave it stability and a huge library of community profiles, but it also imposed hard limits that got harder to defend as printer farms and multi-material workflows scaled up. The most visible of those was a ceiling of nine build plates per session — fine for a hobbyist queuing up small prints, restrictive for anyone running a rack of printers or juggling several client jobs at once. Alpha11 removes that ceiling entirely and, more significantly, lets a single session hold multiple projects in tabs, each potentially targeting a different printer. That's a workflow lift aimed squarely at people running mixed fleets — a farm mixing several printer models, say — who previously had to run separate slicer windows or close and reopen projects to switch context.
What Actually Changed Under the Hood
The GitHub release groups the changes into a few buckets, and they read like a checklist of things power users have asked for since roughly the CoreXY era of desktop printing began. The interface gets a new left-hand sidebar splitting Slicing, Connect, and Printables into distinct panels, with configurable favorites so frequently used settings don't get buried in menus. Visually, PrusaSlicer finally gets a light UI mode alongside the familiar dark theme, paired with PBR-like rendering — physically based shading that should make it easier to judge overhangs and surface quality on the 3D preview before a print starts.
The profile system itself has been reworked. Alpha11 introduces "free parameters" that adjust automatically alongside a new class of ToolPrint profiles, a change aimed at decoupling machine capability data from print-setting presets so both can evolve independently — useful for anyone maintaining custom profiles for modified hardware, though the release notes are light on migration specifics for existing presets. On the calibration side, Prusa has built flow-rate and temperature towers directly into the slicer, folding in a step that most experienced users previously handled with separately downloaded STL test objects and manual measurement.
Two features stand out as aimed at different audiences entirely. The first is an experimental, sandboxed Lua plugin system with cryptographic signing — Prusa's release notes mention a marketplace is planned, which would turn PrusaSlicer from a closed tool into an extensible platform, something Cura's plugin ecosystem has had for years and PrusaSlicer has conspicuously lacked. The second is a fully disable-able set of online services, letting the entire application run offline or behind a firewall with nothing phoning home. Prusa frames this in the release notes around user privacy and autonomy — pushback after 2.8.0 deepened the slicer's integration with its own web services led some users to worry about where that integration was headed. But the practical draw runs wider than privacy optics: 3DPrint.com's hands-on review calls the offline toggle "a great update for defense and aerospace firms," useful for forward-deployed personnel and production-floor staff at facilities where any network dependency is a compliance problem. It's an unusual use case to see a slicer vendor and a reviewer both flag explicitly, and it signals Prusa is chasing institutional and industrial customers as deliberately as it's chasing hobbyists.
Performance gets a callout too: Prusa says 3MF project files now save more than twice as fast as in 2.9.6. The whole build remains under the AGPLv3 license, consistent with PrusaSlicer's open-source history.
Hands-On: Faster, But Not Finished
3DPrint.com's Joris Peels got hands-on with the alpha build itself and published his impressions on 3DPrint.com on September 3. His verdict leans toward "renovation" rather than incremental update, and he specifically calls the software "light-years faster" than prior versions in day-to-day use. He also notes reorganized panels and improved layer visualization and shading in the preview — corroborating the rendering and UI-reorganization claims in the GitHub notes from an actual usage standpoint rather than a changelog reading.
That distinction matters for an alpha. Release notes describe intent; a hands-on from someone who has actually loaded models and watched the interface respond tells you whether the intent survived contact with real use. So far, on speed at least, it appears to have.
What It Means for Makers
Prusa is explicit that this is not a feature-complete build: SLA slicing, support for third-party printer profiles, and a handful of other named features are called out in the release notes as not yet implemented. That's a meaningful gap — anyone slicing on an SL1-class resin printer, or relying on a community-maintained profile for a non-Prusa machine, has no reason to move yet, and shouldn't expect this alpha to replace their daily driver. For everyone else, alpha11 is worth installing in parallel with a stable 2.9.x setup rather than in place of it. Multi-bed and multi-project support alone will matter immediately to farm operators and anyone running mixed printer fleets, and the built-in calibration towers save a small but real amount of setup friction for new printers or new filaments. The Lua plugin system and offline mode are longer-horizon bets — the former promises an extensibility path PrusaSlicer hasn't had, the latter courts a customer base (defense, aerospace, other locked-down environments, per 3DPrint.com's review) far removed from the hobbyist desktop. Neither is fully proven yet: the plugin system is explicitly experimental, and Peels' hands-on didn't specifically stress-test the offline mode or plugin marketplace, since neither is likely populated yet at the alpha stage.
The practical read: back up your presets, install the alpha alongside — not over — your working PrusaSlicer install, and treat this as a preview of where 3.0 is headed rather than a print-day tool. Given the scope of the rewrite, expect several more alpha and beta builds before this reaches the stability people expect from a Prusa release.
