Start in the Figma plugin
Authorize with your StringsOS account, choose or create a project, and complete its shared setup inside the plugin.
Documentation: Figma integrationExpand navHide nav
Documentation
Start in the StringsOS Figma plugin, connect or create a project, and send selected designs to StringsOS before mapping text layers and pulling approved copy back into Figma.
Navigation
For a fresh connection, begin in the StringsOS plugin inside Figma. Choose or create the StringsOS project there, finish project setup, and send selected artboards. After the first send, the content appears under Sync & Integrations → Design source in StringsOS.
1Figma
2Plugins
3StringsOS
4Send to StringsOS
Two-way workflow
A fresh connection begins in the Figma plugin. The plugin pairs or creates the StringsOS project and sends only the content you select. StringsOS becomes the workspace for mapping, localization, review, and approved writeback plans.
Push selected designs
Send only the artboards you choose. StringsOS receives their text, layout context, and style metadata.
Map and localize
Reuse or create keys, translate the copy, resolve mapping changes, and complete review and QA.
Pull approved copy
Preview approved source or translated copy and apply it to the same Figma layers after confirmation.
Push
Figma → StringsOS
Select artboards, confirm the naming pattern, and send the chosen text layers to Design source for mapping and localization.
Pull
StringsOS → Figma
Fetch approved source or translated copy, inspect the diff, and confirm the write to the original mapped layers.
Setup
For a fresh project, start inside Figma. The plugin authorizes as you, and there is no Figma token or bridge key to copy.
- 1Open the 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.
- 3Return to the plugin. Choose the existing StringsOS project for this file, or select Create new project if you have permission and plan capacity.
- 4Complete the Project defaults, Key naming, and Writeback & review steps. For a new project, enter its name, workspace, and source language first.
- 5Select Save & continue to reach Action Home, then choose Send designs to StringsOS.
- 6Select the artboards to share, review the generated key naming and preview privacy options, then select Send to StringsOS.
- 7After the send succeeds, open Sync & Integrations → Design source in StringsOS to map the received layers and begin localization.
Push workflow
Send a deliberate artboard set, map its layers to localization keys, and prepare the copy for translation.
- 1
Choose the push workflow
Open the StringsOS plugin in Figma and select Send designs to StringsOS (Push · Figma → StringsOS). The plugin does not scan the file while it is idle.
- 2
Select the artboards
Choose text-bearing artboards across the file. The picker groups them by Page and Section, and only checked artboards are prepared for upload.
- 3
Confirm key naming
Review the saved key pattern and editable Page, Section, Journey, and Artboard values. Fix any validation errors before continuing.
- 4
Choose preview privacy
Leave private Visualizer previews off for metadata-only intake, or explicitly enable previews for the selected artboards.
- 5
Send and map content
Select Send to StringsOS, then open the new artboard set under Design source. For each text layer, choose reuse, create, or ignore and save the mapping.
- 6
Translate and approve
Complete translation, QA, and approval in StringsOS. Target-language copy must be approved before it can be included in a pull plan.
Privacy by selection
Unchecked artboards are not extracted or uploaded. Preview images are optional and private; leaving the option off sends text and design metadata without retaining an artboard image.
Pull workflow
Build a reviewed writeback plan, fetch it in the plugin, and update the exact mapped layers only after confirming the diff.
- 1
Build a push plan in StringsOS
From the mapped artboard set, select Build push plan, choose the target languages, and generate a preview. Despite the product term “push plan,” this prepares the pull from StringsOS into Figma.
- 2
Review and approve the plan
Compare current and proposed values and review risk flags such as source changes, mixed styles, possible overflow, and placeholder mismatches. Approving the plan does not change Figma.
- 3
Choose the pull workflow in Figma
Open the plugin and select Apply translations from StringsOS (Fetch · StringsOS → Figma), then choose a language card.
- 4
Preview the exact diff
Check every writable layer and its old → new value. Rows that are unsafe to overwrite remain marked as not writable.
- 5
Confirm the write
Select Apply N changes. The plugin updates the mapped layers in place and reports applied, skipped, and failed rows separately.
Source copy and translations behave differently
Source-language copy can be fetched directly from its language card because StringsOS treats the current source value as authoritative. Target languages require an explicit, approved push plan before the plugin can fetch them. Blank source values never erase a Figma layer.
Safety and recovery
StringsOS stores the previous value and style information for every applied layer, giving each confirmed write a traceable recovery path.
Preview before write
The plugin displays old and new values and the number of layers that will change before Apply is enabled.
Protect newer design edits
A layer changed after mapping is skipped for review instead of being silently overwritten.
Preserve styles
Mixed font and text styles are captured and reapplied. Missing fonts cause a safe skip, not a partial style write.
Undo the writeback
After a successful apply, select Undo this writeback, review the restore preview, and confirm Restore N layers.
Keep an audit trail
Design source records apply and rollback runs with applied, skipped, and failed outcomes.
Retry safely
Idempotent requests prevent duplicate intake and duplicate result records after a retry or reconnect.
Troubleshooting
Start with the message shown in the plugin or push-plan review. Safety blocks are designed to be resolved without losing design work.
No approved push plan is ready
Build and approve a plan for the same artboard set and target language, then fetch the language again in Figma.
The plan is out of date
The design, mapping, or translation changed after the plan was built. Rebuild the plan, review the new diff, and approve it again.
A layer is skipped as source changed
The layer was edited in Figma after it was mapped. Review the newer Figma copy, update or re-anchor the mapping if needed, and build a fresh plan.
A layer is skipped because a font is missing
Make the layer font available in Figma and retry. StringsOS skips the row instead of risking a broken style write.
No languages are available
Add a source language and at least one target language to the StringsOS project, then reopen the plugin.
The plugin session expired
Reconnect the plugin with your StringsOS account, authorize access in the browser, and choose the project again.
Continue the localization workflow
Use the Translation Editor to review the keys created or reused from Figma, then return to the mapped artboard set to build the pull plan.
Connect the StringsOS plugin, send a focused set of designs, and complete the first safe round trip.
Free during beta · No credit card required