Skip to content

Blockstudio vs create-block

The same block.json, without the React editor and the build.

@wordpress/create-block is the officially supported tool for starting a block: a plugin, a block.json, a React edit component, and a webpack build. Blockstudio keeps block.json and the WordPress block API, and replaces the edit component with fields it renders for you and a template the server renders, with nothing to build.

What changes without the build

A Blockstudio block is a folder: block.json for fields, a template for markup, and optional assets next to them.

Fields, not controls

Declare a field in block.json and its control appears. 27 built-in types, from text to repeaters.

One template

The same PHP, Twig, or Blade template renders the editor preview and the page.

Editor components as tags

Write RichText or InnerBlocks tags in the template; the editor swaps in React.

Assets by file name

style.scss compiles on the server, and npm imports in script.js download into the block.

When create-block is the better pick

When the editing experience is the product: custom toolbars, drag interactions, canvases, or anything that needs React state in the editor. When a block must save static markup that renders without PHP. And when your team already writes React and wants the full @wordpress/components library.

Core has also moved toward PHP. Since WordPress 7.0, a block registered with autoRegister and a render callback gets generated controls for string, number, integer, and boolean attributes, with no JavaScript. Rich text, inner blocks, and media still need an edit component there.

They work side by side

Blockstudio registers any block.json without a blockstudio key through register_block_type(). Build a create-block block with wp-scripts, drop the output folder into a Blockstudio directory, and it loads next to your Blockstudio blocks.

The Blockstudio registry copies block folders between projects, so the same works for sharing: a create-block folder travels like any other block.

Side by side

The same block API, two ways to author the editor side.

The editor UI
create-blockNo: A React edit component you write
BlockstudioYes: Generated from fields in block.json
Build step
create-blockNo: wp-scripts build before the block loads
BlockstudioYes: None; templates and assets load as files
Editor preview
create-blockNo: Your edit component, separate from the output
BlockstudioYes: The same server-rendered template
Changing markup later
create-blockNo: Static by default; save() changes need deprecations
BlockstudioYes: Existing blocks re-render from the template
Interactivity API
create-blockYes: Interactive template, module build flag
BlockstudioYes: One flag; script.js loads as a module
Custom editor interactions
create-blockYes: Anything React can do
BlockstudioNo: Fields, custom field controls, RichText, InnerBlocks, media
Licence
create-blockYes: Free, GPL-2.0-or-later
BlockstudioYes: Free, GPLv2 or later

create-block questions

What block developers ask about leaving the build behind.

Do I still need Node?

Not for Blockstudio blocks: templates, SCSS, and ES module imports are handled in PHP. A create-block project needs Node for wp-scripts, and @wordpress/scripts 36.1.0 requires Node 22.22.2 or a later 22.x, 24.15.0 or a later 24.x, or Node 26 and later.

Is it the same block.json?

Yes. Blockstudio reads a standard block.json and adds a blockstudio key for fields and settings. Name, title, category, supports, and the rest mean what WordPress says they mean.

Can I keep my create-block blocks?

Yes. Drop their build output into a Blockstudio directory and Blockstudio registers them with register_block_type(), or keep them in their own plugin. Rewrite a block only when the generated fields would serve it better.

When is create-block the better pick?

When you need editor behavior that fields and templates cannot express, static save output, or a team that already works in React. Blockstudio is for the many blocks that are fields plus markup, where the edit component is mostly boilerplate.

What about the Interactivity API?

Both support it. The create-block interactive template sets up supports.interactivity, a viewScriptModule, and the experimental modules build flag. In Blockstudio you set interactivity under the blockstudio key, and script.js loads as a module with the import map generated for you.

Write the block, skip the build

Fields in block.json, a template in PHP, Twig, or Blade, and a block that shows up in the editor the moment the folder exists.

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