Editor React Components

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.

An Editor React Component on a Studio Two site

When to use an Editor React Component

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:

  • Building a reusable component with rich design controls, like a testimonial card with editable text, image, and color presets.
  • Offering a content-driven widget where Wix users edit data inline, like an event lineup or a pricing table.
  • Providing a layout block whose styling Wix users can adjust through the editor's standard design panels, like a feature grid or a hero section.

Tip: For widgets that need to work across Studio Two, Wix Studio, Wix Editor, and Harmony, use a site widget instead.

Component and manifest

An ERC has 2 main parts:

  • React component: The UI code that renders in the editor and on the live site.
  • Manifest: A configuration object that describes the component to the editor. The manifest lists which props are customizable, how they map to editor controls, and which DOM elements receive Wix-user style changes.

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:

  • Props you declare become editable data in the Settings panel. Text-based props also get an Edit Text panel.
  • Elements you mark as selectable become inner elements, each with their own panels.
  • CSS properties you style become controls in the Design panel.

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.

Runtime model

Wix users place an ERC on a page like any other component, through the editor's component picker. From there:

  1. The editor reads the manifest to determine which parts of the component are customizable.
  2. The editor configures the appropriate panels and controls in its UI based on the manifest.
  3. As the Wix user makes changes, the editor stores those values. Data changes are passed to the component as React props. Style changes are applied as CSS directly to the DOM elements that match the selectors in the manifest.

The component renders the same way in the editor and on the published site, with whatever props and styles the Wix user has configured.

Authentication and permissions

ERC code runs in 2 contexts, each with its own identity:

  • In the editor, the component renders for the Wix user editing the site, with that user's identity.
  • On the live site, the component renders for the visitor or member viewing the page, with that visitor or member's 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.

Editor React Components across development paths

  • Sites:

    • Studio Two: Add ERCs directly to the site project through the Wix Extension Builder.
    • Wix Studio and Wix Editor: Don't support ERCs.

    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

Did this help?