Is Umbraco 13 Still Supported? End-of-Life Dates (2026)
Short answer
Umbraco 13 is supported until 14 Dec 2026 (in less than a month).
Umbraco 13 reaches end of life on 14 December 2026. After that, Umbraco's paid XLTS adds 6, 12 or 24 months of security patches at a price Umbraco does not publish. Umbraco 17, which reaches end of life on 27 November 2028, is the upgrade target its docs name.
Legacy Technology Tracker · Status as of 21 Nov 2026. Data checked 12 Nov 2026; refreshed monthly, with quarterly snapshots kept unchanged.
What to do now
Decide before 14 December 2026 whether to upgrade to Umbraco 17, buy XLTS or rebuild. Sites keep running after Umbraco 13 reaches end of life (Umbraco), but Umbraco strongly advises against using Umbraco 13 after that date.
- Upgrade to Umbraco 17. Umbraco's upgrade docs name Umbraco 17, the closest long-term support version, as the target for a site on 13, and Umbraco 18 can't upgrade from 13. Its upgrade path for 13 is a single "13.latest to 17.latest" section. Separately, the docs say a major version upgrade can be done "directly by using NuGet". The docs describe automatic database migrations at first start, not a standalone 13-to-17 tool.
- Buy XLTS. Extended Long-term Support (XLTS) is Umbraco's paid extension: 6, 12 or 24 months of security patches, starting the day after end of life (15 December 2026), with no gaps allowed between extensions and updates delivered through a private NuGet feed. The comparison table lists "Security patches only", a "Frozen feature set" and "No code changes needed". Order through the form, or through your partner manager if you are an Umbraco partner. Umbraco's XLTS pages do not say whether the .NET 8 runtime or add-ons such as Forms and Deploy are covered, so ask when you request the quote.
- Replatform. Umbraco's own end-of-life page lists rebuilding as one of three recommended options: start fresh on Umbraco 17 LTS or above. A move to another CMS is a rebuild with a different target. Umbraco gives no cost or duration for an upgrade or a rebuild. If the work will run past 14 December, XLTS is Umbraco's way to keep receiving security patches in the meantime.
What the upgrade to 17 involves
- .NET 8 to .NET 10. Umbraco 13 requires .NET 8 and Umbraco 17 requires .NET 10; Umbraco's docs say switching to a new major version of the CMS also means switching to a new .NET version.
- AngularJS backoffice extensions are rebuilt. AngularJS code does not run in the new backoffice, so each AngularJS-based extension has to be rebuilt; dashboards, property editors and Content Apps are examples. The
package.manifestfile is replaced byumbraco-package.json, and the same page says the change will likely affect custom property editors. - Removed features need rework. Nested Content and Grid Layout were removed in Umbraco 14; Umbraco recommends Block Grid or Block List. Macros and partial-view macros were removed in 14, and the legacy Media Picker is removed on the 13-to-17 path (upgrade path, breaking changes). On upgrade to 16, TinyMCE data types migrate to TipTap, and keeping TinyMCE needs a third-party package installed before the upgrade (breaking changes).
- Forms and Deploy go first. Umbraco says to upgrade packages like Forms or Deploy before Umbraco.CMS. Deploy 17 needs CMS 17.0.0 or later and .NET 10 (Deploy notes).
- One-off
.liclicences are converted. If you have a one-off.liclicence, it has to be converted to the subscription-based model, and from version 14 the keys are configured underUmbraco:Licenses:Products(licence docs). From version 17, Umbraco Forms supports only licence keys.
Umbraco 17 is the most recent LTS and reaches end of life on 27 November 2028; Umbraco 18 is an STS release ending 25 June 2027. Umbraco 17 runs on .NET 10 LTS, which Microsoft supports until 14 November 2028.
What staying costs
Umbraco does not publish an XLTS price. Its XLTS page describes the cost only as "Predictable per-period cost". Quotes come through the order form, a booking call or a partner manager.
- Doing nothing. Umbraco's XLTS comparison table lists "No protection" for security and "High risk of violations" for compliance in its do-nothing column.
- The runtime is already out of support. Umbraco 13 requires .NET 8, and Microsoft lists .NET 8 end of support as 10 November 2026 (Microsoft support policy), 34 days before Umbraco 13 itself ends.
- On Umbraco Cloud, hosting and patches are separate. Hosting continues through the XLTS period without an XLTS contract, but only projects with an active XLTS contract receive security and compliance patches.
Risk rating
Elevated: support ends 14 Dec 2026. How ratings work
Key facts
Every value links to its source and shows when we last checked or retrieved it. Data checked 12 Nov 2026; status as of 21 Nov 2026.
| Fact | Value | Source | Checked |
|---|---|---|---|
| Support status | SupportedUmbraco CMS 13 (long-term support release). | ||
| End of mainstream support | |||
| End of standard support (security updates) | |||
| Extended support offer | Umbraco XLTS (6, 12 or 24 months; the date is the 24-month maximum) (vendor), until 14 Dec 2028 | ||
| Known exploited vulnerabilities (CISA KEV) | 0 CVEs all time; 0 added in the last 24 monthsScoped to these versions through NVD product (CPE) data. Scoped to Umbraco CMS 13.x via NVD CPE version range; KEV lists no Umbraco product. | ||
| Last release | release-13.16.5, 17 Nov 2026Maintainer: Umbraco HQ | ||
| Job postings and salaries | Not tracked for this entry | — | — |
Versions in scope
Umbraco CMS 13 (long-term support release). Dates per version, each with its source.
| Version | Status | Standard support ends | Extended support ends | Latest release | Source | Checked |
|---|---|---|---|---|---|---|
| 13 | Supported | — | 13.16.5 (17 Nov 2026) |
If you still run Umbraco 13
Start with an inventory of what the move will touch: custom backoffice extensions, content built on Nested Content, Grid Layout or macros, Forms and Deploy, and every third-party package. For packages, Umbraco's upgrade docs say to check the "Umbraco versions" field on the Marketplace for a version that supports the target. Umbraco says the effort depends on which breaking changes affect your project, and gives no duration or cost.
The database upgrades itself. When Umbraco starts on a newer version it detects and applies the needed changes, and large sites may take time at that first start, so rehearse it on a copy first (docs).
Umbraco's own blog post on going from 13 to 17 (30 June 2026) describes two paths: upgrade the existing solution and run the migrations, or prepare a fresh Umbraco 17 solution and move content and schema with Umbraco Deploy import and export. It also says that for most cases it makes more sense to build fresh on 17. The post also promotes Umbraco Cloud and Deploy.
If the site is on Umbraco Cloud, do not run major version upgrades directly in Umbraco Cloud: do them locally, with at least two environments. The Cloud end-of-service policy gives these example dates for Umbraco 13: end of life 14 December 2026, end of XLTS 14 December 2028, hosting ending 14 December 2029, then 30 days of data access (policy). The policy says projects not upgraded or migrated to a supported version by then will stop working.
Frequently asked questions
Is Umbraco 13 still supported?
Yes, until 14 December 2026. Umbraco 13 is a long-term support release that entered its final 12-month Security Phase, in which only security issues are fixed, on 14 December 2025 and reaches end of life on 14 December 2026 (Umbraco support and end-of-life page).
What happens when Umbraco 13 reaches end of life?
The site keeps running, but Umbraco stops supporting it. Umbraco says projects "will technically continue to function" after 14 December 2026, strongly advises against using Umbraco 13 after that date, and recommends upgrading, rebuilding on Umbraco 17 or above, or buying XLTS (Umbraco 13 end of life).
What is Umbraco XLTS?
XLTS (Extended Long-term Support) is Umbraco's paid extension of security patches for a long-term support version after end of life. You choose 6, 12 or 24 months, coverage starts the day after end of life, and extensions must be continuous (Umbraco XLTS). Umbraco's table lists it as security patches only, with a frozen feature set.
How much does Umbraco XLTS cost?
Umbraco does not publish an XLTS price. Its XLTS page describes the cost only as "Predictable per-period cost". Quotes come through the order form, a booking call, or your partner manager if you are an Umbraco partner.
Can I upgrade from Umbraco 13 to 17?
Yes. Umbraco's docs name Umbraco 17, the closest long-term support version, as the upgrade target for Umbraco 13, and say Umbraco 18 can't upgrade from 13 (upgrade path). Expect a move from .NET 8 to .NET 10, plus rework for any AngularJS extensions, removed features such as Nested Content, and one-off .lic licences.
What .NET version does Umbraco 13 need?
Umbraco 13 requires .NET 8, which Microsoft lists as out of support from 10 November 2026 (Microsoft). Umbraco 17 requires .NET 10 (Umbraco docs), which Microsoft supports until 14 November 2028.