Statamic 6: Playing the Long Game
Most teams wait until something breaks to fix it. The Statamic team didn't. Statamic 5 worked. But Vue 2 was aging, the Control Panel architecture had limits, and security features that should have been in core were handled by third-party addons. Instead of adding features on top, they rebuilt it.
Statamic 6, released January 28, 2026, is the result of a year spent doing exactly that. There were over 1,000 pull requests, most of which were invisible to anyone not reading the source code. The goal wasn't to impress. It was to build a foundation that Statamic can stand on for years to come.
The control panel: rebuilt from scratch, feels like home
The Statamic team wanted the Control Panel to feel calm. Spend just 10 minutes with it, and you’ll see what they mean.
Most CMS interfaces get worse over time. Features accumulate, navigation becomes more complex, and eventually the interface gets in the way. Statamic 6 goes the other way: every screen was rethought to provide consistency, resulting in a cleaner, tighter experience than version 5. Publish forms now have collapsible sections, which seems trivial until you're managing a blueprint with 40 fields, half of which are irrelevant for the current entry.
The Command Palette (Cmd+K / Ctrl+K) is the most underrated addition in this release. Jump to any content, asset, user, blueprint, or fieldset without using a menu. Power users will wonder how they got by without it. Editors who don't know shortcuts will probably never use it, and that's fine because the rest of the interface works for them too.
The redesign isn't dramatic. The more you use it, the more you notice how much thought went into it. Interfaces like that are rarer than people admit.
Vue 3, Inertia, Laravel 12: why the tech stack update actually matters
The tech stack changes are the easiest part of this release to scroll past. That would be a mistake. The Control Panel had been running on Vue 2 since the beginning, a framework that officially reached end of life in December 2023. Staying on it wasn't just about keeping up with the times. It actively limited what could be built on top of it. Addon developers faced the same walls, and custom Control Panel interfaces never felt native. The new UI component library, built on Reka UI with Vue 3 and the Composition API, changes what's buildable. Custom interfaces can now look and behave as if they were part of the system from the start.
For addon developers, that means updating to Vue 3, adopting the Composition API, and rebuilding custom UI components with Reka UI. Statamic provides a dedicated Vue 2 to 3 migration guide covering everything from Vite configuration to component substitutions.
The Laravel 12 alignment matters too. Frameworks that track dependencies closely tend to age better. Those that don't become a maintenance burden someone, usually the developer or client, ends up paying for.
This kind of investment is easy to postpone indefinitely. The Statamic team didn't.
Security that belongs in core
Until now, two-factor authentication in Statamic required a third-party addon. For something this fundamental, that's not good enough.
Statamic 6 brings 2FA into the core. Users set it up directly from their profile in the Control Panel, and administrators can enforce it for designated roles via configuration. Passkeys are supported natively as a passwordless alternative. Users can add them from their profile and then sign in with Touch ID, Face ID, or a password manager instead of typing their credentials. Elevated sessions add another layer, requiring re-confirmation before sensitive operations. These aren't advanced features. They are basics that should have been there from the start.
If you're running Statamic for clients with multiple editors, the security changes alone make the upgrade worth considering.
The stuff editors will actually feel
Not everything worth noticing makes the feature list.
Replicator and Bard image previews let you see what a content block contains without opening it. When managing a page built from a dozen stacked blocks, this saves real time.
Live Preview now hot-reloads instantly. The previous lag was a small but constant irritant for teams doing visual editing. It's gone.
Timezone-aware dates. Content scheduled for 9 am should be in your timezone, not the server's. Statamic 6 handles this correctly now. International teams and those running multilingual sites will notice immediately.
The collection calendar view lets you browse date-based content in a calendar. Useful for editorial planning, events, and anything organized by time. Not glamorous. Genuinely practical.
The feature requests they said no to
Jack McDade's release post is worth reading in full. It's unusually candid. Good ideas were deferred. Long-standing requests stayed open. The team kept returning to the same answer: not until the foundation is solid.
That takes discipline. In an industry pressured to move faster and ship more, saying "not yet" to reasonable requests is hard. The payoff is a codebase without hidden landmines. Anyone who has inherited someone else's system knows what that's worth.
Multi-site and multi-language improvements, Forms 2.0, and Workflows are all on the roadmap. The foundation is laid. What gets built on it is the interesting part.
Should you upgrade?
New project? Start with version 6. There is no reason to start on version 5.
Existing Statamic 5 site? The upgrade isn't complicated for most. The parts needing attention are addons that affect authentication or the Control Panel UI, as both have changed enough to require auditing. The official upgrade guide is thorough. Budget time for testing, especially on the editorial side, but this isn't a painful migration.
The honest case for Statamic 6 isn't the feature list. It's the decisions behind it. A team that spends a year fixing what's broken instead of building on top of it is a team you can trust. That matters more than any single feature they could have shipped in its place.