WordPress Custom Fields in 2026: ACF, SCF, Meta Box, Pods and Block Bindings

Custom fields let WordPress store structured data alongside a post: a property's price, an event's date, a recipe's cook time, a team member's job title. WordPress has stored this kind of data (post meta) for a long time, but building friendly editing screens for it usually means a plugin or custom code.

In 2026 there are four common routes. Advanced Custom Fields (ACF), owned by WP Engine and listed on WordPress.org again. Secure Custom Fields (SCF), a fork of ACF maintained under the WordPress.org account. Framework-style plugins such as Meta Box and Pods. And core WordPress itself, whose Block Bindings API can now connect custom fields directly to some core blocks.

This guide explains how ACF and SCF came to exist side by side, what each option does, how to evaluate them, and what to do if your site already depends on one. It sticks to verified facts as of October 2026 and takes no side in the dispute behind the fork.

What custom fields are, and what core already does

Every post, page, user and term in WordPress can carry extra key-value data called metadata. Core provides the storage and developer functions to register and read it. What core does not provide out of the box is a polished field builder: grouped fields with types like date pickers, image selectors, relationship pickers and repeaters, shown on the right edit screens.

That gap is why field plugins exist. They give you a visual builder, validation, conditional logic and template functions. Many also register custom post types and taxonomies, which we explain in how to create custom post types in WordPress.

Block Bindings: custom fields in core blocks

WordPress 6.5 (April 2024) introduced the Block Bindings API. It lets a block attribute pull its value from a source such as the built-in core/post-meta source. Per the WordPress developer blog, the initial supported blocks were Image (url, alt, title), Paragraph and Heading (content) and Button (url, text, link target, rel). The meta must be registered with show_in_rest enabled.

WordPress 6.7 added a default editor panel that shows bindings on compatible blocks and lets you connect attributes to custom fields. According to the 6.7 dev note, the ability to edit bindings in the editor is on by default for administrators and off for other users, with a filter to change that.

Block Bindings is a developer feature, not a field builder. You still register the meta in code (or with a plugin), and only certain blocks support it. For simple "show this field in this block" needs on a block theme, though, it can replace a plugin dependency.

ACF and SCF: a factual timeline

The two plugins share code history, which is why they look so alike. Here is the sequence, with sources:

The wider legal dispute between WP Engine and Automattic is still active as of October 2026. Our WP Engine and Automattic dispute explainer covers it in more detail.

Advanced Custom Fields (ACF)

ACF has 2+ million active installs on WordPress.org as of October 2026. The free plugin covers the field builder, over 30 field types, fields on posts, pages, users, terms, media and comments, and registration of post types and taxonomies in its interface. ACF PRO adds features its PRO page lists as the Repeater field, ACF Blocks, the Flexible Content field, Options Pages, the Gallery field and the Clone field.

As of October 2026, ACF PRO costs $49 per year for one site (Personal), $149 for 10 sites (Freelancer) and $249 for unlimited sites (Agency). PRO is sold on the ACF website rather than the WordPress.org directory.

Secure Custom Fields (SCF)

SCF is listed under the WordPress.org account. Its directory page describes field groups for posts, pages, users, taxonomy terms, media, comments and options pages, over 30 field types, and registration of post types and taxonomies. It advertises features such as options pages and blocks that ACF reserves for PRO.

Two practical points from its listing matter most. First, "Installing this plugin will deactivate plugins with matching function names/functionality, specifically Advanced Custom Fields, Advanced Custom Fields Pro". You cannot run both. Second, its documentation lives on developer.wordpress.org. Its changelog shows several security-focused releases in July and August 2026.

Meta Box and Pods

Meta Box (500,000+ active installs) is a free framework plugin with over 40 field types for posts, pages, custom post types, taxonomies, settings pages, users and comments. Its vendor says "the core Meta Box plugin is completely free" and sells extension bundles. As of October 2026, its pricing page lists personal bundles from $49 per year and lifetime options.

Pods (100,000+ active installs) creates custom content types and fields. Its site says "Pods is fully funded by donations". A separate Pods Pro add-on is offered by a third party (SKCDEV).

Side-by-side comparison

How to evaluate a custom fields tool

Field plugins sit deep in your theme and content, so switching later is expensive. Use the general checks in how to choose WordPress plugins, plus these:

• Feature fit: list the field types you need (repeaters, flexible layouts, relationships, galleries, options pages, custom blocks) and check which are free and which are paid.
• Maintenance: last-updated date, "Tested up to" version (WordPress 7.1.2 is current as of October 2026) and changelog cadence.
• Security history: search the Patchstack and Wordfence databases for past issues and how fast they were fixed.
• Data storage: does the plugin store values as standard post meta, or in custom tables? Standard meta is easier to move.
• Field definitions in code: can field groups be saved as JSON or PHP and kept in version control?
• Exit cost: how many templates call plugin-specific functions? Those calls break if the plugin is removed.

If your site already uses ACF or SCF

Most sites need no action beyond normal maintenance. A few practical steps help:

1. In Plugins, check which one is active and who the listed author is. ACF from WordPress.org shows WP Engine; SCF shows WordPress.org.
2. Keep whichever you use updated. SCF alone shipped three security or hardening releases between late July and early August 2026.
3. If you use ACF PRO, keep your license active so updates continue.
4. Do not install SCF on a site running ACF without testing on staging first, because SCF deactivates ACF and ACF PRO.
5. Export field groups to JSON or PHP and keep them in version control, whichever plugin you use.

A developer can help you weigh a move to native Block Bindings for simple cases. Our post on developing a custom WordPress theme shows where fields fit in theme work.

Conclusion

Custom fields in 2026 come down to a practical choice: ACF from WP Engine, the WordPress.org-maintained SCF fork, framework plugins like Meta Box and Pods, or core Block Bindings for simpler needs. Each is actively maintained as of October 2026. Choose on features, maintenance, security history and exit cost, and keep field definitions in code so you can change course later. eSEOspace builds and maintains custom WordPress sites through our WordPress development services, and our WordPress hub has more guides.

Frequently asked questions