# DOCX

> DOCX file localization

URL: https://store.crowdin.com/docx
Category: File Formats
Type: System
Author: Crowdin

DOCX is a natively supported file format, you can use it without an additional installation. Just upload it to your projects and start the localization.

## Available Configurations


The DOCX file format can be configured to optimize its use with Crowdin for better content handling. The following is a list of available configuration options.


- Superfluous tags сleaning.

- Translate hyperlink URLs.

- Translate hidden text.

- Translate hidden rows and columns (.xlsx).

- Import hidden slides (.pptx).

- Import notes (.pptx).

- Enable content segmentation.

- Custom segmentation rules.

## File Format Details

| Attribute | Value |
| --------- | ----- |
| File Extension | .docx, .xlsx, .pptx |
| [API Type](https://developer.crowdin.com/api/v2/#operation/api.projects.files.post) | docx |
| Source can be edited in Crowdin | No |
| Generating translated files via [Bundles](https://support.crowdin.com/bundles/) | [Search Crowdin Store](https://store.crowdin.com/tags/string-exporter) |
| Supports pluralization | No |
| WYSIWYG Preview in the editor | Yes |
| Supported types of contextual information | Text comments, Screenshots |
| Custom attributes | No |
| Existing translations import possibility | ML-based technology |

## Translating DOCX


**Translating DOCX Files in WYSIWYG View**



While translating a DOCX file in addition to a regular string list view, its content can be displayed in a WYSIWYG view, in a form close to how the document looks in regular document editors. This allows for translating strings taking into account the context of the entire document, which in turn results in higher quality translation.



**Dealing With Rogue Codes/Junk Tags in DOCX Files**



Periodically, when translating DOCX files, you might encounter strings overflown with so-called rogue codes or junk tags. In most cases, it happens to files created with OCR software by converting scanned images into text.



Such files might look okay in MS Word or other text processing editors, but the issue becomes apparent when you open them in Crowdin. For example, when a section of text is bolded, italicized or has some other formatting, instead of having tags for a whole section, each word might be tagged, or tags might appear even in the middle of the words. As a result, such strings become hard to read and impossible to use TM suggestions and glossary terms.



To solve this problem, use *Cleaning superfluous tags* option when importing a docx file. It can be enabled for new files in the project settings, Parsers Configuration section, or changed for already imported file in the file settings.