Figma screenshots
The Figma plugin creates reviewable screenshot-copy proposals from selected Figma frames. A human reviews current text, agent suggestions, keyword usage, warnings, and diffs in LocalizeASO before the plugin applies approved copy back into Figma. App Store Connect upload is a separate human-run handoff through LocalizeASO hosted submit convenience or local asc.
Before you start
Prepare Figma frames for App Store screenshots:
- Select frames that belong to the same screenshot size.
- Keep the marketing title and optional subtitle as real text layers.
- Keep frames organized by source screenshot.
- Connect App Store Connect only if you want live locale import or hosted submit convenience. BYO Agent review jobs can use a known app id without storing ASC credentials in LocalizeASO.
You do not have to rename every relevant layer manually. A connected coding agent can classify all visible text, while the plugin applies only the validated title/subtitle i18n: names locally. Product UI, legal copy, prices, badges, and decorative text stay in the visual.
The plugin checks the selected frames, coding-agent capabilities, text candidates, and frame-size mismatches before creating a job.
Guides (linked from the plugin):
- Figma plugin step-by-step — install, app context, review proposal, approval, apply (live UI previews)
- Prepare screenshot text for every language — text boxes, grouping, line breaks, multi-device layout
Setup screen
In the plugin setup flow, configure:
- Source language.
- Target languages.
- Glossary terms.
- Custom instructions.
- App Store Connect locales, manual locales, or BYO-agent locale context.
- ASO keyword context from the dashboard.
You can import target locales from App Store Connect when connected, or select/provide locales manually for BYO workflows.
Coding-agent layer preparation
The plugin enables automatic text-layer preparation only while the current app and Figma file have a fresh coding-agent capability lease. The agent inspects the full frame preview and classifies every visible text layer. Only the primary marketing title and optional subtitle become editable localization overlays.
For each title/subtitle overlay, the agent also inspects the source bounds, frame dimensions, alignment, rotation, parent layout, and surrounding composition. It proposes a bounded width/height expansion only when real empty space is available, helping longer locales remain readable without excessive font shrinking. Auto-layout, rotated, crowded, or uncertain layers stay unchanged.
The agent submits a structured plan; the open plugin validates frame boundaries and performs both the Figma rename and safe text-box adjustment locally. Product UI, prices, legal copy, badges, and decorative layers are never resized. This keeps document mutation local, compatible with Figma undo/history, and makes stale, incomplete, or out-of-frame plans fail safely.
Optional BYO visual polish
Visual polish is opt-in and never uses a LocalizeASO-hosted image model. It is enabled only when the connected coding agent declares all three current capabilities: layer classification, reference-image editing, and binary artifact output.
For each source frame, the plugin exports one text-free source after applying the title/subtitle plan. The client coding agent downloads it, edits the supplied image with its own image tool, inspects the result, and uploads one locale-neutral candidate with a hash-bound structured audit. That base is reused for every locale; localized title/subtitle layers remain editable in Figma.
If the current coding agent cannot edit images, the visual option stays disabled. There is no automatic paid or hosted fallback.
The agent must preserve product truth, core composition, authentic product UI, brand direction, and empty title/subtitle zones. Invented features, claims, text, prices, people, logos, competitor marks, or lookalike branding fail the workflow. Possible rights or trademark issues remain visible for human review.
LocalizeASO also measures the uploaded image bytes. A candidate must keep the source aspect ratio within 2% and have at least a 1024-pixel long edge, preventing an image-model output from being silently cropped or heavily upscaled when the plugin places it back into the source-sized Figma frame.
Proposal generation
The plugin sends selected text keys, source locale, target locales, glossary, custom instructions, and ASO keyword context to the backend or agent workflow. It creates a structured screenshot review job and proposal instead of treating generated copy as final.
The reviewer can accept, reject, edit, or request another agent pass before anything is applied. Long translations should be checked against the Figma preview and warning signals during review.
Approved apply
After approval, the plugin fetches the approved apply plan for a concrete screenshot review job. It checks the selected app and current Figma file before changing layer text.
The apply preview shows the approved locale/frame/layer changes, assigned and unassigned keywords, warnings, and skipped targets. The plugin changes Figma text only after explicit human confirmation.
App Store Connect handoff
After approved copy has been applied in Figma, upload/submission remains human-only:
- Agent Pass users can keep ASC credentials local and upload through
asc, Transporter, or another local workflow. - Hosted passes can use LocalizeASO submit convenience after human approval when ASC credentials are connected; hosted screenshot upload/reorder is tied to the applied review job and approved apply-plan fingerprint.
- Mark review jobs as submitted only after the human-run upload has completed.
Agents can generate proposals and keyword context, but they must not apply Figma changes, mark status, or submit screenshots.