> ## Documentation Index
> Fetch the complete documentation index at: https://developers.phrase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MXLIFF Overview

## What is MXLIFF?

MXLIFF (Memsource XLIFF) is Phrase's bilingual file format. It's based on [XLIFF 1.2](http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html) with an added `m:` namespace that carries Phrase-specific segment and job metadata — translation memory and machine translation matches, confirmation and lock state, tag metadata, custom field values, and more.

MXLIFF is the format used to move translation content into and out of Phrase TMS jobs for editing outside the platform, and to feed translated content back into a translation memory.

For a product-level introduction, see the [MXLIFF Files (TMS)](https://support.phrase.com/hc/en-us/articles/5709739992860--MXLIFF-Files-TMS-) support article. This guide documents the format itself for developers who generate, parse, or round-trip MXLIFF programmatically.

For the full element and attribute reference, see [MXLIFF structure](/en/guides/mxliff/structure).

## When to use it

Reach for MXLIFF when you need to:

* Export a job's segments — source, target, TM/MT matches, confirmation and lock state — for editing with an external tool
* Re-import edited segments back into a job
* Store translations from a bilingual file into a translation memory

## Working with MXLIFF via the API

| Task                                                             | API operation                                                                                                                                              |
| ---------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Export a job as a bilingual MXLIFF file                          | [Download bilingual file](/en/api/tms/latest/job/download-bilingual-file-also-used-to-bulk-edit-translations-confirm-or-lockunlock-segments-via-re-import) |
| Import a bilingual MXLIFF file into a job                        | [Upload bilingual file](/en/api/tms/latest/bilingual-file/upload-bilingual-file)                                                                           |
| Store translations from an MXLIFF file into a translation memory | [Import translation memory](/en/api/tms/latest/translation-memory/import-translation-memory)                                                               |

<Note>
  The same actions are available from the Phrase TMS web UI: **Project → Jobs → Select job(s) → Download → Bilingual MXLIFF** to export, and **Project → Jobs → Tools → Upload → Select MXLIFF** to import.
</Note>

<Note>
  The `m:version` attribute on the root `<xliff>` element identifies the MXLIFF schema version of a given file. New optional elements and attributes are occasionally added as the version increments; unrecognized elements/attributes should be ignored rather than treated as errors.
</Note>