Frequently asked questions
Answers before you translate.
Clear guidance on features, AI providers, support, licensing and getting Diplo Translator Omni running.
Features
Translation and content management
What Omni translates, how it protects content, and who can use it.
What languages are supported?
Omni can translate between any cultures configured as languages in your Umbraco site. The practical language coverage and translation quality depend on the AI model you choose, so check your provider's model documentation for less common languages. In tests Omni has successfully translated content into Chinese, Arabic, Hebrew and Japanese, as well as many European languages.
What property editors are covered?
Omni supports Textbox, Textarea, Rich Text, Multiple Textstring, Block List, Block Grid and Single Block, including supported editors nested inside other blocks. It also recognises selected Contentment editors: Text Input, Textbox List, Content Blocks and Notes. It preserves structure and translates only the meaningful text within supported values. Custom editors can be supported through configuration or an adapter. The Markdown editor is currently skipped. See the documentation for exact editor aliases and the full list of skipped values.
Can I roll back changes?
Translations are saved as drafts, so editors can review or discard them through the normal Umbraco workflow. Existing target values are skipped unless an authorised user enables overwrite. If existing content is overwritten, recovery relies on your normal Umbraco versioning and backup arrangements.
Is there an audit trail?
Yes. Translation Jobs records page, section and Dictionary jobs, including the requester, source and target cultures, timestamps, status, progress, summary counts and errors. Retention can be configured by an administrator.
Which Umbraco users have access to the tool?
Administrators and backoffice users whose user group grants access to Umbraco's built-in Translation section can access Omni. Normal content permissions still apply: a user needs browse permission to preview a page and update permission for the page and target culture to translate or cancel it.
Where do I find advanced settings or configuration?
Administrators can open Translator settings in Umbraco's Settings section to govern available AI profiles, choose a default, inspect stored translation metadata and manage job-history cleanup. Request timeouts, retries, concurrency, access and retention can also be configured under DiploTranslatorOmni in appsettings.json.
What happens when a page's source content changes?
Omni stores hashes for translated source text. The Source Changes dashboard can then identify changed, newly added or removed text—including text nested inside supported blocks—and whether the translated target was edited independently. Affected properties can be preselected for retranslation. Remember that Omni reads saved content, so unsaved browser edits are not detected until the page is saved.
Can it translate entire sections or only one page at a time?
Both. You can translate a single page or choose Page and descendants to process a whole branch of the content tree as a monitored, cancellable background job. Preview the scope first and choose the pages and properties to include.
Does it translate Dictionary items?
Yes. Use the Translate action on the Dictionary root or an individual item, select a source language and one or more targets, and run the work as a background job. Existing Dictionary values are preserved; Omni fills missing translations. Dictionary values are saved directly because Umbraco does not provide a draft or publishing stage for them.
Does it support custom property editors?
Yes, when the stored value can be handled safely. Editors that store plain text or compatible HTML can be mapped in configuration; more structured values need a small code adapter. Anything Omni cannot read confidently is skipped and reported rather than guessed at.
Will it publish translated content automatically?
No. Content translations are always saved as drafts. An editor reviews, adjusts and publishes the target language through the normal Umbraco workflow.
What content is deliberately not translated?
Omni skips media and content pickers, URLs, aliases, keys, UDIs, booleans, numbers, dates, colours, settings and unsupported raw JSON. For rich and block content it preserves layout, keys, links, media references and other structural data.
AI
Providers, profiles and costs
How Umbraco.AI connects Omni to the model you choose.
What AI providers are supported?
Omni works with Chat-capable providers supported by Umbraco.AI, including OpenAI, Anthropic, Google, Copilot, DeepSeek and Mistral. Provider availability can change as the Umbraco.AI ecosystem evolves; confirm that the provider package supports your Umbraco version and exposes a Chat profile.
What is Umbraco.AI and why is it required?
Umbraco.AI is the official shared integration layer that connects Umbraco packages to AI providers and profiles. It is completely free. Omni uses it so provider credentials, model choice and governance stay in one standard place, rather than building a separate integration for every vendor.
Where is my content sent, and is any of it stored?
Omni sends the text you select to the Umbraco.AI provider configured on your own site, using your own credentials. No translation content is sent to Diplo, and no copy of your content is stored outside your Umbraco installation. Only selected, supported text is sent rather than the whole page. How the provider handles the text it receives — including retention and any use for training — is governed by that provider's own terms, so review them when choosing a provider for client content.
Does this package come with a free AI provider?
No. The Omni licence does not include an AI service, API credits or token usage. Some providers may offer free tiers or trial credit under their own terms, but those offers are separate and can change.
How do I get an API key for a provider?
Create an account with your chosen provider, enable billing if required, and create a key in that provider's developer console. Then follow the matching Umbraco.AI provider package instructions. Keep the key in secure application configuration—never commit it to source control or send it in support requests.
Do I need an account with an AI provider?
Usually, yes. You are responsible for the provider account, credentials, usage limits and charges. The exception would be a centrally managed provider supplied by your hosting organisation or agency, in which case ask its administrator for an approved Umbraco.AI profile.
What AI model should I use?
Start with a current general-purpose model that supports your source and target languages well. Test representative pages before running a bulk job: smaller models cost less, stronger models usually handle nuanced or less common languages better. Have an editor review the result either way.
How long does a translation take?
That depends mostly on your chosen model and the amount of text, so it is worth measuring a representative page with your own provider rather than relying on a headline figure. A single page is typically a short wait; a large section is a background job you can leave running, monitor and cancel. Omni sends several requests in parallel — four by default, configurable — and each request has its own timeout and retry settings, so throughput can be tuned to your provider's rate limits.
Can different editors use different models?
Yes. Administrators can allow multiple Umbraco.AI Chat profiles and set a default. Editors can then select an approved profile for a Dictionary, page or section job.
Support
Licensing, updates and help
What to expect after purchase and where to ask for help.
What does the licence cover?
The £249 annual Single Site Licence covers one production Umbraco website and includes Omni's page, section, Dictionary and translation-management features. Development, staging, multisite, transfer and agency-use details are governed by the final licence supplied at purchase; contact support if your setup is unusual. AI provider usage is separate.
Can I license Omni for multiple sites or agency use?
Yes. Agency and multi-site licensing options are available by arrangement. If you need Omni for multiple production sites or for client sites managed by an agency, contact us to discuss your setup.
How do I contact support?
Email support@diplo.co.uk for purchase, licence, setup or usage help. Include your Omni, Umbraco and .NET versions, AI provider and profile, cultures involved, property editor alias, relevant job message and reproducible steps—without API keys or private content.
Do I get free updates within the licence period?
Update entitlement and the maintenance period are defined by the purchase description and final licence in force when you buy. Check those terms at checkout or email support before purchasing; the website does not currently promise an update period beyond them.
Is there a trial version available?
A free evaluation will be available when online licensing opens. Rather than a countdown that expires before you have time to test properly, it will give you a limited number of page translations that do not run out with time, alongside unlimited previews and read-only access to the coverage and reporting tools — enough to check Omni against your own content model and languages. Section jobs and bulk Dictionary translation are not included. Until then, contact Dan to discuss evaluating Omni on your site.
How do I update?
Update the Diplo.Translator.Omni NuGet package in your Umbraco web project using your normal NuGet workflow, rebuild and deploy the site, then review the release notes for any version-specific steps. Test the update and back up the site and database before deploying to production.
How do I report an issue or feature request?
Use the public GitHub issue tracker for reproducible bugs and feature ideas, or email support for licensing questions or anything containing private context. Never post credentials, customer content or access tokens.
Installation
Getting Omni running
The package, platform and provider setup you need.
How do I install it?
Add the Diplo.Translator.Omni NuGet package to your Umbraco web project, rebuild and restart the site, then sign in to the backoffice. Install and configure a compatible Umbraco.AI Chat provider as well. See the documentation page for the exact command and configuration example.
What requirements are there?
You need Umbraco 17, .NET 10, at least two languages configured in Umbraco, and a working Umbraco.AI Chat provider and profile. Users must be administrators or have access to Umbraco's Translation section, as well as the appropriate permissions for any content they translate.
What Umbraco versions are supported?
The current release targets Umbraco 17 and .NET 10. Do not assume compatibility with earlier or later major versions unless a release specifically states it.
Why do I need to install Umbraco.AI?
Umbraco.AI supplies the standard Chat provider and profile abstraction Omni uses to request translations. It lets you choose and change compatible providers without Omni storing a provider-specific key or being tied to one vendor.
How do I configure an API key?
Install the Umbraco.AI package for your chosen provider and follow that provider package's configuration instructions. Store the key in a secure environment variable, secret store or protected production configuration rather than source control. Once its Chat profile works, select or allow that profile in Translator settings; Omni can otherwise use the host site's default profile.
Where can I find setup documentation?
The documentation page covers requirements, the NuGet command, appsettings configuration, a suggested profile prompt and the first translation workflow. Umbraco.AI's own documentation covers provider-specific installation and credentials.
Diplo Translator Omni
Still have a question?
Email support@diplo.co.uk, or explore the setup guide before you buy.