Skip to content

Blockstudio vs GUI block builders

Lazy Blocks, Genesis Custom Blocks, and MB Blocks, compared with files.

Lazy Blocks, Genesis Custom Blocks, and Meta Box’s MB Blocks let you build a custom block from an admin screen: add fields, write a template, save. Each also has a code path. Blockstudio starts from files: the block is a folder in your project, so git has it from the first commit and there is nothing to export.

The three, one by one

Lazy Blocks (4.4.1, August 2026) stores each block as a post you build in the admin, with the template in Handlebars or PHP, or as a theme file at blocks/lazyblock-<slug>/block.php. Blocks can also be registered in PHP through the Lazy Blocks add_block() API and exported as JSON or PHP. Per-block CSS and JS files, nine extra controls, and custom namespaces are Pro.

Genesis Custom Blocks stores blocks as posts built in the admin and renders PHP templates from the theme with block_field(). It has 15 free and 6 Pro fields, and Genesis\CustomBlocks\add_block() registers blocks in code. Its feature request template says no new features are being added; the latest release, 1.7.3 in April 2026, fixed WordPress 7.0 compatibility.

MB Blocks is the most code-friendly of the three: a block is a PHP field group, optionally registered through a standard block.json with a render file, and Meta Box Local JSON keeps field groups built in its UI as JSON files in the theme. It renders PHP, or Twig through MB Builder or the premium MB Views. MB Blocks needs a paid licence; the Meta Box framework itself is free on WordPress.org.

What starting from files changes

When the block is a folder, the workflow around it is the one you already use for code.

No export step

The definition you edit is the one in git, so nothing drifts between admin and repository.

One schema

block.json fields validate against a published JSON schema in your editor.

Assets by file name

style.scss compiles, npm imports in script.js download into the block, and each file is enqueued by its name.

More than blocks

Pages, patterns, and extensions on core blocks come from files too.

Side by side

What holds for all three builders, against Blockstudio.

Defining a block
GUI block buildersYes: An admin screen, or PHP registration
BlockstudioYes: A block.json in a folder
Admin-built blocks in git
GUI block buildersNo: Need an export or a JSON sync
BlockstudioYes: No admin; the files are the definitions
Who builds blocks
GUI block buildersYes: People who write HTML, in the admin
BlockstudioNo: Developers, in files
Template languages
GUI block buildersYes: PHP, plus Handlebars or Twig in some
BlockstudioYes: PHP; Twig with Timber, Blade with a filter
Styles and scripts
GUI block buildersNo: Plain CSS and JS; no documented SCSS step
BlockstudioYes: SCSS compiled, npm imports downloaded
Licence
GUI block buildersNo: Free cores with Pro features; MB Blocks needs a paid licence
BlockstudioYes: Free and open source, GPL

Block builder questions

What to ask before you choose between a builder screen and a folder.

Are these builders UI-only?

No. Lazy Blocks registers blocks in PHP through its add_block() API, Genesis Custom Blocks has Genesis\CustomBlocks\add_block() and a theme blocks.json that its Pro export writes, and MB Blocks is built around PHP and block.json. The difference is the default: Lazy Blocks and Genesis Custom Blocks start in the admin and save to the database, while Blockstudio has no admin builder at all.

Which one is closest to Blockstudio?

MB Blocks: it can register through a standard block.json with a PHP field group, renders a PHP file, and Local JSON keeps field groups in the theme. What Blockstudio adds is the asset pipeline, Blade templates through a render filter, pages, patterns, and extensions from files, and a free licence.

When is a GUI builder the better pick?

When someone who writes HTML but not PHP builds the blocks, or when a site needs a few simple blocks and nobody wants a repository. Blockstudio assumes a developer and a codebase.

Is Genesis Custom Blocks still maintained?

It receives compatibility fixes, such as 1.7.3 for WordPress 7.0 in April 2026, but its feature request template says no new features are being added. Factor that in before starting new work on it.

What do they cost?

Lazy Blocks and Genesis Custom Blocks are free on WordPress.org, with Pro features under a paid licence; MB Blocks needs a paid Meta Box licence. All three are GPL. Blockstudio is free and open source with every feature included.

Build the block in a folder

Fields in block.json, a template beside it, and git from the first commit. No export step and no licence key.

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