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.
Localize mobile applications across different devices.
Localize web & desktop software.
Localize your help documentation and video subtitles.
Localize images associated with your product to improve your product’s user experience.
Note! Custom services are available only on Organization Plans.
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 firstname.lastname@example.org and we will help you manage custom files effectively.
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 email@example.com