Advanced Custom Fields is the closest thing WordPress has to a default answer for "I need to attach structured data to a post and render it in a template." After running both editions across client work for years, the free-versus-Pro question is less about field types than most people assume and more about two things: whether your content has repeating structure, and how comfortable you are with the licensing landscape after the 2024 fork. Here is the honest breakdown.

What free ACF actually covers

The free plugin is not a crippled demo. It ships the field engine, the local JSON sync, the location-rules system, and most of the field types you reach for daily: Text, Textarea, WYSIWYG, Number, Email, URL, Image, File, Select, Checkbox, Radio, True/False, Date Picker, Color Picker, Google Map, Post Object, Page Link, Relationship, Taxonomy, and User. You can build a fully custom editorial experience entirely on free ACF as long as every field is a single instance per location.

A portfolio where each project carries a client name, a role, a year, a hero image, and an external URL? Free. A custom post type for "Properties" with price, bedrooms, square footage, and an address map? Free. The free tier comfortably powers a surprising amount of real custom development, and for a brochure site or a simple CPT-driven directory you may never hit a wall.

The four features that are genuinely Pro-only

People remember "Repeater is Pro" and forget the rest. The complete list of meaningful paywalled features is:

Repeater — a variable number of the same sub-field group. Team members, FAQ rows, spec tables, timeline entries.
Flexible Content — Repeater's bigger sibling, where each row can be a different layout the editor picks from a menu. This is, functionally, a section builder.
ACF Blocks — register native Gutenberg blocks whose edit UI is an ACF field group and whose output is a PHP render template.
Gallery, Clone, and Options Pages — the Gallery field (multi-image with reordering), the Clone field (reuse a field group inside another), and ACF Options Pages (site-wide settings not tied to any post) are also Pro. These get forgotten but they matter: theme-wide footer settings live on an Options Page, and Clone is what keeps large field schemas DRY.

Everything else is free. So the real upgrade trigger is almost always one specific need: repeating content the site owner will edit themselves.

The Repeater vs. custom-post-type fork in the road

When you hit repeating data on free ACF, you have two escape hatches, and neither is great. You can create numbered fields (member_1_name, member_2_name…), which caps growth and looks horrible in the editor. Or you spin up a dedicated custom post type and query it. The CPT route is actually more scalable and is the right call when the items are first-class content with their own URLs (think real estate listings or staff bios that need individual pages). But it's overkill for a block of three testimonials that only ever appear on the homepage. Repeater exists precisely for that middle ground: inline, ordered, editor-friendly lists that don't deserve their own post type. If you find yourself reaching for a CPT purely to fake a Repeater, that's your signal to upgrade.

What three years of upgrade decisions look like

The pattern is remarkably consistent. Sites that start on free ACF and later pay for Pro almost never cite "we wanted Flexible Content" or "we needed ACF Blocks." The upgrade is triggered by a content editor asking to add a fourth team member, or a fifth FAQ, and the developer realising the numbered-field hack has run out of road. Repeater is the gateway feature; the rest of Pro is gravy you discover afterward.

The reverse almost never happens. Nobody downgrades Pro to free, because Repeater and Flexible Content store their data as serialized meta keyed by index, and free ACF cannot read or edit those structures. Removing Pro means rebuilding every page that used those fields by hand. That asymmetry is worth understanding before you commit: Pro is a one-way door for any non-trivial content model.

Pricing in 2026, and why the old "$249" number is misleading

ACF Pro is licensed annually with three tiers: Personal at $49/yr for one site, Freelancer at $149/yr for ten sites, and Agency at $249/yr for unlimited sites. A lot of older write-ups quote $249 as if that's the price of admission — it isn't. For a single project the cost is $49 a year, which is roughly fifteen minutes of billable developer time. Against that, Repeater alone saves hours on any list-heavy build. The license also follows the standard premium-plugin model: let it lapse and the plugin keeps running on its last installed version, but you stop receiving updates. ACF is security-sensitive (it touches meta and admin UI), so running an unmaintained copy for years is a genuine, if slow-moving, liability rather than a free ride.

The fork you can't ignore: Secure Custom Fields

This is the piece every pre-2024 comparison is missing, and it changes the calculus. In October 2024, during the Automattic–WP Engine dispute, WordPress.org took over the ACF plugin's listing and shipped a fork called Secure Custom Fields (SCF), stripping out the Pro upsells and patching a vulnerability. A court injunction later forced control of the original ACF listing back toward WP Engine, but the practical fallout persists: sites that auto-updated during that window may have silently swapped ACF for SCF, and the two are now diverging codebases.

What this means in practice:

SCF is a real, maintained free alternative for the core (non-Repeater) feature set, available on WordPress.org. If you only ever needed free ACF's capabilities, SCF is a legitimate option with no WP Engine dependency.
Check what's actually installed. On sites you inherited or that auto-update unattended, verify whether the active plugin is ACF or SCF before assuming. They share field data formats today, but feature parity is not guaranteed going forward.
Pro still comes only from WP Engine. There is no "SCF Pro." Repeater, Flexible Content, Blocks, Gallery, Clone, and Options Pages remain exclusively in the paid ACF Pro distributed by WP Engine. The fork did not democratise the paywalled features — it forked the free tier.

So the modern decision tree has a third branch. It's no longer just "free ACF or Pro ACF." For genuinely simple sites you can now sit on SCF and skip the WP Engine relationship entirely. The moment you need Repeater-class structure, you're back to ACF Pro and its annual license, fork or no fork.

The recommendation

Start on the free tier — ACF or SCF, depending on your appetite for the licensing situation — whenever your content model is flat and every field is a single instance. Plan to buy ACF Pro the day a content editor needs to manage a repeating list themselves, and buy the correct tier ($49 for a one-off, $149 if you run a handful of client sites) rather than defaulting to the $249 figure floating around old blog posts. Treat the move to Repeater and Flexible Content as a deliberate architectural commitment, because the data structures it creates are effectively permanent. And whatever you build, document whether the install is ACF or SCF in your project notes — after 2024, that's no longer a detail you can take for granted.

Advanced Custom Fields: Free vs Pro After Three Years