Skip to content

Blockstudio vs headless WordPress

Files, and static HTML once you turn it on, in one system.

Headless WordPress turns WordPress into a content API behind a separate frontend, for example Next.js reading the REST API, or Next.js with Faust.js reading WPGraphQL. You get the React ecosystem and full control of every block’s markup, and you run two systems to get it. Blockstudio keeps one WordPress: templates in files, plugins that render, and static prerendering when you want stored HTML.

What the second system costs

Each of these is documented by the tools that make headless work. None is a bug; all of them are work.

Blocks rebuilt in React

Faust.js renders mapped blocks with React components and ships 12 core blocks as a reference set; unmapped blocks arrive as HTML without their scripts.

Previews need plumbing

Faust previews need authentication, a preview route, and a secret key shared with WordPress.

Plugins need extensions

WPGraphQL lists ACF, WooCommerce, SEO, and form plugins as needing extensions or custom code.

Freshness is a pipeline

You wire WordPress to call revalidatePath, and the page regenerates on its next visit. A CDN copy needs its own purge.

One WordPress, still static

With static prerendering on, Blockstudio stores the HTML anonymous visitors receive, purges a post’s copy and the front page when the post is saved, or re-renders them when warming is on, and with early serving sends stored pages before WordPress boots. A CDN in front of either setup still needs its own purge.

Plugins render on the same pages, previews are WordPress previews, and the block editor shows the template the visitor gets. With prerendering on, list a plugin’s dynamic paths, such as checkout and account, under dynamicPaths so they skip the stored copy. There is no second build, no second host, and no revalidation hook to wire up.

Where headless is the better choice

When the frontend is an application: heavy client-side state, React components shared with other products, or one content API feeding a website, mobile apps, and other clients. The REST API and WPGraphQL exist for exactly that, and Faust.js lets you override any block’s markup in React.

Blockstudio has limits too. Pages render from PHP, Twig, or Blade templates, not React, and static prerendering is off until blockstudio.json turns it on.

Side by side

The same content in WordPress, one system or two in front of it.

Systems to run
Headless WordPressNo: WordPress plus a Node frontend and its host
BlockstudioYes: One WordPress install
Rendering blocks
Headless WordPressNo: Rendered HTML without block scripts, or a React component per block
BlockstudioYes: Each block renders its own template
Previews
Headless WordPressNo: Auth, a preview route, and a shared secret
BlockstudioYes: WordPress previews as they ship
Plugin frontends
Headless WordPressNo: An API extension plus frontend code each
BlockstudioYes: They render like they always did
A content edit goes live
Headless WordPressNo: Your code calls revalidatePath; a CDN copy needs its own purge
BlockstudioYes: With prerendering on, saving purges the post and home page
Static, fast pages
Headless WordPressYes: Static and ISR pages, cacheable at the edge
BlockstudioYes: Static prerendering, once you turn it on
Frontend stack
Headless WordPressYes: React and the Next.js ecosystem
BlockstudioNo: PHP, Twig, or Blade templates

Headless questions

What to ask before you split WordPress in two.

Is headless faster?

Both can hand visitors stored HTML. Next.js static and ISR pages carry cache headers a CDN can keep at the edge; Blockstudio with static prerendering on serves stored pages from your WordPress host, before WordPress boots when early serving is on. The difference is how many systems it takes to produce that HTML.

What is the state of Faust.js?

It is maintained: its packages had releases on October 7, 2026. It targets the Next.js Pages Router with Apollo Client 3 and provides previews, authentication, the template hierarchy, and block rendering. In January 2025, when they retired its App Router experiment, its maintainers said WP Engine’s Headless WordPress Toolkit would replace Faust.

Do my plugins still work headless?

Their admin screens and data do. Their frontend output does not carry over: WPGraphQL documents an extension per plugin for ACF, WooCommerce, SEO, and forms, and WooGraphQL’s recommended checkout hands the session back to WordPress’s own checkout page.

When is headless the better pick?

When the frontend is a React application, when one content API feeds several clients, or when you want to control every block’s markup in React. If the site is a website that clients edit and plugins extend, one WordPress with Blockstudio is less to run.

Can I use React with Blockstudio at all?

In the editor, yes: RichText, InnerBlocks, and MediaPlaceholder are React components that Blockstudio swaps in from template tags, and script.js can import npm packages for frontend behavior. The page itself renders from PHP, Twig, or Blade.

Keep one WordPress

Write templates as files, turn on static prerendering, and let plugins, previews, and the editor keep working the way they ship.

Sources, checked

Plus

The official extension kit

Premium site templates, AI system instructions, and a private Discord community. One-time purchase, lifetime updates.

  • 500+ site templates
  • AI system instructions
  • Lifetime updates
  • Private Discord community