Search result not found.

How to translate a file and download the results?
What do I have to consider if my translation texts may contain confidential information?
How to style text within locize?
Word Counter
i18next vs. locize
i18n vs. i18next
How do I open and edit JSON files?
Why do I see strange new keys marked as ONE, FEW, MANY, OTHERS?
Is it possible to integrate multiple projects in the same app/website?
I want to use the locize CDN, but would like to have a fallback that uses local/bundled translations
Why a new namespace is created, when I upload a translation file?
How can a segment/key be copied/moved or renamed?
Where do I find the namespace backups?
Why is there such a high download amount?
How to delete or rename a namespace?
How to manually publish a specific version?
How to import translations from a file?
How to change credit card or billing information or download the invoices?
Why is the pricing so complicated?
Why does my namespace contain an array with a lot of null items?
How to change the publish format?
Why is my namespace suddenly a flat json?
Is there any visibility on project’s level of completion that shows how translators are progressing?
What is the regular way to update the translation memory?
Is locize only for developers and translators or is project management within the process too?
Why do I get “The passed json is nested too deeply.” when consuming the API?
How is locize different from the alternatives?
Do I have to use the locize CDN or can I host / bundle the translations directly?
Which integration option should I use?
General questions
Convince Your Boss Letter
2-factor authentication with Yubikey
2-factor authentication with WebAuthn
2-factor authentication with TOTP
2-factor authentication
Latency Optimization – Tips for Optimal Performance
Backend Fallback
Alternative Caching with i18next
Caching
Multi-Tenant
Notifications
Namespaces
Versioning
Figma Plugin
Migrating from the old InContext editor
InContext Editor
Migrating from Transifex to locize
Migrating from Phrase to locize
Migrating from ...
Migrating an i18next project
Working with translators
Keeping track of new translations
Going to production
How to search
Find unused translations
File Formats
I18n Formats
GitHub Action
CLI
GitHub Repository Dispatch Event
Microsoft Teams
Slack
Webhook
API
Instrumenting your code
Add content
Add a new project
Create a user account
Getting started
Using locize as a translator
Checks/Issues
Focus
InContext
Global
Control Center
The different views
Context
User management
Automatic Translation
History
Review workflow
Glossary
Translation Memory
Tags
CDN (Content Delivery Network)
What's inside?
Introduction
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

On this page

Locize Docs

Introduction

Using locize

What's inside?
CDN (Content Delivery Network)TagsTranslation MemoryGlossaryReview workflowHistoryAutomatic TranslationUser managementContext
The different views
Control CenterGlobalIn ContextFocus
Checks/Issues
Using locize as a translator

Integration

Getting started
Create a user accountAdd a new projectAdd content
Instrumenting your code
API
Webhook
Slack
Microsoft Teams
GitHub Repository Dispatch Event
CLI
GitHub Action
I18n Formats
File Formats

Guides / Tips & Tricks

Find unused translations
How to search
Going to production
Keeping track of new translations
Working with translators
Migrating an i18next project
Migrating from ...
Migrating from Phrase to locizeMigrating from Transifex to locize

More

InContext Editor
Migrating from the old InContext editor
Figma Plugin
Versioning
Namespaces
Notifications
Multi-Tenant
Caching
Alternative Caching with i18next
Backend Fallback
Latency Optimization – Tips for Optimal Performance
2-factor authentication
2-factor authentication with TOTP2-factor authentication with WebAuthn2-factor authentication with Yubikey
Convince Your Boss Letter
General questions
Which integration option should I use?Do I have to use the locize CDN or can I host / bundle the translations directly?How is locize different from the alternatives?Why do I get “The passed json is nested too deeply.” when consuming the API?Is locize only for developers and translators or is project management within the process too?What is the regular way to update the translation memory?Is there any visibility on project’s level of completion that shows how translators are progressing?Why is my namespace suddenly a flat json?How to change the publish format?Why does my namespace contain an array with a lot of null items?Why is the pricing so complicated?How to change credit card or billing information or download the invoices?How to import translations from a file?How to manually publish a specific version?How to delete or rename a namespace?Why is there such a high download amount?Where do I find the namespace backups?How can a segment/key be copied/moved or renamed?Why a new namespace is created, when I upload a translation file?I want to use the locize CDN, but would like to have a fallback that uses local/bundled translationsIs it possible to integrate multiple projects in the same app/website?Why do I see strange new keys marked as ONE, FEW, MANY, OTHERS?How do I open and edit JSON files?i18n vs. i18nexti18next vs. locizeWord CounterHow to style text within locize?What do I have to consider if my translation texts may contain confidential information?How to translate a file and download the results?
More

Figma Plugin

Learn how to install and use the locize Figma plugin in order to start translating your Figma files in locize the right away.

The locize Figma plugin allows you to send text content to your locize project, directly from within Figma and to fetch translations from locize to test your designs. Bridging the gap between translation and product design with our Figma integration creates an efficient workflow from end-to-end.

Install the plugin

You can find the locize Figma plugin in Figma's plugin browser.

Just click the install button on the top right corner of the page.

Ofter the installation, you can access the plugin via the menu of Figma. Next to all your favorite plugins.

Connect Figma with locize

To use the locize Figma plugin, you have to connect Figma with locize. If you do not have access to locize yet, you need to be invited to a project by someone with admin role or you need to create a new locize project.

  1. On your locize project's information card or on your settings page, grab your project-id.
  2. Go back to Figma, open the locize plugin and paste in the project-id.
  3. Choose the appropriate version (usually latest).
  4. If you also want to send missing translations from Figma to locize, make sure you copy your API-Key or create a new one on your locize project's settings page.
  5. If your chosen locize version is configured with private publish mode, click the private checkbox.
  6. Finally, confirm your settings by clicking the Save button.

Send missing translations to locize

If you have not yet started with filling locize with translations yet, this is a good option to start with.

  1. In Figma, select one ore multiple layers.
  2. In the locize plugin window, open the Extract tab.
  3. Click the Extract from current selection button.
  4. The plugin tries to automatically scan your selection for possible translation content.
    1. It will use the layer name as translation segment key.
    2. It will use the frame name as namespace name or if not a single frame is selected, the page name.
  5. You'll now see which resources are missing, and you have the possibility to send those missings to locize. (This is only possible if you provided the API-key in the plugin settings)

‍

Validate your product design with translated content

Having some translated segments in locize, you have the possibility to validate your design with that translations.

  1. In Figma, select the layers or the frame you want to validate.
  2. In the locize plugin window, open the Translate tab.
  3. Chose the desired language.
  4. Click the Translate button.

Step by step example

1. Create a new locize project

Follow this getting started section, if you have not yet started with locize.

You can skip this step, if you already use a locize project.

2. Copy your project id and api key

Like described here, run the locize plugin in figma and copy your project id and api key in the Settings tab.

3. Send first texts to locize

Like described here, select something in your figma design.

When clicking "Extract from current selection", you'll see it uses the layer names as segment key names for locize and it uses the frame name (or page name) as namespace name for locize.

At the bottom of the Extract box, click the "Yes" button to send those texts to locize.

When clicking "Extract from current selection", you'll see it uses the layer names as segment key names for locize and it uses the frame name (or page name) as namespace name for locize.

At the bottom of the Extract box, click the "Yes" button to send those texts to locize.

You can now translate the texts in all your other languages. Depending on your project settings it might also be the segments are already automatically translated thanks to the automatic translation.

4. Validate other languages

Back to figma, you can now switch to the "Translate" tab, choose another language, and click the "Translate" button, like described here.

You can see the Text components are updated accordingly and your layer names stay unchanged.

Now you can add new languages in locize or change the text in locize and validate it in figma with the "Translate" tab.

If you want to send new texts to locize, just select another frame name and repeat step 3.

‍

FAQs

Possible problems with special fonts.

If you're using a special font which is not installed locally, the plugin might not work correctly.

In this case you can try to fix this like described here.

On this page

© 2025 inweso Ltd liab. Co. All Rights Reserved.