---
schema_version: "1"
id: ba576cb64505a11201dec555b159b7e047413a0c5ff1cccfe984f73b57eac220
title: Work with Content in the Translation Lifecycle
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/cms_translation_content.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.cms_translation_content.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 695d3c094739c3fdf7a5067600d535c3b70147e801698f68be42b4e19d9747cc
description: When your CMS workspace is set up with multiple languages, you can offer translated content and manage all versions of your content from your CMS workspace. Identify content to be translated, export it for your localization partner, import the translated content, and publish it to the destination.
products:
  - Salesforce CMS
  - Cross Cloud
release: "264"
---
# Work with Content in the Translation Lifecycle

When your CMS workspace is set up with multiple languages, you can offer translated content and manage all versions of your content from your CMS workspace. Identify content to be translated, export it for your localization partner, import the translated content, and publish it to the destination.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

<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="d11485e66">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d11485e66 ">To export and import content in a CMS workspace:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d11485e66 ">A CMS workspace contributor role of content admin or content manager</td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d11485e66 ">To export and import content with taxonomy tags in an enhanced CMS
              workspace:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d11485e66 ">
              <p>A CMS workspace contributor role of content admin or content
                manager</p>
              <p>AND</p>
              <p style="margin-bottom:0;">View Content Taxonomy</p>
            </td>

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

Your Salesforce org has a limit of 500 content items per license. Versions and translations of content items are counted as one content record. For example, a content item with two versions and three translations is counted as one record against your license.

1. In Lightning Experience, from the App Launcher, open the Digital Experiences app (previously named Salesforce CMS).
2. Identify content to export for translation.
    1. In the CMS workspace, open the content.
    2. On the content details page, click **Ready for Translation**.
        
        The content is locked from changes.
3. To edit content marked as Ready for Translation, click **Edit as Draft**.
    
    A copy of the content is created in Draft status, and the old version is archived. Content is initially created or posted to a CMS workspace in Draft status. You can change the content when it’s in Draft status.
4. Export content for translation from the CMS workspace.
    
    1. In the CMS workspace, click **Export for Translation**.
        
        All content with a status of Ready for Translation is selected for export and the export process begins. The content is exported into a separate .xlf file for each CMS workspace language. Depending on the amount of content you’re exporting, it can take time for the process to finish. You receive a notification email with a link to download a .zip archive of the .xlf files.
    2. Send the downloaded files to your localization service.
        
        When you get the files back, you’re ready to import.
    
    ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-communities_managed_content-264-0-0-production-enus/8b149fc1-875c-4018-8e9e-2843a2196457/images/icon_important.png)
    
    Important Keep the original content in Ready for Translation status until you import your translation files. You can import translated versions of your content when the original content is in Ready for Translation status only.
5. Import translated content into the CMS workspace.
    1. Take the .xlf file from your localization service and create a .zip archive. Keep the .zip archive locally available.
    2. In the CMS workspace, click **Import Translated Content**.
    3. Use the file selector to navigate to the .zip archive and select your file.
        
        A confirmation message notifies you when the import is in process. Then you get a confirmation email when the import is complete and the content is added to your workspace.
6. View and manage your translated content.
    1. In the CMS workspace, open your content.
    2. On the content details page, click the Translations tab. From here, view the available translations of the content for each language.
    3. After you’ve reviewed the translated versions of your content and everything is ready, click **Publish**.
    4. If you have an update for a published content item, click **Edit as Draft** to create a draft. To remove the content from your destinations, click **Unpublish**.
        
        In both cases, the original content version and all translations are archived.