Advanced Custom Fields: what it is and when you need it
ACF adds structured fields to WordPress so editors fill in a form instead of designing a page. When you need it, free vs PRO, and Secure Custom Fields.
By Sohail Hussain21 November 20265 min read
Advanced Custom Fields (ACF) is a WordPress plugin that adds form fields to the editing screen: a text box for "Client name", a date picker for "Completed", an image field for "Logo", a list of related services. Editors fill in the fields, and the theme decides where and how each value appears. You need it when your content has a fixed structure that repeats, such as projects, team members, products or locations, and you want every item to look the same and be searchable by its details. You do not need it for one-off pages the block editor already handles well.
What does ACF actually do?
WordPress has always been able to store extra data against a post. It is called post meta. What WordPress lacks is a friendly way for editors to enter it, and ACF provides that.
A developer, or a confident site owner, creates a field group in ACF's settings: a set of fields, each with a name, a type and rules. Location rules decide where the group appears, for example "on all Projects" or "on the page using the Contact template". ACF offers over 30 field types, including text, number, image, file, date, select, true/false, link, relationship and Google Map.
The theme then reads the values and displays them. That part matters. ACF does not change the front end by itself, and fields with no template code behind them are invisible to visitors.
We use ACF, or its fork Secure Custom Fields, on most WordPress sites with structured content that we build in our website design and development work. It pairs with custom post types: the post type is the kind of thing, and the fields are its details.
When do you need custom fields, and when are blocks enough?
| Situation | Blocks | Custom fields |
|---|---|---|
| A one-off About or landing page | Better | |
| Forty projects that must look identical | Better | |
| Data shown in several places, such as a team member's photo on four pages | Better | |
| Content filtered or sorted by a value, such as jobs by city | Better | |
| A layout editors want to vary freely | Better | |
| Content sent to an app or another site through the API | Better; structured data is easier to use |
The rule of thumb: if you would describe the content as a record with properties, use fields. If you would describe it as a page with sections, use blocks.
The two also combine. ACF Blocks, a PRO feature, let a developer build custom blocks whose settings are ACF fields, so an editor can drop a "Project highlights" block into an ordinary page.
What is in the free version, and what needs PRO?
The free plugin, from the WordPress.org directory, includes the standard field types and a screen for registering custom post types and taxonomies without code.
ACF PRO adds the features larger builds tend to rely on:
- Repeater: a set of fields that repeats, such as a specification list with a label and a value on each row.
- Flexible Content: a set of predefined layouts editors can stack in any order.
- Gallery and Clone fields.
- Options pages: site-wide settings, such as office addresses or footer links, edited in one place.
- ACF Blocks.
As of October 2026, ACF PRO costs $49 a year for one site, $149 for up to ten and $249 for unlimited sites, according to the ACF PRO page.
What about Secure Custom Fields?
In October 2024, during a public dispute between Automattic and WP Engine, which owns ACF, WordPress.org forked ACF into a plugin called Secure Custom Fields (SCF). SCF is maintained under WordPress.org and listed in the plugin directory separately from ACF, which WP Engine continues to develop.
Two practical points:
- SCF includes field types that ACF reserves for PRO, such as Repeater and Flexible Content, at no cost.
- The two share their origins and their template functions, such as
get_field(), so theme code written for one generally works with the other today. They are developed separately, though, and may drift apart.
Installing SCF deactivates ACF, so you run one or the other. For a new site, either is a sound choice. Pick the one whose maintainers you trust to keep it updated, and avoid switching back and forth. The Secure Custom Fields plugin page lists its current features and changelog.
How does a developer show the fields in a theme?
In a PHP template, get_field() returns a field's value for the current post. ACF's documentation is clear that values returned by get_field() are not escaped, so the template must escape them when it prints them:
<?php
$client = get_field( 'client_name' );
$year = get_field( 'completed_year' );
?>
<?php if ( $client ) : ?>
<p class="project-client"><?php echo esc_html( $client ); ?></p>
<?php endif; ?>
<?php if ( $year ) : ?>
<p class="project-year">Completed <?php echo esc_html( $year ); ?></p>
<?php endif; ?>
The function and its escaping guidance are in the get_field() documentation.
Field group definitions can also be saved as JSON files inside the theme, which ACF calls Local JSON. That puts them in version control alongside the templates that use them, so a field change and the template change ship together. Our JSON formatter makes those files readable when you review a change.
What are the downsides?
- Another dependency. Your templates call ACF functions. If the plugin is deactivated, pages that use them break or show nothing. Keep it updated like any other plugin.
- Data stays, display goes. Values are stored as ordinary post meta, so uninstalling ACF does not delete content. But nothing displays it until the templates are rewritten.
- Overbuilding. A field for every sentence turns editing into data entry, and makes simple changes need a developer. Use fields for real data and let blocks handle the prose.
- Performance at the extremes. Very large repeaters or long flexible content layouts mean many database rows per post. For normal company sites this does not matter.
- Headless sites. If a separate front end reads WordPress through the REST API, each field group's REST setting must be switched on. See headless WordPress with Next.js.
ACF is not worth adding to a small site whose pages are all one-offs. The block editor does that job, and one fewer plugin is one fewer thing to update. For the bigger picture of when WordPress, with or without ACF, is the right platform, see WordPress for business websites.
Was this guide useful?