Supported Formats

Crowdin supports a wide range of localization formats including but not limited to files for mobile, software, documents, subtitles and graphic assets. The list of supported file formats, sorted by category and details about custom file formats are listed below.

Mobile

Localize mobile applications across different devices.

Android
*.xml
iOS
*.strings
Windows Phone
*.resx
Firefox OS
resource files

Software

Localize web & desktop software.

Microsoft .NET
.resx
Java
.properties
GNU GetText
.po, .pot
Ruby on Rails & YAML
.yml
PHP
.php
Generic JSON
.json
Generic XML
.xml
Generic INI
.ini
Windows
.rc, .resw, .resjson
Qt
.ts
Joomla Localization File
.ini
Google Chrome Extension
.json
XUL
.dtd
DKLang
.dklang, .lng
Flex
.properties
NSIS Installer
.nsh
WiX Installer
.wxl
Steamworks Localization
.vdf
Application Resource Bundle
.arb
XLIFF
.xliff, .xml
CSV
.csv

Documents, Subtitles

Localize your help documentation and video subtitles.

XLIFF
.xliff, .xml
HTML
.htm, .html, .xhtml, .xht
HAML
.haml
Plain Text
.txt
CSV
.csv
Markdown
.md
Jekyll Markdown & HTML
.md, .html
MadCap Flare
.flsnp, .flpgl, .fltoc
MediaWiki
.wiki, .wikitext, .mediawiki
OpenDocument
.odt, .ott, .ods, .ots, .odg, .otg, .odp, .otp
Microsoft Office
.docx, .dotx, .xlsx, .xltx, .pptx, .potx
Adobe InDesign
.idml
Adobe FrameMaker
.mif
Youtube Subtitiles
.sbv
WebVTT
.vtt
SubRip
.srt

Graphics and Assets

Localize images associated with your product to improve your product’s user experience.

  1. Upload graphics to Crowdin.
  2. Add all the necessary references for a translator to understand how these graphics should be handled.
  3. Wait for translators to upload localized files.
  4. Download the localized graphics and use them in production.

Custom Services

Note! Custom services are available only on Organization Plans.

Custom File Formats

Note: File formats which are not officially supported will be recognized as plain text files (if they have text content) or as graphic assets.
Our team can help you modify import/export of most of the custom localization files, so you can easily work with the custom file formats used for your software. This way we’ll make sure that translators will see only translatable texts, not the whole file content. Also, you’ll be able to receive the translations in the expected file format (even if you upload files in another format).

To use custom file import/export configurations in your project – email Crowdin customer success team at support@crowdin.com and we will help you manage custom files effectively.

Custom Placeholders

Crowdin supports all the placeholders typical for the supported file formats. They are all automatically highlighted in the Editor, so translators know that they shouldn’t be translated. Even if translator attempts to save translation with some modified or missing placeholder, enabled QA checks will notify translator about the mistake.

As various file formats allow the creation of custom placeholders, we can also add a support of the custom ones you use in your project. To request the support of your custom placeholders – email Crowdin customer success team at support@crowdin.com

See Also