Every few years, the digital world reshapes itself. New frameworks appear, codebases evolve, and what once felt modern starts to age quietly in the background. For teams running websites on Umbraco, that rhythm has always been familiar. Each release brings cleaner structure, steadier performance, and a little more breathing room for editors and developers alike.
Now, with Umbraco 17 Beta out in the open, we’re standing at another one of those turning points and this is not a complete rebuild, but a thoughtful continuation of what has made Umbraco reliable for so long.
A smoother rhythm for upgrades
Umbraco’s development cadence has become one of its quiet strengths. Two major releases each year keep the platform modern, while every fourth release becomes a Long-Term Support (LTS) version aligned with Microsoft’s own .NET LTS cycle.
Version 17, launching this November, is the next of those LTS milestones. It’s built on .NET 10 LTS, giving organisations a full three-year support window until late 2028. For anyone who has already moved to Umbraco 13 LTS, the path to 17 is designed to be direct. All in-between migrations are handled automatically during the move, which means no incremental hops and far fewer unknowns.
That rhythm with Beta, Release Candidate, then Final, signals a platform maturing in how it delivers stability. The days of worrying about breaking changes or endless patch cycles are fading.
A backoffice that finally feels complete
If you’ve followed Umbraco’s evolution over the past few years, you’ll remember the introduction of the Bellissima backoffice in version 14. It was a major rewrite, that replaced the old AngularJS foundation with Web Components and TypeScript.
In 17, that transformation reaches a point of confidence. Extensions are now treated as first-class citizens. Instead of workarounds that developers hope survive the next release, you get a stable, well-documented framework.
For editors, that translates into subtle but meaningful polish. You will notice faster interface response, new keyboard shortcuts, validation badges, and deep links that make navigation feel effortless.
The backoffice now supports load-balanced environments, so larger teams can manage content simultaneously without conflict. And behind the scenes, the entire system keeps its data in sync using a new distributed cache model.
Details that make daily work easier
Much of the excitement around Umbraco 17 isn’t about big, flashy features. It’s the smaller things that remove friction from everyday work.
-
UTC-friendly date handling brings consistent time data across global teams, avoiding the subtle errors that used to appear between time zones.
-
The TipTap rich-text editor replaces TinyMCE as the default, offering a modern editing experience that feels cleaner and more predictable. (TinyMCE remains available through the Marketplace for those who prefer it.)
-
Developers gain server-side preview URLs, a more efficient Models Builder, and a reworked dependency layer optimised for .NET 10.
Each of these changes points in the same direction: less time debugging, more time creating.
Why this release matters
For many organisations, Umbraco 13 LTS already offers a solid foundation. So why think about 17 now? Because 17 marks the first LTS built entirely on the modern backoffice and the latest .NET stack.
That means fewer legacy bridges to maintain, fewer plugin surprises, and a clearer upgrade path for the future. It’s not about chasing the newest thing; it’s about staying aligned with the supported core of the platform.
Upgrading from 13 to 17 isn’t a redesign, but a continuity plan. You carry forward your content models, your workflows, and your integrations, but you land on a codebase built for the next three years of Microsoft’s ecosystem.
How an upgrade really works
When we help teams plan their move, the first step is always clarity. A readiness audit identifies what’s customised, property editors, dashboards, integrations, and any legacy AngularJS elements. From there, we rebuild those pieces as Web Components connected through the Management API, test them against 17’s runtime, and prepare deployment in a staging environment that mirrors production.
Once migration begins, Umbraco automatically applies the intermediate updates. Databases migrate on startup, and packages checked for compatibility keep the transition clean.
For larger content libraries, we run staged indexing and blue-green deployments so the new version can warm up quietly while editors continue working.
When done well, the result is almost uneventful. That is the best kind of upgrade.
Looking beyond version numbers
Every major release is a reminder that software doesn’t stand still. The value isn’t in the number itself but in the momentum it represents: security patches that keep hosting providers happy, frameworks that stay compatible with modern tooling, and a backoffice that feels current for your team.
For anyone still on older versions, such as Umbraco 8 or 10, the door hasn’t closed. The route may take an extra step, but the upgrade path is well-documented and proven. Starting with a stable 13 LTS and planning toward 17 is often the most efficient way forward.
If you’d like a deeper overview of how to plan that move, my colleague Afreed, a fellow Umbraco MVP here at Phases, recently explored this in detail in his article Planning Your Umbraco Upgrade From Version 8 Today to Version 17 Tomorrow.
Staying ready for what’s next
Umbraco 17 isn’t trying to reinvent the CMS; it’s refining it. The platform feels lighter, faster, and more dependable, especially for teams working across multiple regions or running large editorial workflows.
And perhaps the most encouraging part is the tone of the release itself: measured, transparent, and clearly shaped by feedback from the developer community. The Beta phase invites real testing, the Release Candidate focuses only on regressions, and the final build is expected to land steady, not rushed.
Those of us who have worked with Umbraco for years recognise what that means. The foundation is solid, and the future releases are becoming more predictable, which is a rare and valuable quality in modern software.
If you’re reviewing your current setup or planning ahead for Umbraco 17, it’s a good time to take stock.
At Phases, we’ve been working closely with Umbraco through every LTS cycle, helping teams understand what to expect and how to prepare with minimal disruption.
A short discussion can often clarify what the upgrade path would look like for your site.