ACF Blocks is a WordPress plugin that provides 29 custom Gutenberg blocks built on Advanced Custom Fields (ACF). Every block uses ACF Block API v3 with block.json metadata, and field groups are registered automatically from JSON files. No manual ACF imports are needed.
The ACF Blocks plugin gives you 29 production-ready Gutenberg blocks built on Advanced Custom Fields: accordions, product boxes, opinion boxes, callouts, and the rest of the editorial toolkit this site runs on daily. This course documents version 2.7.1, the build currently shipping.
The plugin is designed as a standalone package. Install it, activate it, and the blocks appear in your editor. Each block is self-contained with its own render template, styles, field definitions, and optional extra functionality.
What This Plugin Provides
- 29 production-ready blocks for content, products, media, navigation, and forms
- Automatic field group registration from JSON (no ACF admin imports)
- Conditional asset loading (CSS only loads when a block is used on the page)
- Block transforms between core WordPress blocks and ACF blocks
- Structured data (JSON-LD) output for FAQ, product review, star rating, and TOC blocks
- External image localization on post save
- A license system for automatic updates
Requirements
- WordPress 6.0 or higher
- PHP 7.4 or higher
- Advanced Custom Fields Pro 6.0+ or Secure Custom Fields (free)
If neither ACF Pro nor Secure Custom Fields is installed when the plugin is activated, the plugin will attempt to install and activate Secure Custom Fields from the WordPress.org repository automatically.
Plugin Constants
The plugin defines four constants on load:
ACF_BLOCKS_VERSION– Current plugin version (e.g.2.1.6)ACF_BLOCKS_PLUGIN_DIR– Absolute path to the plugin directoryACF_BLOCKS_PLUGIN_URL– URL to the plugin directoryACF_BLOCKS_PLUGIN_FILE– Absolute path to the main plugin file
License
GPL v2 or later.
Quick answers to common questions:
What do I need to run the ACF Blocks plugin?
Advanced Custom Fields Pro 6.0+ or Secure Custom Fields, WordPress 6.0+, and PHP 7.4+. The plugin registers nothing without ACF active, by design: every block is an ACF Block API v3 registration.
How is this different from building blocks with ACF myself?
It’s the 29 blocks already built, tested, and maintained: field groups, render templates, styles, JSON-LD where it matters, and an auto-discovery system for adding your own. You skip months of block development and inherit the upgrade path.