Translating Content in the Content Management System
Beta Feature Liferay DXP 2025.Q4+
Currently, this feature is behind a beta feature flag (LPD-17564) and also depends on release feature flags (LPS-179669 and LPD-34594). Read Feature Flags for more information.
Liferay provides integrated tools for translating content to create engaging, localized experiences for your global users. With these tools, you can translate content manually (1) or export (2) and import (3) translations from XLIFF files.
You can also translate specific fields while creating/editing files in the CMS, as well as other elements like vocabularies and categories.
Additionally, you can enable a custom workflow to manage the review and publishing process for translations.
The languages available for translation are determined by your instance’s localization settings. See Initial Instance Localization and Virtual Instance Localization for more information.
Manually Translating Content
-
Open the Global Menu (
) and click CMS. -
Navigate to the All or Contents sections:
-
Click Actions (
) for the content you want to translate and select Translate (
).The translation interface appears, where you can view the content’s original text alongside your translation.
The left column displays the language you’re translating from, and the right column provides editable fields for your translation.
-
Select the language you want to translate.
-
Enter the translation for the available fields. The number of translatable fields appears next to each language, including Title and Friendly URL. When all fields have translations, the language is marked as Translated.
NoteTranslations work regardless of whether the language is marked as translated. Fields with translations appear in the selected language; fields without translations appear in the default language.
-
Choose how to apply your translations:
-
Click Publish to apply your translations immediately.
-
Select Schedule Publication by clicking
next to Publish to set a publication date and time. -
Click Save as Draft to store your changes without publishing.
Publishing your translations applies them to the content and saves a draft.
If a workflow is enabled, publishing starts the review process before the translations are applied.
-
Exporting and Importing Translations
You can export content for translation as .xliff or .xlf files, send them to translators, and then import the completed translations individually or as a .zip file.
Liferay supports both XLIFF 1.2 and 2.0 files. However, it may not support all features and capabilities those formats provide.
Exporting Content for Translation
-
Open the Global Menu (
) and click CMS. -
Navigate to the All or Contents sections:
-
Click Actions (
) for the content you want to translate and select Export for Translation. -
Select an export format: XLIFF 1.2 or XLIFF 2.0.
-
Select the content’s language.
-
Choose the language(s) for the translation(s).
-
Click Export.
Liferay generates a ZIP archive that contains an XLIFF file for each selected experience. You can then use these files with compatible translation software.
Importing Content Translations
-
Open the Global Menu (
) and click CMS. -
Navigate to the All or Contents sections:
-
Click Actions (
) for the content you want to translate and select Import for Translation. -
Click Select Files and select the
.xliff,.xlf, or.zipfiles you want to import.
ImportantLiferay supports importing XLIFF files created using the Export for Translation action, but it cannot guarantee the successful import of files generated by other tools.
-
Click Publish.
If import is successful, Liferay displays a success message with the imported files, and the translations are applied to the content. If workflow is enabled, the translations must be approved before they’re applied.
If errors occur during import, Liferay lists the failed files and provides a downloadable CSV error report.
Translating Files, Vocabularies, and Categories
You can also translate other assets and elements in the CMS, including specific fields for files, content structures, vocabularies, and categories.
-
Start by creating or editing a file, content structure, vocabulary, or category.
See Creating Assets and Folders, Creating Content Structures, and Categorizing Assets to learn more.
-
Click the flag + language icon at the top of the page (1).
-
Select a language to translate. The number of translatable fields appears next to each language, including Title (3) and Friendly URL (4). When all fields have translations, the language is marked as Translated.
NoteTranslations work regardless of whether the language is marked as translated. Fields with translations appear in the selected language; fields without translations appear in the default language.
-
Choose how to apply your translations:
-
Click Publish to apply your translations immediately.
-
Select Schedule Publication by clicking
next to Publish to set a publication date and time. -
Click Save as Draft to store your changes without publishing.
Publishing your translations applies them to the content and saves a draft.
If a workflow is enabled, publishing starts the review process before the translations are applied.
-
