How Lightning Out 2.0 Compares to Lightning Out (Beta)
Lightning Out 2.0 is generally available. It’s a new feature that completely replaces–and isn’t an extension of–Lightning Out (beta), which is still subject to Beta Service Terms. Learn how the architecture and features currently available in Lightning Out 2.0 compare to those in Lightning Out (beta). The feature comparison list is updated as more Lightning Out 2.0 features are added.
- Lightning Out 2.0
Lightning Out 2.0 uses core Web Components standards and is built on Lightning Web Runtime (LWR). Each embedded Lightning web component (LWC) loads in an iframe and is encapsulated in a closed shadow Document Object Model (DOM). This approach provides stronger security through a Content Security Policy (CSP) directive that allows only your external apps to load the Lightning Out 2.0 app. For more information, see Understand Lightning Out 2.0 Architecture.
- Lightning Out (Beta)
Lightning Out (beta) is a standalone Aura application that dynamically creates Lightning components directly on the external host page.
Lightning Out (beta) is a pilot or beta service that is subject to the Beta Services Terms at Agreements - Salesforce.com or a written Unified Pilot Agreement if executed by Customer, and applicable terms in the Product Terms Directory. Use of this pilot or beta service is at the Customer's sole discretion.
| Feature | Lightning Out (2.0) | Lightning Out (Beta) |
|---|---|---|
| App configuration | Supports both declarative and programmatic configuration. | Supports only programmatic configuration. |
| Embedded component types | Currently supports only custom Lightning web components. | Supports custom Lightning web components and custom Aura components, as well as certain Lightning base components. |
| Lightning security architecture | Lightning Web Security (LWS) is automatically applied to the embedded LWC components. Lightning Locker isn't supported. | Requires Lightning Locker. LWS isn't supported. |
| User access | Currently supports only authenticated users. Unauthenticated user access is on the roadmap. | Supports authenticated users and unauthenticated users. For unauthenticated access, the Salesforce org must enable Digital Experiences. |
| Component styling | Declare LWC styles using a CSS stylesheet in the component folder or in a CSS module. Set SLDS styling hooks and other CSS custom properties values in the Lightning Out 2.0 app. Otherwise, components inherit styles from Salesforce Lightning Design System (SLDS). | Components either inherit styles from Salesforce Lightning Design System (SLDS) or are unstyled. |
| Events | Supported. | Not supported. |
See Also