Asset Localization

Crowdin lets you localize both text-based and visual content in one place. Visual files that are not supported for text translation (e.g., .png, .jpeg, .psd, .ai) are recognized as assets, helping you combine localized visuals with translated text for a consistent product experience across languages.

Astuce

There is an option to add custom formats instead of using assets. Search the Crowdin Store or contact our Support Team for more details or available workarounds.

Use Cases

You may upload assets and make all localization data accessible for translators in Crowdin. This helps to:

• Keep all translation data stored under the same roof
• Avoid miscommunication, as you may provide detailed translation instructions for project members by adding context
• Ease the integration of translated content back online, as the initial file formats will be preserved

Typical Workflow

To work with assets, follow these steps:

1. Upload files to your Crowdin project.
2. Add necessary references for the translators to understand how the translations should be done. Use Context for additional details.
3. Allow translators to download the files. For this, open your project and go to Settings > Privacy & collaboration > Translations and enable Allow offline translation.
   Read more about offline translation.
4. Translators will download the files, localize them offline, and upload the translated versions back.

Typical Asset References

• Adobe Photoshop PSD file (an editable source file that translators can modify according to the localization requirements).
• Font files since some assets may use custom fonts.
• Style guide (is shown in the editor as a context or additional downloadable file).
• Manual/instruction that guides through the localization process step by step.

Assets in TXT Format

Some unsupported text formats (e.g., .toc, .gitignore) will be imported to Crowdin as .txt files. Users can translate such files in Crowdin directly.