Multi-language checklist for Figma files

Source and scope

• Confirm the source language and locked terminology (product name, feature names).
• Decide which pages/frames are in scope for v1; defer edge cases to a follow-up pass.
• Note any legal or compliance copy that must not be paraphrased by AI.

File hygiene

• Text in real text layers, not outline shapes (unless intentionally).
• Auto-layout on key components so longer strings reflow where possible.
• Check button max width and one-line rules for tiny breakpoints.

Locales that need extra care

• RTL: mirror layout expectations for Arabic, Hebrew, etc.
• CJK: line height and emphasis differ from Latin-only designs.
• Formal vs informal "you" in European languages (set instructions in the plugin).

After translation in Figma

• Spot-check truncated CTAs and navigation.
• Export a PDF or prototype link for regional stakeholders if needed.
• Align with engineering on string keys or copy deck handoff. See also i18n workflow.