Skip to content

Everything for WordPress, web development — and beyond

🥇 9 best WordPress custom post type plugins 2026

🥇 9 best WordPress custom post type plugins 2026

Need a product catalog, portfolio, knowledge base, or classifieds on your site? Standard WordPress Posts and Pages are powerless here. Without custom post types (CPT), you either bury logic in workarounds or end up with admin chaos.

According to W3Techs, WordPress powers a significant portion of internet sites, and a good half of commercial WP projects rely precisely on CPT. A properly configured custom post type separates a content project from a hobby blog.

Below are nine tools that create and configure CPT without a single line of code. From lightweight registrars to frameworks with their own database tables, each tested on a live site.

💡 Quick overview:

  • Decide what you need: just register CPT or also custom fields with frontend display.
  • For simple registration, take CPT UI or Post Types Unlimited, both free and work with any theme.
  • If you need fields + output templates, Pods or Meta Box will cover the vast majority of scenarios without plugin bloat.
  • For client sites with visual configuration, Toolset Types or Themify Post Type Builder.
  • E-commerce on WooCommerce? You already have some CPT out of the box, see point 7.

Comparison table

Plugin

For whom

Price

Active installations

JetEngine

Developers and agencies: CPT + fields + listings + CCT

Free / from $199

tens of thousands

Pods

Intermediate level: CPT + fields + relationships

Free

100,000+

Meta Box

Developers: custom fields + CPT

Free / from $149

700,000+

ACF

Developers and agencies: fields + CPT (from v6.1)

Free / from $49

2,000,000+

Toolset Types

Agencies: visual templates

from $69

tens of thousands

Custom Post Type UI

Beginners: clean CPT registration

Free

1,000,000+

1. JetEngine: visual CPT builder from Crocoblock

CPT and taxonomy creation interface in JetEngine by Crocoblock

JetEngine, part of the Crocoblock ecosystem, is tailored for creating dynamic content in WordPress. The visual interface registers custom post types, taxonomies, meta fields, and even custom database tables (Custom Content Types, CCT), all without PHP.

The main advantage over competitors is deep integration with Gutenberg and Elementor. You create a CPT, add fields, and immediately output them via Dynamic Tags in Elementor or through JetEngine blocks in Gutenberg. Listing Grid configures record listings: cards, tables, sliders.

For non-trivial scenarios, REST API for every CPT out of the box, parent-child relationships between different content types, and a calendar for CPT with dates. In practice, enough for real estate portals, classifieds, and catalogs of any complexity.

  • Pros: CPT + fields + CCT in one plugin, visual listing builder, Elementor/Gutenberg integration, REST API.
  • Cons: full functionality is part of paid Crocoblock (from $199/year). Free JetEngine version registers CPT and basic fields, but CCT and listings are in Pro.
  • Price: free for basic CPT registration; full Crocoblock package from $199 per year.
  • Download: 🔗 JetEngine on Crocoblock

2. Pods: CPT, fields and relationships in one framework

Content types management interface in Pods

Pods is not just a CPT registrar. It's a content management framework: you create a post type, add fields to it (40+ types), configure relationships between different content types, and output everything via shortcodes, blocks, or PHP templates.

The difference from competitors is Advanced Content Types: Pods can create content stored in its own database tables, bypassing wp_postmeta. On sites with millions of records, this radically reduces load.

The built-in Pods Templates templating system lets you layout output without editing the theme. For developers, full REST API, integration with WPGraphQL, Timber, WPML, and Polylang out of the box.

  • Pros: all in one framework (CPT + fields + relationships + output), own DB tables, active community, Slack support.
  • Cons: a beginner needs a day or two to get up to speed, interface not as flat as CPT UI. Some premium addons are paid.
  • Price: free.
  • Download: 🔗 Pods on WordPress.org

3. Toolset Types: visual templates for agencies

Custom post types creation panel in Toolset Types

Toolset Types, part of the Toolset ecosystem, is tailored for building dynamic content sites without code. You register CPT and taxonomies, add repeatable field groups, and immediately layout output templates in Toolset Blocks (based on Gutenberg).

The main feature is reusable field groups. Configure a "Product characteristics" block once and add it to any CPT in two clicks. Parent-child relationships between different post types are configured visually.

In practice, Toolset Types fully unfolds paired with Toolset Blocks. For agencies assembling typical sites (catalogs, classifieds, knowledge bases), it saves dozens of layout hours, pricing on the developer site.

  • Pros: field groups are reusable, visual template builder, relationships between CPT without code.
  • Cons: full functionality only as part of the paid Toolset package. Free Types version registers CPT and fields, but without templates.
  • Price: from $69 per year.
  • Download: 🔗 Toolset Types on developer site

4. Advanced Custom Fields (ACF): industry standard now for CPT too

CPT and taxonomy registration interface in ACF

From version 6.1, ACF stopped being "only about fields," now it has built-in full-fledged registration of custom post types and taxonomies via a convenient visual interface. This means 2 million active ACF installations can create CPT without additional plugins.

The interface follows ACF logic: field group → display rule → CPT. First you create a post type, then attach fields to it, all in one window. All standard WordPress CPT API parameters are supported: public, hierarchial, has_archive, supports, rewrite, and REST API.

For those already using ACF for fields, migrating to built-in CPT registration reduces the plugin stack by one and eliminates compatibility conflicts. PHP export allows transferring CPT between sites without reconfiguration.

  • Pros: 2M+ installations, CPT registration + fields in one plugin, PHP export, active development and documentation.
  • Cons: for complex relationships between CPT, additional solutions needed. ACF Pro ($49/year) only for Pro fields (gallery, repeater, flexible content).
  • Price: free for CPT + basic fields; ACF Pro from $49 per year.
  • Download: 🔗 ACF on WordPress.org | 🔗 ACF Pro

5. Post Type Builder: drag and drop from Themify

Drag-and-drop CPT template builder in Post Type Builder

Post Type Builder (PTB) from Themify is a visual tool that walks the user through steps: create CPT → add custom fields (20+ types) → layout output template → publish post. Drag and drop at every stage.

The difference from competitors is built-in addons: Map View, Relation between CPT, Search with field filtering, and frontend Submissions. Users can add posts from the frontend without admin access.

The license gives access to all addons and lifetime updates. Import/export of CPT and taxonomies works with one click, convenient when transferring between dev server and production.

  • Pros: step-by-step wizard, rich addon set, frontend submissions, lifetime license for $49.
  • Cons: tied to Themify ecosystem (though works with any theme). For complex relationships between dozens of CPT, the interface becomes cumbersome.
  • Price: $49 (lifetime).
  • Download: 🔗 Post Type Builder on Themify

6. Meta Box: field framework with CPT registration

Fields and meta boxes overview in Meta Box plugin

Meta Box grew from a custom fields framework into a full-fledged ecosystem. The free MB Custom Post Types & Custom Taxonomies extension adds visual CPT registration right in the admin, with the same principles as fields: minimalist, fast, without extra code.

Developers value Meta Box for its lightweight API and storage in native WordPress tables (no blob). The plugin doesn't impose its own output method, use any page builder: Elementor, Bricks, Breakdance, Beaver Builder, Divi.

The free version covers most typical scenarios. Paid addons (pricing on Meta Box site) add repeatable groups, conditional logic, custom tables, and frontend forms, needed mainly on complex client projects.

7. WooCommerce: CPT for store out of the box

WooCommerce control panel with products as CPT

If you have an e-commerce site on WooCommerce, you already have three custom post types right after installation: Product (products), Shop Order (orders), and Shop Coupon (coupon codes). Each with its own taxonomy, categories, tags, shipping types.

The plugin doesn't provide a visual interface for creating NEW CPT, but for a store owner, this isn't needed: the product structure is ready, customized via WooCommerce hooks, and for extension (adding fields to Product), you connect Meta Box or ACF.

Practical scenario: WooCommerce CPT + ACF fields for product (dimensions, material, delivery time) + CPT UI for "Brands" as a separate post type, and you have a full-fledged catalog without a single line of PHP.

  • Pros: ready CPT for store, native integration with REST API and WP_Query, 5M+ active installations.
  • Cons: doesn't create new CPT, only its own three. For registering additional ones, you need another plugin from the list.
  • Price: free.
  • Download: 🔗 WooCommerce on WordPress.org

8. Custom Post Type UI: the most popular CPT registrar

Main CPT registration panel in Custom Post Type UI

With over a million active installations, CPT UI has become the de facto standard for registering custom post types. The interface is form fields: name, labels, slug, visibility parameters, supports. Nothing extra.

The plugin updates steadily (version 1.19.2, May 2026), tested up to WP 7.0 and PHP 7.4+. For multisite, there's a premium CPT UI Pro addon with network management, output blocks, and extended REST API.

In practice, CPT UI doesn't try to do everything, it brilliantly does one thing: registers CPT and taxonomies. Add fields via ACF or Meta Box, configure output with the theme. This approach eliminates vendor lock-in.

  • Pros: 1M+ installations, minimalist interface, CPT import/export, active development, portability.
  • Cons: doesn't work with fields and output, only registration. For frontend, you need CPT UI Pro.
  • Price: free.
  • Download: 🔗 CPT UI on WordPress.org

9. Post Types Unlimited: no ads and upsells

Adding new CPT interface in Post Types Unlimited

Post Types Unlimited from WPExplorer is CPT UI without ads and without a Pro version. At all. The plugin does exactly what it promises: registers CPT and taxonomies using native WordPress API, using the standard admin interface.

The key difference is the plugin stores CPT and taxonomies as posts in its own table. This gives two advantages: first, standard WordPress export/import works (Tools → Export), second, no ads and upsells in the admin. Ideal for client sites.

If you use the Total theme from WPExplorer, you get additional CPT display settings: archives, single view, post cards, and related posts. With any other theme, registration is clean and portable.

  • Pros: no ads and Pro upsells, native export/import, updates (v1.2.9, May 2026), 10,000+ installations.
  • Cons: doesn't create fields, only CPT and taxonomies. For advanced display settings, you need the Total theme.
  • Price: free.
  • Download: 🔗 Post Types Unlimited on WordPress.org

⁉️🤔 Frequently asked questions

How does CPT differ from taxonomy?

CPT is a content type (analogous to Posts or Pages). Taxonomy is a way of grouping that content (like categories and tags). For example, CPT "Products" uses the taxonomy "Product categories." Plugins from the list register both.

Do I need to know programming to create CPT?

To register CPT via plugin, no. All nine tools from the list work through the admin without code. PHP is needed only if you output CPT in a non-standard way, but most WordPress themes automatically pick up registered post types.

Does CPT registration slow down the site?

The registration itself, no, it's a line in the database. Slowdown occurs with a large number of CPT records (hundreds of thousands) due to wp_postmeta bloat. In this scenario, Pods and Meta Box offer custom DB tables, queries execute faster.

What happens if I deactivate the CPT plugin, will the posts disappear?

CPT posts remain in the database but become inaccessible on the frontend (404 error). The admin won't show them either. When reactivating the plugin with the same slug parameters, the posts will be restored. This is precisely why CPT UI and Post Types Unlimited store exportable configuration.

Can I use two CPT plugins simultaneously?

Yes, this is common practice: CPT UI for type registration + Meta Box for fields. Important not to register the same slug in two plugins, this will cause a conflict. Stick to the rule: one plugin registers CPT and taxonomies, another handles fields and output.

What to install in 2026: final breakdown

Nine plugins cover the entire spectrum of tasks, from "just register CPT" to "build a portal with dynamic content." The choice comes down to three questions: do you need custom fields, do you need visual frontend output, and what's the budget.

  • If you need clean CPT registration without extras, take CPT UI or Post Types Unlimited. Both free, both work with any theme. CPT UI is more popular (1M+), PTU is cleaner (no upsells).
  • If you need fields + relationships + output in one framework, Pods or Meta Box. Pods is more powerful for complex data structures, Meta Box is more flexible for developers used to PHP.
  • If you're building a site for a client with visual configuration, Toolset Types or Themify PTB. Both paid, both save hours on templates.
  • If you already use ACF for fields, enable built-in CPT registration from version 6.1 and reduce the plugin stack by one.
  • If you have an e-commerce site on WooCommerce, CPT for products and orders already work. Add CPT UI for auxiliary post types.

Start with free CPT UI: in 5 minutes, you'll register your first custom post type and understand if you need something more complex. And which plugin handles CPT on your project, share in the comments.