Custom Post Type UI

Quick take

Custom Post Type UI is still one of the clearest ways to register custom post types and taxonomies without writing the registration code yourself. This Custom Post Type UI review recommends it when you need structured content types but want WordPress to keep handling the underlying post type and taxonomy system.

Best fit: Custom Post Type UI makes the most sense for site builders and developers who need custom post types or taxonomies without hand-coding registration. A different tool will usually make more sense for users expecting the free plugin to create custom fields or design front-end templates automatically.

What Custom Post Type UI actually does

The free plugin gives you an admin interface for registering and managing WordPress custom post types and taxonomies. You define settings such as slugs, labels, visibility and supported features, then CPTUI registers those content structures with WordPress.

That distinction matters. CPTUI creates the content type definition. It does not automatically design the front-end archive or single template for that content.

Where CPTUI fits in a real WordPress build

A common workflow is to use CPTUI for a content type such as Team Members, Properties, Events or Case Studies, then use another field system for extra data and a theme or builder for display. That separation keeps the job of content registration simple.

I see CPTUI fitting best when you already understand what a post type or taxonomy is and mainly want to avoid maintaining registration code in a theme or custom plugin.

Free vs CPT UI Pro

Custom Post Type UI Free handles the core registration work. The official plugin page states that the free version will remain maintained and that CPT UI Pro is optional.

CPT UI Pro goes beyond registration with front-end display tools, including block-editor layouts, filters and templates. Pro does not require the free plugin, and existing CPTUI content can integrate without a content migration.

Strengths that matter

The biggest strength is focus. CPTUI does one foundational WordPress job and exposes the settings through the admin. It also includes tools for reviewing registered content types and generating registration code, which can help when moving a configuration into a code-managed project.

It is also widely compatible because the resulting content uses normal WordPress post type and taxonomy concepts rather than a proprietary content database.

Trade-offs and limits

CPTUI does not replace a custom-fields plugin. Registering a Property post type does not create bedrooms, price or location fields. You still need a field solution if the content requires structured metadata.

The free plugin also does not solve front-end presentation by itself. If your real problem is designing archive cards, filters and single templates, plan that layer before choosing CPTUI as the registration tool.

Custom Post Type UI pricing

Custom Post Type UI pricing starts at $0 for the free plugin on WordPress.org. CPT UI Pro is an optional commercial product, but I could not verify a current public price from an official pricing page on September 10, 2026, so I am not publishing an unverified amount.

PluginSuggest verdict

CPTUI remains a sensible choice when the job is registering custom post types and taxonomies cleanly without hand-writing code. Use the free plugin if registration is all you need. If you want one product to cover more of the display layer, compare CPT UI Pro with the builder and field stack you already use before paying for overlap.

Where CPT UI fits in a larger content stack

Custom Post Type UI is strongest when the problem is registering post types and taxonomies, not defining a complete field system. Many production sites pair it with ACF, Meta Box, Secure Custom Fields, or another data plugin. That separation can be useful because registration and field configuration remain independent, but it also means teams must document which plugin owns each part of the content model.

For deployments across staging and production, use the available code-export and configuration tools rather than manually recreating post types on every site. After any slug or rewrite change, flush permalinks and test archive URLs, REST responses, taxonomy routes, and builder templates before releasing the change.

Custom Post Type UI FAQs