ACF is the more established choice with 30+ field types, native Gutenberg block support, and the largest WordPress developer community behind it. ACPT is the faster, more visual option built for agencies and users who want custom post type management without writing code. Your choice comes down to team skill level, project complexity, and long-term licensing cost.
I run Meta Box on every project I own, personal or client. That is my default. But when it comes to the wider WordPress market, the two names that dominate the same conversation are ACF and ACPT. Both solve the same core problem. How they solve it, at what cost, and with what long-term commitment differs enough to matter.
The 2024 legal dispute between WP Engine and Automattic pulled ACF into a conflict it had nothing to do with. WordPress.org temporarily took over the plugin’s repository, renamed it Secure Custom Fields, and unlocked Pro features for free.
Millions of people had built sites on ACF long before any of that happened, and none of them should have been caught in the middle of someone else’s corporate fight.
A court injunction restored WP Engine’s control in December 2024, and ACF is back on the right track. But the incident reshaped how a lot of agencies now think about plugin dependency. That context belongs in this comparison.
Here is the honest breakdown.
Key Highlights
- ACF Pro writes two database rows per populated custom field: one for the value and one for the reference key. A page with 30 fields generates 60 rows in
wp_postmeta - ACPT writes one database row per populated custom field in the
wp_postmeta, which consolidates field values into fewer rows as compared to ACF - ACF Pro removed its lifetime license entirely. The unlimited agency plan is $249/year with no one-time exit option
- ACPT’s lifetime unlimited plan is $199 one-time, one of the lowest entry points in this category
- 64% of Google searches now end without a click. Structured output from your custom fields affects how often your site gets cited in AI-generated answers
- Pages with FAQPage schema are 3.2x more likely to appear in Google AI Overviews. Both ACF and ACPT support schema output through Rank Math and Yoast
What is The Difference Between ACF & ACPT?
ACF (Advanced Custom Fields) is a custom fields plugin that handles custom post types and taxonomies from version 6.0 onwards. ACPT (Advanced Custom Post Types) is a visual, all-in-one builder designed around custom post type management, with fields, taxonomies, front-end templates, and a form builder bundled into a single interface. ACF is developer-first. ACPT is visual-first.
This distinction shapes everything downstream: how data is stored, what the admin experience looks like, how well each tool works with specific page builders, and which type of project each is actually suited for.
How Do ACF & ACPT Compare on Features?
ACF has a larger field library and the deepest Gutenberg integration in the category through its native PHP block builder. ACPT matches it on standard fields, adds a visual drag-and-drop template builder, and includes a front-end form builder without needing a separate plugin. Both support conditional logic, repeater fields, relational fields, REST API, and WP GraphQL.
| Feature | ACF Pro | ACPT |
|---|---|---|
| Field types | 30+ | 30+ |
| Custom post types and taxonomies | Yes (from v6.0) | Yes (core function) |
| Native Gutenberg block builder | Yes (PHP-based ACF Blocks) | No |
| Visual template builder | No | Yes (drag-and-drop) |
| Front-end form builder | Limited (acf_form()) | Yes (native visual builder) |
| Conditional logic | Yes | Yes |
| Relational fields | Yes | Yes |
| REST API and WP GraphQL | Yes | Yes |
| Local JSON (version control) | Yes | No |
| WooCommerce integration | Yes | Yes |
| WPML support | Yes | Yes |
| Rank Math and Yoast integration | Yes | Yes |
How Does Each Plugin Handle Database Storage?
ACF Pro stores all custom field data in WordPress’s default wp_postmeta table. Each populated field writes two rows: one for the value and one for the ACF field key reference. ACF also writes empty rows when fields are left blank, which adds table bulk over time. Retrieving multiple fields on a single template requires JOIN operations, and those compound into real CPU load on pages with complex data structures.
ACPT also stores data in WordPress’s default wp_postmeta table. Each populated field writes one indexable row, which matches Meta Box’s default behavior and is better than ACF Pro. But it cannot move data to dedicated tables, which limits its scalability on sites with large field sets or high traffic volumes.
For a standard marketing site or simple portfolio, postmeta storage is not a bottleneck. For a directory, a product catalog, or any site exceeding a few thousand posts with dense custom fields, the storage model starts to affect real performance, and in that case,
Meta Box is the best solution out there as it supports custom database tables.
| Database Factor | ACF Pro | ACPT |
|---|---|---|
| Storage location | wp_postmeta (default only) | wp_postmeta (default only) |
| Rows per populated field | 2 (value + reference key) | 1 |
| Empty field rows | Yes, written automatically | Standard behavior |
| Custom table option | Requires a third-party plugin | Not supported yet |
| Performance risk on large sites | Moderate to high | Lower with custom tables active |
What Does ACF Pro Cost Versus ACPT?
ACF Pro starts at $49/year for a single site and $249/year for unlimited sites, with no lifetime option. ACPT starts at $29/year for one site, $99/year for unlimited sites, and offers a lifetime unlimited plan for $199 one-time.
ACF removed its lifetime license years ago. For any agency building more than a handful of client sites per year, the math on ACPT’s lifetime plan breaks even before the second annual ACF renewal.
For agencies in India and Kolkata, where software overhead directly compresses project margins, this is not just a pricing table entry. It is a real business decision.
| Pricing | ACF Pro | ACPT |
|---|---|---|
| Single site (annual) | $49/year | $29/year |
| Unlimited sites (annual) | $249/year | $99/year |
| Lifetime unlimited | Not available | $199 one-time |
| Long-term agency cost model | High (no exit from annual billing) | Low (lifetime pays off before year 3) |
Where Does ACF Make the Most Sense?
ACF is the strongest choice when Gutenberg block development is at the center of the project. The ACF Blocks system lets PHP developers build custom block types without writing React or JavaScript, which cuts development time on editorial and marketing sites that rely on the block editor.
The community advantage is also real. Stack Overflow answers, YouTube tutorials, Facebook groups, and third-party plugin documentation all default to ACF’s API functions. When you hand a project to another developer or a client’s internal team, the chances are higher that someone already knows how get_field() works.
Local JSON is another genuine edge. ACF saves field group definitions as JSON files in your theme directory, which makes version control, deployment, and site-to-site migration significantly cleaner for development teams.
ACF Pro works best for:
- Projects where Gutenberg block development is a core deliverable
- Sites being handed off to teams already familiar with ACF’s API
- Developers who rely on Local JSON for clean deployment workflows
- Complex content architectures with many field groups that need careful synchronization across environments
Where Does ACPT Make the Most Sense?
ACPT is the right choice when visual setup speed and budget are both priorities. The drag-and-drop template builder and integrated form builder remove a significant amount of friction for users who do not want to work in PHP template files. For a solo developer or a small team trying to ship a client project quickly, that matters.
The developer behind ACPT has earned real community trust. The plugin is particularly strong among Bricks Builder and Breakdance users, where its native integrations are solid. Its broader ecosystem is still not as wide as ACF’s across the full range of WordPress tools. That is expected from a newer product, and it is narrowing with each release. It is still worth factoring in if the project involves a complex multi-plugin stack.
The $199 lifetime unlimited license is the sharpest financial argument for ACPT. For agencies building client sites at volume, that number removes recurring overhead entirely.
ACPT works best for:
- Freelancers and small agencies that need a fast visual setup without deep PHP knowledge
- Projects using Bricks Builder or Breakdance as the primary front-end framework
- Directory sites and listings pages that benefit from ACPT’s visual archive template builder
- Budget-first builds, where the lifetime unlimited license eliminates annual software costs
Read the full ACPT showcase on WPnomy for a closer look at its interface and field capabilities.
Which One Should You Actually Choose?
For most WordPress projects, both tools are capable. The decision comes down to three variables: how your team works, what builder you use on the front end, and how much you want to spend over time.
Choose ACF Pro if: Gutenberg block development is central to the project, Local JSON clean deployment matters, or you are working with teams that already know ACF’s functions and API.
Choose ACPT if: Visual setup speed is a priority, Bricks or Breakdance is your builder, or your agency wants to stop paying annual licensing fees for a tool you will use for years.
| Scenario | Recommended tool |
|---|---|
| Gutenberg-heavy editorial or news site | ACF Pro |
| Bricks Builder or Breakdance project | ACPT |
| Team with an existing ACF codebase | ACF Pro |
| Agency building 10+ client sites per year | ACPT (lifetime unlimited) |
| Client handoff to a non-developer team | ACF Pro (larger community) |
| Directory or listings site, visual setup | ACPT |
| Large data catalog needing custom DB tables | ACPT (or Meta Box) |
FAQs About ACF vs ACPT
Is ACF still safe to use after the WP Engine and Automattic dispute?
Yes. A US District Court granted a preliminary injunction in December 2024, requiring Automattic to restore WP Engine’s access and return control of the advanced-custom-fields plugin repository. ACF continues to receive active development from the WP Engine team.
The WordPress.org fork, Secure Custom Fields (SCF), remains in the repository as a separate plugin. Downloading ACF Pro from the official website ensures you are on the official version.
Can ACPT fully replace ACF for most WordPress projects?
For most standard projects, yes. ACPT covers custom post types, taxonomies, 30+ field types, conditional logic, relational fields, REST API, and front-end output.
Where it trails ACF is in Gutenberg block development depth, Local JSON support, and overall ecosystem breadth.
For block-editor-heavy builds or projects with complex developer handoffs, ACF holds its edge. For visual builds on Bricks or Breakdance, ACPT is the stronger practical choice.
Does ACF Pro have a lifetime license option?
No. ACF removed its lifetime license entirely and now operates on annual subscriptions only. The personal plan is $49/year for one site, and the unlimited agency plan is $249/year.
ACPT offers a lifetime unlimited plan for $199 one-time. For agencies building multiple client sites, that gap becomes a real cost argument within the first two years of subscription.
Is ACPT’s single-developer model a risk for long-term production sites?
It is worth weighing for sites you plan to maintain over several years. ACPT is primarily maintained by one developer, which means release cycles can be slower and support can bottleneck during high-demand periods.
The developer has a strong track record, and the WordPress community response has been consistently positive. For builds you own and maintain directly, the risk is manageable.
For sites you plan to hand off entirely with no ongoing involvement, ACF or Meta Box carries less continuity uncertainty.
Conclusion
ACF and ACPT are genuinely different tools, not just two brands solving the same problem in the same way.
ACF is the right pick for Gutenberg-heavy builds, teams that run Local JSON workflows, and projects where developer familiarity across the community matters at handoff. ACPT earns its place for visual-first builds, Bricks and Breakdance projects, and any agency that wants to stop paying annual fees on a tool they will use for the next several years. The 2024 controversy added noise to a decision that was already straightforward: pick the tool that fits the actual build.
If you are regularly building client sites and have not done the lifetime licensing math yet, that is the first place to start.
If you are building or restructuring a WordPress site and want the custom content architecture set up for both performance and AI search visibility, our premium WordPress service handles this from the foundation up.
For WordPress professionals and agencies in India and Kolkata: if annual licensing costs are eating into your project margins, we help teams in Kolkata and across India build sustainable, cost-effective WordPress stacks. Get in touch with SyncWin Media to talk through the right setup for your situation.
