Template Limitations

The Build Your Own (LWR) template doesn’t include the same features as Aura sites. Check out the current limitations before you begin creating your site.

Unsupported Features and Settings

The following items are unavailable.

Most of the default components and pages that you get with Aura templates, including record components
Most preconfigured standard pages, such as Knowledge, Account Management, and Contact Support, used when creating custom pages
The default Navigation Menu component, although you can build your own
Audiences and page variations
Progressive rendering
Out-of-the-box themes and theme management
Right-to-left languages in standard components
Template, page, and theme export and Lightning Bolt Solutions
Template-level accessibility features, such as a skip link
App-level events that you get with Aura templates, although you can use CustomEvent
Some base components and features from the Lightning Component Library
Mobile and value providers such as $Browser
The pageAccess property in the ExperienceBundle metadata type.
Salesforce Community Page Optimizer
Trialforce template compatibility in Developer Edition orgs
Surveys
Contributor roles in unauthenticated sites

Experience Workspaces Limitations

Only the Administration, Builder, Dashboards, and Guided Setup workspaces are available.

Experience Builder Limitations

In the toolbar, the Undo and Redo buttons and some Help options are unavailable.
In the Theme panel, branding sets and the CSS editor are unavailable. You also can’t change themes or theme settings. For alternative solutions, see Brand Your LWR Site.
When in the Mobile view mode, the Mobile workspace editor is unavailable.
When working with components, some hover actions and some of the action menu options in the property editor are unavailable.
When you modify records while previewing your site in Experience Builder, you can sometimes see stale record data if you navigate to a previous page. To fix this issue, refresh your browser.
Experience admins can't access record pages in Experience Builder for objects that they don't have access to.

Lightning Locker Limitations

LWR sites use an upgraded version of the Lightning Locker library, which currently includes some limitations.

Scripts loaded through lightning/platformResourceLoader run in system mode outside of a Lightning Locker sandbox. As a result, the component loading the script doesn’t have access to the same global variable scope as the script itself, preventing it from accessing any global variable set by the script.
Get around this restriction by implementing your own loadScript function. See an example within codeSamples/resourceLoader in the code sample files.
Tip
The await and async expressions aren’t supported. Instead, use promises.
The following properties are currently unsupported:
- document.domain
- document.location
- shadowRoot.host
- this.template.host
- window.location
- window.top

Asset Files in Sandbox Limitations

Full and Partial Copy sandboxes can support asset files along with other content entities. Asset files are unsupported in Developer and Developer Pro sandboxes. When defining the sandbox template for Full and Partial Copy sandboxes, make sure to select Content Body in the template also.

For unsupported sandboxes, if your site contains a Lightning web component with a @salesforce/contentAsset reference, the reference breaks in the site on the sandbox org. In LWR sites, the component can’t render, and you can’t publish the site unless you delete the component from the page or else remove the asset reference from the component. In Aura sites, the imported reference resolves to an invalid URL.

Privacy Compliance

Don’t include sensitive information or personal identifiable information (PPI) in user agent headers.

LWR Sites for Experience Cloud