WPML XLIFF export and import provides a file-based way to move translation jobs between WordPress and external translators who work with compatible desktop CAT tools. Instead of completing the translation entirely inside WPML, an administrator prepares selected jobs, generates XLIFF files, sends them to the translator, and then imports the completed files back into WordPress.
This workflow is specialised rather than a universal requirement for every multilingual team. It is most useful when an external translator already uses a CAT tool and needs a structured handoff. The process depends on careful configuration, a suitable XLIFF version, clear translator notes, and a review of the imported content in its actual WordPress context.
When WPML XLIFF workflows make sense
An XLIFF workflow separates the administrative work from the translation work. The site administrator selects the content and prepares the files in WPML. The translator receives those files, works in a compatible CAT tool, saves the translated result, and returns the completed XLIFF files. WPML then applies the translated content to the relevant translation jobs.
This approach can suit website owners, agencies, and freelancers who coordinate translation outside WordPress. It can also help when a translator’s established process is based on CAT-tool files rather than direct editing in the WordPress dashboard. However, WPML documents XLIFF as a specialised path for translators who already use desktop CAT tools, so it should not be presented as the default choice for every team.
The workflow at a glance
- Configure XLIFF options in WPML → Settings → Translators.
- Select the relevant jobs under WPML → Translations → Translation Tasks.
- Choose the XLIFF version and export the files.
- Send the files to the external translator or through the notification workflow.
- Receive the completed XLIFF files and upload them through WPML.
- Review the translated pages, templates, WooCommerce content, or other relevant context.
Configure WPML XLIFF options before exporting
Start with the configuration rather than exporting immediately. WPML places the XLIFF options under WPML → Settings → Translators. The available settings control the XLIFF version and the elements included in generated files. The wording and screen layout can vary between WPML installations, so use the documented location as the starting point while checking the labels shown on your site.
The receiving CAT tool should influence the choice of version. WPML documents XLIFF 1.2 and 2.0 as available options and notes that different CAT tools may have different preferences. Its workflow guidance describes version 1.2 as the most broadly compatible, but this should not be treated as a promise that one version works with every application. Confirm the receiving tool’s supported or preferred version before creating the handoff.
Choose the XLIFF version and file contents
Review two areas before export. First, select the XLIFF version expected by the translator’s CAT tool. Second, review which elements should be included in the generated files. The right selection depends on what the external workflow needs to process, so do not assume that a single configuration suits every project.
Before applying the export action, confirm the source and destination languages, the intended CAT-tool workflow, and the content fields that should travel with the job. If the translator has supplied file requirements, compare them with the settings in WPML. This small check can prevent an avoidable mismatch between the exported file and the receiving application.
Enable XLIFF attachments in translator notifications
WPML also documents an email-based CAT-tool workflow. In the translator notification options under WPML → Settings → Translators, administrators can enable XLIFF attachments in translator notification emails. This provides a documented way to include the files when the handoff is organised through email notifications.
Email attachment delivery is an alternative to sending exported files directly. Whichever method you use, keep the file handoff associated with the correct translation jobs and tell the translator which XLIFF version and return process are expected.
Export WPML translation jobs as XLIFF files
When the settings are ready, open WPML → Translations → Translation Tasks. Select the translation jobs that should be handled externally. Use the actions menu to choose the required XLIFF version, then apply the export action. WPML generates the files for the selected work.
Selection is an important part of the procedure. Check that the chosen jobs belong to the intended project and language direction. Avoid exporting a broad or uncertain set of tasks simply because the files can be generated quickly. The receiving translator needs a clearly defined scope, and the returned files must be easy to associate with the original jobs.
Before sending the files, also verify the file origin, target language, and intended receiving workflow. Retaining the original exported files provides a practical record of what was handed off. It can help distinguish the original job set from the completed files later in the process.
Add notes before the handoff
Translator notes can carry context that is not obvious from the source text alone. WPML allows notes to be added from the Translations dashboard and included directly in the XLIFF files. Use this opportunity to provide clear, relevant instructions for the particular translation job.
Notes should be connected to the content being translated and should not expand the job beyond what was selected. After adding them, check the generated workflow where possible so that the translator receives the intended context. WPML does not define one universal note format for every CAT tool, so keep the wording straightforward and ensure that the notes support, rather than replace, later editorial review.
Send files to external translators and CAT tools
After export, the files can be delivered directly to the external translator or included through WPML translator notification emails when XLIFF attachments are enabled. The practical handoff should identify the translation jobs, source language, destination language, selected XLIFF version, and expected return path.
In the documented CAT-tool flow, the translator receives the XLIFF file, opens it in a compatible CAT tool, completes the translation, saves the translated result, and returns the completed file. Compatibility should be checked with the receiving application rather than inferred from the file extension. The available research does not establish a complete compatibility matrix for individual CAT tools.
Direct delivery versus notification emails
Direct delivery uses the files exported from Translation Tasks and gives the administrator control over the handoff. The notification workflow connects the files with translator emails and can include XLIFF attachments. Both methods require the same basic discipline: confirm the job scope, preserve the original files, and associate the returned files with the correct translation tasks.
If the translator has a preferred XLIFF version, use that requirement when configuring WPML. Do not describe version 1.2 or 2.0 as universally interchangeable. The appropriate choice depends on the receiving CAT tool and the requirements of the particular workflow.
Import completed XLIFF files into WordPress
When the translator returns the completed files, go to WPML → Translations → Translation Tasks. Locate the Import / Export XLIFF section and use Select File to upload the completed XLIFF file or files. In the notification-based workflow, WPML documents a return path that can support uploading individual files or a ZIP where applicable.
Before uploading, create a current WordPress backup or use a staging copy. The import applies translated content to the site, so this precaution gives the site owner a safer place to verify the result. Also confirm the file source, source language, destination language, selected file set, and translator notes. Do not import files whose origin or contents cannot be trusted.
Uploading a file is not the same as completing quality control. After import, inspect the translated content in the relevant WordPress context. This may include a page, template, WooCommerce content, or another translated area. Review is necessary because the XLIFF workflow moves translation data; it does not replace linguistic, editorial, or contextual checking.
Review imported translations before publication
Check the imported translation where visitors will encounter it. Look at the relevant page or template and verify the translated content in context. For WooCommerce content or another specialised area, review the corresponding translated location rather than relying only on the upload result.
If corrections are needed after upload, WPML documents editing uploaded XLIFF translations with the Classic Translation Editor. That editor must be selected for new translations in WPML settings. Use it for documented post-import corrections, then complete the necessary editorial and layout review before publication.
Troubleshooting and an operational checklist
When an XLIFF workflow does not produce the expected result, begin with the handoff details rather than assuming that the file extension explains the problem. Check whether the receiving CAT tool supports the selected XLIFF version, then verify the original job selection and language direction. The available documentation does not provide a complete compatibility matrix, so changing a setting should be treated as a controlled troubleshooting step, not as a guaranteed fix.
Also confirm that the generated file included the elements required by the external workflow and that translator notes were added before export. On the WordPress side, use the documented Import / Export XLIFF area and inspect the result after upload. Retain the original files and record which jobs were sent, returned, and imported so that the process remains traceable.
Pre-import checklist
- Confirm that the current WordPress backup or staging copy is available.
- Verify the origin of each completed XLIFF file.
- Check the source language and destination language.
- Match the returned files to the intended translation jobs.
- Review the translator notes and confirm that the selected file set is complete.
- Compare the XLIFF version with the receiving CAT tool’s documented requirements.
- Do not upload files when their contents or origin cannot be trusted.
Post-import checklist
- Inspect the translated content in the relevant page or template.
- Review translated WooCommerce content or another applicable WordPress context.
- Use the Classic Translation Editor for documented corrections when required.
- Complete linguistic and editorial review before publication.
- Check the layout and context instead of assuming that successful upload means the work is finished.
- Keep the exported and completed files for workflow traceability.
WPML XLIFF export and import works as a structured handoff: configure the options, choose the translation jobs, add useful notes, select a CAT-tool-appropriate version, exchange the files, import the completed results, and review them in WordPress. XLIFF is a specialised workflow, so its suitability depends on the external translator’s process and the receiving CAT tool’s requirements. There is no universal compatibility promise or substitute for linguistic review. A careful backup, file check, and post-import inspection help keep the process controlled. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.
https://addlinks.pro/SThuI