Diplo Translator Omni

Complex content

Made for the way modern Umbraco pages are built.

Omni finds the words people should read inside structured editors, translates them and reconstructs the target value around the original content model.

Deep editor support

Blocks, rich text and the editors in between.

Marketing pages rarely live in plain text fields. Omni understands nested text inside Block List, Block Grid and Single Block editors, as well as rich-text content and common text editors.

TextboxTextareaRich TextBlock ListBlock GridSingle BlockMultiple TextstringContentment

See the full list of supported property editors for exact editor aliases and the values Omni deliberately skips.

Site-specific property editors can be supported explicitly too. Map simple plain-text or rich-text values in configuration, or add a code adapter for structured persisted values. Omni only opts these editors in when their storage format is understood and can be validated.

Learn about custom property editor support →
Preview reports the real translatable text inside supported properties.
A page preview containing complex Umbraco properties

Preview reports the real translatable text inside supported properties.

Nested blocks

Translate nested blocks without rebuilding the page.

Omni follows supported text properties through nested Block List and Block Grid content. It translates the readable values at each level while retaining the block hierarchy, keys, settings and order.

Nested block content translated from English to Spanish with the original editor structure intact.
English and Spanish Umbraco variants showing translated text inside nested blocks

Nested block content translated from English to Spanish with the original editor structure intact.

Block List walkthrough

From English blocks to a French variant.

See how Omni discovers text inside a mixed Block List, translates it and preserves the original block structure for side-by-side review.

Step 1 of 6Start with the English blocksThe page combines ordinary properties with a Block List containing rich text, image, video and code content.
An English Umbraco page containing a Block List with rich text, image, video and code blocks

Start with the English blocks — The page combines ordinary properties with a Block List containing rich text, image, video and code content.

Step 2 of 6Look inside the rich-text blockText, formatting, a link and an embedded image are stored together inside this block.
English rich-text content inside a Block List item in Umbraco

Look inside the rich-text block — Text, formatting, a link and an embedded image are stored together inside this block.

Step 3 of 6Choose the content to translateOmni finds the translatable text inside the Content Rows Block List alongside the page's other supported properties.
Omni property overview ready to translate an Umbraco Block List from English to French

Choose the content to translate — Omni finds the translatable text inside the Content Rows Block List alongside the page's other supported properties.

Step 4 of 6Translation completeThe report confirms that every selected property and text item was translated successfully into the French draft.
Completed English to French block translation report with no errors

Translation complete — The report confirms that every selected property and text item was translated successfully into the French draft.

Step 5 of 6Compare the complete Block ListThe French variant keeps the same block order, media selections and structure while translating the readable text.
English and French Block List content displayed side by side in Umbraco

Compare the complete Block List — The French variant keeps the same block order, media selections and structure while translating the readable text.

Step 6 of 6Review the translated rich-text blockInside the block, the French text retains its heading, link, formatting and embedded image.
Translated French rich-text content inside a Block List item in Umbraco

Review the translated rich-text block — Inside the block, the French text retains its heading, link, formatting and embedded image.

Rich-text walkthrough

From English to Japanese, step by step.

Follow one complex rich-text property through selection, translation and a side-by-side review. Use the controls to move through the four steps, or select an image to advance.

Step 1 of 4Start with the English contentHeadings, formatted text, lists, links, a table, code and an embedded block all live in one rich-text property.
Complex English rich-text content in the Umbraco editor before translation

Start with the English content — Headings, formatted text, lists, links, a table, code and an embedded block all live in one rich-text property.

Step 2 of 4Review what will be translatedOmni identifies the supported properties and individual text items before creating the Japanese draft.
Omni property overview ready to translate the rich-text content from English to Japanese

Review what will be translated — Omni identifies the supported properties and individual text items before creating the Japanese draft.

Step 3 of 4Translation completeThe result reports every translated property and text value, including anything skipped or needing attention.
Completed English to Japanese translation report with no errors

Translation complete — The result reports every translated property and text value, including anything skipped or needing attention.

Step 4 of 4Compare English and JapaneseThe translated variant retains the original headings, emphasis, lists, links, table, code and embedded content structure.
English and Japanese rich-text content displayed side by side in Umbraco

Compare English and Japanese — The translated variant retains the original headings, emphasis, lists, links, table, code and embedded content structure.

Contentment compatibility

Support for popular community editors.

Omni recognises selected persisted values from Contentment without requiring a direct package dependency.

Text Input
Textbox List
Content Blocks
Notes
The translated language variant remains familiar and editable.
Translated page ready for review in Umbraco

The translated language variant remains familiar and editable.

Technically considered

The right text is translated. The Umbraco model stays Umbraco.

  • Block order, content keys and settings stay connected
  • Media and content selections remain selections
  • Rich-text elements, links and attributes are retained
  • Unsupported non-text editors are clearly reported

This focused approach makes Omni useful on sophisticated agency builds, not just simple brochure pages.

Diplo Translator Omni

Ready to translate your first page?

Bring AI translation into the Umbraco backoffice — and keep the final say with your editors.

View pricing and licensingRead the docs