Skip to content

Blockstudio vs ACF Blocks

The same PHP templates, with fields, assets, and pages in files.

ACF Blocks and Blockstudio agree on more than they differ: both register blocks from block.json and render them with PHP on the server. The differences sit around the template: how fields are defined, how blocks get registered, what compiles your assets, and what else lives in files.

What both get right

If you build ACF blocks today, most of your habits carry over. The template is still the heart of the block.

block.json first

ACF has recommended block.json registration since ACF 6.0; Blockstudio reads the same file.

Rendered on the server

Template changes apply to every existing block on the next render.

InnerBlocks in templates

Both accept an InnerBlocks tag with allowed blocks, a template, and a lock.

What Blockstudio keeps in files

Everything a block needs sits in its folder, and the rest of the site can live in files too.

Folder discovery

A folder with block.json and a template is a registered block. No init hook.

Twig and Blade

PHP out of the box, Twig once Timber is installed, and Blade through illuminate/view 8 to 12 with a short filter that calls Blockstudio\Blade_Renderer. Blade also covers pages, patterns, and Site Editor templates.

Assets by file name

SCSS compiles on the server, a .scoped.scss file is scoped to the block, and script.js loads as a module.

Extensions

Add fields to core and third-party blocks with one JSON file.

Pages and patterns

Pages sync from template files into real blocks; patterns register from files into the inserter.

Data, RPC, and cron

db.php, rpc.php, and cron.php next to the block that uses them.

Static analysis

The PHPStan preset fails a template that reads a field block.json lacks.

Tailwind in PHP

Tailwind v4 compiled per page on the server, with no Node.

Where ACF is the stronger tool

ACF has been developed since 2011 and the free plugin alone reports more than two million active installations. Non-developers can build field groups in the admin, and options pages and post types come with a UI.

Its block editing has improved too. Blocks V3 (ACF PRO 6.6) keeps the rendered preview in the canvas with an expanded field panel beside it, and since 6.7 a block can opt in so editors type straight into Text and Text Area fields in the preview.

Side by side

The same server-rendered block, and what surrounds it.

Registering a block
ACF BlocksNo: A register_block_type() call per block
BlockstudioYes: Drop a folder, it is discovered
Where fields live
ACF BlocksYes: Field groups, or acf.fields since 6.8.1
BlockstudioYes: blockstudio.attributes in block.json
Template languages
ACF BlocksNo: PHP template or callback
BlockstudioYes: PHP; Twig with Timber, Blade with a filter
Styles and scripts
ACF BlocksNo: Bring your own build for SCSS
BlockstudioYes: SCSS compiled, npm imports downloaded
Fields on core blocks
ACF BlocksNo: Block Bindings to core attributes
BlockstudioYes: Extensions add fields to any block
Options pages and post types
ACF BlocksYes: Built in, with an admin UI
BlockstudioNo: No options pages; post types only for page collections
Licence
ACF BlocksNo: ACF PRO, a paid licence
BlockstudioYes: Free and open source, GPL

ACF Blocks questions

What ACF developers ask before they switch.

Can ACF define fields in block.json now?

Yes. Since ACF PRO 6.8.1 a block can declare its field group inline under acf.fields, using ACF field arrays, and those groups stay out of the Field Groups screen. Blockstudio uses blockstudio.attributes with a published JSON schema, and it also discovers the folder, so there is no register_block_type() call per block.

When is ACF the better pick?

When non-developers build field groups in the admin, when the site needs options pages or post types configured in a UI, or when a team already runs many ACF blocks and has no reason to move them. ACF is mature, widely known, and keeps improving its block editor.

How do I move ACF blocks over?

Block by block. Move each field into blockstudio.attributes, replace get_field() with $a, and delete the registration call; the migrating from ACF guide maps the field types. Relational fields become a select, radio, or checkbox field populated from a query.

Can both run on one site?

Yes. They register different block names through the same WordPress block API, so existing ACF blocks keep rendering while new ones are written in Blockstudio.

What does each cost?

Blockstudio is free and open source under the GPL, with every plugin feature included. ACF Blocks need ACF PRO, a paid licence sold as a yearly subscription. If it lapses, updates stop and new ACF blocks cannot be created, but existing blocks keep working for editors and visitors.

Bring your blocks into one folder

Fields in block.json, a template in PHP, Twig, or Blade, and assets picked up by file name. No registration code 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