Advanced Custom Fields (ACF) in 2026: When to Use It, When to Skip It

Advanced Custom Fields is either the most useful WordPress plugin ever built, or an over-engineered crutch that turns simple sites into unmaintainable spaghetti. Depends who you ask. Here’s when I use it, when I don’t, and what the WP Engine acquisition actually means for your project in 2026.

What ACF Actually Does

ACF lets you add custom fields to any post type, page, taxonomy, user, or options page — without writing PHP. You define a field (text, image, repeater, relationship, etc.), assign it to a post type, and it appears in the editor. On the frontend you fetch the value with get_field().

That’s it. It’s a UI wrapper around WordPress’s built-in post_meta table.

When ACF Is the Right Tool

1. Portfolio / case study sites. Structured data like “Client Name”, “Project Duration”, “Tech Stack”, “Live URL” — perfect for ACF fields on a custom post type.
2. Team / staff pages. Name, role, bio, photo, social links per person. Cleaner than pasting into the editor.
3. Complex product data (beyond WooCommerce). Real estate listings, cars, event tickets — anything with structured attributes.
4. Landing page templates for marketers. Instead of teaching them Elementor, give them a template with 8 fields and let them fill in the blanks.
5. Site-wide options. ACF Options Pages let you build a proper theme settings panel in 20 minutes.

When ACF Is the Wrong Tool

1. Simple blogs. If you have a title, featured image, and body content — you don’t need ACF. Native Gutenberg is fine.
2. Sites where the client will edit layout. If they want to move things around, use Gutenberg blocks or Elementor. ACF fields are rigid.
3. Sites you’ll hand off to another developer who doesn’t know ACF. They’ll have to relearn your custom field structure. Native code is more portable.
4. Simple contact forms. Use a form plugin. ACF isn’t a form builder.

Free vs Pro (2026 Pricing)

Free gives you: text, textarea, image, file, WYSIWYG, select, radio, checkbox, true/false, relationship, post object, page link, taxonomy, user, date, color picker. That covers 80% of real projects.

Pro ($49/year single site, $149/year unlimited) adds: Repeater, Flexible Content, Gallery, Clone, Options Pages, and Blocks (turns ACF fields into Gutenberg blocks).

Repeater alone is worth Pro. Every real project needs a repeater eventually — testimonials list, FAQ list, service list, team roster.

The WP Engine Acquisition Drama

Delicious Brains sold ACF to WP Engine in 2022. In late 2024, Automattic (WordPress.org’s controller) forked ACF into “Secure Custom Fields” and removed the original ACF plugin from the WordPress.org repository during a public dispute with WP Engine.

What this means for you in 2026:

• ACF Pro (paid) is unaffected — you update directly from WP Engine.
• ACF Free is still maintained by WP Engine but you install it from their site, not WordPress.org.
• Secure Custom Fields (SCF) is the WP.org fork. It’s compatible with existing ACF field groups but is diverging over time.

For new projects in 2026: if you’re already paying for ACF Pro, keep using it. If you were on ACF Free and want to stay on the WordPress.org repository for auto-updates, migrate to SCF — it’s a one-click swap right now.

Performance Considerations

ACF stores every field as a row in wp_postmeta. Every get_field() call is a database query unless cached. On sites with lots of fields per post, this adds up.

Mitigations:

• Use get_fields() once at the top of your template — it fetches everything in one query.
• Enable object cache (Redis). ACF caches heavily when object cache is available.
• Don’t use relationship or post_object fields with hundreds of options — the admin dropdown becomes slow.

ACF + Elementor

The combination is powerful. Create ACF fields, then use Elementor’s Dynamic Tags to display them in any widget. This is how you build editable landing pages without teaching clients how to use Elementor’s editor.

ACF + Gutenberg Blocks

ACF Pro’s Blocks feature lets you build custom Gutenberg blocks with a PHP template and ACF fields for the settings. Much faster than writing React. I use this for client sites that want Gutenberg but need custom blocks.

The Honest Verdict

ACF Pro is one of the two or three plugins I install on almost every custom build. It saves days of work per project and produces cleaner, more maintainable sites than trying to force everything into Gutenberg or Elementor.

But don’t reach for it on a simple blog. Use the right tool for the job.

Building something that needs structured content? Let’s discuss the right architecture.