Get WordPress

Plugin Directory

Pods – Custom Content Types and Fields

Pods – Custom Content Types and Fields

By Scott Kingsley Clark
Download
Live Preview

Description

Manage all your custom content needs in one location with the Pods Framework.

  • Create content types including Custom Post Types, Custom Taxonomies, and our special Advanced Content Types (ACTs get their own custom tables)
  • Extend and customize content types including Posts, Pages, Categories, Tags, Users, and Media with one easy click
  • Create custom settings pages easily within seconds
  • Add custom fields to any content type
  • Conditionally show fields based on the value of other fields with Conditional Logic
  • Group your fields however you’d like into their own sections and add additional headings to help organize
  • Show your fields anywhere using our blocks, shortcodes, widgets, or the non-coder Pods Template approach along with our automatic theme integration
  • Create connections between any of your content with relationship fields to keep your content organized

Let Pods help you grow your development and site building skills so that you can manage content beyond the standard WordPress Posts & Pages.

Want to check it out? Give Pods a test drive with our new One-click Demo.

Check out our Documentation, Support Forums, and our Live Community Slack Chat for assistance building your dream project with Pods.

Introduction

Content types that evolve with your needs

Create any type of content that you want — small or large — we’ve got you covered. Every content type created with Pods gets all the love it needs to grow up big and strong. You’ll get an easy-to-use interface that lets you manage field groups, custom fields, and how your content type will look or function.

Create new content types

With Pods, you can create entirely new content types and settings pages.

Every Field Type, FREE

If you choose to use Pods for your custom fields, you’ll get every field type you need, free of charge. Pods works great alongside other custom field plugins like Advanced Custom Fields too.

We have an extensive collection of over 25 different input types to choose from on 20+ different field types for any content structure. Each field type comes with their own additional options to help you customize content entry and display.

You can also control visibility by role/capability and other advanced options.

  • Repeatable Fields: Turn almost any field into a repeatable field with multiple values
  • Text: Plain Text, Website, Phone, Email, Password
  • Paragraph: Plain Paragraph Text, WYSIWYG (Visual Editor), Code (Syntax Highlighting)
  • Date / Time: Date and Time, Date, Time
  • Number: Plain Number, Currency (30+ international currencies)
  • Relationships / Media: File / Image / Video (Media library and basic upload options available), Avatar (for extended Users), oEmbed, Relationship (Dropdown, Multi Select, Autocomplete, Checkboxes, Radio Buttons, and List View available)
  • Checkbox (Yes / No)
  • Color Picker
  • Layout Fields: Heading text, HTML content

Relationships to rule the world with

The power is in your hands with our comprehensive support to relate your content to anything.

  • Custom defined lists of text options
  • Relate to any Post Type or Taxonomy posts / terms
  • Relate to any User profile
  • Relate to User Roles or Capabilities
  • Relate to any Comment

And many other relationships are also available including:

  • Image Sizes
  • Navigation Menus
  • Relate to content within any Database Table
  • Countries (predefined)
  • US States (predefined)
  • Canadian Provinces (predefined)
  • Calendar – Days of Week (predefined)
  • Calendar – Months of Year (predefined)
  • And many more!

Optional Components to do even more

You can enable some of our included components to extend your WordPress site even further:

  • Types-only Mode – On our Pods Settings page, you can choose to disable creating custom fields for a performance boost if you only want to use Pods for content types or you plan on using it alongside of other custom field plugins
  • Pods Templates – Use our template engine to create templates that can be handed off to clients for care-free management
  • Markdown Syntax – Parses Markdown Syntax for Paragraph Text / WYSIWYG fields
  • Advanced Relationships – Add even more relationship objects including Database Tables, Multisite Networks, Multisite Sites, Themes, Page Templates (in the theme), Sidebars, Post Type Objects, and Taxonomy Objects
  • Table Storage – Enable table-based database storage for custom fields on Post Types, Media, Users, and Comments
  • Roles and Capabilities – Create or edit Roles for your site and customize what they have access to
  • Advanced Content Types – Create entirely custom content types that have their own database table, and they will exist outside the normal WordPress context avoiding meta database tables
  • Pods Pages – Create custom pages that function off of your site’s URL path with wildcard support and choose the Page Template in the theme to use — most useful paired with Advanced Content Types

Plugins that integrate with Pods

Themes that integrate with Pods

  • Genesis (StudioPress) has direct integration in Pods itself

Extend Pods with Free Add-Ons

Extend Pods with Free Third-party Add-Ons

Pods Pro by SKCDEV Premium Add-Ons

How can I translate Pods into my own language?

Many thanks go out to the fine folks who have helped us translate the Pods plugin into many other languages.

Join us in further translating the Pods interface on the official Translating WordPress dashboard

We are also available through our Live Community Slack Chat to help our translators get started and to support them on the process.

Are you looking to translate your Pods and Fields themselves? You’ll want to enable the “Translate Pods” component from Pods Admin > Components.

Contributors

Pods really wouldn’t be where it is without all the contributions from our donors and code/support contributors.

Screenshots

  • Create new content types or extend existing ones
  • Add groups of fields and manage your content type
  • Add fields of many types with individual options for each
  • Creating or extending a Post Type will add groups of fields to the Post Editor
  • Creating or extending a Taxonomy will add groups of fields to the Term Editor
  • Extending Users will add groups of fields to the User Profile and Edit forms

Blocks

This plugin provides 6 blocks.

  • Pods View Include a file from a theme, with caching options
  • Pods Item List List multiple Pod items.
  • Pods Single Item Display a single Pod item.
  • Pods Form Display a form for creating and editing Pod items.
  • Pods Field Value Display a single Pod item's field value (custom fields).
  • Pods Single Item – List Fields Display fields for a single Pod item.

Installation

  1. Unpack the entire contents of this plugin zip file into your wp-content/plugins/ folder locally
  2. Upload to your site
  3. Navigate to wp-admin/plugins.php on your site (your WP Admin plugin page)
  4. Activate this plugin

OR you can just install it with WordPress by going to Plugins >> Add New >> and type this plugin’s name

FAQ

Where do I go for Support on your plugin?

Our primary Support is handled through our Support Forums. For the fastest support, you can contact us on our Live Community Slack Chat in the #support channel. We do not staff our Slack channel 24/7, but we do check any questions that come through daily and reply to any unanswered questions.

We do have a community of Pods users and developers that hang out on Slack, so you’re sure to get an answer quickly. We answer our Forum questions once a week with follow-up during the week as we’re prioritizing resources towards restructuring and improving our documentation.

Where do I report bugs or request features?

If you’ve encountered a bug or have an idea for a new feature, we kindly request you to create an Issue on our GitHub Repository at https://github.com/pods-framework/pods/issues/new. Please be very specific about what steps you did to create the issue you’re having and include any screenshots or other configuration parameters to help us recreate or isolate the issue.

Will Pods work with my Theme?

Most likely the answer is yes. We don’t require any special CSS or display attributes to use Pods with your theme, so you should have little to no difficulty showing your content in your theme. If you encounter any issues, contact your theme developer and ask them about their support for the standard WordPress theming functions and how to use WordPress Template Hierarchy with their theme.

Reviews

Great plugin to extend WP easily!

April 10, 2025
Wow, I am impressed by this plugin! So easy to add custom post types with taxonomies, extend existing post types, and even add options pages. Very well done, you have one more happy user 🙂 Thank you!

WOW! Game changer

January 10, 2025
At first glance, this plugin looks complicated. But after watching the main demonstration video on the Pods Framework website and then building my first “Pod”, which was a new Post type, HOLY COW does this ever open up so much customization possibilities! At first I started with the “Auto Template” and got something cool working with custom fields, but then I saw there are some “Pod” blocks. I turned off Auto-Template and created a couple more Pod templates for my custom Post type and that opened up so much in terms of putting in custom fields and content into more complex layouts! All without touching the PHP files! Very happy with this. I’ll be ditching “Theme Builders” from now on. To the developers of this great plugin: Keep it up!

Building a customized CMS with Pods is poetry

October 18, 2024
I know I should provide as much detail as possible for this brilliant plugin but it simply leaves me speechless. Every time I use it it makes me feel like I have WordPress super powers. I only wish I started using it sooner. My recommendation for new WordPress users and developers: start your journey on a high ground with Pods!
Read all 415 reviews

Contributors & Developers

“Pods – Custom Content Types and Fields” is open source software. The following people have contributed to this plugin.

Contributors

“Pods – Custom Content Types and Fields” has been translated into 129 locales. Thank you to the translators for their contributions.

Translate “Pods – Custom Content Types and Fields” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

3.3.7 – February 25th, 2026

  • Fixed: Resolve issues using WP_Filesystem to check session paths before starting a session. (@sc0ttkclark)

3.3.6 – February 25th, 2026

  • Fixed: Resolve a fatal error with WP_Filesystem usage. (@sc0ttkclark)

3.3.5 – February 24th, 2026

  • Minimum Requirements Notice: Pods 3.4 coming in 2026 will require new minimum versions of WordPress 6.8+, PHP 8.0+, and MySQL 5.7+
  • Feature: Added support for showing fields as “Read Only” in forms when a user does not have edit access to them while allowing admins to continue editing them. You can find this under the Edit Field modal in Advanced > Visibility > UI Access. (@sc0ttkclark)
  • Enhancement: When detecting malformed shortcodes broken by < or > characters within the where clause, Pods now shows a helpful notice with workaround instructions instead of just breaking. #7451 #7482 (@sc0ttkclark)
  • Enhancement: New replacements within Pods shortcodes clauses for replacing __LESS_THAN__, __LESS_THAN_OR_EQUAL__, __GREATER_THAN__, and __GREATER_THAN_OR_EQUAL__ with their corresponding <, <=, >, and >= characters to work around broken WP shortcodes. This is also available in the [if] Pods template shortcode compare attribute. #7451 #7482 (@sc0ttkclark)
  • Enhancement: New option for conditional logic that will allow saving conditional field values even when the field is hidden. #7475 #7484 (@faisalahammad, @sc0ttkclark)
  • Enhancement: New setting at Pods Settings > Performance that allows you to “Limit autocomplete search results in Relationship fields” to specify larger numbers if needed. #7454 (@sc0ttkclark)
  • Enhancement: PodsUI > Implement pods_ui_after_heading hook for additional UI customizations. (@sc0ttkclark)
  • Enhancement: PodsUI > Move restricted() checks before callbacks to prevent additional unnecessary calls when user doesn’t have access. (@sc0ttkclark)
  • Enhancement: Add pods_v_bool that uses pods_is_truthy to enforce boolean values on variables from various sources. (@sc0ttkclark)
  • Enhancement: Add Manage link to the Navigate section of the Pods content admin forms. (@sc0ttkclark)
  • Enhancement: Underlying code support for multiple condition checks for Conditional Logic. (@sc0ttkclark)
  • Tweak: Remove trim from pods_is_truthy and pods_is_falsey functions. (@sc0ttkclark)
  • Tweak: In the Edit Field modal, under the Advanced > Visibility section — the Restrict Access and UI Access are now separate checkbox groups. (@sc0ttkclark)
  • Tweak: Pods now follows WP Admin Theme color schemes more closely using dynamic CSS color references to the scheme colors. (@sc0ttkclark)
  • Fixed: Shortcode unit test issue resolved. #7472 #7473 (@devlamconstructie, @sc0ttkclark)
  • Fixed: Loading a form with WYSIWYG React Quill used as Repeatable fields now loads without breaking the editor. #7465 #7487 (@faisalahammad, @sc0ttkclark)
  • Fixed: Resolved reordering of values for Repeatable Date/Time, Currency, and Number fields. #7471 #7486 (@faisalahammad, @sc0ttkclark)
  • Fixed: Resolve sync associated taxonomy with relationship issues when not using bidirectional relationship field. #7477 #7485 (@faisalahammad, @sc0ttkclark)
  • Fixed: Resolved reordering of values in List View relationship fields. (@sc0ttkclark)
  • Fixed: Allow empty values in email fields when field is not required. #7476 #7483 (@faisalahammad, @sc0ttkclark)
  • Fixed: esc_html_e usage when not used for translating in PodsUI. #7462 (@DAnn2012)
  • Fixed: The default storage type for Settings is set to option when creating as it should have been. (@sc0ttkclark)
  • Fixed: When using repeatable fields on a Pod that uses Table-based storage, a notice now shows explaining that it’s not an available feature. (@sc0ttkclark)
  • Fixed: Better support when values are sent as WP_Error and now show appropriate errors in save_pod_item validation handling. (@sc0ttkclark)
  • Fixed: Resolve heredoc issue with Migrate PHP component. (@sc0ttkclark)
  • Fixed: WordPress 7.0 compatibility issues fixed. (@sc0ttkclark)
  • Fixed: Conditional logic now works properly for Boolean Group sub fields (used in Edit Field modal and other Pods Admin areas). (@sc0ttkclark)
  • Extensive cleanup to resolve important WP Plugin Checker results, PHPCS, and PHPStan issues across the codebase. (@sc0ttkclark)
  • Extensive testing upgrades to PHPUnit 10+ and wp-browser 4. (@sc0ttkclark, @lucetume)
  • New hourly verification of the Pods PLC DID and FAIR metadata. (@johnbillion)

3.3.4 – September 24th, 2025

  • Feature: Official support for DID did:plc:e3rm6t7cspgpzaf47kn3nnsl for optional installation via DID using the FAIR plugin. (@sc0ttkclark)
  • Fix: Prevent duplicates in Pods::field() and Pods::display() for simple relationships. (@sc0ttkclark)

3.3.3 – September 4th, 2025

  • Tweak: Support referencing ID for PodsMeta::groups_get(). (@sc0ttkclark)
  • Tweak: Update edit capability used for settings Pods so it can be displayed on the edit pod screen correctly. (@sc0ttkclark)
  • Fixed: Resolve issues with TinyMCE and Quill editors not loading when used as repeatable fields or conditional logic. #7448 #7438 #7430 (@multisme, @altermulti, @sc0ttkclark, @ztackett11)
  • Fixed: Resolve PHP fatal errors for undefined constant \Pods\Whatsit\Store::PLACEHOLDER in some edge case circumstances. #7445 (@sc0ttkclark, @Hue-SPetrovic)
  • Fixed: Resolve PHP 8.4 deprecation warnings with DI52 usage. #7448 (@sc0ttkclark, @doehry)
  • Fixed: Resolve warnings when using --args with WP-CLI commands. #7452 (@sc0ttkclark, @KhaledSakr)
  • Fixed: Resolve handling of decimals when auto-formatting to prevent removing zero number values and expand decimal handling for more cases. Improve logic matching (except dashes) for PHP vs JS. (@sc0ttkclark)
  • Fixed: Resolve field assigment issue in pods_config_merge_data() to reference the correct field. (@sc0ttkclark)

3.3.2 – July 8th, 2025

  • Tweak: Updated Swagger docs for Pods REST API endpoints. (@sc0ttkclark)
  • Tweak: pods_error() handles any Exception object including those extending the base Exception class. This allows for more refined error handling in Pods code. (@sc0ttkclark)
  • Tweak: PodsAPI now allows for passing in Pods related objects to be passed into various save/load methods without breaking those objects. (@sc0ttkclark)
  • Tweak: Allow setting new group when duplicating a field. (@sc0ttkclark)
  • Tweak: Added Jest testing coverage for more areas of the DFV code and updated to support the React Testing Library. #7427 (@sc0ttkclark)
  • Fixed: Block Editor saves no longer trigger full saves when an autosave is sent and Pods form validation passes. (@sc0ttkclark)
  • Fixed: Ensure Pods cache flushes when changing settings to prevent issues with Pods Blocks configs not showing fields conditionally linked to those settings. #7429 (@sc0ttkclark)
  • Fixed: When duplicating a pod, group, or field it will now add a space between the label and the copy number. (@sc0ttkclark)
  • Fixed: Typos corrected across the codebase. #7434 (@szepeviktor, @sc0ttkclark)
  • Fixed: PHP deprecated warnings resolved in Pods REST API and DI52 usage. #7401 #7437 (@BrookeDot, @sc0ttkclark)
  • Fixed: Saving Pods settings will now properly flush the Pods cache to ensure that the new settings are applied immediately to all areas that may be cached based on those settings. (@sc0ttkclark)
  • Fixed: Added a “doing it wrong” notice and debug log line for when a non-string gets sent to Pods::do_magic_tags() to prevent PHP warnings. (@sc0ttkclark)
  • Fixed: Better caching around the pods_can_use_dynamic_feature_sql_clauses() setting usage to prevent additional DB calls. (@sc0ttkclark)
  • Fixed: Resolve issues when saving featured image based on the first value of a file field so it only saves files with the image type. #7433 (@sc0ttkclark)
  • Fixed: Add support for Value_Field in pods_config_for_field() to ensure bidirectional relationships work as expected for saving on both sides. #7435 (@sc0ttkclark)
  • Fixed: Prevent erroneous ? and # characters in website formatting. (@sc0ttkclark)

3.3.1 – May 2nd, 2025

  • Fixed: Resolve issue with get_block_wrapper_attributes() usage. (@sc0ttkclark)

3.3 – May 1st, 2025

  • New minimum WP version required: WordPress 6.3+ (previously: WP 6.0+)
  • Removed: PHP support for Pod Templates and Pod Pages has been officially removed from Pods. This feature was deprecated in Pods 2.3. We recommend you follow the newer more secure way: https://docs.pods.io/displaying-pods/pod-page-template-hierarchy-for-themes/ and https://docs.pods.io/displaying-pods/pod-template-hierarchy-for-themes/ and a snippet if you absolutely still need PHP support for now https://gist.github.com/sc0ttkclark/35a15e6f93622c45f12d671184fb1315 (@sc0ttkclark)
  • Feature: Form validation for the Block Editor now prevents saving a post if there are required fields and shows the appropriate error message. #7343 #7369 (@JoryHogeveen, @sc0ttkclark)
  • Feature: Upgraded Pods Blocks to the WP Blocks API version 3 to support more features like block wrapper attributes and the iframe editor. (@sc0ttkclark)
  • Feature: Added support for WYSIWYG field type when using the TinyMCE editor to allow Delayed initialization and not showing the editor until clicking. This is optional and can be enabled per field. (@sc0ttkclark)
  • Feature: Added support for WYSIWYG field type when using the TinyMCE editor to refresh the editor if you encounter compatibility issues with other plugins on load. (@sc0ttkclark)
  • Tweak: Allow forcing pods_serial_comma() to use exactly what is sent instead of relying on the field config itself. (@sc0ttkclark)
  • Tweak: Remove Pods Pro WPGraphQL deactivation message to support future features there. The core functionality of that was merged into Pods 2.9 but new work is still being done in the add-on. (@sc0ttkclark)
  • Tweak: Pods Forms now wrap div / p form output types within a new div.pods-form-fieldset wrapper element. The table form output type has the new class pods-form-fieldset added to it too. (@sc0ttkclark)
  • Fixed: Prevent doing it wrong notices in WP from unintentionally loading translatable strings too early. (@sc0ttkclark)
  • Fixed: Improved PHP compatibility with strlen() usage. #7394 (@lbonomo, @sc0ttkclark)
  • Fixed: More PHP 8.x compatibility fixes for PodsUI. (@sc0ttkclark)
  • Fixed: Docs link for Date / Time field type now points to the correct URL. #7405 (@BrookeDot)
  • Fixed: Remove unnecessary duplicate IDs in the fetching within Pods::field(). (@sc0ttkclark)
  • Fixed: Name check handling when duplicating pod now works as expected and prevents weirdly named duplicate pod names. (@sc0ttkclark)
  • Tooling: Generate build provenance attestation during deployment for .org zip. #7419 (@johnbillion)

Our GitHub has the full list of all prior releases of Pods: https://github.com/pods-framework/pods/releases

Meta

Ratings

4.8 out of 5 stars.

Add my review

See all reviews

Support

Issues resolved in last two months:

23 out of 23

View support forum

Donate

Would you like to support the advancement of this plugin?

Donate to this plugin