Working Offline: Export and Import

You can export a job, project, translation memory, or termbase to work on it outside the Editor: in your own CAT tool, in Word or Excel, or with an external collaborator. When you're done, import the file back to apply your changes. For Flex content (string management), see Export and Import.

If Export and Import are grayed out or missing from the File menu, you're not allowed to use them.


Exporting Your Content

Each export is a bilingual file with the source language and one target language:

  • Jobs and projects: XLIFF, Word, or Excel.

  • Translation memories and termbases: XLIFF only.

Follow these steps to export:

  1. Select File > Export > XLIFF / Word / Excel. In a memory or termbase, select File > Export > XLIFF.

  2. Under Format, select the file format.

  3. Under Languages, select the target language if you have more than one.

  4. Under Template, select what the file includes (see Templates below).

  5. Click Export. The file downloads straight away.

If filters are active in the grid, only the filtered segments are exported.

The file is named after the document when one document is open. Otherwise it's named after the job, project, memory, or termbase. The language codes follow the name, for example _en-fr, and _filtered is added when filters are active.

image-20260508-163620.png
image-20260508-163712.png
The Export menu and its XLIFF, Word, and Excel options.

Templates

Jobs and projects:

Template

What it includes

Basic (source + target)

Source and target text only.

With comments

Adds the comments on each segment.

With comments and TM/terminology hits (80%)

Also adds memory and terminology suggestions from 80% similarity, so the offline translator has context.

Full (comments, TM/terminology hits (80%), custom fields)

Also adds the project's custom fields.

Translation memories and termbases:

Template

What it includes

Basic (source + target)

Source and target text only.

With comments

Adds segment comments.

Full (comments, custom fields)

Also adds custom fields.


What Gets Exported and Imported

The format and the template you choose decide what the file contains and what the import brings back.

Content

Templates

Word

Excel

XLIFF

Source text

All

Exported only

Exported only

Exported only

Target text

All

Exported and imported back

Exported and imported back

Exported and imported back

Existing comments

All except Basic

Exported only: edits and deletions are not imported

Exported only: edits and deletions are not imported

Exported only, as notes: edits are not imported

New comments (see Adding Comments Offline)

All except Basic

Write them in the Add comment row under each segment: imported as new comments

Write them in the Add comment column after the comments: imported as new comments

Add a <note annotates="target">: imported as new comments

TM/terminology hits (80%)

With comments and TM/terminology hits (80%), Full

Exported only

Exported only

Exported only

Custom fields

Full

Exported and imported back, for fields you can edit

Exported and imported back, for fields you can edit

Exported only, as notes

Segment status

All

Not exported

Not exported

Exported in the state attribute. See Statuses in XLIFF Files.

Lock state

All

Not exported

Not exported

Exported as translate="no", not imported

Labels

None

Not exported

Not exported

Not exported

Memories and termbases export to XLIFF only, and their templates have no TM/terminology hits. Changes to locked segments are imported only when you select Overwrite locked segments and you can lock and unlock segments.


Importing Your Edits

Import the edited file to update the segments. You see a preview of the changes before anything is saved. Supported formats are .xlf, .xliff, .xlsx, and .docx, up to 1 GB.

Follow these steps to import:

  1. Select File > Import.

  2. In the Upload step, drag your file into the upload area or click to browse. To also update locked segments, select Overwrite locked segments. Click Continue.

  3. In the Preview step, check the counts under Segments to import: Processed, Changes, No changes, and Skipped segments. For line-by-line detail, click Download report. To pick another file, click Back. When the preview looks right, click Import.

  4. In the Results step, check how many segments changed, then click Done.

Import wizard showing upload and preview steps
The import dialog: the Upload and Preview steps.

To change custom fields when you work in XLIFF, or to change labels, use the Batch Actions Panel.


Adding Comments Offline

Files exported with a template that includes comments let you write new comments offline. When you import the file, each new comment is added to its segment, as if you had typed it in the Editor.

  • Word and Excel: write the comment in the Add comment field for the target language, for example Add comment - French. In Word, it's a row under each segment; in Excel, it's a column right after the existing comments. Leave the field empty where you have nothing to add.

  • XLIFF: there is no Add comment field. Instead, add a note to the translation, <note annotates="target">, inside the segment, and keep the Wordbee information stored in the file. This works for jobs, projects, memories, and termbases. Translation tools that write notes differently may not bring them back.

Changes to existing comments are not imported: if you edit or delete a comment that was already in the file, the segment keeps the original. What you write in the Add comment field is always added as a new comment and doesn't replace an existing one. To change or delete an existing comment, use Edit comment or Delete comment in the Editor.

The Basic (source + target) template has no Add comment field, and notes added to a Basic XLIFF file are not imported.

The Add comment field is included only if you can edit the target language, or if you had edit rights before the job switched you to review-only. A comment on a locked segment is imported only when you select Overwrite locked segments and you can lock and unlock segments.


Statuses in XLIFF Files

In an XLIFF file, each segment records where its pre-translation came from and its status, in the standard state and state-qualifier attributes. If you work in another CAT tool, these attributes decide how each segment comes back.

On Export

Origin

state

state-qualifier

In-context match: same text in the same context, from a memory or a previous version

translated

exact-match

100% match, not in context

needs-review-translation

exact-match

Fuzzy match

leveraged-mt

fuzzy-match

Machine translation

leveraged-mt

mt-suggestion

Auto-correction or rule-based

needs-translation

None

Not pre-translated

new

None

On Import

state in the file

Status after import

final, signed-off

Confirmed (green)

translated, new, needs-translation

Neutral (gray)

needs-review-translation with state-qualifier="exact-match"

Neutral (gray)

needs-review-translation with any other qualifier or none

Error (red)

needs-review-l10n, needs-review-adaption, needs-l10n, needs-adaption

Error (red)

No state, or any other value

Neutral (gray)

As a result, in-context and 100% matches you didn't change come back Neutral, not Error. The online QA check still flags any real issues.

This applies when you import a bilingual XLIFF back into a job, project, memory, or termbase. Uploading an XLIFF as a new source document works differently.


Learn More