ACF is the most widely used custom content plugin in WordPress, with the cleanest admin UI in the category, the largest third-party ecosystem, and deep native Gutenberg block support. The main weakness is pricing: it dropped its lifetime license entirely a few years back and now charges $249/year for unlimited sites. For teams that can justify the annual cost, it remains a strong and well-supported tool.
- Overall rating: 3.7 / 5
- Features: 3.8
- Ease of use: 4.5
- Support: 4
- Performance: 3.5
- Pricing: 2.5
Years ago, someone in the Oxygen Builder community announced that ACF was going to end the lifetime deal, which was then costing around $60. I skipped it. I still think about that sometimes.
Fast forward to today: ACF no longer offers a lifetime license at any price. What was available for $60 a few years ago now costs $249 every year with no exit option. That shift changed how I talk about ACF when someone asks whether to buy it.
I have been inside ACF on client sites regularly. Maintaining builds, creating field groups, navigating settings, and understanding what it can and cannot do. It is, without question, the most commonly installed custom fields plugin you will find when taking over a WordPress project. It is also the most polished and the most connected to the broader WordPress ecosystem.
This review covers where that reputation is earned and where the gaps are.
Key Highlights
- ACF has the cleanest, most polished admin UI in the custom fields category. Field group creation, conditional logic, and settings navigation are all more intuitive than most other alternatives out of the box
- ACF has more third-party integrations and add-ons than any competing tool in this category. If a feature is missing from core ACF, a third-party solution almost certainly exists
- Developers use ACF as a foundation for building their own WordPress plugins, not just for adding fields to sites. Advanced Themer, a well-regarded plugin in the Bricks Builder ecosystem, is built on ACF
- ACF changed its bundling policy approximately one year ago: developers who ship plugins or themes with ACF included can no longer allow end users to use ACF’s field creation features without their own separate ACF license
- ACF dropped its lifetime license entirely. The unlimited agency plan is now $249/year with no one-time payment option. After the WP Engine acquisition, existing LTD holders reportedly faced a potential move to subscriptions, but community pressure reversed that decision, and LTDs were honored
- ACF writes two rows per populated custom field in
wp_postmeta: one for the value and one for its reference key. Meta Box’s custom table extension bypasses this entirely. On large builds, that architectural gap matters
What is ACF & Who is it Built For?
ACF (Advanced Custom Fields) is a custom fields plugin with 30+ field types, a polished admin interface, and native PHP-based Gutenberg block support. It is built for developers of all experience levels, from beginners who want a clean field management interface to experienced developers who use it as the structural foundation for building their own WordPress plugins and commercial themes.
ACF is the Elementor of custom fields plugins. It got to market first, built the largest community, and has the most resources, tutorials, and third-party products built around it. If you want the deepest bench of outside support for any custom fields decision, ACF has it.
Read the full ACF vs Meta Box comparison and ACF vs ACPT comparison if you are evaluating all three tools side by side.
What Does ACF Do Well?
ACF’s strongest areas are its admin UI, third-party ecosystem, and Gutenberg block development. It has the cleanest field management interface in the category, more third-party integrations than any competing tool, and an ACF Blocks system that lets PHP developers build custom Gutenberg block types without React or JavaScript.
The Cleanest Admin UI in The Category
This is the area where ACF is genuinely ahead of the competition. Field group creation is clean and well-organized. Conditional logic is presented clearly. The settings navigation does not feel buried or overwhelming. For developers who maintain client sites and hand them off to non-technical users, the ACF admin experience sets the standard.
Ease of use earns a 4.5/5 in this review, the highest score across all three categories. That is not accidental. ACF has had more years of UI iteration than ACPT, and it shows in how quickly you can navigate from a field group to its settings and back.
Third-Party Ecosystem & Integrations
ACF has more third-party integrations and addons than any other custom fields plugin. Page builders, form plugins, query tools, admin column plugins, and import/export utilities all list ACF compatibility as a priority.
The ecosystem extends into plugin development itself. Developers use ACF as a structural base to build their own plugins instead of writing custom field handling from scratch. Advanced Themer, a well-regarded plugin in the Bricks Builder community, is built on ACF. There are courses on Udemy specifically teaching WordPress plugin development using ACF as the foundation. This depth of integration and developer trust is something Meta Box and ACPT have not yet matched.
If a feature is missing from ACF’s core, a third-party addon almost certainly exists. That is the practical value of the ecosystem: you are rarely stuck.
Gutenberg Block Development with ACF Blocks
ACF Blocks allows PHP developers to build custom Gutenberg block types using standard template files, with no React or JavaScript required. This has been available since ACF 5.8 and is widely regarded by the community as one of the cleanest PHP-based block development workflows in WordPress. Based on what developers consistently report, ACF Blocks reduces the barrier to custom block creation significantly for teams that work primarily in PHP.
I have not used ACF Blocks personally, so the above reflects community consensus rather than direct experience. For a no-code alternative that builds on top of ACF fields, DPlugin’s Gutenberg Studio offers a visual block-building interface that connects directly to your ACF field groups.
Where Does ACF Fall Short?
ACF’s main weaknesses are its annual-only pricing with no lifetime exit, moderate database performance compared to Meta Box’s custom table architecture, and a recent policy change that affects how developers can bundle and ship ACF with their own products. These are meaningful factors for agencies, freelancers, and plugin developers evaluating long-term tool costs.
No Lifetime License & Annual-Only Pricing
This is where ACF scores lowest in this review: 2.5/5 on pricing.
ACF’s unlimited agency plan is $249/year with no one-time alternative. For agencies that build client sites and then move on without maintaining the license, that is a recurring cost that never stops. You are paying for a tool even on projects you finished two years ago.
Years ago I had the chance to pick up ACF’s lifetime deal for around $60. I did not take it and I have thought about it since. Now that deal is gone entirely. The lesson I took from it: for infrastructure tools you use on every project, the lifetime option is almost always worth grabbing when it exists. That is why I have Meta Box’s ultimate lifetime bundle instead.
After WP Engine acquired ACF, LTD holders reportedly faced a potential migration to annual subscriptions. Community pushback on social media reversed that decision and existing LTDs were confirmed to be honored. That episode highlighted how dependent long-term users are on a licensing decision they have no control over, and it contributed to why many agencies now prioritize lifetime options when evaluating new tools.
Database Storage Performance at Scale
ACF stores two rows per populated custom field in WordPress’s wp_postmeta table: one for the field value and one for the ACF reference key. It also writes empty rows for unpopulated fields, which adds bulk over time. On pages with many active fields, this compounding row count creates JOIN query overhead that increases Time to First Byte and database CPU load.
Meta Box handles this more efficiently by default, and its MB Custom Table extension bypasses wp_postmeta entirely. For large directories, catalogs, or any site with high post volumes and dense custom data, the architectural difference produces measurable performance differences. ACF can address this with a third-party plugin, but the solution is not native.
A note that applies to all custom fields plugins: PHP’s default max_input_vars limit of 1000 can silently block fields from saving when a large number of fields are active. This is a server and PHP limitation, not specific to ACF. Increasing it to 10000 in php.ini resolves it on any large build.
The ACF Bundling Policy Change
Approximately one year ago, ACF updated its licensing policy to close a long-standing loophole. Previously, if a plugin or theme bundled ACF as a dependency, the end user of that product could access ACF’s field creation features without a separate ACF license. That is no longer permitted.
Under the updated policy, developers who ship products with ACF included must ensure their users hold their own ACF licenses to use field management features. Many ThemeForest themes and commercial plugins built on ACF previously shipped with this understanding. That model has changed.
For most site builders using ACF directly, this does not affect day-to-day use. For plugin developers who ship products that extend or rely on ACF, the licensing structure now requires more careful planning. Worth knowing before you build a product or client workflow that depends on ACF as a bundled dependency.
How Does ACF Compare to Meta Box & ACPT?
ACF leads on UI polish, community resources, and Gutenberg block development. Meta Box leads in database architecture, extension depth, and lifetime licensing value. ACPT leads on pricing and visual setup speed. Your choice depends on project complexity, budget model, and how much you rely on the WordPress developer community for support.
| Factor | ACF Pro | Meta Box | ACPT |
|---|---|---|---|
| Admin UI and polish | Best in category | Clean, updated | Clean, logical |
| Field types | 30+ | 40+ | 30+ |
| Gutenberg block builder | Yes (ACF Blocks) | Yes (MB Blocks) | No |
| Custom database tables | Third-party only | Yes (native) | No |
| Third-party ecosystem | Largest | Large | Small but growing |
| Lifetime unlimited license | Not available | $699 one-time | $199 one-time |
| Bundling policy | Restricted (updated ~2025) | Open | Open |
| Beginner accessibility | High | Moderate | High |
(Full breakdowns: ACF vs Meta Box, ACF vs ACPT, Meta Box vs ACPT)
What Does ACF Pro Cost?
ACF Pro starts at $49/year for one site and $249/year for unlimited sites. There is no lifetime option at any tier. ACF Free is available on the WordPress plugin directory and covers basic custom fields. The Pro license unlocks repeater fields, flexible content, options pages, ACF Blocks, gallery fields, and clone fields.
One important note: always install ACF from advancedcustomfields.com or via the WordPress plugin directory under the advanced-custom-fields slug. Avoid the “Secure Custom Fields” (SCF) fork that WordPress.org maintains separately. The two codebases are diverging, and SCF’s long-term roadmap is less certain than ACF’s.
| Plan | Cost | Sites |
|---|---|---|
| ACF Free | Free | Unlimited (basic fields only) |
| Personal (annual) | $49/year | 1 |
| Freelancer (annual) | $149/year | 10 |
| Agency (annual) | $249/year | Unlimited |
| Lifetime option | Not available | — |
Is ACF Worth It?
For the right use case, yes. ACF earns 3.7/5 overall: strong on ease of use, support, and ecosystem; pulled down by the annual-only pricing model. For teams that need Gutenberg block development, the cleanest admin experience in the category, or the widest third-party compatibility, ACF earns its place.
For cost-sensitive agencies building at volume, the lifetime alternatives are now impossible to ignore.
| Area | Rating | Notes |
|---|---|---|
| Features | 3.8 / 5 | Solid but fewer field types than Meta Box. No custom DB tables natively |
| Ease of use | 4.5 / 5 | Best admin UI in the category. Clean and polished throughout |
| Support | 4 / 5 | Largest community, most tutorials, most third-party documentation |
| Performance | 3.5 / 5 | Double-row postmeta storage limits performance at scale |
| Pricing | 2.5 / 5 | Annual-only, no lifetime, and recurring cost regardless of active use |
Overall: 3.7 / 5
The case for ACF:
- Best admin UI and onboarding experience in the category
- Largest third-party ecosystem and integration library
- Native PHP-based Gutenberg block development via ACF Blocks
- Developers use it as a base to build their own plugins and commercial products
- Most recognized and documented custom fields plugin in WordPress
The case against ACF:
- No lifetime license at any price point
- $249/year continues billing even after client projects end
- Double-row postmeta storage limits performance on large builds
- Bundling policy change affects plugin developers who ship with ACF
- Fewer field types than Meta Box; no native custom database table support
FAQs About ACF
ACF is the most widely recognized custom fields plugin in WordPress. The questions below cover the post-controversy status, the bundling policy change, Gutenberg block development, pricing, and how ACF compares to Meta Box and ACPT for different build types.
Is ACF still safe to use after the WP Engine vs Automattic dispute?
Yes. The dispute between WP Engine and Automattic was resolved through a court injunction in December 2024, restoring WP Engine’s control of the plugin.
ACF continues to receive active development and updates from the WP Engine team. Always install from advancedcustomfields.com or via the advanced-custom-fields plugin directory slug.
Avoid the Secure Custom Fields (SCF) fork maintained separately by WordPress.org, as the two codebases are diverging and SCF’s long-term roadmap is uncertain.
What changed with ACF’s bundling policy?
Approximately one year ago, ACF updated its licensing terms to close a loophole that previously allowed end users of bundled products to access ACF field-creation features without their own licenses.
Under the current policy, if a plugin or theme ships with ACF as a dependency, end users of that product must hold their own ACF license to use field management features.
his primarily affects ThemeForest themes and plugin developers who built products on ACF. Standard site builders using ACF directly are not affected.
Is ACF Free enough, or do I need ACF Pro?
ACF Free handles basic custom field types: text, textarea, image, file, select, checkbox, and a few others. It is sufficient for simple custom-field needs on smaller sites.
ACF Pro adds the features that make it genuinely powerful: Repeater fields, Flexible Content, Options Pages, ACF Blocks for Gutenberg development, Gallery fields, and Clone fields.
For any professional build, ACF Pro is the product you need. Start with the personal plan at $49/year and upgrade if the project scale requires it.
How does ACF compare to Meta Box for performance?
Meta Box performs better at scale. ACF writes two rows per custom field in wp_postmeta, which compounds into a significant query load on pages with large numbers of fields.
Meta Box writes one row and can move data into dedicated SQL tables entirely. For small to mid-size sites, the difference is not noticeable. For large directories, product catalogs, or sites with thousands of posts and complex custom data, Meta Box’s architecture is measurably faster.
Read the ACF vs Meta Box comparison for the full database breakdown.
Should I choose ACF or Meta Box for a new WordPress project?
ACF is the right choice when Gutenberg block development is central, the site needs a clean handoff to teams familiar with ACF’s API, or the project inherits an existing ACF structure.
Meta Box is the right choice when database performance matters, the project is data-heavy, or an agency wants to eliminate recurring license costs through the $699 lifetime unlimited bundle.
The ecosystem advantage ACF holds is real, but for most new builds, the long-term pricing math increasingly favors Meta Box. Read the full Meta Box review and ACPT review alongside this one before deciding.
Conclusion
ACF is still a serious, capable tool. The UI is the best in the category. The ecosystem is unmatched. The Gutenberg block workflow is trusted by a large portion of the WordPress developer community. None of that has changed.
What has changed is the pricing model and the bundling policy. An annual fee that never stops, on a tool you may only actively need for the duration of a client project, is a real ongoing cost. The bundling change affects a specific segment of developers, but is worth understanding before you build anything on top of ACF.
My honest view: ACF is the one tool in this category whose ecosystem advantage is still meaningful enough to justify the annual cost for the right type of team. For Gutenberg-heavy editorial builds, agency handoffs, and developer education, it is hard to replace. For everything else, the alternatives have caught up on features and left ACF behind on lifetime value.
I skipped that $60 lifetime deal years ago. I have Meta Box now and do not regret it. But I also understand why ACF is still the first name most developers reach for.
If you want your WordPress project built with the right custom content architecture from the start, our WordPress support handles custom fields setup, database performance, server configuration, and client handover documentation.
For WordPress developers and agencies in India and Kolkata: if recurring plugin costs are compressing your project margins, we help teams in Kolkata and across India build cost-effective, well-structured WordPress setups with the right tools for each project. Get in touch with SyncWin to talk through your next build.
