Supported Formats

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

Mobile

Localize mobile applications across different devices.

Android

.xml

iOS

.strings, .stringsdict

Windows Phone

.resx

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

Flex

.properties

NSIS Installer

.nsh

WiX Installer

.wxl

Steamworks Localization

.vdf

Application Resource Bundle

.arb

XLIFF

.xliff, .xml

CSV

.csv

Angular

.xlf

Mac OS

.plist

Salesforce

.stf

DITA

.dita, .ditamap

JavaScript

.js

Go

.gotext.json

TOML

.toml

i18next

.json

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, .ods, .odg, .odp

Microsoft Office

.docx, .xlsx, .pptx, .doc, .ppt, .xls, .rtf

Adobe InDesign

.idml

Adobe FrameMaker

.mif

YouTube Subtitles

.sbv

WebVTT

.vtt

SubRip

.srt

XAML

.xaml

DITA

.dita, .ditamap

PDF

.pdf

SVG

.svg

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

Custom File Formats

File formats that are not officially supported will be recognized as plain text files (if they have text content) or as graphic assets.

Our team can add special code to support your original file formats and make sure that translators see only translatable texts instead of the whole file content. With this approach, you can manage custom file formats more effectively.

Email Crowdin customer success team at support@crowdin.com to start working with custom file formats in your project.

Custom File Export

By default, we export the translations in the same format as the source files. For example, if you upload XML file to Crowdin you’ll have XML file exported.
Our developers can make a special processor if you want to configure custom settings for your file export. Some use cases:

• You manage both iOS and Android applications. With our help, you can upload just one file format (e.g. XML) to Crowdin and then have 2 separate file types (.xml for Android and .strings for iOS) on export.
• You upload a key-value file (e.g. JSON) and want to modify it in Crowdin directly. We can temporarily convert your file to CSV file format to allow you adding strings online. The exported file will remain in the original format.

Get in touch with our support team at support@crowdin.com and we’ll gladly help you with setting custom export options based on your needs.

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

• Creating a Project
• Translation Strategies
• Inviting Project Participants
• Downloading Translations