Umbraco 13 reaches end-of-life on 14 December 2026. If your site runs on 13, you will no longer receive security patches from that moment on. Since 14 December 2025 you already receive no bug fixes at all — security only.
Almost every other version has already expired. Umbraco 17 is the current LTS and is supported until 27 November 2028.
| Version | Type | Released | End-of-life | Status |
|---|---|---|---|---|
| Umbraco 7 | — | 21 November 2013 | 30 September 2023 | Expired |
| Umbraco 8 | — | 26 February 2019 | 24 February 2025 | Expired |
| Umbraco 9 | STS | 29 September 2021 | 16 December 2022 | Expired |
| Umbraco 10 | LTS | 16 June 2022 | 16 June 2025 | Expired |
| Umbraco 11 | STS | 1 December 2022 | 1 December 2023 | Expired |
| Umbraco 12 | STS | 29 June 2023 | 29 June 2024 | Expired |
| Umbraco 13 | LTS | 14 December 2023 | 14 December 2026 | Security phase: security patches only |
| Umbraco 14 | STS | 30 May 2024 | 30 May 2025 | Expired |
| Umbraco 15 | STS | 14 November 2024 | 14 November 2025 | Expired |
| Umbraco 16 | STS | 12 June 2025 | 12 June 2026 | Expired |
| Umbraco 17 | LTS | 27 November 2025 | 27 November 2028 | Fully supported (.NET 10) |
| Umbraco 18 | STS | 25 June 2026 | 25 June 2027 | Supported |
Source: Umbraco LTS & EOL. An LTS version gets three years: 24 months of support with bug fixes and security, followed by 12 months of security only.
No more security patches. A vulnerability found in your version after that date will no longer be fixed. Your site keeps running, but the risk is yours.
You receive security patches until 14 December 2026, and none after that. Bug fixes already stopped on 14 December 2025.
A migration is not something you plan from scratch in a few weeks: the inventory and migration plan take time. The earlier you start, the more room there is to decide what moves over, what gets rebuilt and what can go. What such a project costs is in what does an Umbraco migration cost?
An LTS version (Long Term Support) is supported for three years: 24 months of support, followed by 12 months of security only. An STS version (Standard Term Support) roughly a year.
For most organisations only the LTS line is relevant. Umbraco releases a new LTS shortly after a new .NET LTS ships.
The site simply keeps working. The risk is in security and compliance: you no longer receive patches, and for anyone subject to certifications or vendor requirements, a CMS outside support is often simply not allowed.
Umbraco offers Extended Long Term Support: security patches for 6, 12 or 24 months after the EOL date. That buys time, but solves nothing. Your underlying .NET version and your packages keep aging in the meantime, and the step you're postponing only gets bigger.
Umbraco 17. It is the current LTS, runs on .NET 10 and is supported until 27 November 2028. We migrate from any version to 17 — including from 8 or 10.