
Advanced Custom Fields is the plugin that quietly powers a huge share of custom WordPress builds, and the free-versus-Pro question is one of the most common decisions a developer or site owner makes. The short answer: free ACF is genuinely complete for static custom fields, and you reach for Pro the moment you need repeating or variable-length content, or a global settings screen. But in 2026 there's a wrinkle nobody could have predicted two years ago — "free ACF" is now ambiguous, and you need to know why before you install anything.
In October 2024, during the legal dispute between WP Engine (which owns ACF) and Automattic, WordPress.org invoked guideline 18 of its plugin directory rules and took over the advanced-custom-fields plugin slug. It forked the code into a new plugin called Secure Custom Fields (SCF), positioned as a free, drop-in replacement.
This matters practically. If you go to WordPress.org today and search "Advanced Custom Fields," the listing you find is Secure Custom Fields — not the official ACF maintained by WP Engine. The genuine free ACF now ships primarily from advancedcustomfields.com and is auto-updated by the ACF team's own update server when you have it installed.
So in 2026, "free ACF" can mean one of two different code lineages:
wp scf json commands, integration hooks for newer WordPress APIs).For new sites, either free option will give you the same field-building experience. SCF is the path of least resistance if you only ever want free, never want Pro, and prefer something installed directly from the .org directory. If you anticipate upgrading to Pro, or you want to stay on the lineage that most third-party add-ons and documentation target, install official ACF from the source site. The two are functionally compatible at the data level — fields are stored as standard post meta — but don't run both at once, and migrating from SCF to ACF Pro is cleaner than the reverse.
People underestimate free ACF. It is not a crippled demo. The free version includes the entire library of basic and content fields you need for the vast majority of custom builds:
That list covers an enormous range of real work: a custom "Team Member" post type with a photo, role, bio, and social links; a landing page with a few selectable hero variations; an event with a date, location map, and related sessions pulled via a Relationship field. None of that needs Pro.
Pro is not "free plus polish." It's a specific, well-defined set of features that solve specific problems. Here's the real boundary:
The single most-cited reason people buy Pro. The Repeater lets editors add an unlimited, ordered list of sub-rows — think FAQ items, pricing tiers, a list of stats, gallery captions, a timeline. In free ACF you'd have to fake this with a numbered set of Group fields ("Feature 1," "Feature 2," "Feature 3"), which is rigid and miserable to maintain. If your content has the word "add another" anywhere in the spec, you need Repeater.
The Repeater's more powerful sibling, and the backbone of most custom page builders built on ACF. Flexible Content lets you define multiple layouts (a text block, an image-and-text block, a CTA, a testimonial carousel) and let editors stack them in any order. This is how agencies build genuinely flexible page templates without Gutenberg or a third-party builder. It's a Pro-only feature, full stop.
A proper multi-image field with drag-to-reorder and bulk add from the media library. Free has a single Image field; Gallery is the curated set.
Lets you reuse an existing field or whole field group inside another, keeping your definitions DRY. Invaluable on larger sites where the same "address" or "SEO override" block appears in five places.
Via acf_add_options_page(), Pro lets you create global, non-post settings screens — a place to store the site phone number, footer text, default social links, or a global announcement bar. Without Pro there's no native home for "site-wide" custom data, and bolting it onto a hidden post is a hack you'll regret.
Pro lets you register native Gutenberg blocks backed by ACF fields and rendered with a PHP template instead of React. For teams comfortable in PHP who want first-class blocks in the block editor, this is a far gentler path than learning the full block-development toolchain.
Ask one question: does the content repeat or vary in length, or do you need site-wide settings?
ACF Pro is sold as an annual license with three tiers based on the number of sites you can activate it on: a single-site tier, a roughly ten-site tier, and an unlimited tier. The license includes a year of updates and support; let it lapse and the plugin keeps working, but you stop receiving updates until you renew. New-customer discounts are frequently available, so check the official pricing page for the current numbers rather than trusting a figure quoted in any blog post, including this one — ACF has changed its pricing model more than once.
For a single client site, Pro is one of the highest-value-per-dollar purchases in the WordPress ecosystem; the Repeater and Flexible Content fields alone routinely save days of bespoke development. For an agency running many sites, the multi-site and unlimited tiers make the per-site cost negligible.
Free ACF and SCF are not lesser tools to be tolerated until you can afford Pro — they're the correct, complete answer for static custom fields, and plenty of professional sites never need more. Pro isn't an upsell trick; it's a clean, well-drawn line around repeating content, flexible page layouts, and global settings. Decide based on the shape of your content, not on fear of missing out. And in 2026, just be deliberate about which "free" you install — the SCF fork and the official free ACF will both serve you well, but knowing which lineage you're on saves confusion later.
Site
Tools
We do not sell your email. We do not spam.
© 2026 RevealTheme. All rights reserved.