Figma Translating Plugin: App Store Screenshots, CPP, PPO
In Development Coming Soon
How to work with the Figma Plugin
After installing the plugin, enter the activation code that will be sent to your email.
Then open the page with screenshots and launch the localization plugin.
In Development Coming Soon
Automate screenshot translation to 39 languages.
Get free access code to the plugin.
Selecting Components for Translation
The plugin automatically detects all visible components on the current screen.
You can manually enable or disable any elements you want to use for generation.
Since the plugin creates translations by copying the entire structure of the original frame and placing translated versions below the original, it is recommended to organize the working file in advance:
- place screenshots in one row, or
- group them by language frames so that the structure repeats during generation.
When working with frames, the plugin creates each new language frame directly below the original.
If you work with individual components, translated versions will appear in columns - which may complicate finding related elements.
If vertical space runs out in Figma, the plugin will automatically continue placing new groups slightly to the right and down again, maintaining the correct order of elements.
Top Control Panel
The top panel of the plugin contains system settings and service tools that control the plugin’s behavior and interface.
Interface Language
Changes the plugin’s interface language.
Does not affect translation generation languages - that is a separate Languages tab.
Theme
Allows switching the plugin’s appearance between light and dark themes.
The theme choice is saved and applied to all plugin screens.
Debug Information on Failures
Service button.
Creates a file with technical data useful for the ASO.dev team:
- current frame structure,
- list of keys,
- error descriptions.
Use this button if something is not working correctly - so that ASO.dev can quickly understand the cause and help.
Brief Description
Opens a help block with answers to the most frequent questions about the plugin’s operation.
Suitable for quick familiarization and transition to documentation.
Components Tab
The Components tab displays the search for all frames, sections, and text elements on the page.
Here you select which components will participate in generating translated versions.
The plugin analyzes the frame structure and automatically determines:
- which elements contain text,
- which are groups/sections.
The header displays the total number of found components and the number already selected.
The 🔽 button to expand all components opens all nested elements in the component tree.
The ▶️ button to collapse all components closes all nested elements in the tree.
The key button 🔑 changes the visibility of system component names. The refresh button 🔄 rescans the page and updates the component list.
The ✓ Select All button allows quickly marking all components for generation.
The X Clear button disables all components.
The search bar allows quickly finding the necessary elements by name in the component tree.
Component Tree
The plugin displays the hierarchy of all found components on the Figma page.
They are located and named the same as in Figma’s Layers.
Each component has a checkbox to select its participation in translation generation.
- If the component is selected, its elements will be included in the export, and if there is text - it will go into the json for translation.
- If the component is not selected, it will not be generated and will be skipped.
Languages Tab
In the Languages tab, you select which languages to generate translated screen versions for.
The plugin supports all 39 App Store localizations.
Each selected language will be created as a separate version (frame or component), fully preserving the structure of the original layout.
Language Filters
At the top are quick filters for selecting languages by categories:
- App Store – shows only App Store localizations.
- EU, Asia, Americas, Middle East – regional filters.
The search bar allows quickly finding the desired language by name or code (e.g., FR, pt-BR, zh-Hans).
Language Selection
Next to each language there is a checkbox for selection.
You can:
- select languages one by one,
- use the All button to select all localizations,
- use Clear Selection to reset the selection.
Labels:
- APP STORE - official App Store localization
- RTL - language with right-to-left writing direction
The counter at the bottom shows the current number of selected localizations (e.g., Selected: 39 out of 39).
The primary language (English US) is always included in the export.
Import/Export Tab
The Import/Export tab allows exporting text elements for translation, and then loading ready translations back into Figma.
This is convenient if you work with external translators, use ASO.dev for translations, or want to manually edit localizations.
Export Texts for Translation
At the top, a summary is displayed:
- Number of text blocks found for export
- Number of selected languages for translations
- Export format (currently only JSON format is supported)
Settings:
- Name of the created file or archive for further translation
- File export format (currently only JSON format is supported)
- Primary language used as the source of text for export.
Default: English (US). - Translations will be exported in one file or archive
When enabled, a ZIP archive is created with a separate file for each language. (E.g.:de.json,fr.json,ja.json).
Translation Instructions for AI
Hints and restrictions that will be applied if you later use this file in machine translation in aso.dev via AI (e.g., ChatGPT, DeepSeek, Claude).
String length limit (e.g., “no longer than 10 characters”).
Automatically add context of other texts from the page for large models.
The Export button creates a file with texts for translation and saves it to your computer. This file can be passed to translators, used in automated pipelines, translated using AI in ASO.dev.
Import Ready Translations
After the translations are ready, you can upload the file back into the plugin.
In the import area you can:
- drag the file with the mouse,
- or click to select manually.
Supported formats:
- .json
- .zip (multiple localization files)
File structure determination happens automatically based on content.
After uploading, the plugin will check if the file structure matches the current components and keys, which helps avoid errors in case of mismatch.
Overwrite existing translations: If enabled - existing translated values will be replaced with new ones. If disabled - only empty lines will be updated.
Import: All translations are read from the file into the plugin’s memory for further generation.
Clear all translations: Deletes all uploaded translations from the plugin’s memory.
Does not touch screenshots.
Generation
In the Generation tab, you launch the creation of localized components or updating already created versions.
Here you see the final information about the number of selected languages, text elements, and the expected number of created components.
At the top, a summary of the upcoming generation is displayed:
- number of selected source components
- number of selected languages
- number of text layers that will be localized
- total number of new elements that will be created
Also displayed here:
- list of languages,
- list of selected components,
- RTL language labels,
- additional component tags.
The system warns in advance if the number of generated elements is very large. For example: 20,000 components will be created. This may take time.
This helps assess the load and waiting time.
Starting Generation
The tab has two generation modes available.
Creating new components and Updating existing components.
When creating, localized versions will be created next to the originals, without changing the source components.
Characteristics:
- only new components are created,
- structure is fully copied,
- originals remain unchanged,
Suitable for first generation or with significant design changes.
When updating existing components, the plugin searches for already created localized versions and replaces texts in them with new translations.
Used when:
- you updated strings in the export,
- new text was added,
- you want to update previously generated frames without recreating all copies.
The plugin calculates the approximate execution time.
This indicator depends on:
- number of components,
- number of languages,
- complexity of frame structures,
- Figma performance.
The plugin always protects source frames - changes are made only to localized copies.
Image Export
In the Image Export tab, you can export localized components as images.
Export Settings
Format: PNG or JPG Scaling: 1x / 2x / 3x
Export sliced images (slices) if available.
Group by languages: creates folders for each language. Without grouping: saves all images in one folder
The plugin shows all available frames and localized groups. You can:
- expand/collapse groups,
- select languages for export,
- Select All / Clear Selection,
If something changed in Figma - click Update.
For each frame, the sizes and number of sliced images (slices) are displayed.
Export
- Click Export to save the selected images. The plugin will collect them into a ZIP archive with the correct structure (by languages or without grouping).
Upload your set of localized screenshots to App Store Connect using ASO.dev.