Advanced Custom Fields (ACF®)

Quick take

Advanced Custom Fields is one of the clearest ways to turn WordPress from a post-and-page editor into a structured content system. This ACF review recommends the free plugin for many custom-field and content-modeling projects, while ACF PRO becomes important when you need repeaters, flexible layouts, galleries, options pages or ACF Blocks.

Best fit: Advanced Custom Fields (ACF®) makes the most sense for developers and site builders creating structured content models in WordPress. A different tool will usually make more sense for users expecting every custom field to design and render itself without template or builder work.

What ACF actually changes in WordPress

ACF lets you create field groups and attach them to posts, pages, users, taxonomy terms, media, comments and other WordPress objects through location rules. You can then retrieve those values in templates with ACF functions such as get_field().

Current ACF also lets you register custom post types and taxonomies from its interface, so many projects can model both the content type and its fields without a separate CPT plugin.

Features that matter for content modeling

The free plugin includes a broad set of field types for text, numbers, images, files, links, relationships, selections, dates and other structured data. Local JSON helps teams synchronize field-group definitions between environments, while import/export supports moving configurations between sites.

ACF 6.8 added WordPress Abilities API integration, automatic Schema.org structured-data capabilities and new WP-CLI commands for ACF JSON. These additions are especially relevant for sites using structured content in automation, search and AI-connected workflows.

ACF Free vs Pro

ACF Free is enough when you need standard field groups, location rules, custom post types, taxonomies and the core developer API. That covers a large amount of real client work.

ACF PRO adds the Repeater, Flexible Content, Gallery and Clone fields, Options Pages and ACF Blocks. The ACF Free vs Pro decision is therefore straightforward: upgrade when your content model requires repeatable structures, layout-building patterns, reusable global data or custom block development.

Trade-offs to understand

ACF stores structured data but does not automatically decide how your theme or builder should display every field. On developer-led sites, that is a strength because templates remain under your control. For non-technical users, it can mean additional template or builder work before the data appears on the front end.

Large or highly relational data models also deserve planning. WordPress post meta is flexible, but not every data-heavy application should be modeled as unlimited meta rows simply because custom fields make it easy.

ACF pricing

ACF pricing for ACF PRO is currently $49/year for Personal covering one website, $149/year for Freelancer covering 10 websites, and $249/year for Agency covering unlimited websites. Each paid plan includes the full PRO feature set, with the license level mainly changing the number of sites.

Pricing checked September 10, 2026. ACF Free remains available from WordPress.org.

ACF vs Meta Box

ACF and Meta Box both solve structured content and custom-field problems, but their packaging differs. ACF has a very familiar field-group workflow and a single PRO product with site-count tiers. Meta Box uses a free framework plus Lite/AIO and a wider extension system.

For teams already standardized on ACF templates and APIs, switching usually needs a concrete reason. New projects should compare field types, frontend needs, custom-table requirements, block workflows and licensing rather than choosing only by popularity. This ACF review treats both as serious developer tools.

PluginSuggest verdict

ACF remains a strong default for structured WordPress content. Start with free unless your model clearly needs a PRO-only field or feature. ACF PRO is easiest to justify when repeaters, flexible layouts, options pages or custom blocks are central to the build, not simply because a premium tier exists.

Schema discipline matters more than field count

ACF is easy to start with, but large projects benefit from treating field groups like application schema. Use stable field names, predictable group naming, and clear location rules. Local JSON or PHP registration can make changes reviewable in version control and reduce configuration drift between development, staging, and production.

Before replacing ACF, inventory repeaters, flexible content layouts, options pages, blocks, relationship fields, and template calls such as get_field(). Those dependencies are often more important than the raw database values because they define how the theme or builder retrieves and renders the content.

Advanced Custom Fields FAQs