Skip to content
WPJury
No. 00723 Developer Tools

Toolset Types: worth it for visual content modeling, not simple custom fields

The verdict Toolset Types is worth buying when you want to define post types, fields, taxonomies, and relationships through a unified visual system and plan to use the wider Toolset suite. It is not the best default for a new site that only needs custom fields: ACF, Pods, or Meta Box are usually simpler, more widely adopted, or cheaper. Choose Toolset for an integrated no-code build, not because it is the leanest custom-fields plugin.
Situational The ruling
Get v3.6.2

via WorldPressIT · complete package

Best for
  • No-code content modeling
  • Directory and listing websites
  • Agencies building Toolset-powered sites
  • Sites needing post relationships
  • Editors who prefer visual configuration
Skip it if
  • You only need a few custom fields
  • You want a lightweight developer-first setup
  • You need the largest third-party ecosystem
  • You do not want recurring Toolset dependencies
Version 3.6.2 Updated 17 Sep 2026 Licence GPL
Toolset Types: worth it for visual content modeling, not simple custom fields screenshot

Toolset Types is a capable content-modeling plugin, but it is no longer an obvious default. It lets you create custom post types, custom taxonomies, and custom fields from the WordPress admin, without writing PHP. It also supports repeating field groups and relationships between post types, including parent-child and many-to-many connections. That makes it more than a basic custom-fields add-on: it is the data-structure layer of the broader Toolset system.

The strongest reason to use it is consistency. Toolset Types works alongside Toolset Views, Blocks, Forms, Maps, and Access, so one vendor provides the tools for defining content, displaying it, filtering it, collecting it, and controlling access. For a directory, property catalog, membership portal, or classified site, that integrated approach can save substantial custom development. It is particularly attractive to teams that want editors or site builders to manage structured content without maintaining a large amount of PHP.

Relationships are another genuine strength. A site can model connections such as properties and agents, courses and instructors, or events and venues instead of forcing everything into flat custom fields. Toolset’s documentation also clearly explains when to use a field versus a taxonomy, which is useful for non-developers making decisions that will affect future queries and templates.

There are important catches. Types is most valuable inside the Toolset ecosystem, which can make a site more dependent on one vendor’s conventions and extensions. The visual workflow is broad rather than minimal, so a small project can feel over-equipped. Developers who prefer registering post types and fields in code may find the admin-first approach less portable and less transparent than code-defined ACF field groups or a custom plugin.

The support history also deserves attention. The WordPress.org listing shows an overall 4.2-star rating from 282 reviews, but many of the visible reviews are old and focus on the transition from a free plugin to a paid product. The old WordPress.org support forum is largely historical, while Toolset’s own community forum is closed for technical questions and directs paid customers to professional support. That does not mean the product is abandoned: Toolset Types 3.6.3 was released on September 15, 2026, supports PHP 7.4 through 8.5, and the developer recommends updating all Toolset components together.

Compared with ACF, Toolset offers a more complete visual suite and stronger built-in relationships, while ACF is usually the cleaner choice for developers and has a larger ecosystem. Pods is the better value if you want a free, broad content-modeling tool, although its interface can require more editor training. Meta Box is attractive for developers who want modular extensions and more control, while Custom Post Type UI is sufficient when you only need to register post types and taxonomies. The verdict is therefore situational: Toolset Types is worth it for integrated, no-code builds, but excessive for ordinary custom-field work.

Questions people ask

Is Toolset Types still supported?
Yes. Toolset Types continues to receive releases; version 3.6.3 was released on September 15, 2026. Toolset recommends updating the components used on a site together.
Is Toolset Types better than ACF?
It is better when you want an integrated visual system for post types, relationships, templates, forms, and access control. ACF is usually better for developers who want a focused custom-fields tool with a larger ecosystem.
Can Toolset Types create custom post types and taxonomies?
Yes. It can define custom post types, custom taxonomies, and custom fields through the WordPress admin, without requiring PHP.
Does Toolset Types support repeatable fields?
Yes. Toolset documents repeating field groups as a core feature, allowing multiple structured sets of fields to be attached to content.
Should I use Toolset Types for a simple blog?
Usually not. If you only need a few extra fields or one custom post type, ACF, Pods, Meta Box, or Custom Post Type UI will generally be simpler and less dependent on a larger suite.

Get Toolset Types: worth it for visual content modeling, not simple custom fields 3.6.2

Complete package, ready to install, via WorldPressIT.

Download

Other rulings

Meta Box Tabs: worth it for complex admin screens, not simple fields Meta Box Tabs is worth buying when you already use Meta Box and need to turn a long custom-field form into a cleaner editing interface. It is a focused, well-documented extension, but it is not a compelling standalone purchase: ACF already includes a comparable Tab field, and simple Meta Box field groups may not need another paid add-on. Buy it for client-facing admin usability and large field groups, not for basic custom fields. Situational OxyExtras Premium Oxygen Addon: worth it for Oxygen Classic power users OxyExtras is worth buying if you already build client sites with Oxygen Classic and regularly need advanced accordions, tabs, carousels, lightboxes, menus, or dynamic content without writing custom components. It is not a good buy for new projects on Oxygen v6, Breakdance, Bricks, or Elementor, and its value drops sharply if you only need a few basic visual effects. Situational Gravity Perks: Entry Blocks is worth it for block-based portals Gravity Perks is worth buying when you already use Gravity Forms and need a front-end directory, dashboard, member area, or editable entry list built in Gutenberg. Entry Blocks is unusually flexible for block-based layouts, but it is not the best choice for complex data applications: GravityView is more mature for advanced filtering, approvals, maps, and large-scale directory work. Situational Bit Integrations Pro: worth it for WordPress-first automation Bit Integrations Pro is worth buying if your automations start in WordPress and need to push data into CRMs, email tools, spreadsheets, WooCommerce, LMS platforms, or webhooks. It offers unusually broad plugin coverage, unlimited data transfers, conditional logic, and custom API/PHP options at a lower ongoing cost than Zapier, but it is less suitable than dedicated workflow platforms for complex branching, long-running jobs, or automation that must keep working independently of WordPress. Recommended