---
schema_version: "1"
id: 041793eabf233be08ea3a22cdf31a4740ed78cbc3699e6beb1e59fa8ec4b3e44
title: Export Language Content
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/experience/264-0-0/community_builder_multilingual_export.md
canonical_url: https://help.salesforce.com/s/articleView?id=experience.community_builder_multilingual_export.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 0d470b5a04b46afc5f53becdabe1232d83e481642d43300a9232905b6841fc79
description: Export and prepare Experience Builder site content as one or multiple .xml files. Prepare the files for translation by creating nodes for specific languages. Then send the file to your translation service.
products:
  - Experiences
release: "264"
---
# Export Language Content

Export and prepare Experience Builder site content as one or multiple .xml files. Prepare the files for translation by creating nodes for specific languages. Then send the file to your translation service.

### 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: Experience Builder sites accessed through Lightning Experience, Salesforce Classic, and mobile devices, and is available in <strong>Essentials</strong>, <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="d21108e67">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d21108e67 ">To customize or publish an Experience Cloud site:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d21108e67 ">
              <ul>
                <li>Create and Set Up Experiences AND View Setup and Configuration AND be a member
                  of the site<p>OR</p>
                </li>

                <li>View Setup and Configuration AND be a member of the site AND have appropriate
                  <a href="https://help.salesforce.com/s/articleView?id=experience.networks_access_control_overview.htm&amp;language=en_US" target="_blank">role-based site access</a>
                </li>

              </ul>
            </td>

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

Before you begin, let’s look at the structure of the .xml file that’s created when you export language content. The file consists of several elements, and these elements are the key ones to focus on.

- `component` elements represent the page components that make up your site. Many of these components contain text that must be translated.
- The `field` element contains the component’s properties for a particular language. The language is defined by the `language` attribute.
- `property` elements include `CDATA` tags that contain the text strings for translation.
    
    As you can see in this sample XML for a component, several `CDATA` tags don’t contain any content. So the only `CDATA` tags that you and your translators must focus on are the ones that contain text.

```markup
<component context="Contact Support Form (Aura)" documentId="2342fd59-55da-5bdd-b013-d0a3cb6ce523" id="1242fd59-76da-4cdd-b025-d0a3cb6ce496">
    <field name="AuraAttributes" language="en_US" exportcrc="811168867">
        <property name="requestSummaryText"><![CDATA[Case summary]]></property>
        <property name="callToActionText"><![CDATA[]]></property>
        <property name="headerSubtitle"><![CDATA[Tell us how we can help.]]></property>
        <property name="callToActionButtonText"><![CDATA[]]></property>
        <property name="confirmationText"><![CDATA[Your case was created.]]></property>
        <property name="confirmationSubtext"><![CDATA[We'll get back to you soon.]]></property>
        <property name="headerTitle"><![CDATA[Contact Customer Support]]></property>
    </field>
</component>
```

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/images/icon_note.png)

Note If you exported your site content for translation before Winter ’22, you can’t import the resulting translated file. To ensure a successful import, export your site content again and translate it in this more recent .xml file.

To export and prepare content for translation:

1. In Experience Builder, click **![Settings](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/communities/images/community_builder_settings.png)** | **Languages**.
2. Click **Export Content**.
3. Select your default language.
    
    You can select a language other than your default language, but we don’t recommend it unless you must export existing translations for that particular language. If you haven’t yet added translations for the language, the exported file is empty.
4. (Optional) Change the export file name.
    
    The default name of this file is Languages.xml, but you can rename it. Consider exporting a file for each translation and renaming each file by its country code. For example, if you intend to get translations for French, German, and Spanish, you can rename the files language\_fr.xml, language\_de.xml, and language\_es\_mx.xml, respectively.
5. Click **Export**.
6. If you’re prompted to, choose where to save the file.
7. Prepare the .xml file for translation.
    1. Copy the `field` element for the content to be translated, and paste the copy under the original.
        
        ![A field element in a Languages.xml file](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/communities/images/community_builder_multilingual_export_1.png)
        
        You can copy a `field` element multiple times for multiple translations in one file. However, to reduce the chance of overwriting existing translations when importing new ones, we recommend that you export a separate Languages.xml file for each translation.
    2. Update the `language` attribute in the pasted `field` element to the new language.
        
        ![A duplicate field element ready for translation](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/communities/images/community_builder_multilingual_export_2.png)
    3. Save your changes.

After you export and prepare the .xml file, you can send it for translation. Ask your translators to put translated content between the brackets that follow the `CDATA` tags.

![The CDATA element in a field element](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/communities/images/community_builder_multilingual_export_3.png)

If possible, avoid updating the site’s default content until after you receive and import your translated content. Because the translated file contains the original default content and the translated content, when you import the file, you overwrite updates made in the interim.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/images/icon_note.png)

Note Keep this consideration in mind for translations when you make a new property of a custom component available for edit in Experience Builder: If the component is in use on a page in Experience Builder, delete the component from the page and replace it with the updated version. Otherwise, when you export the site content for translation, the property that you added is omitted for that component instance in the exported file. If the component contains content that’s already translated, export the site content first to preserve the existing translation. Then replace the component with the updated version. For more information, see [Aura Component Bundle Design Resources](https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/components_config_for_app_builder_design_files.htm) or, for Lightning web components, [Configure a Component for Experience Builder](https://developer.salesforce.com/docs/component-library/documentation/en/lwc/use_config_for_community_builder).

When you receive the translated .xml file, [import it back into the site.](https://help.salesforce.com/s/articleView?id=experience.community_builder_multilingual_import.htm&release=264.0.0&type=5 "After your translation service has completed the translations, import the translated .xml file into your Experience Builder site.")

#### See Also

- [Import Translated Content](https://help.salesforce.com/s/articleView?id=experience.community_builder_multilingual_import.htm&release=264.0.0&type=5 "After your translation service has completed the translations, import the translated .xml file into your Experience Builder site.")