Umbraco 17 isn’t just a version bump – it’s a turning point. Built on .NET 10, this version tightens up performance, improves scalability, and sets a consistent foundation for multi-region teams. Whether you’re running a high-traffic content platform or just tired of managing CMS workarounds, this update finally clears a few long-standing roadblocks. Let’s walk through what’s actually new, what’s changed under the hood, and what that means for your projects.

What Makes Umbraco 17 Different?

Umbraco has been releasing updates on a steady six-month cycle, but 17 is more than just “the next version.” It’s the new Long-Term Support (LTS) release, backed by three years of updates: two years of full support, followed by one year of security patches. That alone makes it a strong candidate for enterprise adoption or larger projects that need platform stability.

But it's not just about support timelines. This release finalizes the transition to a modernized backoffice, supports true horizontal scaling (finally!), and brings in consistent time handling, which might seem minor until you’ve dealt with timezone bugs across continents.

Release Highlights That Matter

While the version number might look like a simple step forward, Umbraco 17 is anything but a routine upgrade. This release brings some major under-the-hood changes, many of which reshape how developers interact with the platform on a day-to-day basis. Whether you're building new projects, maintaining legacy sites, or planning a migration, these updates are worth knowing. Here’s a breakdown of the changes that will likely shape how you work with Umbraco going forward.

Built on .NET 10 LTS

Umbraco 17 runs on .NET 10, which is also a Long-Term Support release. That means you’re getting a stable foundation from both the CMS and the runtime. For many organizations, that alignment is a big deal. It allows infrastructure, security, and dev teams to plan long-term without juggling unpredictable upgrade cycles.

On top of that, .NET 10 offers improvements in performance and memory usage. It also helps future-proof your project for at least the next few years without being locked into outdated tools.

Load-Balancing the Backoffice: Big News for Larger Teams

Historically, Umbraco’s public-facing sites could be load balanced, but the backoffice had to run on a single server. That limitation made things tricky for larger editorial teams or projects with heavier workflows.

With version 17, the backoffice now supports multi-server environments. That opens up:

• Better performance for teams publishing at scale.
• More resilience (no more single points of failure).
• Simpler infrastructure when scaling out.

If you’ve ever had editors complain about sluggish responses or if you’ve run failover simulations and seen the backoffice choke, this change alone could justify an upgrade.

UTC-Based Time Handling: Small Feature, Big Impact

If you've ever tried scheduling content across multiple time zones, you know how fragile time handling can be. Umbraco 17 addresses that with full UTC standardization for system dates.

Every log, publish time, and update timestamp is now stored in UTC. What this really means is:

• Server location no longer affects scheduling accuracy.
• Editors see time in their local zone while the backend stays consistent.
• Logs and reports are no longer a mess when switching regions or servers.

Umbraco 17 stores all system dates in UTC, ensuring consistent scheduling and timezone‑agnostic behavior across servers and editors. It’s customizable, so you can restrict visible timezones if you’re targeting specific markets.

Backoffice Architecture: From “New” to Default

The redesigned backoffice first appeared back in Umbraco 14 as part of the Bellissima project. With Umbraco 17, that vision finally feels complete. What was once experimental is now the default experience. The extension APIs are more mature, packages play nicely with the new setup, and the UI has reached a point of stability with clear, well-maintained documentation to support it.

For developers, this shift offers a more reliable foundation for building custom editors, dashboards, or integrations without worrying about breakage down the line. Editors, meanwhile, get a backoffice that loads faster, looks sharper, and feels easier to navigate. It’s no longer about adapting to a work-in-progress – it’s just how Umbraco works now.

Accessibility Improvements: Quiet but Important

Not every change in Umbraco 17 is flashy. The accessibility upgrades might not get much attention, but they’ll have a big impact over time.

The Umbraco team worked with external consultants to bring the backoffice in line with WCAG standards, including:

• Better screen reader support.
• Improved keyboard navigation.
• Consistent UI behavior.

Some deeper issues, like support for custom text spacing or advanced keyboard movement, are still on the roadmap for 17.1 and beyond. But what’s in place now already makes the platform more usable for a broader set of teams.

Release Sets: Smarter Publishing Workflows

Version 17 brings Release Sets to the table as a default feature. Instead of publishing one page at a time, editors can now group content items together and schedule them as a batch.

This is ideal for:

• Campaign launches.
• Seasonal content.
• Coordinated updates across sections.

The feature was optional in Umbraco 16 (hidden behind a feature flag). Now it’s on by default and controlled through granular permissions. Teams can enable it selectively based on roles and needs.

Licensing Changes for Umbraco Forms

If you're using Umbraco Forms, there's an important shift in how licensing works. As of version 17, the platform has moved away from the old .lic file system and fully embraced a subscription-based model. That means if you’ve been using a traditional license file, it won’t work out of the box anymore. 

Umbraco 17 introduces a new subscription‑based licensing model for Umbraco Forms, replacing the legacy .lic file. Details on how this integrates with specific hosting setups may vary. 

If you’re on Umbraco Cloud, things are even simpler since the upgrade is handled automatically with no manual configuration needed. This new model brings Forms in line with the rest of Umbraco’s DXP tools, making licensing more consistent across the board while ensuring you continue to receive updates, patches, and support.

Umbraco Cloud: 17 Ready from Day One

If you’re using Umbraco Cloud, you can start building with version 17 immediately. The platform already supports it and includes:

• The latest CI/CD pipeline (with faster deploys and targeted environment setups).
• Bandwidth monitoring tools.
• Custom Identity Provider support for enterprise login flows.

Umbraco 17 supports load‑balancing of the backoffice for horizontally scalable environments; specific cloud platform options may depend on your hosting setup.

Other Add-ons and Enhancements

Beyond the headline features, Umbraco 17 includes a range of smaller updates that still carry weight, especially for teams working with multiple extensions or planning long-term upgrades. These changes might not grab as much attention as the new backoffice, but they quietly improve stability, compatibility, and future readiness across the ecosystem. Here’s what’s worth noting.

Umbraco Commerce

Commerce has matured considerably and is now easier to adopt with version 17. There’s a full starter kit with:

• A ready-to-use shopping cart and checkout.
• A built-in My Account area.
• Step-by-step documentation to help teams onboard faster.

It’s also fully integrated with Umbraco Deploy and Engage, making it suitable for DXP-grade projects.

Umbraco MCP

The Management Control Panel (MCP) for developers continues to evolve. In version 17, it reaches API parity with other management layers and includes better media creation tools and multilingual support.

Umbraco UI Builder

If you're creating custom management interfaces, the UI Builder now ensures forward compatibility with 17+. Custom sections and dashboards upgrade cleanly with the package.

Developer and Community Contributions

A big part of Umbraco 17’s polish comes from the work of contributors. Over 20 developers submitted pull requests, and the community documentation team rewrote or updated over 40 articles to support the new backoffice model.

It’s worth calling out that this isn’t just surface-level polish. There’s been deep cleanup of deprecated code, smarter caching strategies, and better extension points throughout the system.

Upgrade Paths and LTS Timelines

If you’re running Umbraco 13, you can upgrade directly to 17. The platform now supports LTS-to-LTS migrations, with automated schema updates and upgrade guides available.

Support timeline for version 17:

• Full support until: November 27, 2027
• Security updates until: November 27, 2028

This gives development teams and IT leads enough breathing room to commit to the platform long-term without disruption.

Why We’re Excited About Umbraco 17 at OSKI Solutions

At OSKI Solutions, we’ve built and maintained Umbraco-based solutions for clients across industries – from e-commerce platforms to enterprise portals. With version 17, we see a release that finally checks a lot of the boxes we’ve been waiting for. It’s not just about the LTS label. The new load-balanced backoffice, better date handling, and a more stable architecture mean we can build smarter systems for clients with fewer compromises.

We’ve already started transitioning projects to Umbraco 17 where it makes sense, and for new builds, it's our default recommendation. The performance gains from .NET 10, combined with predictable upgrade paths and modern deployment options, give our team a clean runway to deliver long-term value. Whether you’re modernizing a legacy CMS or launching something fresh, this version gives us the confidence to scale with you, not around the platform.

Our clients come to us for reliability, clean architecture, and a practical approach to implementation. Umbraco 17 helps us keep that promise. If you’re considering the jump or just need clarity on how it fits your stack, we’re ready to walk through the details and help plan your next step.

When Should You Upgrade?

Here’s a quick way to decide if Umbraco 17 is worth your time right now:

Yes, upgrade if...

• You’re building something new and want the most stable foundation.
• Your editorial team needs better scalability and reliability.
• You rely on timed publishing and need better timezone consistency.
• You’re planning for long-term support.

Wait if...

• You rely on legacy packages not yet updated for 17.
• Your current version is already heavily customized and you can’t spare the upgrade overhead.

Final Thoughts

Umbraco 17 is one of those releases that earns the title “major.” Not because of marketing, but because it addresses real pain points that have lingered for years. The new backoffice is no longer experimental. Scaling content teams finally get the infrastructure they need. And the technical debt from time handling, licensing, and extensibility is getting cleaned up.

If you’ve been waiting for a version to justify moving forward, this is it.

FAQ