Documentation Index

For the complete documentation index, see llms.txt. Markdown versions of docs pages are available through the page's alternate Markdown link.

Current page: Translating your email designs with Locize - Use Emailify with the Locize API to upload source text from Figma and import translated email variants from a Locize namespace.. Machine-readable page: /emailify/localization/locize.md.

Translating your email designs with Locize

Use Emailify with the Locize API to upload source text from Figma and import translated email variants from a Locize namespace.

Use the Locize API with Emailify ​

If you use Locize, Emailify can upload the source copy from your email designs to a Locize namespace and import translated variants back into Figma.

Before you start ​

You will need:

  • A Locize project with a reference language and at least one target language.
  • An existing version and namespace for your email translations.
  • A project-scoped Locize API key.

Step 1: Connect your Locize project ​

  1. Click the Localize button in Emailify.
  2. Choose Locize API from the localization options.
  3. Enter your Project ID and API Key.
  4. Enter the Locize Version you want to use, such as latest or production.
  5. Enter the Namespace that contains your email translations, such as emails.
  6. Choose the Standard CDN or Pro CDN option that matches your Locize project.
  7. Choose how Emailify should create Locize string keys under String Key Source.

After Emailify connects, it displays the reference language and target languages configured in your Locize project.

Make sure the CDN type matches your Locize project. The Standard CDN is public and uses a fixed one-hour cache, while the Pro CDN supports private publishing and configurable caching. See Locize's CDN comparison for more detail.

Choose how Locize string keys are created ​

Figma Node ID (Default) keeps the existing Emailify behavior and uses generated Figma node IDs for Locize keys. Existing Locize workflows continue using this option unless you change it.

Choose Figma Text Layer Name when your Figma text layer names already match the string keys in your Locize namespace. Emailify preserves the complete layer name, including dots, so a layer named templates.assistant_invited.h01 uses that exact Locize key.

Every included text layer name must be present and unique across the selected emails. Emailify stops the upload or import and identifies duplicate keys before any source strings are sent to Locize. Link and image alt-text keys use the text or image layer name with Emailify's _LINK or _ALT_TEXT suffix. Subject and preheader rows continue using their generated Emailify keys because they are email metadata rather than Figma text layers.

Step 2: Select your emails and target locales ​

Choose the Emailify frames you want to localize, then select the Locize target languages you want to import later.

Keep Import Markdown Formatting enabled if your email copy contains bold, italic, linked text, or line breaks that you want to preserve during the translation round trip.

Step 3: Upload the reference copy to Locize ​

Click Upload to send the selected Emailify text to your namespace using the reference language configured in Locize. If you update the source copy in Figma later, upload it again to update the corresponding Locize keys.

Step 4: Translate in Locize ​

Open your Locize project and translate or review the uploaded keys for each target language.

Step 5: Import translated emails into Figma ​

Return to Emailify, select the target locales you want, and click Import Translations. Emailify matches the translated Locize keys to the selected source emails and creates cloned email frames for each imported locale.

Emailify stores your Locize API key in Figma's local client storage for your current user instead of saving it in the shared Figma file. Use a project-scoped API key rather than a broader personal access token.