Short answer: Umbraco provides language variants and Dictionary items, but the best translation workflow depends on content volume, languages, review requirements and budget. Small sites may need only native editing; larger teams may use professional translation management; and integrated AI packages can accelerate first drafts while keeping content in the backoffice.
Does Umbraco support multilingual content without a package?
Yes. Umbraco language variants let one content item hold values for multiple cultures, while Dictionary items supply translated interface strings to templates and code. Editors can switch between languages, use split view and publish selected variants without installing a translation product.
Native features provide the content model and editorial surface. They do not automatically produce translated copy, manage external translators, apply an AI glossary or report which source values have changed since translation.
Which approach fits which project?
| Approach | Best suited to | Strengths | Watch for |
|---|---|---|---|
| Native manual editing | Small sites and bilingual editorial teams | No extra integration; complete editorial control | Repetitive work and limited change tracking |
| Human translator workflow | Regulated, legal, medical or premium brand content | Nuance, accountability and subject expertise | Handoffs, turnaround, import/export and cost |
| Translation management platform | Large organisations and established localisation teams | Assignments, translation memory and professional workflows | Integration complexity and content round-tripping |
| Custom AI integration | Teams with unusual requirements and development capacity | Maximum control over models and workflow | Security, structured values, testing and maintenance remain your responsibility |
| Integrated AI package | Teams wanting fast drafts within Umbraco | Backoffice workflow, variants and bulk translation | Editor compatibility, provider charges and mandatory human review |
Examples of Umbraco translation tooling
Umbraco language variants
The built-in starting point for any current multilingual implementation. Use the official language variants documentation to understand the native editing model.
Translation management products
Products such as Translation Manager provide a dedicated workflow for moving Umbraco content through translation and review. This category is appropriate when assignments, translators and localisation operations matter more than immediately generating an AI draft. Confirm support for the exact Umbraco version and editor types used by the project.
Umbraco.AI-based tools
Umbraco.AI supplies a shared integration layer for AI capabilities and supported providers. Translation packages can build on that layer so organisations choose their provider and profiles instead of sending content through one hard-coded service. See Umbraco's current AI integrations overview.
Diplo Translator Omni
Omni is an integrated AI translation and management package for Umbraco 17. It translates supported page, descendant and Dictionary content into reviewable variants and adds coverage, source-change, glossary and job-history tools. It is designed for teams that want AI assistance while keeping selection, governance and publishing inside Umbraco.
How to evaluate a translation package properly
Feature lists rarely separate these products. What separates them is how they behave on your content, on your Umbraco version. Run these checks during a trial or proof of concept, before committing.
| Check | Why it matters | How to test it |
|---|---|---|
| Structured content survives | Block List, Block Grid and nested blocks are where naive tools corrupt data | Translate your most complex real page and diff the persisted JSON |
| Nothing publishes automatically | Unreviewed machine output reaching a live site is the main reputational risk | Run a job and confirm the target variant stays in draft |
| Unsupported editors are reported | Silent skipping creates gaps nobody notices until launch | Include a custom or third-party editor and read the job result |
| Existing translations are protected | Overwriting reviewed copy destroys real editorial work | Retranslate a page that already has an approved target variant |
| Change detection exists | Without it, maintenance becomes a full manual re-audit every release | Edit source text after translating and see whether the tool notices |
| Permissions are respected | Translation should not become a way around content permissions | Attempt a job as a non-administrator with limited node access |
| Failures are partial, not total | One bad property should not abandon a 200-page job | Force an error mid-job and check per-item reporting |
If you are choosing a package to standardise on across client projects rather than for a single site, offering translation as an agency service covers scoping, licensing and delivery. These are also fair questions to ask any supplier, including this one. If a tool cannot demonstrate the first four, the cost of repairing content will outweigh any licence saving.
Questions to ask before choosing a package
- Which Umbraco versions does it actively support?
- Does it use language variants or create separate content structures?
- Which property editors and nested block structures can it preserve safely?
- Can editors preview and select content before translation?
- Does it overwrite existing translations?
- How are drafts reviewed and published?
- Can it translate Dictionary items as well as pages?
- Does it track changed source content?
- Which providers or translation services can be used, and where is data processed?
- What licence, API, token and support costs apply?
- Does it need to send content to external services or can everything be done inside Umbraco?
Which option should you choose?
Use native manual editing when the site is small and the editors already write every required language. Choose a professional workflow when translation quality, accreditation or external assignments dominate. Build a custom integration only when the requirements justify owning that engineering. Consider an integrated AI package when content volume and update frequency make first-draft automation valuable, but keep editorial review explicit.
Evaluate Omni against the checklist
Review the complete feature set, supported property editors, provider configuration and costs, and the £249 annual Single Site Licence. For the underlying CMS setup, start with how to build a multilingual Umbraco site.