React in Salesforce means building native apps with React through Salesforce Multi-Framework, a runtime on the Agentforce 360 Platform. It runs alongside Lightning Web Components, not instead of them, and is currently in open beta for sandboxes and scratch orgs.
For years, Salesforce development meant learning Lightning Web Components, whether you liked it or not. That changed when Salesforce Multi-Framework moved into open beta, giving React developers a first-party way to build on the platform without leaving their existing skills behind.
This guide walks through what Multi-Framework actually does, how it compares to LWC, and how to start building a React app on Salesforce today.
What Is React in Salesforce?
React in Salesforce refers to Salesforce Multi-Framework, a framework-agnostic runtime that lets you build native Salesforce apps using React, with the same authentication, security, and governance model LWC already uses.
Once your org is set up, a React app can:
Query and update records with GraphQL
Call Apex methods directly
Access user context through the UI API
It's live in open beta now, so you can build and test it today.
How Multi-Framework Differs from Lightning Web Components (LWC)
LWC is Salesforce's own framework, built for declarative data access through @wire, Lightning Data Service, and drag-and-drop placement in Lightning App Builder. React is a general-purpose library with a much broader ecosystem. Multi-Framework brings that ecosystem onto Salesforce without asking you to give up platform security or data access.
Is Multi-Framework Replacing LWC?
No. Multi-Framework runs alongside LWC, not in place of it. Your existing Lightning Web Components keep working exactly as they do now. React components can even be embedded as micro-frontends inside Lightning pages, though that capability is still in developer preview, so treat it as early stage rather than production ready.
LWC vs React on Salesforce: Which Should You Choose?
The honest answer is it depends on what you're building. Here's how to think it through.
When to Use LWC
Choose LWC when you need declarative data binding through @wire, Lightning Data Service, the full base component library, or drag-and-drop placement in Lightning App Builder. It's the more mature option, tightly woven into the platform, and still the right default for most internal, Salesforce-first apps built today.
When to Use React
Choose React when you're sharing components across Salesforce and non-Salesforce surfaces, or when your project needs something specific from the React ecosystem, like a state management library or component set without a native LWC equivalent. It also helps when your team already knows React well.
Performance and Ecosystem Differences
React apps don't currently support Lightning base components or built-in Salesforce Lightning Design System styling, so you'll style them manually using SLDS blueprints, SLDS for React, or a utility framework like Tailwind. LWC keeps SLDS styling built in automatically, which still makes it the faster path to platform-consistent UI.
How to Build a React App on Salesforce (Step-by-Step)
Getting started takes a few setup steps before you write a single component. Here's the order that works.
Prerequisites: CLI, Node.js, and Scratch Orgs
Before you start, install the Salesforce CLI and Node.js v18 or later, then set up a scratch org or sandbox. Multi-Framework apps can't deploy to production during beta, so all your early building and testing needs to happen in a non-production environment first.
Connecting to Salesforce Data with GraphQL and Apex
Once your project is running, use the @salesforce/sdk-data library to query and mutate Salesforce records with GraphQL, or invoke Apex methods directly from your React components. This keeps your data calls efficient and within your org's API limits, without writing separate integration code.
Handling Authentication with createDataSDK()
The createDataSDK() utility handles authentication automatically, so you don't manage tokens by hand. It applies the same security and governance model your Salesforce org already enforces, meaning your React app respects user permissions exactly the way an LWC app would.
Embedding React Components into Lightning Experience Pages
React isn't limited to standalone apps. You can bring it directly into your existing Lightning pages too.
Micro-Frontend Support: Current Limitations
React components can be embedded as micro-frontends inside Lightning Experience pages, with the platform handling shared data and permissions between them. This is currently in developer preview, and drag-and-drop placement inside Lightning App Builder isn't supported yet, so plan for manual configuration for now.
What's Coming Next (Roadmap)
Salesforce has said React is supported today, with additional frameworks planned for future releases. As Multi-Framework moves from beta toward general availability, deeper Lightning App Builder integration is expected to follow, though Salesforce hasn't published exact dates yet.
Conclusion
Salesforce Multi-Framework means you don't have to choose between your platform and your framework anymore. If your team thinks in React, you can now build directly on Salesforce without a long detour through LWC first. I'm Prateek Pareek, a tech freelancer who helps businesses navigate exactly this kind of Salesforce platform decision, from architecture calls to hands-on builds. If you're weighing React against LWC for your next project, let's talk.
Frequently Asked Questions
Can I deploy React apps to production yet?
Not yet. Multi-Framework is in open beta, and beta apps can't be deployed to production orgs right now. You can build and test freely in scratch orgs and sandboxes, and production support is expected as the feature matures toward general availability.
Does React support the same security and governance as LWC?
Yes. Multi-Framework apps use the same authentication, security, and governance model as the rest of the platform. The createDataSDK() utility manages authentication automatically, so your React app respects the same permissions and sharing rules an LWC app would.
What frameworks are coming after React (Vue, Angular)?
React is the only framework supported today. Salesforce has confirmed additional frameworks are planned for future releases, though specific names and timelines haven't been published yet, so it's worth checking Salesforce's official developer blog for updates.
Does a React app on Salesforce use Salesforce styling automatically?
No. React apps don't currently include built-in Salesforce Lightning Design System styling like LWC does. You'll need to apply SLDS blueprints, use the SLDS for React package, or style with a framework like Tailwind to match the Salesforce look and feel.
What do I need installed before building a React app on Salesforce?
You need the Salesforce CLI and Node.js version 18 or later, plus a scratch org or sandbox to build in, since Multi-Framework apps can't be deployed to production during the beta period.
Top comments (0)