Umbraco July 2026 Update: New Features to Review
Review the Umbraco 18.0 and 17.5 features Australian teams should assess in July 2026, from redirect management to backoffice performance.
If you are asking about the Umbraco July version, the important detail is timing. As of 27 June 2026, the official Umbraco CMS release sources checked do not show a separate July 2026 release. The relevant new release set for July planning is Umbraco 18.0.0 and Umbraco 17.5.0, both published on 25 June 2026.
For Australian businesses running Umbraco, that means July should be a review and testing window. Version 17.5.0 brings the clearest editor-facing and operational improvements, including a Redirect URL Management workspace, a Current User workspace modal, table-style collection views, fuzzy search in the Property Editor UI Picker, block action extension support, variant sync improvements, and several backoffice performance changes. Version 18.0.0 is the new major release line and points teams back through the 18.0 release candidate notes for the full change set.
This article focuses on what business owners, marketing teams, and technical leads should actually do with the release notes: identify useful features, check upgrade risk, test editor workflows, and decide whether to upgrade now or wait for package and implementation readiness. If you need implementation help, start with our Umbraco development services or broader CMS consulting.
What Changed in the June Release Set
These are the areas most likely to matter during July planning, QA, and upgrade conversations.
No Separate July Release Yet
Official sources checked on 27 June 2026 show 18.0.0 and 17.5.0 as the latest relevant releases, both published on 25 June 2026.
Umbraco 18.0.0
Version 18.0.0 is the new major release line. The final release notes point to the earlier 18.0 pre-release notes for the full change set.
Umbraco 17.5.0
Version 17.5.0 carries the practical feature list many existing Umbraco 17 teams should review first.
Editor Workflow
Redirect management, current user access, collection views, property picker search, and culture switching improvements can reduce day-to-day editor friction.
Backoffice Performance
Release notes call out JavaScript chunk coalescing, reduced startup requests, faster traversal work, and a Tiptap editor bottleneck fix.
Upgrade Risk
Major upgrades still need package checks, custom backoffice extension testing, content workflow QA, hosting checks, and rollback planning.
The New Features Worth Reviewing First
The feature list in the 17.5.0 release candidate notes is the most useful starting point for existing Umbraco 17 teams. It includes editor workflow improvements, developer extension points, collection management changes, and performance work.
| Feature | Why it matters | What to test |
|---|---|---|
| Redirect URL Management workspace | Redirect handling is directly tied to SEO, migration quality, campaign URLs, and old content cleanup. | Create, review, and retire redirects in staging. Check permissions, audit workflow, and URL conflict handling before production use. |
| Current User workspace modal | Backoffice users often need quicker access to their own account, language, or profile context. | Test login, user group changes, permissions, and whether custom backoffice extensions still behave correctly. |
| Table kind collection view | Large content lists can be easier to scan when editors need denser operational views. | Check collections with real content volume, sorting, filtering, custom columns, and permissions. |
| Property Editor UI Picker fuzzy search | Searchable picker experiences can save time on sites with many property editors and data types. | Test common editor searches, misspellings, custom property editors, and performance on larger installations. |
| blockAction extension type | Teams building custom block-based editing experiences get another extension point to shape editor workflows. | Review custom block editors, extension manifests, package compatibility, and documentation for internal developers. |
| Value Type and Value Summary extensions | Backoffice extension teams can expose clearer summaries and value handling for custom editor experiences. | Check custom backoffice packages, schema assumptions, previews, and editor-facing summaries. |
| Variant sync when switching app culture | Multilingual sites can be sensitive to variant state and culture-switching behaviour. | Test multilingual editing, preview, publish, unpublish, rollback, URL generation, and translation workflows. |
| Rich Text Editor read-only support | Read-only states help governance where editors can view content but should not change certain fields. | Check permissions, workflow states, archived content, rollback screens, and any custom RTE configuration. |
For sites that already have migration work planned, connect this review to a structured upgrade checklist. Our Umbraco 17 LTS migration checklist covers package audits, hosting readiness, content QA, SEO checks, and rollback planning.
What to Test Before You Upgrade
Use the July review period to prove the release works with your actual site, not only a clean Umbraco install.
Backoffice Extensions
Check custom dashboards, property editors, block extensions, package manifests, imports, and permissions.
Redirects
Validate redirect creation, deletion, URL conflicts, old campaign links, migration redirects, and SEO crawl behaviour.
Multilingual Content
Test variant switching, preview, publishing, unpublishing, rollback, and editor permissions for every active culture.
Rich Text Editing
Open documents with Tiptap-heavy content, custom blocks, links, images, embeds, and read-only states.
Load-balanced Hosting
Review SignalR transport settings, distributed cache behaviour, deployments, health checks, and session assumptions.
Performance
Measure backoffice startup, editor load time, large collections, descendants traversal, and content publishing in staging.
How to Decide Between 17.5 and 18.0
If your production site is already on Umbraco 17, version 17.5.0 is likely the first release to evaluate because it is closer to your current platform line and contains the editor-facing improvements listed above. That does not make it automatic. You still need a staging upgrade, package checks, regression testing, and a rollback plan.
Umbraco 18.0.0 is a major release. The final 18.0.0 release notes list a dependency bump since the last release candidate and direct readers to the earlier 18.0 pre-release notes for the broader change set. For businesses, the practical meaning is simple: do not treat 18.0 as a routine patch. Check whether critical packages support it, whether custom backoffice extensions use affected APIs, and whether your hosting and deployment process are ready.
For a marketing-led site, the strongest reasons to review the release are redirect governance, better editor workflows, multilingual behaviour, and backoffice speed. For a development-led platform, the stronger reasons are extension points, backoffice package changes, manifest/startup improvements, and load-balanced deployment settings.
Recommended July Action Plan
- Confirm your current version. Record Umbraco version, .NET version, hosting model, packages, custom backoffice extensions, forms, search, member login, and integrations.
- Choose the target line. Existing Umbraco 17 sites should usually test 17.5 first. Treat 18.0 as a separate major-version assessment.
- Clone production to staging. Use a realistic content and media copy so collection views, redirects, culture switching, rich text, and performance checks mean something.
- Run editor workflow QA. Ask real editors to create pages, update blocks, manage redirects, switch cultures, preview content, and publish.
- Run technical regression tests. Check custom controllers, APIs, scheduled jobs, package features, backoffice extensions, deployment scripts, and logs.
- Protect SEO before launch. Crawl key URLs, export redirects, validate metadata, check canonical tags, confirm XML sitemaps, and test analytics after deployment.
If your team needs ongoing release support, VaniTech can help with website support and maintenance, Umbraco development, and practical CMS governance. For AI-related CMS planning, see our article on Umbraco AI governance.
Sources Checked
Umbraco July 2026 Update FAQs
Short answers for teams planning whether to test or upgrade.
Review Your Umbraco Upgrade Risk
VaniTech can assess your Umbraco version, packages, custom code, editor workflows, hosting, SEO risks, and support plan before you commit to a production upgrade.