Umbraco 13: What's New and Why It Matters

Key Takeaways

• Umbraco 13 is built on .NET 8 (LTS), meaning it has Microsoft''s long-term support until November 2026 — this matters for security patches, performance gains, and knowing your platform won''t go stale. Businesses still on Umbraco 8 (end-of-life 24 February 2025) are already running unsupported software. See the official .NET 8 LTS roadmap for lifecycle dates.
• The new Bellissima backoffice is a complete rewrite using Lit/Web Components — it''s faster, more accessible, and dramatically easier for non-technical editors to use day-to-day. This is the single improvement clients notice most after an upgrade, and it directly reduces the time they spend asking us for help with their CMS.
• The built-in Content Delivery API makes Umbraco headless-ready without any extra configuration, opening the door to decoupled front-ends, mobile apps, and composable architectures for businesses that need more than a traditional website. Umbraco Content Delivery API docs cover the full specification.
• Block-level variants and improved media management mean multilingual and media-heavy sites are significantly easier to manage — features that used to require custom workarounds or third-party packages are now first-class citizens in the CMS core.

We''ve been building on Umbraco 13 since its release, and the backoffice improvements alone have changed how our clients manage their content. This isn''t a minor maintenance release — v13 is the biggest leap forward in Umbraco''s history, and if you''re still running an older version, this post will show you exactly what you''re missing.

What Is Umbraco 13 and Why Does It Matter?

Umbraco 13 was released in December 2023 and marked the transition from .NET 7 to .NET 8 — Microsoft''s current long-term support runtime. That might sound like an internal technical detail, but it has real business implications: .NET 8 receives security patches and performance improvements through to November 2026, which means your website is running on a foundation that Microsoft is actively maintaining.

For context, Umbraco 7 and 8 both ran on the older ASP.NET platform. When Umbraco 9 arrived in 2021, it made the jump to .NET 5, and each subsequent version has tracked the .NET release cycle. Umbraco 13 is the current stable LTS release, and it''s the version we recommend for all new builds and migration targets.

It''s worth knowing the supported versions as of early 2026:

• Umbraco 8: End-of-life February 2025 — no longer supported
• Umbraco 10: Supported until November 2025
• Umbraco 13: LTS, supported through November 2026
• Umbraco 14/15: Available but built on Bellissima (same architecture as 13), with shorter support windows

For most businesses, v13 is the sweet spot — stable, well-documented, with a long runway before the next required upgrade.

Bellissima: A Backoffice That Editors Actually Enjoy

The most visible change in Umbraco 13 is the complete rewrite of the backoffice — the admin interface where your team edits content, manages media, and controls the site. This new interface is called Bellissima, and it''s built from the ground up using Lit (a lightweight Web Components framework).

What Changed

The previous backoffice (used in v8 through v12) was built on AngularJS, a framework that Google deprecated in 2022. While it worked, it was starting to show its age: slower page loads in the editor, accessibility issues, and a UI paradigm that felt dated compared to modern SaaS tools.

Bellissima fixes all of this. The interface loads faster, is fully keyboard-navigable, passes modern accessibility standards (WCAG 2.1 AA), and has been redesigned with a cleaner visual hierarchy. Navigation is more intuitive — finding content sections, media folders, and settings no longer requires hunting through nested menus.

What This Means for Your Team

In practice, the Bellissima upgrade means your content editors spend less time confused by the CMS and more time actually updating content. We''ve seen the onboarding time for new editors drop noticeably on sites we''ve migrated from v8 to v13 — the interface simply makes more sense to people who aren''t developers.

It also means less time your team spends emailing us to ask "how do I do X in the CMS." That might sound like a small thing, but for a business managing a 50-page website with two or three non-technical editors, it adds up.

The Content Delivery API: Headless Out of the Box

Previous versions of Umbraco supported headless architecture, but it required either third-party packages (like Umbraco Headless/Heartcore, a separate paid product) or significant custom development to expose content as an API.

Umbraco 13 ships with a built-in Content Delivery API — a RESTful endpoint that lets any front-end framework or external application query your site''s content in JSON format.

Why This Matters for Businesses

Most businesses running a standard website won''t use the Content Delivery API directly. But knowing it''s there matters for a few reasons:

Flexibility for the future. If you later want a mobile app, a digital signage system, or a third-party integration that needs to read your website content, the infrastructure is already in place. You''re not locked into a traditional coupled CMS architecture.

Decoupled front-ends. For businesses with high-performance requirements — e-commerce sites, data-heavy portals, or marketing sites where Core Web Vitals are a competitive priority — a decoupled architecture (Umbraco as the CMS back-end, Next.js or similar as the front-end) is now a realistic option without custom scaffolding.

Composable commerce and integrations. If your site pulls in product data, booking systems, or CRM integrations, a headless Umbraco can serve as the orchestration layer more cleanly than a tightly coupled setup.

For businesses we build custom websites for who anticipate significant growth or complex integrations, we''re increasingly recommending Umbraco 13 in a headless or hybrid configuration precisely because of this capability.

Block-Level Variants: Multilingual Just Got Manageable

Multilingual content has always been possible in Umbraco, but it was historically painful to manage. Content variants (different language versions of a page) existed at the page level, meaning you''d maintain entire parallel page structures for each language.

Umbraco 13 introduces block-level variants, which allow individual content blocks within a page to have language-specific versions. This is a significant improvement for businesses that:

• Serve customers in multiple languages (common in Cornwall and Devon businesses with French or German tourist audiences, or London businesses with international B2B clients)
• Have pages where some content is universal (company values, team bios) and some is localised (pricing, product names, regional contact details)
• Want to roll out multilingual support incrementally without rebuilding entire page structures

In practice, this means your editors can open a page, flip to the French variant, update just the hero text and pricing table, and leave the rest unchanged — without duplicating the entire page structure. It''s a workflow improvement that previously required custom extensions.

Improved Media Management

Media handling in Umbraco 13 has been significantly overhauled, with improvements to both the backoffice media library and the underlying processing pipeline.

What''s New

Automatic image focal point detection is now more reliable, which matters for responsive designs where the same image crops to different aspect ratios on mobile and desktop.

Improved media picker UX in Bellissima makes it faster to find, select, and replace images within content blocks. The old media picker was a common source of frustration for editors — in our experience, it accounted for a disproportionate share of "how do I do this" support requests.

Better handling of SVG and modern formats aligns with a web environment increasingly built around WebP and AVIF delivery. While Umbraco doesn''t replace a proper CDN or image optimisation pipeline, the foundation is cleaner.

Webhooks: Automation Without Custom Code

Umbraco 13 ships with improved webhook support directly in the core — no package required. Webhooks allow the CMS to notify external services whenever content is published, updated, or unpublished.

Practical Uses

• Cache invalidation: Automatically clear a CDN or static cache when content changes, without waiting for a scheduled purge
• Build triggers: For headless setups, trigger a front-end rebuild on Vercel or Netlify whenever content is updated
• Notification workflows: Ping a Slack channel or send a Teams message when a new page is published
• CRM or marketing automation sync: Push content changes to HubSpot, Mautic, or similar tools

None of these required custom development before — they required custom development. Now they''re configuration, which makes automation accessible to businesses without a development retainer.

Umbraco Marketplace Improvements

The Umbraco Marketplace (replacing the older "Our Umbraco" package repository) has matured significantly in the v13 era. Package compatibility information is clearer, version targeting is more explicit, and the quality bar for listed packages has improved.

This matters because Umbraco''s strength as a CMS has always partly come from its ecosystem — form builders, SEO tools, media CDN connectors, analytics integrations. With a more reliable marketplace, the risk of installing a package that breaks on upgrade is lower, and the range of officially supported tools for v13 is now comprehensive.

How Does v13 Compare to What Came Before?

For context, here''s the practical progression:

| Version | Runtime | Backoffice | Headless | Support Status | |---------|---------|-----------|---------|----------------| | v8 | ASP.NET | AngularJS | Package only | EOL Feb 2025 | | v10 | .NET 6 | AngularJS | Package only | EOL Nov 2025 | | v13 | .NET 8 | Bellissima (Lit/WC) | Built-in CDA | LTS (long-term support) | | v14/15 | .NET 8/9 | Bellissima | Built-in CDA | Shorter window |

The jump from v8 to v13 is the most significant platform upgrade in Umbraco''s history. The jump from v10 to v13 is more modest in terms of architecture but still delivers Bellissima and the Content Delivery API.

If you''re on v8, the urgency is high — you''re running unsupported software. If you''re on v10, that support window closed at the end of 2025 — meaning v13 is now the only actively supported LTS release for most businesses.

Is Umbraco 13 Right for Your Business?

Umbraco isn''t the right CMS for every business. It''s a .NET platform that requires experienced developers to build and maintain. It''s a better fit for:

• Medium-complexity websites where WordPress feels limited but full custom development feels excessive
• Businesses with content teams who need an intuitive CMS without constant developer support
• Multi-site or multilingual requirements that would be unwieldy in WordPress
• Organisations with existing Microsoft/.NET infrastructure where technical alignment matters
• High-security environments where you need detailed access control and audit trails

If your business is in one of these categories and you''re evaluating CMS platforms for a new web design project, or you''re already on an older version of Umbraco and considering your options, we''d be happy to talk through whether v13 makes sense.

You can see our full pricing for custom CMS builds on our pricing page.

Frequently Asked Questions

Is Umbraco 13 free to use?

Yes, Umbraco CMS is open source and free to use under the MIT licence. You pay for hosting, development time, and any commercial add-ons or cloud services (like Umbraco Cloud, which is a managed hosting option). The core platform itself — including all the v13 features covered in this post — is free. See the Umbraco licensing page for full details.

How long will Umbraco 13 be supported?

Umbraco 13 has long-term support (LTS) status, meaning it will receive security patches and bug fixes through its LTS window (November 2026). After that, you''ll need to plan an upgrade to a later LTS version. The Umbraco support schedule is publicly published and generally aligns with the .NET release lifecycle that underpins each version.

Can I upgrade directly from Umbraco 8 to Umbraco 13?

Not in a single automated step — upgrading from v8 to v13 requires a migration rather than an in-place upgrade, because the underlying .NET runtime changed fundamentally between those versions. In practice, this means rebuilding the site on v13 and migrating your content. It''s a project, not a software update. We walk through the full process in our Umbraco upgrade guide. If you''re planning this, get in touch early — lead times fill up, especially for sites with complex content structures.

Related Reading

• Umbraco vs WordPress: Which Should You Choose?
• Umbraco 8 End of Life: What You Need to Do Now
• Umbraco Upgrade Guide: v8 to v13
• Should You Upgrade Your Umbraco Website?
• Umbraco Development Costs in the UK