Pods is the free alternative in the custom-fields space occupied by paid tools like Advanced Custom Fields Pro and Toolset: it handles custom post types, taxonomies, and field groups with relationships, and adds a template engine and shortcodes for displaying that data – all in the free core. Where ACF focuses on field UI and leaves display to developers, Pods tries to cover the full content-type lifecycle: define the type, add fields, relate content types to each other, and render with Pods Templates or PHP. For budget-constrained projects that need real content architecture – directories, catalogs, structured data models – Pods is the open-source answer.
The 3.3.9.x series is a major security hardening cycle: 3.3.9.1 and 3.3.9.2 shipped fixes covering multiple areas, backported to every major Pods version from 2.7 upward – a responsible maintenance pattern for a plugin with a large installed base on older versions. Running current matters here more than usual.
Competitive Features
- Free full content-type management – CPTs, taxonomies, and fields without licensing
- Bi-directional relationships – connect content types to each other
- Pods Templates and shortcodes – display layer included in the core
- Advanced custom fields – repeatable groups, relationships, and varied input types
- ACT (Advanced Content Types) – custom data tables beyond WordPress post storage
- Security hardening cycle (3.3.9.x) – backported fixes across major versions
- REST API integration – content types exposed via WordPress REST
Key Features
- Pod builder – visual interface for defining content types and fields
- Field types – text, date, file, relationship, WYSIWYG, color, and more
- Conditional display logic – field visibility by context
- Role-based access – restrict content and fields per capability
- Migration tools – import from ACF and other field plugins
- Multilingual compatible – WPML and Polylang support
- Blocks and shortcodes – display anywhere
Comparison with Competitors
Pods vs Advanced Custom Fields Pro
| Aspect | Pods | ACF Pro |
|---|---|---|
| Billing model | Free core | Paid license |
| Field UX | Functional | Industry-standard polish |
| Content types | Native (CPTs + taxonomies + fields) | Fields only (CPT UI separate) |
| Relationships | Bi-directional, native | Via Pro relationship fields |
| Display layer | Templates and shortcodes included | Developer-coded |
| Ecosystem | Smaller | Largest |
Bottom line: ACF Pro is the polished industry standard with the largest ecosystem and third-party support; Pods is the full-stack free option – content types, fields, relationships, and display in one package. Budget projects and full-content-model needs pick Pods; UI polish and ecosystem pick ACF.
Pods vs WP All Export Pro
| Aspect | Pods | WP All Export Pro |
|---|---|---|
| Job | Define and structure content | Move content out of WordPress |
| Data model | Custom fields and relationships | Export templates from any post type |
| Output | Frontend display | XML/CSV feeds |
| Overlap | None | Reads what Pods defines |
Bottom line: Complementary ends of the data lifecycle. WP All Export Pro exports the structured data other plugins define; Pods defines that structure in the first place. Sites moving structured content between systems run both – Pods models it, the exporter moves it.
Pods vs Post SMTP Pro
| Aspect | Pods | Post SMTP Pro |
|---|---|---|
| Layer | Content architecture | Email delivery |
| Job | Custom types and fields | Reliable transactional email |
| Relationship | Data model | Delivery infrastructure |
| Overlap | None | None |
Bottom line: Different infrastructure jobs. Post SMTP Pro makes sure email leaves your server reliably; Pods structures the content your site runs on. Complex sites usually need both – structured data and dependable notifications – without either touching the other’s layer.
Recommended Stack – structured content needs structural display: pair Pods with FacetWP for faceted filtering over your custom content types, turning directories and catalogs into searchable, filterable interfaces.
Official Changelog
Version 3.3.9.2
Release Date: August 31, 2026
- Security: Major hardening release covering multiple areas of the plugin. Updating as soon as possible is recommended.
- Compatibility: Additional releases with these security fixes backported to each major Pods version from 2.7 and above.
Version 3.3.9.1
Release Date: August 14, 2026
- Security: Major hardening release covering multiple areas of the plugin, with fixes backported to each major Pods version from 2.8 and above.
Version 3.3.9
Release Date: August 5, 2026
- Maintenance release: stability improvements ahead of the security hardening cycle.
Frequently Asked Questions
Is Pods really a free ACF alternative?
For the core feature comparison, yes – custom post types, taxonomies, field groups, relationships, and display templates all ship free. ACF Pro’s polish and ecosystem are what the license buys; Pods buys you the full content-model stack at no cost.
Why are the 3.3.9.x releases marked as critical security updates?
They covered multiple hardening areas with fixes backported all the way to Pods 2.7 – an unusually wide backport range signaling severity. Any Pods installation should be on 3.3.9.2 or the appropriate backported release for its major version.
What are Advanced Content Types (ACT)?
Pods can store custom data in dedicated tables rather than the WordPress posts table – useful for large datasets that do not need to be posts (logs, records, imported data), keeping the posts table lean.
Does Pods handle bi-directional relationships?
Yes – natively. Two content types can reference each other, and updates propagate in both directions, which most field plugins handle only through workarounds.
Can I migrate my existing ACF fields to Pods?
Yes – migration tools import ACF field groups, so moving a site to Pods (or testing it) does not mean rebuilding field definitions by hand.
Leave a Reply