Crowdin Enterprise supports a wide range of localization formats, including but not limited to files for mobile, software, documents, subtitles, and graphic assets.
Localize images associated with your product to improve your product’s user experience.
On import, some file formats are automatically converted into other formats to be further parsed and processed. You can see the list of the initial file formats and the file formats they’re being converted into in the table below.
|Initial file format||Converted file format|
File formats that are not officially supported will be recognized as plain text files (if they contain text) or as graphic assets.
Our team can add special code to support your original file formats and ensure that translators see only translatable text rather than the entire file content. This approach allows you to manage custom file formats more effectively.
Contact our support 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 Enterprise, you’ll have the XML file exported.
Our developers can create a special processor if you want to configure custom settings for your file export.
Our developers can create a special processor if you want to configure custom settings for your file export. You upload a key-value file that doesn’t support string editing by default and want to modify it directly in Crowdin Enterprise. The exported file will remain in the original format.
Contact our support team at firstname.lastname@example.org, and we’ll gladly help you set custom export options based on your needs.