ACPT

ACPT is a WordPress content-modeling framework for building custom post types, taxonomies, meta fields, relationships, forms, dynamic blocks, and custom content structures from one plugin. This ACPT review focuses on where that all-in-one approach fits compared with narrower tools such as ACF, Meta Box, Pods, and JetEngine.

What ACPT covers

ACPT can register custom post types and taxonomies, create meta boxes and field groups, connect records through relationship fields, define option pages, and expose structured values to builders and templates. The current product advertises more than 60 meta field types, which gives it a wider input catalog than many lightweight custom-field plugins.

The plugin also supports dynamic blocks and frontend forms, so the same data model can be used for editor-facing input, public submissions, and reusable front-end output. That makes ACPT relevant for directories, catalogs, internal tools, editorial databases, and other projects where the data model is more important than a conventional blog-post workflow.

Custom post types, fields, and relationships

ACPT combines post-type registration and field management inside the same interface. A team can define a content type, attach field groups, add relationships, and then expose that data to a supported page builder or custom template without maintaining separate registration and field plugins.

Relationships are especially important on larger builds. Instead of flattening everything into repeated text fields, ACPT can connect content entities and let the implementation treat those connections as part of the schema. That is useful for structures such as properties and agents, courses and instructors, products and suppliers, or venues and events.

Custom Content Types and dedicated tables

ACPT 2.1 introduced Custom Content Types in beta. These records can use dedicated database tables rather than storing every entity as a normal WordPress post. Relational columns can connect one custom content table to another or link records to WordPress posts, users, terms, and option pages.

This gives ACPT a different ceiling from field-only plugins, but it also raises the importance of architectural planning. Custom tables can be valuable for large structured datasets, yet migrations and developer handoffs become harder if nobody documents the table structure, field names, indexes, and relationships.

Builder and developer workflows

ACPT advertises integrations with more than 20 page builders and related tools. It also exposes APIs and developer hooks for teams that want code-level control. Recent documentation shows native dynamic-data integrations and support for modern WordPress patterns such as block bindings.

The practical advantage is that a site can begin with visual configuration and still retain a developer path when the build becomes more complex. The trade-off is product breadth: there are more concepts to learn than in a simple field-group plugin.

Pricing and licensing

Pricing checked: September 26, 2026. ACPT currently lists Personal at $29 per year for 1 site, Business at $49 per year for 5 sites, and Agency at $99 per year for unlimited sites. The vendor states that all plans include the complete feature set, updates and support for the billing period, plus a 30-day money-back guarantee.

That pricing model is notable because site count, rather than feature tier, is the main difference between annual plans. Agencies should still compare the cost with ACF PRO, Meta Box, JetEngine, and free tools after accounting for any extra plugins needed for listings, forms, or front-end rendering.

Where ACPT differs from ACF, Meta Box, and JetEngine

ACF remains a familiar standard for field groups and template integration. Meta Box emphasizes a modular framework with extensions and custom-table options. JetEngine combines structured data with query and listing tools inside the Crocoblock ecosystem. ACPT positions itself as a broader data framework that includes post types, fields, custom content types, forms, blocks, and relationships in one package.

The right choice depends on which layer should own the architecture. A developer-heavy project may prefer Meta Box or code-first CMB2. A design team already standardized on ACF may value ecosystem familiarity. A Crocoblock site may get more from JetEngine because the listing and filtering stack is already integrated.

Migration and maintenance considerations

Before moving to ACPT, inventory post types, taxonomy slugs, field keys, repeaters, relationship rules, option pages, frontend forms, and any template code that reads existing metadata. Preserve field names where possible because changing keys can turn a plugin migration into a content migration.

For large sites, test representative records in staging and compare REST responses, builder dynamic tags, search/filter behavior, imports, exports, and multilingual workflows. If custom content types are used, document table names and relationships so future developers can maintain the data model without reverse-engineering it.

PluginSuggest verdict

ACPT is a serious content-modeling option for structured WordPress projects. Its strongest argument is breadth at relatively simple site-count pricing. The main decision is whether that breadth reduces plugin sprawl for your project or creates more framework than the site actually needs.

ACPT 2.1.1 and current compatibility

ACPT 2.1.1 was released on September 25, 2026. The release focuses on stability and permission hardening: it fixes SEOPress-related crashes when ACPT fields are empty, restores frontend output for ACPT and Dynamic Blocks, corrects several field-group and repeater save issues, improves taxonomy compatibility, and tightens front-end form permissions for fields and custom tables.

The same release also fixes builder and Site Editor edge cases involving Elementor, Bricks, Divi, Oxygen, Breakdance, maps, Basic Fields blocks, and required values such as zero. For sites using ACPT as a data framework rather than only a field plugin, these integration fixes matter because one schema can feed templates across several builders.

Schema portability and migration planning

ACPT can define post types, taxonomies, 60+ meta field types, relationships, custom content types in dedicated database tables, frontend forms, and dynamic blocks. Before replacing it, inventory not only field names but also relationships, option pages, CCT tables, REST/GraphQL exposure, builder bindings, validation, and front-end form permissions. Custom content types and relationship data will usually need a deliberate migration path rather than a simple ACF-style field export.

ACPT FAQs