What Umbraco 13 end of life actually means for you and your website
- 6 min read
Umbraco 13 support ends December 14, 2026. See what changes, why it isn’t only an IT problem, and how to choose between an upgrade, a rebuild, or a bridge.
The short version
Umbraco 13 reaches end of life on December 14, 2026. Your site won't go down that day. It will look and work the same on December 15 as it did on the 13th. What stops is the safety net of security patches and technical support from Umbraco HQ.
While that may seem simple enough, if you're still on Umbraco 13 you have three options for moving ahead. The right one depends on things only your team knows: how much custom code your site uses, how marketing and IT work together, and how much time you can give this before the holidays.
Below is what changes, why the decision is a group effort, and how we advise organizations on choosing a path.
What changes on December 14
After that date, Umbraco HQ stops providing security patches and technical support for version 13. If someone finds a new vulnerability in the core, there won't be an official fix. Umbraco's own guidance says the site will technically keep working, but it advises against running version 13 past the deadline.
Umbraco Cloud follows the same deadline. Cloud sites keep running after December 14, and automatic security patches end the same as any other install.
There's an earlier date to know about too. Umbraco 13 runs on .NET 8, and Microsoft ends support for .NET 8 on November 10, 2026, about five weeks before Umbraco's deadline. After that, Microsoft stops providing servicing updates, security fixes, and technical support. Umbraco 17, the next long-term support release, runs on .NET 10, which Microsoft supports through November 2028.
Why this isn't only an IT problem
It's easy to file an end-of-life date under "technical task" and hand it to the developers. In our experience it shows up in more places than that. Umbraco lists four risks of running unsupported software: security exposure, instability as the platform stops working well with other systems, compliance problems, and no official support when something breaks.
Each of those lands on someone different. IT is likely responsible for the security review. Finance may have a budget line nobody planned for. Whoever owns compliance gets a question from an auditor or a customer's vendor assessment. And marketing gets the part that's easiest to miss: the site is where campaigns, forms, and analytics live, so an upgrade that goes badly or runs late shows up as lost leads and a stalled content calendar.
This is also where marketing and IT run the risk of talking past each other when there's a time crunch. IT is responsible for security and a stable platform. Marketing wants to publish campaigns without delays. A plan that only considers the perspective of one of them usually stalls. We like to get both teams in one room, agree on what the site needs to do, and then pick the path that makes the most sense for all stakeholders. In fact, a neutral party like Lighturn can often break through any confusion at times like this.
Your three options
We recommend three paths for Umbraco 13 sites, depending on your unique needs.
Path | What it is | Best when | Wrong when |
|---|---|---|---|
Upgrade | Move the existing site to Umbraco 17, the next long-term support release | The site is in good shape and the custom code and packages can carry over | Years of technical debt push the upgrade cost close to a rebuild |
Rebuild | Start fresh on Umbraco 17 or above and rethink the setup | The site no longer fits the business, or you want to change the structure, content model, or design | The deadline is close and the site mostly does its job |
Bridge | Buy Extended Long-term Support: security patches past December 14, in 6, 12, or 24-month terms | You need more time to plan, budget, or work around a launch or campaign | You have a plan in place for an upgrade that can happen before the December 14 deadline. |
Going from 13 to 17 crosses several versions, so plan for real testing and some coordination with your content team. It's a project, not a ticket. A bridge is a legitimate choice, and it works best when it comes with a date for the upgrade or rebuild that follows. We love that Umbraco offers flexible timeframes for the bridge, so you don't rushed into a hasty decision.
How to decide
These are the four questions that help determine which path is right for you.
How much custom code and how many packages does the site have? A lot, especially if some are no longer maintained, points toward a rebuild. Just a handful indicates that an upgrade may work well.
Does the site still fit the business? If you've added brands, products, regions, or a configurator since it was built, an upgrade may be quick but avoids the hard work of learning what your site really needs to do for the business.
How much time do you have, especially if there are other projects pulling focus in Q4. If you can't finish by December 14, a bridge is a reasonable plan as long as the next step has a date on it.
Who has to say yes? Security, finance, and whoever owns the budget should all see the same summary: the date, the options, the rough scope, and the open questions. It's much easier to get a decision when everyone understands the options clearly.
What to do next
Ask your developer to confirm the exact Umbraco version and the .NET version the site runs on.
List the custom code, packages, and integrations the site depends on.
Check where the site is hosted, and whether that host supports .NET 10.
Get marketing and IT into one conversation about what the site needs to do over the next year.
Decide what you'd do if the work isn't finished by December 14.
If this feels daunting, or you'd rather not sort this out alone, we're offering free 30-minute planning calls for Umbraco 13 sites. Book a planning call
Sources
Umbraco 13 End-of-Life (EOL), Umbraco
Long-term Support and End-of-Life, Umbraco
End of support looms for .NET 8 and .NET 9, InfoWorld, citing Microsoft