Figma i18n XLIFF Plugin
Export and re-import translations from Figma without breaking your localization pipeline
The Figma i18n XLIFF plugin connects design to the tools localization teams already use. Designers keep working in Figma; translators keep XLIFF, TMS, and review workflows. Exports preserve frame context, imports surface conflicts early, and copy changes stop forcing manual spreadsheet reconciliation.
- Built for
- Product designers, Localization managers, Agencies, Design systems teams
- Availability
- Coming soon
- What was done
The challenge
Design and translation usually live in separate systems. Handoffs rely on CSV exports, informal layer naming, and screenshots. When copy changes after translation starts, teams rework strings manually and ship late.
- Translators lack visual context for where text appears in the UI.
- String keys drift when layers are renamed or duplicated in Figma.
- Round-trips through spreadsheets hide conflicts until QA.
The approach
Export structured XLIFF from text layers, send files through your existing TMS, and import updates back into Figma with guardrails. Frame-aware grouping keeps related strings together; conflict hints flag what needs designer review before merge.
- XLIFF 1.2 and 2.0 export paths for standard tooling
- Frame-aware grouping for screens and flows
- Import review before strings overwrite live layers
- Built for design and localization leads jointly
Four steps, no manual
-
Select frames to localize
Choose screens or flows ready for string freeze. The plugin lists eligible text layers.
-
Export XLIFF
Download a package for your TMS or agency. Metadata keeps frame references attached.
-
Translate externally
Use your existing review workflow, glossaries, and MT policies without changing tools.
-
Import and review
Load translated XLIFF, resolve conflicts, and apply approved strings back to Figma.
What it looks like
What it does
-
Standards-based export
Generate XLIFF packages compatible with mainstream translation systems. No proprietary lock-in for your localization stack.
-
Frame-aware grouping
Strings stay organized by screen and flow so linguists understand layout context, not only isolated sentences.
-
Safe round-trip import
Preview changes and resolve conflicts before text hits components. Reduces accidental overwrites on shared libraries.
-
Component and instance aware
Handles text in components, variants, and instances so design systems stay consistent across locales.
-
Fewer manual exports
Replace ad hoc CSV passes with a repeatable plugin action designers can run before each string freeze.
-
Clear handoff checklist
Built-in guidance on what to name, group, and freeze so localization starts once, not after rework.
Who uses it, and for what
-
Product and localization leads
Multilingual product releases
Ship the same release in English, German, and Japanese without maintaining a parallel spreadsheet someone does not open in Figma.
-
Design studios
Agency client handoffs
Deliver a clean XLIFF package from the design source of truth instead of screenshots plus ad hoc string lists.
-
Design ops
Design system localization
Keep component copy consistent across variants when text lives in instances and properties, not only top-level frames.
-
Growth teams
Continuous localization
Re-export after copy tweaks and see conflicts before strings reach staging builds.
Common questions
Which XLIFF versions are supported?
The plugin targets XLIFF 1.2 and 2.0 export paths used by common TMS products. Final vendor matrix will publish at launch.
Will this replace our TMS?
No. It connects Figma to the stack you already run. Translation memory, review, and vendor management stay in your TMS.
How do I get notified at launch?
Use the contact form on the homepage and mention the Figma plugin. Early access cohorts will open before public release.
Try Figma i18n XLIFF Plugin
Get in touch to join the waitlist for early access.