This documentation applies to Omni for Umbraco 17 and 18. Both version lines have the same functionality and configuration. Choose the package version for your Umbraco site.
Translate single content page
- Save the source culture, including any draft changes you want Omni to read.
- Open the document's Translate workspace view or entity action.
- Choose source (to translate from) and target culture (to translate to) and, when permitted, overwrite behaviour.
- Preview the report and select the supported properties.
- Start the job and inspect its property-level results.
- Review and manually publish the target-culture draft.
Translation jobs require an active licence. The free evaluation includes five accepted single-page draft runs; overwriting existing values and forced retranslation require a paid licence. See licence setup.
Supported fields under Requires review start deselected. Compare the saved source and target before selecting a review field for deliberate replacement, then confirm the replacement when prompted. Permission and paid-licence checks still apply.
Check progress while working elsewhere
A page translation continues in the background when you switch toContent or open another document. Return to the same document's Translate tab to see current progress, or the completed report if the job finished while you were away. You do not need to start the translation again.
If progress cannot be fetched, choose Reconnect to translationto check the same job again. After a successful translation, chooseReview translation to inspect the target draft, orNew translation to start from a fresh preview.
The connection to the job is retained while the current backoffice browser page stays open. After a full browser refresh or closing the tab, use Translation jobs to check its status and results.
Translate multiple pages
Use the content entity action and choose Page and descendants to scan the selected root and its culture-variant descendants. The aggregate preview lets you refine the pages and properties included before starting a monitored job that tracks translation progress.
Section jobs continue past individual page errors and can be cancelled while active. Configured page and property limits prevent accidental oversized jobs.
Section translation requires a paid licence. You can also select pages for one target language in Missing Variants, preview them and start a selected-page batch job. This is separate from translating every descendant of a root.
What Omni preserves
- Block layout, order, keys, settings and connected content
- Media references, picker values, URLs and identifiers
- Rich-text elements, links and attributes
- Existing target text by default; tracked new or changed nested block units may still be translated when safe
Picker values and other non-text fields are deliberately preserved because they contain references or structured data rather than translatable prose. Invariant fields are shared across languages and are skipped. Unsupported or uncertain stored values are reported rather than sent as arbitrary JSON to a model.
Page names and review warnings
When the target-culture page name is missing, Omni translates it alongside selected properties. If properties translate successfully but the name cannot be translated safely, Omni may copy the source name as a reported fallback so the draft variant can be created. Check the target name before publishing.
Amber Review suggested messages identify non-blocking concerns such as retained fragments or changed digits in translated prose. Placeholder text such as “lorem ipsum” may be retained because it has no coherent meaning to translate. Review the reported text, dates, prices and quantities; red errors identify translation, validation or save failures. See Troubleshooting for examples.
Background jobs and restarts
Jobs continue while you navigate around the backoffice, but execute inside the application and do not resume after a restart, recycle or process failure. Stale persisted jobs are marked failed during startup or maintenance. Previously saved drafts remain; inspect them and refresh the preview before starting another job.
Executing jobs and waiting jobs have separate host-wide limits. A job can wait for capacity, and a full queue rejects new work. Overlapping page, section and batch jobs cannot write the same content scope at the same time. Cancellation stops further work where possible; it does not undo drafts already saved, and a provider that ignores cancellation may finish its current request later.
Review and publishing
Content translations are saved as normal Umbraco language variants in draft state. Omni never publishes translated pages; editors retain the final review and publishing decision.
Dictionary items
For reusable interface text and other Dictionary values, follow the dedicated Dictionary translation guide. It covers selecting languages and profiles, bulk jobs, finished-job review and consistent terminology.