Umbraco V13 reaches end of life in December 2026
What if your editors are still running on V13?
If your organisation is running on it, editors can still publish, manage content, and build layouts. The CMS works brilliantly but V13 and V17 aren't equivalent anymore.
V17 introduces Umbraco.AI, a layer that doesn't exist in V13 and powers Copilot, Automate, Promote, the upcoming Editor MCP, and other integrations available only on V17.
In terms of core CMS capabilities, V13 and V17 are close. In terms of AI capabilities, they're not close at all, and that gap will widen as Umbraco.AI matures.
Umbraco 17 opens access to the AI modular layer, which is changing how enterprises handle content at scale.
With Umbraco V13's December 2026 End-of-Life deadline fast approaching, now is a sensible time to upgrade.
V13 vs V17 for content editing
V13 is a great CMS. Your editors can build pages, manage media, set up workflows with the right customisation, and publish content. Most of the great core editing experience carries across versions.
The difference is what happens around the editing, made possible by Umbraco V17's Umbraco.AI: an optional, modular, flexible layer that lets you use AI where it adds value, in your control, as AI evolves.
| On V13 | On V17 |
|---|---|
❌SEO metadata written manually | ✅ AI generates it from the page content in one click |
❌Alt text typed in by hand | ✅ AI drafts alt text the moment you upload. Editors approve before it goes live |
❌Brand compliance is checked manually | ✅ Copilot reviews copy against your actual guidelines, in the backoffice |
❌Editors switch between tools | ✅ Everything happens inside the backoffice — no tab switching, no lost focus |
❌Content freshness requires a developer report | ✅ Umbraco Automate audits content against the rules you set |
❌Bulk updates need a developer or a manual sprint | ✅ Automate runs governed workflows |
❌Customer journeys set up in external tools | ✅ Triggers, actions and automations built directly in the CMS |
V17's new AI layer puts genuinely useful AI assistance directly into your editors' hands. That layer does not exist on V13.
Breaking distractions, tightening accuracy and speed
With Umbraco Copilot on V17
Most content editors have the same habit: write content somewhere else, copy it into the CMS, and hit publish. Copilot is designed to break that pattern.
It's an AI chat window built directly into the Umbraco V17 backoffice. It knows which page you're on, has access to your content, and can act on it, reviewing SEO metadata, checking copy against your brand tone of voice, or suggesting rewrites, and rewriting it, without you leaving the backoffice.
You configure it with your own guardrails. For a professional services firm, you might set rules like:
• "Always match this tone of voice"
• "Never give financial advice"
• "Flag anything that contradicts our compliance guidelines"
It's simple to use. When an editor asks, "Does this page match our brand?" Copilot reads the page, reads the rules, and gives specific recommendations.
It runs on whichever AI provider your organisation has approved, OpenAI, Anthropic, or Microsoft. In our experience working with the regulated sector, clients are locking it to their existing Microsoft Copilot instance, which means content stays within their corporate data boundary. It's a seriously neat tool. If you want a demo, get in touch.
On V13: Your editors manually check brand compliance, switch between tools, and make judgment calls from memory. Every tab you switch to is a chance to lose your focus.
On V17: Copilot keeps your editors in one place. Doing everything you need in the back office, against your organisation's rules, on the page you're already editing.
Triggering checks, connecting teams, closing gaps
With Umbraco Automate
Copilot is a conversation. You ask it something, it answers and makes changes on the page you're on.
Umbraco Automate is a trigger. You set the rules, what to check, what counts as a problem, and who needs to know. Automate then runs in the background and sends approvals straight to the tools your team already uses, like Slack (for example). Nobody has to check a dashboard or remember to ask each other.
This is a huge benefit to enterprise content teams; it means people in different roles, using different systems, can all work off the same workflow without being in the same room or even online at the same time. An editor in one time zone can publish. A reviewer in another sees the Slack alert, approves or blocks it, and the editor sees the outcome next time they log in.
In a recent Financial Services demo, we ran Automate against 20 articles, including some with deliberate errors. One article promised "guaranteed returns", a clear compliance issue. Automate caught it, blocked the publish, and flagged it in Slack for review.
On V13: A compliance issue like that is only caught if someone happens to spot it, and only if they know who to tell.
On V17: Automate can catch a defined set of rules, block them, and automatically notify the right person in the right system.
There are many other use cases for Umbraco Automate beyond day-to-day content tasks, spanning sales, marketing, and customer service workflows across the wider business.
Talking to Umbraco, not just logging into it
With Hosted Editor MCP in Umbraco
MCP capability is coming for Umbraco editors
Soon, editors will have the same precision and control as Umbraco developers; they will be able to manage site-wide content simply by conversing with an AI!
Umbraco HQ has confirmed a Hosted Editor MCP, built specifically for content editors. Instead of logging into the backoffice, you'll open your preferred AI tool, connect to the Editor MCP, and describe what you need in plain language: create a landing page, draft hero copy, rewrite a section to match your tone of voice, and generate meta descriptions across a set of pages.
On V13: Every content task means logging into the backoffice and working through it screen by screen.
On V17 and beyond: The backoffice groundwork (Copilot, Automate, and the wider Umbraco.AI layer) is what makes a conversational Editor MCP possible in the first place. Editors who are already comfortable working alongside AI in the backoffice will find this a natural next step, not a big leap.
Coming to V17: Hosted Editor MCP for Umbraco
What V17 offers practically and commercially
for content teams
Efficient content operations
Every page that needs an SEO title, a meta description, alt text on images, or a brand compliance check currently costs someone time. Multiply that across hundreds of pages, and it adds up fast. AI-assisted editing doesn't eliminate the editor; it eliminates the drudge work. Your team spends their time on judgment and creativity, not on writing the fifteenth meta description of the afternoon. That's how a content operation grows to match the business without the team having to grow alongside it.
Content quality at scale
When metadata is generated from actual page content rather than rushed by an editor at 4 pm on a Friday, the quality is more consistent. When brand voice compliance is checked by an agent that reads your actual guidelines rather than relying on someone's memory, the output is more reliable. Not perfect. But consistently better than "we'll get to it when we have time.
The Umbraco.AI layer: the unlock behind all of this
On Umbraco V17 and beyond
Umbraco.AI is responsible for all of this new functionality for content editors. It's a flexible, optional layer, available from V17 and up, where you set your rules once, and every tool built on top of it follows them.
The Umbraco V13 to V17 upgrade is the point at which your CMS becomes AI-ready, your editors get tools that genuinely save them time, and your content operations can start scaling without increasing headcount.
The question worth sitting with isn't "does V13 still work?" It's "what are we leaving on the table by staying on it?"
We are now working with the new AI layer available in V17.
If you want to understand what the V13 upgrade would look like for your specific content setup, you can book an upgrade chat with me.
This article contains links to Cogworks pages, products or services
For every article containing links back to Cogworks’ website, we donate £50 to our amazing partner, Community Tech Aid, and any successful partnership will result in another £100 donation to help fund purchases to repair and refurbish donated technology.
Innerworks and Cogworks are proud to partner with Community TechAid who aim to enable sustainable access to technology and skills needed to ensure digital inclusion for all. Any support you can give is hugely appreciated.