Toolset Types Pro is the no-code content-architecture tool: register custom post types, taxonomies, and field groups through the admin, with repeatable field groups and relationships – then display everything without PHP through the broader Toolset suite (Views and Blocks). Its differentiator versus field-plugin rivals like Advanced Custom Fields Pro and the free Pods is the display story: ACF handles fields beautifully and leaves rendering to developers, while Toolset’s ecosystem covers the whole path from content model to front-end output, including a native Gutenberg block system. For agencies building data-driven sites without deep PHP, that’s the argument. Against the free Pods, Toolset counters with polish, support, and the complete suite integration.
The 3.6.x line shows steady maintenance on the registration core – version, taxonomy, and field-group updates keeping compatibility current with modern WordPress releases.
Competitive Features
- No-code content types – CPTs, taxonomies, and fields registered from the admin
- Repeatable field groups – grouped repeating data beyond single-field repeats
- Post relationships – connect content types with parent/child and many-to-many links
- Gutenberg blocks (with Toolset Blocks) – display content types without code
- Front-end forms (with Toolset Forms) – user-submitted content into your types
- Access control (with Toolset Access) – permission layer for content types
- Multi-value fields – repeated and grouped data structures
Key Features
- Field types – text, image, file, date, numeric, select, relationship, and more
- Custom taxonomies – connected to content types at registration
- Conditional display – field visibility by logic
- Multilingual ready – WPML integration for translated content types
- REST API exposure – content types via WordPress REST
- Import/export – definitions portable between sites
- Documentation – extensive learning library from the Toolset team
Comparison with Competitors
Toolset Types Pro vs Advanced Custom Fields Pro
| Aspect | Toolset Types Pro | ACF Pro |
|---|---|---|
| Core focus | Content types + fields + display | Fields (best in class) |
| Display layer | Toolset suite (no-code) | Developer-coded |
| Relationships | Suite-level | Field-level |
| Ecosystem | Toolset-integrated | Largest |
| Learning curve | Moderate | Low for fields |
| Best for | No-code data-driven sites | Developer-led projects |
Bottom line: ACF Pro is the field standard with the biggest ecosystem – but display requires development. Toolset covers architecture through display without code, at the cost of being locked into its suite for the full benefit. Developers pick ACF; no-code agencies pick Toolset.
Toolset Types Pro vs Pods (free)
| Aspect | Toolset Types Pro | Pods |
|---|---|---|
| Price behavior | Paid license | Free |
| Display solution | Full no-code suite | Templates (more technical) |
| Polish and support | Commercial grade | Community |
| Relationships | Suite-level | Native bi-directional |
| Best for | Supported no-code builds | Budget full-stack needs |
Bottom line: Pods is the free full-stack alternative – content types, fields, relationships, and templates without licensing. Toolset Types Pro buys polish, support, and the no-code display suite. Budget decides, supported workflows decide otherwise.
Recommended Stack – content types pair with page-building layers: connect Toolset Types with GenerateBlocks Pro so custom-type data renders inside lightweight block layouts.
Official Changelog
Version 3.6.2
Release Date: August 14, 2026
- Maintenance release: stability and compatibility improvements.
Version 3.6.1
Release Date: July 10, 2026
- Maintenance release: fixes for field group handling.
Version 3.6.0
Release Date: June 5, 2026
- Feature release: registration and field updates for current WordPress versions.
Frequently Asked Questions
Do I need other Toolset plugins to display content?
For no-code display, yes – Types registers the content model, Toolset Blocks or Views handles the front-end rendering. Types alone provides the registration and field layer that developers can display directly.
How does it compare to ACF for pure field work?
ACF Pro is the field standard – better field UX and the largest ecosystem. Toolset Types competes when the whole path (registration through display) needs to stay no-code rather than developer-driven.
Can users submit content to my custom types?
Yes, with Toolset Forms – front-end forms create and edit entries in your custom types, the standard setup for directories and listing sites.
Is it multilingual-ready?
Yes – WPML integration makes custom fields and content types translatable, essential for multilingual data-driven sites.
Can I migrate my existing fields to Toolset?
Yes – import tools cover ACF field groups, so switching (or evaluating) doesn’t mean rebuilding field definitions manually.
Leave a Reply