Skip to main content
DOCX
Ilya Krukowski avatar
Written by Ilya Krukowski
Updated over 2 months ago

DOCX files are widely used for creating and managing text-rich documents in Microsoft Word. Lokalise supports the .docx format, allowing users to easily upload, manage, and translate these documents. Files in this format do not require any special formatting, but there are specific considerations to keep in mind when working with .docx files in Lokalise.

Technical information

Overview

Format name:
DOCX

File extensions:
.docx

Common use cases:
Managing and translating documents created in Microsoft Word, such as user manuals, reports, and other text-rich content.

Technical details:

  • Structure: DOCX files are XML-based documents compressed into a ZIP file. They consist of multiple XML files that define the document's text, styles, images, and other elements.

  • Encoding: UTF-8

Using with Lokalise

Supported project types and file uploading

Please note that DOCX files can be uploaded only to Ad hoc documents projects.

After the project is created, proceed to the Upload page:

Choose one or more files from your PC, and adjust the upload options as needed. Then simply hit Import files.

Translating DOC and other plain text files

Lokalise does not support direct uploading of DOC files as this format is quite old and very different from DOCX. However, there is a way to translate your .doc files and other plain text files:

  1. Create a new translation order: Choose a Gengo provider.

  2. Add your files: Include your .doc or other plain text files in the order.

  3. Submit the order

Known limitations

  • Formulas and graphs: Lokalise currently does not support DOCX formulas and graphs. These elements may be missing or improperly formatted in exported files.

  • Content controls: DOCX content controls are not recognized as keys and are unsupported.

  • Page numbering issues with LibreOffice-generated files: If your DOCX file was created in LibreOffice and you notice incorrect page numbering (e.g., an extra digit before each page number), locate the /word/footer1.xml__/w:ftr/w:p key and remove the unnecessary digit. For example, change <l:field1 />4 to <l:field1 />.

Did this answer your question?