All integrations
AvailableDesign

Translate the text in your Figma files.

The Rush plugin reads the text in your frames — by layer, not by screenshot — and creates a translation project in Rush Studio. Translate it with brand voice, glossary and AI quality, and track status right in the plugin. No PNG exports, no re-keying.

Text layers, not screenshotsBrand voice & glossaryPersonal plugin key
Figma · Marketing Site
Hero / DesktopShip in every language.Translate your product without leaving design.Start free
CardTrusted by teams worldwide
Rush · Figma
Hero/titleShip in every language.
Hero/subTranslate your product…
Hero/ctaStart free
Card/labelTrusted by teams…
Pushed to Rush · 4 strings
Category
Design
Authentication
Plugin key
Translate
In Rush Studio
Setup
~2 minutes
What it does

The text in your frames, ready to translate.

Run the plugin on a file and its text becomes a Rush project — the design stays in Figma, the words come to Rush.

Text layers, not screenshots

The plugin reads real text nodes, so translators work with text, never an image.

Structure preserved

Every string keeps its layer and node ID, so nothing loses its place.

Brand voice & glossary

Translate with the same tone rules, glossary and QA as the rest of Rush Studio.

By file or whole project

Run it on one file, specific pages or tagged frames — you decide the scope.

Extract the text, not an image

Every string, straight from the frame.

Point the plugin at a file and it extracts every text layer into a Rush project — each string tagged with its layer and node ID to preserve structure end to end. Only the text you scope is extracted; the design itself stays untouched in Figma.

Every text layer
Headings, body, buttons, empty states — all of it, by node.
Kept in structure
Layer and node IDs travel with every string, so the mapping stays intact.
Scope what is extracted
All text, specific pages or only tagged frames — up to you.
ReplacesScreenshotting frames for translatorsRe-keying text by hand
Rush plugin
Text extracted12 strings
Onboarding/step-1/titleConnect your first file
Onboarding/step-1/bodyPoint the plugin at any frame.
Onboarding/step-2/titlePick your languages
Settings/toggle/labelAuto-translate on change
Empty-state/messageNothing here yet
Extracted by layer — structure kept.
Translate with the whole toolkit

Brand voice, glossary and QA — then track it.

Once the text is in Rush, it is a normal project: brand voice, glossary, translation memory and AI quality apply to every string. The plugin shows each file's translation status so you always know what is done — and when it is, you apply the approved text in your file.

Brand voice & glossary
Your tone rules and approved terms apply to every extracted string.
AI quality on every string
A quality estimate and risk flags before any sign-off.
Status in the plugin
See translated, in review and in progress per file, right in Figma.
ReplacesA translation step disconnected from designGuessing whether the text is ready
Rush plugin · Projects
Landing page
de · fr · ja
Translated
Onboarding flow
de · fr
In review
Settings
es
In progress
Translation status shows right in the plugin. Apply the approved text in your file when you are ready.
How it works

Connected in about two minutes.

1

Generate a plugin key

On the Figma connector in Rush → Sources, generate a personal plugin key. It is yours alone — no OAuth, no broad account access.

2

Install the Rush plugin

Add the Rush Studio plugin from the Figma community — no admin approval required.

3

Paste your key & run

Open the plugin, paste the key and run it on a file to extract its text into a Rush project.

Permissions & security

Only the file you run it on — nothing else.

The Figma plugin works with a personal key you generate, limited to the moment you run it. Here is exactly what that means.

What we access
The file you run it on. The plugin reads the text of the frames you run it on — only when you run it.
The text layers. The strings and their layer/node IDs, to preserve structure for translation.
Your Rush account. To create the project and apply brand voice, glossary and quality control.
What we never do
Browse your other files. The plugin only sees the file you actively run it on — nothing else in your workspace.
Change your design. It reads text; it does not move, restyle or edit anything in your file.
Touch account settings. A plugin key cannot change your Figma account, team or permissions.
The details

How the integration behaves.

The specifics designers ask about before running it on a real file.

Authentication
A personal plugin key you generate in Rush and paste into the Figma plugin. No OAuth or broad account access.
What is read
The text of the frames you run the plugin on — extracted by layer, with node IDs kept to preserve structure.
Where translation happens
In Rush Studio, with brand voice, glossary, translation memory and AI quality on every string.
Getting the text back
Approved translations are managed and exported from Rush. Re-applying them into the layers is a manual step today — the integration does not automatically write into your file.
Scope
Run it by file, by page or on tagged frames — you control exactly what is extracted.
Revocation
Revoke the plugin key any time from Rush; the plugin stops working immediately.
Questions

Figma, in plain terms.

The text layers themselves, by node — never an image. Translators work with real, editable text.

No. The plugin extracts the text and tracks translation status; you apply the approved text in your file. Automatically writing into layers is not part of the integration today — we say so plainly.

Yes. Run the plugin on a whole file, specific pages or only tagged frames — you scope exactly what is extracted.

No. It works with a personal plugin key you generate in Rush, so no team-admin approval is required.

Every string keeps its layer and node ID, so the mapping to your components and styles stays intact.

In your Rush project — with translation memory, glossary and AI quality — where you can review, edit and export them.

Translate Figma text where it lives.

Join the waitlist for early-access pricing and a one-on-one onboarding call to set up the plugin.