WordPress runs the backend.You choose the frontend.

Build inside WordPress with an integrated React theme, or connect an external frontend through ReactWP’s versioned API. Integrated templates can use client, static, or server rendering.

Start building Read the docs

Stay integrated. Or don’t.

The content stays in WordPress. The frontend boundary is the decision.

Build inside WordPress.

Build the frontend inside a WordPress theme. ReactWP selects the React template, manages client navigation, and keeps the browser runtime connected to WordPress.

Install ReactWP

Go headless.

Keep WordPress for content and administration, then consume normalized routes and shared site data through ReactWP’s versioned REST API.

Start headless

Client. Static. Server. Pick per template.

Integrated themes can mix all three modes in one project. Client remains the default for existing registrations.

Compare render modes

client: Render the route in the browser. No Node.js process is required in production.
static: Generate a React HTML fragment ahead of time, serve it through WordPress, and hydrate it in the browser.
server: Render request-dependent HTML through the optional Node service, then hydrate the same template.

registerTemplate('Home', {
  loader: () => import('../../templates/Home'),
  render: 'static'
});

Rendering is configured per integrated template.

WordPress stays in charge.

Across both frontend paths, WordPress keeps content, administration, users, plugins, permalinks, previews, and SEO.

Explore the architecture