XLIFF and HTML export and import for WordPress (Polylang)

Export WordPress posts and pages, with title, content, excerpt, custom and ACF fields set to *Translate* and YOOtheme texts, as XLIFF or HTML, translate them with your agency or CAT tool, and import them as linked draft translations.

XLIFF 1.2HTML

1. Export

Hover a post in Posts or Pages and click the Export for translation row action, which opens Supertext → Translation files. Choose the File format, tick the Target languages and click Download file. Several languages fit into one XLIFF file (wordpress-<post id>.xlf).

2. Translate with your own tool

Open the file in your CAT tool or send it to your translation agency. XLIFF 1.2 works with tools such as Trados Studio, memoQ, Phrase, Crowdin and OmegaT. Translate the texts and leave tags and IDs as they are. HTML suits translators and tools without XLIFF support.

3. Import

On Supertext → Translation files, upload the Translated file (XLIFF or HTML) (up to 10 MB). It's written like an AI translation: the linked translation is created if missing and saved as a draft, YOOtheme and ACF texts go back into their fields, and existing translation texts are replaced. Translations that break, remove or add formatting aren't imported.

What stays intact

In XLIFF, formatting travels as protected tags that translators can move but not break. In HTML files, leave the header (supertext: lines) and the data-st-id attributes unchanged.

Good to know

Requires Polylang Pro.
You need permission to edit the original and its translation.
This is separate from Polylang Pro's own XLIFF export.
HTML files can't mark a text as untranslated: if you import a text unchanged, the source text is written into the target language.