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.

View the multilingual translation demo →

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.

Read Translating content →

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.

Read Translation management tools →

Does it translate Dictionary items?

Yes. Translate on an item includes that item and its descendants; Translate on the Dictionary root or the overview button includes the entire tree. Select a source language and check the scope and item count before starting the background job. Omni fills missing values in every other configured language and preserves existing values unless replacement is explicitly enabled. Dictionary values are saved directly because Umbraco does not provide a draft or publishing stage for them.

Read Translating Dictionary items →

What property editors are covered?

Omni supports Umbraco's core text and block editors, including supported editors nested inside blocks, plus selected third-party editors from Contentment, SeoVisualizer, MetaMomentum, UmbNav, UmbHost.Tables and Community Heading. It translates meaningful text while preserving structure. See Supported property editors for the full list, compatibility details and skipped values.

Read Supported property editors →

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.

Read Custom property editors →

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.

Read Translation management tools →

Can I roll back changes?

Page and section translations are saved as drafts for review through the normal Umbraco workflow. Existing target values are skipped by default, while tracked new or changed block text can be updated selectively. Recovery of overwritten content relies on Umbraco version history and your backups. Dictionary values are saved directly without a draft stage, so use your normal backup arrangements for Dictionary recovery.

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.

Read Permissions →

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.

Read Configuration reference →

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 compatible Umbraco.AI Chat providers, including OpenAI, Anthropic, Google Gemini, Amazon Bedrock, Microsoft AI Foundry, Alibaba Cloud Model Studio, Moonshot AI, OpenRouter and Z.AI. Choose a provider package that supports your Umbraco version, configure its connection and create a Chat profile for translation.

Read Configure Umbraco.AI →

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 installs the core Umbraco.AI package automatically as a dependency. Install a Chat-capable provider integration separately, then configure its connection and profiles. The official integration packages are also free to install, but provider API usage is a separate cost.

Read Configure Umbraco.AI →

Where is my content sent, and is any of it stored?

Omni sends selected, supported text through your site's Umbraco.AI provider, together with translation instructions and matching glossary rules. No translation content is sent to Diplo. Your provider's terms govern its retention and training policies; your site's Umbraco.AI audit, logging and diagnostics settings may also retain request or response data. You control the provider and site configuration, so you can choose a setup that fits your organisation's requirements.

Read Configure Umbraco.AI →

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.

Can I use a local AI model without paying API charges?

In principle, yes, if a compatible Umbraco.AI Chat provider can connect to your local model server. For example, Ollama can run downloaded open-weight models and exposes an OpenAI-compatible API, usually at http://localhost:11434/v1. Run the model server, install a provider package that explicitly supports that endpoint and your Umbraco version, configure its connection and model, then create a Chat profile and approve it in Translator settings. The endpoint must be reachable from the Umbraco server: localhost means the machine running Umbraco, not the editor's computer. A Hugging Face provider does not automatically mean local-model support; check its authentication and model-discovery requirements. A locally run model may avoid per-request API charges, but hardware, electricity, maintenance and any model licence restrictions still apply, and Omni's licence is separate. This describes a possible setup, not a recommendation or a tested Ollama integration. Translation quality, speed and language coverage depend on the model and hardware; test representative content and review the drafts.

Read Configure Umbraco.AI →

Read Ollama API compatibility documentation →

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.

Read Configure Umbraco.AI →

Do I need an account with an AI provider?

Usually, yes, for a hosted AI service. You are responsible for the provider account, credentials, usage limits and charges. A compatible local model setup may not need a hosted provider account. If your hosting organisation or agency supplies a centrally managed provider, 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.

Read Configure Umbraco.AI →

How long does a translation take?

Omni runs translation as a background job with progress you can monitor. Timing depends on the model, text volume, provider limits and retries; try a representative page during your evaluation to measure your setup. Eligible rich-text fragments can run in pairs, and a configurable host-wide limit allows up to four provider requests at once by default across jobs. This is a concurrency ceiling, rather than four requests for every page. Timeout and retry settings help you tune the workflow to your provider.

Read how to measure cost and usage for your own site →

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.

Read AI profiles & prompts →

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 costs the same for Umbraco 17 and 18, with the same licensing terms. It covers one production Umbraco website and includes Omni's page, section, Dictionary and translation-management features. It permits up to three active installations in total across its associated development, test, staging and production environments. These slots do not cover unrelated production sites. Deactivate an unused installation to release a slot; contact support if you need additional installations or have an unusual setup. 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.

Contact us about agency or multi-site licensing →

How do I contact support?

Use the contact form for purchase, licence, setup or usage queries, or use the GitHub issue tracker to open a reproducible bug report or feature request. Include your Omni, Umbraco and .NET versions, relevant messages and steps to reproduce. Use the form for private context; never share licence keys, API keys or confidential content.

Read Contact support →

Open the GitHub issue tracker ↗

Do I get free updates within the licence period?

While your annual licence is active, you can install bug-fix and maintenance updates released for your supported Omni version. Updates may also include new features, but we don’t guarantee particular features or release dates.

Is there a trial version available?

Yes. Try Omni on one Umbraco installation with five accepted single-page draft translation runs and no time limit. Each run targets one language. Install and configure a compatible Umbraco.AI Chat provider with suitable credentials; AI usage costs are separate. Previews and read-only reporting do not consume a run. Section translation, bulk Dictionary translation, overwrite and forced retranslation are included with a paid licence. Use the evaluation link on the pricing page to get started.

Read Pricing & free evaluation →

How do I update?

Update Diplo.Translator.Omni within the version line for your Umbraco major version (17.x.x or 18.x.x) 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. When upgrading from Umbraco 17 to 18, update Diplo.Translator.Omni from 17.x.x to 18.x.x and use matching 18.x Umbraco.AI and provider packages.

Read the release notes on GitHub →

How do I report an issue or feature request?

Use the public GitHub issue tracker for reproducible bugs and feature ideas, or the contact form for licensing questions or anything containing private context. Never post credentials, customer content or access tokens.

Open the GitHub issue tracker ↗

Installation

Getting Omni running

The package, platform and provider setup you need.

What Umbraco versions are supported?

Omni supports Umbraco 17 and 18 on .NET 10. Both use the Diplo.Translator.Omni NuGet package ID: install 17.x.x for Umbraco 17 or 18.x.x for Umbraco 18. Both version lines have identical functionality, configuration, pricing and licensing. Use matching Umbraco.AI and provider packages (17.x or 18.x).

Read Installation & configuration →

How do I install it?

Add the Diplo.Translator.Omni NuGet package with version 17.x.x for Umbraco 17 or 18.x.x for Umbraco 18 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.

Read Installation & configuration →

What requirements are there?

You need Umbraco 17 or 18, .NET 10, at least two languages configured in Umbraco, and a working Umbraco.AI Chat provider and profile using packages that match your Umbraco major version (17.x or 18.x). Users must be administrators or have access to Umbraco's Translation section, as well as the appropriate permissions for any content they translate.

Read Getting started →

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. It is free to install, but you must also install a compatible provider package and configure its connection and profile.

Read Configure Umbraco.AI →

How do I configure a provider API key?

Install the Umbraco.AI package for your chosen provider and follow its credential configuration instructions. Keep keys in a secure environment variable, secret store or protected production configuration. Once the Chat profile works, select or allow it in Translator settings; Omni can otherwise use the site's default profile. Omni uses Umbraco.AI's configured connection, so you do not need to enter a separate provider key in Omni.

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.

Read Documentation home →

Diplo Translator Omni

Still have a question?

Contact support through the form, or explore the setup guide before you buy.

Try it on your own Umbraco site: five single-page draft translation runs, with no time limit. AI provider usage costs are separate.