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 and details about custom file formats are listed below and sorted by category.
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.
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 ensure 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 email@example.com to start working with custom file formats in your project.
By default, we export the translations in the same format as the source files. For example, if you upload an XML file to Crowdin, you’ll have the XML file exported.
Our developers can make a special processor if you want to configure custom settings for your file export. Some use cases:
Get in touch with our support team at firstname.lastname@example.org, and we’ll gladly help you with setting custom export options based on your needs.
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 the translator attempts to save translation with some modified or missing placeholder, enabled QA checks will notify the translator about the mistake.
As various file formats allow the creation of custom placeholders, we can also add support for the custom ones you use in your project. To request the support of your custom placeholders – email the Crowdin customer success team at email@example.com