Adapt your designs for any language

Here’s a list of problems that might surprise you unprepared during the design process:

• Bidirectionality (LTR/RTL) of languages
• Distribution of word lengths in various languages
• Copying strings from design to code (time-consuming duplications)
• Continuous design localization problem & keeping track of updates
• and more…

Figma Plugin by Localazy helps to resolve these problems with ease.

A seemingly perfect design in one language might not necessarily be suitable for every localized variant. And it is the best practice to resolve problems that might appear before implementing the feature.

1. Upload texts from Figma into Localazy.
2. Add languages.
3. Quickly translate strings using the MT pre-translate feature.
4. In Localazy Figma Plugin, download the pseudo-localized content.
5. Test several translations, update the design and fix emerging issues.

Read more about Features & Workflows in the documentation.

Sometimes, when using the Figma Plugin by Localazy, you might encounter an issue that after successfully uploading your text content and translating it in Localazy, when you try to download the translated texts back to Figma, nothing happens.

The most common cause of this issue is missing fonts. Figma should notify you about missing fonts when you open the file by an indicator in the top toolbar.

There are two solutions:

1. Install the missing fonts in your system and get the Figma Font Service if you use Figma in your web browser.
2. Change the texts in Figma to a different font style.

Learn more about solving missing fonts in Figma

Web Upload: The web upload feature is a user-friendly interface provided for uploading screenshots. You can simply drag and drop your screenshot files into the designated area or browse your files to select them. Once the screenshots are uploaded, you can link them to specific phrases in your localization project. This is particularly useful when you want to provide visual context for the phrases being translated. It’s a straightforward process that doesn’t require any technical expertise.

API: For more advanced use cases, we offer a robust API. This allows you to automate the process of uploading and linking screenshots. If you have a large number of screenshots or if you need to integrate this process into your existing development or deployment workflows, the API can be a powerful tool. The API is well-documented and provides flexibility for custom integration. This means you can tailor the API to suit your specific needs, whether you want to automate the upload process, integrate it with your CI/CD pipeline, or build custom features on top of it.

Figma Screenshots: If you’re using Figma for your UI/UX designs, you can take advantage of the our Figma plugin. This plugin allows you to directly upload your screenshots from Figma. It streamlines the process of keeping your designs and localization project in sync. Whenever you update your designs in Figma, you can easily update the corresponding screenshots in your localization project. This ensures that your translators always have the most up-to-date visual context when translating phrases. Find out more about Figma Screenshots feature.

If you’re using Figma as your source of truth, Export Aliases can significantly streamline your workflow. You can upload all your text content from Figma into a single Localazy file (using text node IDs as keys), then use Export Aliases to organize how this content gets exported to your code repositories.

This approach works especially well with Key Clustering, which automatically groups duplicate content. Once set up, your developers can access translated content in the exact format and location they need, while designers can continue working in Figma without changing their process.

Learn more about using Figma as a source of truth with Export Aliases