Glosslark docs
1. Strings and keys
Open Glosslark and pick a scope: the selection, the page or the whole file. The Strings tab lists every text layer's string with its key, the frame path it sits in and the width it has to fit. Hidden layers and layers that only hold numbers or prices are skipped (both can be turned back on). Language copies the plugin made are always skipped, so strings come from the originals.
Each string gets a key, chosen once and saved on the layer:
| Source | Example |
|---|---|
| A key you set in the panel | checkout.place_order |
A layer named like a key, or with @key in its name | layer login.title or Title @login.title |
| Generated: top frame plus layer name | frame "Checkout", layer "Primary button" gives checkout.primary_button |
| Generated: top frame plus the first words of the text (when the layer still has Figma's default name, or with "Frame + text") | checkout.place_order |
Layers with the same key and the same text share one string. A different text under the same generated key gets _2. Keys are saved on the layers at the first export (or with Save keys on layers), so renaming a frame later doesn't break the next import. Text inside component instances is included; if Figma won't store the key on a layer inside an instance, it is kept on the page instead.
2. Tags: notes, limits, plurals, do not translate
Select one text layer to tag it:
- Key: letters, digits,
_,.and-. - Note for translators: goes into the file next to the string.
- Max characters: written as a limit (XLIFF
maxwidthin characters) and checked on import. - Do not translate: the string is locked (
translate="no"in XLIFF,shouldTranslate: falsein String Catalogs,translatable="false"on Android) and left out of translated files. - Plural or variable text (ICU): the message translators get, such as
{count, plural, one {# item} other {# items}}orHi {name}, and the sample values the canvas shows (count=3). Each language copy shows the translated message with the same values, using that language's plural rules.
3. Export
Pick a format, the design's language and the languages to translate into (codes like fr, de, pt-BR, zh-Hant). Every string carries a note with where it sits (page / frame / group), the width it has to fit, line and character limits, your note, glossary terms and the screenshot name.
| Format | Files | Plurals and arguments |
|---|---|---|
| XLIFF 1.2 | Name.fr.xlf per language | ICU text; width limits as maxwidth with size-unit; source hash in extradata |
| XLIFF 2.0 | Name.fr.xliff per language | ICU text; limits and hash in the metadata module |
| Apple String Catalog | Localizable.xcstrings, every language in one file | Plural variations; %@ and %lld |
| Apple .strings | fr.lproj/Localizable.strings | Only the "other" form fits; use the String Catalog for plurals |
| Android | values-fr/strings.xml (values-pt-rBR, values-b+zh+Hant) | <plurals>; %s, %d, positional %1$s |
| i18next JSON | locales/fr/translation.json | key_one, key_other; {{name}}; the plural variable is count |
| ICU JSON | fr.json (FormatJS, react-intl, Lingui, next-intl) | ICU messages |
| Flutter ARB | app_fr.arb | ICU messages, descriptions and placeholders |
| CSV | Name.csv, a column per language | ICU text; UTF-8 with a byte order mark so Excel shows accents |
Options: Only new or changed since the last export (per language, remembered in the file), Screenshots of each frame (the export becomes a ZIP with a screenshots/ folder), Include translations already in this file (from earlier imports, when the source text hasn't changed) and Copy the source into empty translations (some tools want a target in every unit). Translated Android, Apple, i18next and ARB files only list translated strings, so apps fall back to the design language for the rest.
Glosslark has no machine translation. Send the files to your translators, agency or translation platform (Lokalise, Crowdin, Phrase, Smartling and every CAT tool read XLIFF).
4. Import
Choose one or more translated files on the Import tab. Glosslark tells the format from the file and the language from the file (or its name: fr.lproj, values-de, app_es.arb, home.ja.xlf); when it can't, type the code. Before anything changes you see, per language: how many strings match this design, which aren't translated, which were translated from older source text (the design changed after export), and problems: lost or extra ICU arguments, missing plural forms, broken ICU syntax, translations over their character limit, dropped do-not-translate words and glossary terms not used. Keys from the file that aren't in this design are skipped.
Then choose where the translations go:
| Option | What happens |
|---|---|
| Page per language | A copy of each frame on a page named after the language, at the same position as the original. |
| Next to the original | A copy of each frame to the right of the original, on the same page. |
| Variable modes | A string variable per key (in a collection, "Translations" by default) with a mode per language. The original text layers are bound to them, and a copy per language on its own page shows that mode. Switch the mode on any frame to change language. Figma limits modes per collection by plan (Professional 10, Organization 20), so for more languages use pages. |
| In place | The original text changes. One undo puts it back. |
Importing the same language again updates its copies instead of making new ones (tick "Replace existing copies" to rebuild them from the original). Each import is one undo step.
Right-to-left languages (Arabic, Hebrew, Persian, Urdu and others): Figma sets the direction of the text itself from the language, but text layers stay left aligned and auto layout has no direction setting (plugins can't set text direction either), so copies are mirrored: horizontal auto layout rows are reversed with start and end alignment and padding swapped, layers placed by hand move to the mirrored position with their left and right constraints swapped, and left and right text alignment swap. Icons and pictures move but aren't flipped; check arrows and chevrons.
Font per script: lines like Arabic: Noto Sans Arabic switch translated layers that need those letters to that font (in the same style when it has one), unless their font is known to have them.
5. Overflow and missing letters
After every import (and on its own, free, on the Test layouts tab) Glosslark checks each changed text layer:
- A text box with a fixed size, a line limit or truncation that its text no longer fits (measured on a temporary copy that may grow, so your layer isn't touched).
- Text that runs past the edge of a container that clips its content, an auto layout frame with a fixed width or height, or the frame itself.
- Letters the layer's font doesn't have, for well-known UI families (Inter, Roboto, SF Pro, Helvetica, Open Sans, Montserrat, Poppins, Lato, Noto and others). Figma draws those letters in a fallback font, so the design won't match the build.
Each problem has a Select button; Select all picks every layer with a problem, and Report downloads a CSV.
6. Pseudo-localization
Test layouts before translation: Glosslark makes pseudo-localized copies (a "Pseudo (en-XA)" page by default) with accented letters, text 30 to 40% longer (35% by default, or IBM's guideline by length, which doubles short labels) and brackets around each string, so a missing bracket shows text was cut off. Right to left makes an "ar-XB" copy that reads mirrored and is laid out right to left. Arguments and ICU syntax are kept. The overflow check runs on the copies.
7. Glossary and do not translate
Under Glossary on the Strings tab: a do-not-translate list (one term per line, such as product names) and a glossary (Cart = fr: Panier; de: Warenkorb). Both are saved in the Figma file. A string that is exactly a do-not-translate term is locked; terms inside strings go into the translator note, and imports warn when a translation drops them or doesn't use the agreed term.
8. Trial and plans
7-day trial with 10 runs, starting with your first export or import. Each export (any format and number of languages), each import applied to the canvas and each set of pseudo-localized copies is one run, up to 300 strings on the trial. Finding strings, keys and tags, the glossary, reading a file to preview it, and the overflow check are always free. Then $29 a month or $299 a year per designer who exports and imports. Translators don't need a seat.
Questions: hello@greatwork.company. A person replies within one business day.