Skip to content
General

Updated on 6 November 2026

Advanced Custom Fields (ACF): What It Does, What PRO Adds and What Became of the Dispute

What Advanced Custom Fields (ACF) does, when ACF PRO is worth it, who maintains it now and what became of the Secure Custom Fields dispute.

Advanced Custom Fields (ACF): What It Does, What PRO Adds and What Became of the Dispute
Contents

Advanced Custom Fields (ACF) is a WordPress plugin maintained by WP Engine that gives posts, pages and custom content types additional input fields, for a price, a contact person or technical data, say. The free version is enough for many websites, ACF PRO adds repeatable fields, flexible layouts and custom blocks. Since October 2024 there has also been a fork, Secure Custom Fields (SCF), which includes most of those features without a licence. Which of the two to choose is covered further down in the decision guide.

Last reviewed: 6 November 2026, versions and features checked at WordPress.org and advancedcustomfields.com.

What is ACF and what do you need it for?

Out of the box, WordPress knows a title, content and a featured image. On top of that come the built-in custom fields: hidden by default in the block editor and nothing more than pairs of name and value. That is of little use to editors, with no image fields, no select lists and no required fields.

ACF turns this into a proper form. According to its directory listing it has over 30 field types, and fields can be assigned to posts, pages, users, taxonomy terms, media and comments. You create custom content types and taxonomies in the same interface, without code and without another plugin. Typical uses:

  • a team entry with photo, position and phone number
  • a job posting with location, start date and contact person
  • a reference project with client, industry and images
  • a data sheet whose values appear in the same place on every page

In the template, one line of PHP fetches the value:

<?php echo esc_html( get_field( 'phone' ) ); ?>

esc_html() belongs there because, according to the documentation, ACF does not escape values loaded with get_field() itself.

When you don't need ACF

My rule of thumb: if the same kind of content appears several times and should look the same everywhere, a field is worth it. For a single, freely designed page the block editor is enough, and for one single value a built-in custom field often is too.

Every plugin your templates depend on is also a dependency. If you deactivate ACF, the data stays in place, but according to the vendor templates using get_field() stop working because the function no longer exists.

ACF free or ACF PRO

The free version is enough as long as each field appears once. If an entry needs any number of rows, or editors should assemble pages from fixed building blocks, you need ACF PRO. It adds:

FeatureWhat for
Repeaterrepeat fields, such as several contact people
Flexible Contentassemble pages from fixed layouts
ACF Blocksbuild custom blocks in PHP
Options Pagescentral values, for the footer, say
Gallerymanage image collections
Clonereuse fields and groups

ACF PRO is a plugin of its own, the free version does not have to be installed as well, and according to the vendor no data is lost when you upgrade. The licence runs per year: 49 US dollars for one website, 149 for ten, 249 for any number, excluding tax (pricing page on 6 November 2026). Development and staging sites do not count.

If the licence expires, fields and content stay usable, but according to the vendor you can no longer create new PRO fields, and updates end with the licence. I would not underestimate that: ACF 6.8.10 and 6.8.11 alone contain 19 security fixes between them.

Only download ACF PRO from the vendor. Search results also show copies on third-party GitHub accounts. They come without a licence key and so without regular updates, and you don't know what is in the files.

ACF or Secure Custom Fields: the decision guide

The official directory now lists two separate plugins:

  • Advanced Custom Fields (ACF®): WP Engine is listed as the author, the current version is 6.8.11 from 2 November 2026, active on over 2 million websites according to the directory. The PRO features require a licence.
  • Secure Custom Fields (SCF): WordPress.org is listed as the author, the current version is 6.9.8 from 3 November 2026, active on over 100,000 websites. According to the documentation, Repeater, Flexible Content, Gallery and Clone are among its field types, and there is no paid version.
Your situationMy recommendation
ACF PRO with a valid licenceStay with it, switching gains you nothing.
Free ACF, nothing missingStay with it and keep it up to date.
New project, Repeater needed, no licencePut SCF on your shortlist and check first that your theme and extensions run with it.
Theme or page builder requires ACFAsk the vendor first. SCF switches ACF off on installation.
SCF runs without anyone having decided thatNot an emergency as long as updates arrive. Still make a conscious decision.

What this means for your website:

  1. Check which plugin is installed. The plugin list in your WordPress admin shows the author next to the name. "Advanced Custom Fields" by WP Engine is the original, "Secure Custom Fields" by WordPress.org is the fork. Sites that updated automatically in October 2024 may still be running SCF without anyone noticing.
  2. Run only one of the two. According to its directory description, SCF deactivates ACF and ACF PRO on installation to avoid code conflicts.
  3. Keep your chosen plugin up to date and test first. According to the changelog, ACF 6.8.11 contains twelve security fixes, and SCF 6.9.8 follows suit. Two of them can visibly change a website: the [acf] shortcode and block bindings now output only the ID for User fields, and fields added with JavaScript are no longer saved unless a filter allows them. The order in which to update is in the guide Installing WordPress updates the right way.
  4. Test a switch first. If you want to move from SCF back to ACF or the other way round, try it on a staging copy first and then check the fields on your most important pages.

If you'd rather not follow developments like this yourself: that is part of my WordPress support. I test plugin updates on a staging environment before rolling them out instead of letting them run automatically. ACF is also one of the tools I build websites with, on request on behalf of agencies: WordPress development for agencies.

What happened in October 2024

On 12 October 2024, the ACF team reported that WordPress.org had taken over the plugin's listing (statement on advancedcustomfields.com). A modified version called "Secure Custom Fields" was delivered under ACF's address. Matt Mullenweg had initiated this without the consent of the ACF team, which has developed the plugin since 2011.

As a result, sites updating the free version of ACF via WordPress.org suddenly received code that the ACF team was no longer responsible for. WP Engine stated at the time that ACF PRO customers and WP Engine and Flywheel hosting customers were not affected. Everyone else was advised to download version 6.3.8 once from advancedcustomfields.com to get updates from the original again. That workaround was necessary as long as ACF could not be distributed through WordPress.org.

The ACF listing was handed back to WP Engine in December 2024 following a preliminary injunction by a US court, as reported by WP Tavern, among others. SCF has been a separate plugin at its own address since November 2024.

Why the case mattered to the community

The WordPress ecosystem relies on developers distributing their plugins through the official directory and keeping control of their code there. Taking over an actively maintained plugin without its developers' consent was unprecedented. Many called it a "hostile takeover", some even a kind of supply-chain attack, because users received a different plugin via an update than the one they had installed.

For developers who build sites with ACF, it was a practical problem: ACF is part of many themes and custom solutions. Anyone who didn't know which version ran on which client site had to check.

What remains

The lawsuit continues. On 24 September 2026 the US court allowed WP Engine's antitrust claims to proceed, and a jury trial is set for 19 October 2027 (The Repository). For your website this changes nothing at the moment, both plugins receive updates.

The case showed that for important plugins you should know where the updates come from. Automatic updates are convenient, but for plugins an entire website depends on, a quick check before installing them pays off. That is part of proper WordPress maintenance and applies regardless of ACF.

Frequently asked questions

Who maintains Advanced Custom Fields now?

WP Engine. The plugin directory lists WP Engine as the author, and since December 2024 updates have again come directly through WordPress.org. Secure Custom Fields is a separate plugin with WordPress.org listed as its author.

Is ACF free?

The base version is, it is free in the plugin directory. According to its pricing page, ACF PRO starts at 49 US dollars a year for one website (as of 6 November 2026, excluding tax). Secure Custom Fields is free as well.

What is ACF PRO?

The paid version of ACF. It adds Repeater, Flexible Content, ACF Blocks, Options Pages, Gallery and Clone. ACF PRO is a standalone plugin, the free version does not have to be installed as well.

What happens if I deactivate ACF?

According to the vendor the data stays in place, and you can pick up where you left off after reinstalling. If your theme calls get_field() or the_field(), though, those functions no longer exist. The website then stops working properly, often with the critical error message.

Does ACF work with the block editor?

Yes. The fields sit next to or below the content in the editor. Building your own blocks with ACF Blocks requires ACF PRO.

Can I run ACF and Secure Custom Fields at the same time?

No. According to its directory description, Secure Custom Fields deactivates ACF and ACF PRO on installation to avoid code conflicts.