An Editor React Component (ERC) is a custom site widget built in React that integrates natively with the editor. A declarative manifest tells the editor which parts of the component are customizable, so the editor sets up its own panels and controls around the component automatically. Wix users get the same editing experience as with built-in Wix elements.
Editor compatibility: Apps can include ERCs for use on Studio Two and Wix Harmony sites. When you extend a site directly, ERCs are only available in Studio Two. They aren't supported on Wix Studio or Wix Editor sites.

Use an ERC when you want a custom widget to feel like a native Wix element in the editor, without having to build and maintain your own settings panel. Common cases include:
Tip: For widgets that need to work across Studio Two, Wix Studio, Wix Editor, and Harmony, use a site widget instead.
An ERC has 2 main parts:
The manifest follows from the component rather than the other way around. You build the React component first, and Wix tooling generates the editorElement portion of the manifest from that code:
You then adjust those declarations rather than writing them from scratch. For which manifest sections drive which panels, see About Auto Panels for Editor React Components.
The component and manifest must stay aligned. The manifest is what gives Wix users an editing experience that matches Wix's built-in elements, without you having to design or maintain custom settings panels.
Wix users place an ERC on a page like any other component, through the editor's component picker. From there:
The component renders the same way in the editor and on the published site, with whatever props and styles the Wix user has configured.
ERC code runs in 2 contexts, each with its own identity:
What the component can do is bounded by the active identity's permissions, plus the app's permission scopes when the component belongs to an installed app.
For some restricted methods, you can elevate the call from backend code that the component invokes to gain higher authorization than the calling identity has.
Sites:
Harmony sites don't support extending with code, so they get ERCs only from an installed app.
Wix-managed headless projects: Don't support ERCs. Headless projects use a custom frontend, so there's no Wix editor for an ERC to integrate with.
Self-managed headless projects: Don't support ERCs.
Wix-managed apps: Build ERCs with the Wix CLI. An app that includes an ERC can be used on Studio Two and Wix Harmony sites. See Add an Editor React Component Extension with the Wix CLI in Build Apps.
Self-managed apps: Don't support ERCs.
Blocks apps: Don't support ERCs.
Last updated: 2 November 2026