Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Use Lightning Components in Visualforce Pages

Add Aura components to your Visualforce pages to combine features that use both solutions. Implement new functionality using Aura components and then use it with existing Visualforce pages.

Lightning Components for Visualforce is based on Lightning Out (Beta), a powerful and flexible feature you can use to embed Aura and Lightning web components into almost any web page. When used with Visualforce, some of the details become simpler. For example, you don’t need to deal with authentication, and you don’t need to configure a Connected App.

In other ways, using Lightning Components for Visualforce is identical to using Lightning Out. See Use Components Outside Salesforce with Lightning Out (Beta) in the Lightning Web Components Developer Guide.

Important

There are three steps to add Aura components to a Visualforce page.

Add the Lightning Components for Visualforce JavaScript library to your Visualforce page using the <apex:includeLightning/> component.
Create and reference a Lightning Out app that declares your component dependencies.
Write a JavaScript function that creates the component on the page using $Lightning.createComponent().

Add the Lightning Components for Visualforce JavaScript Library

Add <apex:includeLightning/> at the beginning of your page. This component loads the JavaScript file used by Lightning Components for Visualforce.

The Lightning Components for Visualforce JavaScript library loads from the org that the Visualforce page is in, so your Lightning Out app must exist in the same org as the Visualforce page.

Important

Create and Reference a Lightning Out App

To use Lightning Components for Visualforce, define component dependencies by referencing a Lightning Out app. This app is globally accessible and extends ltng:outApp. The app declares dependencies on any Lightning component that it uses.

Here’s an example of a Lightning Out app named lcvfTest.app. The app uses the <aura:dependency> tag to indicate that it uses the standard Lightning component lightning:button.

1<aura:application access="GLOBAL" extends="ltng:outApp"> 
2    <aura:dependency resource="lightning:button"/>
3</aura:application>

Extending from ltng:outApp adds SLDS resources to the page so that your Lightning components can be styled with the Salesforce Lightning Design System (SLDS). If you don’t want SLDS resources added to the page, extend from ltng:outAppUnstyled instead.

Note

To reference this app on your page, use this JavaScript code, where theNamespace is the namespace prefix for the app. That is, either your org’s namespace or the namespace of the managed package that provides the app.

1$Lightning.use("theNamespace:lcvfTest", function() {});

If the app is defined in your org (that is, not in a managed package), you can use the default “c” namespace instead, as shown in the next example. If your org doesn’t have a namespace defined, you must use the default namespace.

For details about creating a Lightning Out app, see Lightning Out Dependencies in the Lightning Web Components Developer Guide.

Creating a Component on a Page

Finally, add your top-level component to a page using $Lightning.createComponent(String type, Object attributes, String domLocator, function callback). This function is similar to $A.createComponent(), but it includes an additional parameter, domLocator, that specifies the DOM element where you want the component inserted.

Let’s look at a sample Visualforce page that creates a lightning:button using the lcvfTest.app from the previous example.

1<apex:page>
2    <apex:includeLightning />
3    <div id="lightning" />
4    <script>
5        $Lightning.use("c:lcvfTest", function() {
6            $Lightning.createComponent("lightning:button",
7                { label : "Press Me!" },
8                "lightning",
9                function(cmp) {
10                    console.log("button was created");
11                    // do some stuff
12                }
13            );
14        });
15    </script>
16</apex:page>

The $Lightning.createComponent() call creates a button with a “Press Me!” label. The button is inserted in a DOM element with the ID “lightning”. After the button is added and active on the page, the callback function is invoked and executes a console.log() statement. The callback receives the component created as its only argument. In this simple example, the button isn't configured to do anything.

You can call $Lightning.use() multiple times on a page, but all calls must reference the same Lightning dependency app.

Important

For details about using $Lightning.use() and $Lightning.createComponent(), see Lightning Out Markup in the Lightning Web Components Developer Guide.

Limitations

If a Visualforce page contains an Aura component, you can’t render the Visualforce page as a PDF.

Browser Third-Party Cookies

Lightning components set cookies in a user’s browser. Because Lightning components and Visualforce are served from different domains, these cookies are “third-party” cookies.

You can use several approaches for enabling Lightning components in Visualforce to work with third-party cookies. See Enable Browser Third-Party Cookies for Lightning Out in the Lightning Web Components Developer Guide.

Lightning Aura Components Developer Guide

Use Lightning Components in Visualforce Pages

Add the Lightning Components for Visualforce JavaScript Library

Create and Reference a Lightning Out App

Creating a Component on a Page

Limitations

Browser Third-Party Cookies