ReRune for Figma
Link Figma text to real keys.
The ReRune plugin connects text layers in Figma to the translation keys in your ReRune project. Designers push copy as drafts and preview every language on the canvas. Developers see where each key is used in the design, and coding agents get the keys through MCP.
Coming soon to Figma Community.
- Free for designers
- Drafts only, never published
- Open source (MIT)
A linked text layer
Checkout
Linked to
- en
- Pay now
- Draft
- de
- Jetzt bezahlen
- de-AT
- Jetzt bezahlen
- from de
- it
- Paga ora
Pushed from Figma as a draft. Publishing happens in ReRune.
From canvas to code
Four steps from design text to shipped keys.
Link layers to keys
Scan a selection or a page and link text layers to existing keys, by search or by exact text match. Layers without a key get a suggested name that follows your project's naming pattern.
Push copy as drafts
Review every change before it leaves Figma. New and edited texts arrive in ReRune as drafts of the main language, and texts changed in both places wait for your decision.
Preview every language
Show any project language on the canvas, draft or published, including variations. Regional languages such as de-AT fall back to their base language where they have no text of their own. Reset restores the original text and styles.
Hand off through ReRune and MCP
Developers open a key in ReRune and see the Figma frames and layers it is linked to, with a screenshot when one was uploaded. Coding agents ask ReRune's MCP server for the keys of a Figma frame. A Dev Mode panel is planned for a later release.
For developers
In ReRune
The key's Design tab shows the frame's screenshot with this layer highlighted and opens the frame in Figma.
For coding agents
get_keys_for_figma_url returns the keys of a Figma frame link with their values.
Free for designers
Designers join ReRune at no extra cost.
The fine print
- Keys created from Figma count toward your plan's key limit.
- Figma bills its own seats. The design-side plugin works on every Figma plan, including the free Starter plan, for anyone who can edit the file; on paid plans that means a Full seat.
- Dev Mode features are planned for a later release and will need a paid Figma plan with a Dev or Full seat.
ReRune stays the source of truth
Nothing is published from Figma.
Drafts, never releases
A push creates keys or updates the main-language draft of existing keys. Publishing happens in ReRune and needs the Publishing permission.
Your permissions, nothing more
The plugin signs in with your ReRune account and can only do what you can do. Pushing needs the Edit keys permission.
Plurals and ReRune edits stay safe
A push never overwrites a plural or ICU message or a disabled key. If a text changed in ReRune since the layer was last synced, you decide which version wins.
The plugin talks only to the ReRune API, and only when you act. Its sign-in stays in Figma's local storage on your device, and you can revoke it in your ReRune profile. How sign-in works
Questions
Questions designers and developers ask.
Contact the ReRune team
Share an idea, report a problem, or ask for help with ReRune.
Is the ReRune Figma plugin free?
Yes. The plugin works on every ReRune plan, Free included, and designers join your organisation as collaborators, which are unlimited on every plan. Keys created from Figma count toward your plan's key limit. The plugin is open source under the MIT licence.
Which Figma plan or seat do I need?
The plugin works on every Figma plan, including the free Starter plan. You need edit access to the file, which on paid plans means a Full seat. Dev Mode features are planned for a later release and will need a paid Figma plan with a Dev or Full seat.
Can the plugin publish translations?
No. Nothing is published from Figma. A push creates keys or updates the main-language draft of existing keys. Publishing stays in ReRune and needs the Publishing permission.
Does ReRune store screenshots of my designs?
Only when the file's Figma link is saved. With Upload screenshots of changed frames on in the plugin, which is the default, a push or Update layers from ReRune uploads one image of each top-level frame it changed, with a box around every linked layer and the text of those layers. ReRune keeps one image per frame, replaces it on the next upload and shows it to members of the project's organisation in the key's Design tab. There, screenshots whose text no longer matches ReRune are marked Outdated, and members can request new ones, which the plugin offers to update the next time a designer opens the file; Update screenshots uploads them even with that setting off. Sandbox accounts never upload images.
Does the plugin work in Dev Mode?
Not yet. The first release works in Figma Design. A Dev Mode panel with each linked key's values and code snippets is planned for a later release and will need a paid Figma plan with a Dev or Full seat. Until then, developers see a key's Figma frames, layers and screenshot in ReRune, and coding agents get the keys of a frame through MCP.
Can AI coding agents use the links?
Yes. ReRune's MCP server has two read-only Figma tools, list_figma_links and get_keys_for_figma_url. An agent that reads a frame through Figma's MCP server passes the same frame link to get_keys_for_figma_url and writes code that calls the returned keys instead of hard-coded strings. ReRune has these links once the file's Figma link is saved in the plugin. No AI runs inside the plugin.
Give your designs real keys.
Figma is a trademark of Figma, Inc. ReRune for Figma is an independent plugin and is not made or endorsed by Figma. Visit figma.com