---
schema_version: "1"
id: 8b693a5ed94977d19209127013317fa3dc102cbec92e9e7526a36d0c96f6c7e8
title: Create Email Language Variants in Marketing Cloud Next
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mktg_content_email_translate.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mktg_content_email_translate.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f0a18927543da60f6c0b44e97545f032d9fa119225d903723db9b379b9186a36
description: Translate content in Email Builder or XLIFF files without re-creating layouts for every language. All translated variants automatically inherit layout, style, and data source updates from the default variant to streamline your localization workflow.
products:
  - Marketing
release: "264"
---
# Create Email Language Variants in Marketing Cloud Next

Translate content in Email Builder or XLIFF files without re-creating layouts for every language. All translated variants automatically inherit layout, style, and data source updates from the default variant to streamline your localization workflow.

### Required Editions

[View supported editions](https://help.salesforce.com/s/articleView?id=mktg.mktg_editions.htm&release=264.0.0&type=5 "Marketing Cloud Next is available in Growth and Advanced editions, and requires Salesforce Enterprise or Unlimited editions. Some features are limited by edition or purchased add-on. All functionality is available in Lightning Experience only.").

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d35431e47">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d35431e47 ">To add languages or edit language variants:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d35431e47 ">
              <p>Marketing Cloud Manager permission set </p>
              <p>AND</p>
              <p style="margin-bottom:0;">Any CMS workspace
                contributor role</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d35431e47 ">To export or import translation files:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d35431e47 ">
              <p>Manage Translation </p>
              <p>AND</p>
              <p style="margin-bottom:0;">Create Documents</p>
            </td>

          </tr>
        </tbody>
      </table>

Before you begin, create the email in the default language. See [Create an Email in Marketing Cloud Next](https://help.salesforce.com/s/articleView?id=mktg.mktg_content_email_create.htm&release=264.0.0&type=5 "The content editing experience in Marketing Cloud Next provides tools to build an email, preview and test it, and publish it for use with a campaign. To make major changes to a published email or to prevent it from sending in a campaign, you can unpublish it.").

All translated variants inherit layout, style, and data source updates from the default variant.

## Add Languages to a Marketing Workspace

Add each language that you need to the marketing workspace before you translate an email. The default language stays selected and locked.

1. From the Content tab, open the marketing workspace that contains the email.
2. Click **Manage**, and select **Languages**.
3. Move each target language to **Selected Additional Language**.
4. Save your changes.

## Translate an Email in Email Builder

Generate or edit the translated copy directly in Email Builder, without rebuilding the layout for each language. Use in-app translation to quickly update individual language variants.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mktg_all-264-0-0-production-enus/e92be4e1-4bef-47a5-a11d-95f4ea1f7d7a/images/icon_note.png)

Note

Upgrading to Winter ’27 doesn’t automatically add the **Translate Text Content** action to Content Builder agents created in Summer ’26 or earlier. To use agentic translation, create a new agent or manually edit your existing agent in Agentforce Builder, and then add the **Translate Text Content** action under the Content Creation topic.

1. From the Content tab, open the marketing workspace, then open the email in Email Builder.
2. Click the **Language Variants** icon, and select the target language.
    
    The list includes the default language, such as Default - English (US), and each additional workspace language.
    
    ![Translate Variants for Email](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mktg_all-264-0-0-production-enus/e92be4e1-4bef-47a5-a11d-95f4ea1f7d7a/mktg_all/images/mktg_translate_variants.png)
3. **Optional:** To generate a translation with AI, open the Agentforce panel and ask the agent to translate the language variant.
4. Click **Translate Variant**.
    
    The canvas shows the email and starts translating the copy, including image alt text.
5. Review and edit the copy in the default components view, or switch to **Code View** or **Text View**.
6. Save your work. Repeat these steps for each language.

Preview each language variant, and then publish the email.

## Translate an Email with XLIFF Files

Export the email as an XLIFF file, translate the source text, and import the .zip archive. Use this method for external or high-volume localization.

1. From the Content tab, open the marketing workspace, select the email, then click **Manage**, and under **Translations**, click **Export**.
2. Move each target language to **Languages to Export**, and click **Export**.
3. On **Job Statuses**, open the completed job and download the files.
4. Translate the source text. Keep the file structure and identifiers unchanged, and save the files in a .zip archive.
5. Click **Manage**, and under **Translations**, click **Import**, and then upload the source .zip file.
    
    Import overwrites any existing translations.
6. Open the email and review each imported language variant.
    
    To fix a variant after import, edit it in Email Builder.

If you create a new draft of a published email, Salesforce archives the previous version and its translations. Translate the new draft again. See [Work with Content in the Translation Lifecycle](https://help.salesforce.com/s/articleView?id=xcloud.cms_translation_content.htm&language=en_US).