---
schema_version: "1"
id: 0081a390b8011554d038b8baf49ebcdf6da271c41551dea2ac877ce9404984ac
title: ExperienceBundleSettings
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_experiencebundlesettings.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_experiencebundlesettings.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: af5ec4c5f009d4e455696fb2fbe8fb37cff569232e702085a93346351b8e8fca
description: Represents the org setting that enables the ExperienceBundle metadata type for Aura sites in Experience Cloud. The setting doesn’t affect LWR sites, which use ExperienceBundle by default. This type extends the Metadata metadata type and inherits its fullName field.
---
# ExperienceBundleSettings

Represents the org setting that enables the ExperienceBundle metadata type for Aura sites in Experience Cloud. The setting doesn’t affect LWR sites, which use ExperienceBundle by default. This type extends the Metadata metadata type and inherits its fullName field.

![Note](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/images/icon_note.png)

#### Note

ExperienceBundle is a text-based code structure of the settings and site components, such as pages, branding sets, and themes, that make up an Experience Builder site. Developers can quickly update and deploy one or more Experience Builder sites programmatically using their preferred development tools.

## File Suffix and Directory Location

ExperienceBundleSettings values are stored in a single file named ExperienceBundle.settings in the settings directory. The .settings files are different from other named components because there’s only one settings file for each settings component.

## Version

ExperienceBundleSettings is available in API version 46.0 and later.

## Fields

| Field Name | Field Type | Description |
| --- | --- | --- |
| enableExperienceBundleMetadata | boolean | Indicates whether the ExperienceBundle metadata type is enabled for Aura sites. Default is false. LWR sites use ExperienceBundle by default. |

## Declarative Metadata Sample Definition

Here’s an example of ExperienceBundle.settings that references the previous definition.

<ExperienceBundleSettings xmlns="http://soap.sforce.com/2006/04/metadata">
        <enableExperienceBundleMetadata\>true</enableExperienceBundleMetadata\>
</ExperienceBundleSettings\>

## Wildcard Support in the Manifest File

The wildcard character \* (asterisk) in the package.xml manifest file doesn’t apply to metadata types for feature settings. The wildcard applies only when retrieving all settings, not for an individual setting. For details, see [Settings](https://developer.salesforce.com/docs/atlas.en-us.264.0.api_meta.meta/api_meta/meta_settings.htm). For information about using the manifest file, see [Deploying and Retrieving Metadata with the Zip File](https://developer.salesforce.com/docs/atlas.en-us.264.0.api_meta.meta/api_meta/file_based_zip_file.htm).

#### See Also

- [ExperienceBundle](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_experiencebundle.htm "Represents a text-based code structure of the settings and site components, such as pages, branding sets, and themes that make up an Experience Builder site. Developers can quickly update and deploy Experience Builder sites programmatically using their preferred development tools. This type extends the Metadata metadata type and inherits its fullName field.")