Last updated: 3 November 2026
Choosing an Umbraco version affects more than the features available to your content team. It also determines how long your website receives updates, when you need to budget for an upgrade and how you plan ongoing maintenance.
You may have seen the terms LTS, STS and end-of-life when discussing your website. Understanding the difference makes it easier to choose a release that fits your organisation.
Currently, Umbraco 17 is the latest LTS release, while Umbraco 18 is the latest stable STS release. Umbraco 19 is scheduled to launch in December 2026. Umbraco 13 also remains within its security-only support period, which ends this December.
Here is how the release cycle works and what it means for your website.
How do Umbraco version numbers work?
Umbraco follows semantic versioning, with three parts to each version number: major.minor.patch.
Using the illustrative version number 17.2.1:
- 17 is the major version. A major release can introduce breaking changes that require development work.
- 2 is the minor version. Minor releases add functionality through changes intended to remain compatible with the existing major version.
- 1 is the patch version. Patches address bugs and may include security fixes.
Umbraco schedules two major releases each year. Minor releases generally follow a six-week cycle during active development, while patches are released as needed. See Umbraco’s versioning and release guidance.
For website owners, the distinction matters when planning work. A major upgrade needs an assessment of compatibility and breaking changes. Smaller updates still need appropriate checks before deployment.
What do LTS and STS mean?
LTS stands for Long-term Support. STS stands for Standard-term Support. They describe the support lifecycle of a major release.
| Lifecycle stage | LTS | STS |
|---|---|---|
| Active development | First 6 months | First 6 months |
| Support phase | Next 18 months | Next 3 months |
| Security-only phase | Final 12 months | Final 3 months |
| Total standard lifecycle | 3 years | 1 year |
During active development, releases receive features and fixes. The support phase focuses on bugs, regressions and security. The final phase addresses security issues only. The release reaches end-of-life when that phase ends. See Umbraco’s lifecycle policy.
The practical choice is about how your organisation manages change.
When does LTS make sense?
An LTS release can suit organisations that need a longer window between major upgrades.
It is worth considering when your website has complex integrations, formal approval processes or limited opportunities for major platform changes. A longer support window can make budgeting and release planning more predictable.
However, choosing LTS still requires ongoing maintenance. Your team needs to apply relevant updates, monitor dependencies and plan the next major upgrade before support expires.
When does STS make sense?
An STS release can suit organisations with an established programme of continuous development.
Your team may want functionality introduced in newer releases and have the capacity to assess, test and deploy major upgrades more frequently.
The shorter lifecycle needs to be reflected in your budget and delivery plan. Before choosing STS, establish who owns upgrades and how that work will fit around other priorities.
Which Umbraco versions are currently supported?
As of 3 November 2026, the standard support position is:
| Version | Release type | Security-only phase begins | End-of-life |
|---|---|---|---|
| Umbraco 18 | STS | 25 March 2027 | 25 June 2027 |
| Umbraco 17 | LTS | 27 November 2027 | 27 November 2028 |
| Umbraco 13 | LTS | Already in this phase | 14 December 2026 |
These dates come from Umbraco’s official support schedule.
A higher version number does not automatically give you a longer support window. For example, Umbraco 17 remains supported beyond Umbraco 18 because it is an LTS release.
That is why choosing a version should involve both the functionality you need and the maintenance commitment you can support.
When is Umbraco 19 launching?
Umbraco 19 is scheduled for release on 10 December 2026 as an STS version. Its scheduled end-of-life date is 10 December 2027.
Further ahead, Umbraco 20 is scheduled for June 2027, followed by the next LTS release, Umbraco 21, in December 2027. These are planned dates and should be checked before making delivery commitments. See Umbraco’s published roadmap and support dates.
If you are planning a project now, consider the likely launch date alongside package compatibility and the support window remaining at launch. Waiting for an upcoming release should also be weighed against any approaching deadline on your existing platform.
What does end-of-life mean for my website?
End-of-life means the version has reached the end of its standard vendor support lifecycle, including publicly available security updates.
Your website will generally continue to function. The concern is that newly discovered vulnerabilities may no longer receive fixes for your version without an appropriate extended support arrangement.
This can affect security management, supplier assurance and internal policies on unsupported software. Review those requirements against your actual support arrangements.
For Umbraco 13, the deadline is 14 December 2026. Organisations still using it should establish an upgrade or rebuild plan now. Paid Extended Long-Term Support is available for projects that need additional time, subject to the agreed coverage and terms. See Umbraco’s guidance for version 13.
Do I need to install every major version?
Your upgrade path depends on the starting version, destination and implementation.
Umbraco’s current documentation directs projects through the closest applicable LTS release. For example, an Umbraco 13 project moving to version 18 should first upgrade to Umbraco 17. The development team must still review breaking changes, packages and custom code along that route. See Umbraco’s upgrade documentation.
Do not assume that every intermediate version needs a separate production launch. Ask your development partner to map the migration steps, test them in a separate environment and recommend a release plan.
What else should an upgrade plan cover?
The CMS version is only one part of your platform.
An assessment should also cover the underlying .NET framework, hosting, official add-ons, third-party packages and custom integrations. Each dependency needs a compatible version and an understood support position.
Testing should reflect how people actually use the website. Include publishing, forms, search, authentication, payments and connected business systems where relevant.
For content-heavy websites, also plan how content and media will be checked after migration. Preserve important URLs and metadata, and agree redirects wherever addresses change.
How should we choose between LTS and STS?
Start with four questions:
- What does the website need? Identify the functionality and integrations that influence your target version.
- How frequently can we upgrade? Account for development capacity, testing and business approvals.
- What support window do we need? Consider the expected launch date and your next budget cycle.
- Who owns ongoing maintenance? Make responsibility for updates, monitoring and future upgrades explicit.
Our recommendation is to make version selection part of your website roadmap. Agree the target release, maintenance approach and next review date together.
How Absurd can help
At Absurd, we assess your website’s code, content and integrations before recommending an upgrade route. As an Umbraco Gold Partner, we help organisations plan migrations, test critical journeys and maintain their platforms after launch.
Whether you are choosing a version for a new website or reviewing an existing implementation, we can help you understand the work involved and build a practical delivery plan.