Connect in Figma
Sign in to StringsOS from the plugin, then choose or create a project.
Documentation
Send your designs to StringsOS with the Figma plugin, then bring approved translations back into the same text layers.
Navigation
Start in Figma: run the StringsOS plugin and send your designs. They then appear in StringsOS under Sync & Integrations → Design source.
1Figma
2Plugins
3StringsOS
4Send to StringsOS
How it works
The plugin sends only what you choose. Everything else happens in StringsOS.
Send your designs
Send only the screens you choose. StringsOS receives their text and how it’s styled.
Match and translate
Match each text layer to its text in StringsOS, translate it, and review.
Bring text back
Preview the approved translations, then apply them to the same Figma layers.
Push
Figma → StringsOS
Choose screens, check how the text will be named, and send them to StringsOS.
Pull
StringsOS → Figma
Fetch approved translations, preview the changes, and confirm to update your Figma layers.
Setup
Start inside Figma. There’s no token or key to copy.
- 1Open your design file in Figma, run the StringsOS plugin, and select Connect Your StringsOS Account.
- 2In the browser tab, sign in to StringsOS if needed and select Allow Access.
- 3Back in the plugin, choose an existing StringsOS project, or select Create new project (if your role and plan allow it).
- 4Work through the setup steps: Project defaults, Key naming, and Writeback & review. For a new project, enter its name, workspace, and main language first.
- 5Select Save & continue to reach Action Home, then choose Send designs to StringsOS.
- 6Choose the screens to share, check the naming and privacy options, then select Send to StringsOS.
- 7When it’s sent, open Sync & Integrations → Design source in StringsOS to match the text layers and start translating.
Send designs
Send a set of screens, match each text layer, and get the text ready to translate.
- 1
Start a send
Open the plugin and select Send designs to StringsOS (Push · Figma → StringsOS). The plugin doesn’t scan your file while it’s idle.
- 2
Pick your screens
Choose the screens (artboards) that contain text. They’re grouped by Page and Section, and only the ones you check are prepared for upload.
- 3
Check the naming
Review how each piece of text will be named. You can edit the Page, Section, Journey, and Artboard values. Fix any errors before continuing.
- 4
Choose privacy
Leave previews off to send only text and design details, or turn on private previews for the screens you selected.
- 5
Send and match
Select Send to StringsOS, then open the new set under Design source. For each text layer, choose whether to reuse an existing key, create a new one, or ignore it, and save.
- 6
Translate and approve
Translate and review in StringsOS. Translations must be approved before they can be sent back to Figma.
You choose what’s shared
Screens you don’t check are never read or uploaded. Preview images are optional and private. With them off, only text and design details are sent.
Bring text back
Build a plan in StringsOS, fetch it in the plugin, and update your layers only after you’ve previewed the changes.
- 1
Build a plan in StringsOS
From your matched screens, select Build push plan, choose the languages, and generate a preview. The button says “push plan”, but it prepares the update that goes back into Figma.
- 2
Review and approve
Compare the current and new text, and check any warnings, like text that may not fit or a placeholder that doesn’t match. Approving the plan doesn’t change Figma yet.
- 3
Fetch in Figma
Open the plugin, select Apply translations from StringsOS (Fetch · StringsOS → Figma), then choose a language.
- 4
Preview the changes
See every layer and its old → new text. Layers that aren’t safe to overwrite are marked as not writable.
- 5
Apply
Select Apply N changes. The plugin updates the layers in place and tells you which were applied, skipped, or failed.
Original text vs. translations
You can fetch your original text straight away. Translations need an approved plan first. Empty text never erases a Figma layer.
Safety
StringsOS keeps the previous text and styling for every layer it updates.
Preview first
You see the old and new text, and how many layers will change, before you can apply.
Your newer edits are safe
If a layer changed after you matched it, it’s skipped for review instead of overwritten.
Styles are kept
Mixed fonts and text styles are preserved. If a font is missing, the layer is skipped.
Undo any time
After applying, select Undo this writeback, review the preview, and confirm Restore N layers.
A record of changes
Design source records each apply and undo, and which layers were applied, skipped, or failed.
Safe to retry
If you retry or reconnect, nothing gets sent or recorded twice.
Troubleshooting
Start with the message shown in the plugin. These stops are designed to keep your design work safe.
No approved plan yet
Build and approve a plan for the same screens and language, then fetch again in Figma.
The plan is out of date
The design, matching, or translation changed after the plan was built. Rebuild it, review the changes, and approve it again.
A layer was skipped (text changed)
The layer was edited in Figma after you matched it. Check the newer text, update the match if needed, and build a new plan.
A layer was skipped (missing font)
Make the font available in Figma and try again. StringsOS skips it rather than risk breaking the styling.
No languages to choose from
Add your main language and at least one language to translate into in StringsOS, then reopen the plugin.
The plugin signed you out
Reconnect the plugin with your StringsOS account, allow access in the browser, and choose the project again.
What to read next
Review your text in the translation editor, then return to your screens in StringsOS to build the plan.
Connect the plugin, send a few screens, and bring your first translations back.
Free during beta · No credit card required