What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Use a custom post type when you are creating a distinct kind of content with its own record structure or editing workflow. Use a taxonomy when you need reusable terms to classify content. Use custom fields for properties that belong to an individual record. These tools can work together: a movie can be a post type, its genre a taxonomy, and its release year a custom field.
Custom post type, taxonomy, or custom field?
Think of the content model as three questions: What kind of thing is this? How should it be grouped? What facts describe this particular item?
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Professional WordPress: Design and Development | $6.04 | Buy on Amazon |
| 2 |
|
WordPress Onder De Motorkap: WordPress aanpassen Onder De Motorkap (Dutch Edition) | $24.99 | Buy on Amazon |
| WordPress structure | Use it for | Example |
|---|---|---|
| Custom post type | A distinct kind of content with its own editorial meaning or workflow | Movies, products, projects, or assignments |
| Taxonomy | Reusable classifications or groupings that can apply across records | Movie genres or cook-time ranges |
| Custom field | A structured value describing one particular record | A movie’s release year or poster image |
WordPress Developer Resources explains how these structures complement one another in its guide to post types, taxonomies, and custom fields.
When should you create a custom post type?
Create one when the content is not naturally just a post or page, and treating it as a separate kind of record would make the site easier to manage. A custom post type can have a separate administrative screen and can support features such as titles, editors, thumbnails, comments, statuses, and custom fields, depending on its registration settings.
#1 Best Overall
- Used Book in Good Condition
For example, a site with a catalog of products may benefit from a Products section in the admin rather than mixing product records with blog posts. WordPress’s Plugin Handbook guidance on registering custom post types also uses Movies, Products, Projects, and Assignments as examples.
When should you use a taxonomy?
Use a taxonomy when visitors or editors need to classify records with shared, reusable terms. A genre can classify multiple movies; a cook-time range can group multiple recipes. Taxonomies can be hierarchical, like categories, or flat, like tags. Their term-management interface and behavior are controlled by registration settings.
A taxonomy is usually a better fit than a custom field when the value is a shared classification that people may use to group, browse, or filter multiple records. WordPress’s Theme Handbook overview of categories, tags, and custom taxonomies describes these grouping patterns.
When is a custom field the better choice?
Choose a custom field for a property that describes an individual item rather than serving as a reusable classification. In a movie catalog, release year, director, and poster image may be fields on each movie record. If a value should act as a shared navigation or filtering dimension, consider whether it belongs in a taxonomy instead.
Can a custom post type and taxonomy work together?
Yes. A custom post type can have one or more taxonomies attached to it, while custom fields store details for each record. For example, register Movies as a post type, attach a Genre taxonomy, and store release year and poster image as fields. This separates the kind of record, its reusable classification, and its individual properties.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Questions to settle before choosing
- What is the thing? If it is a distinct record with its own editorial meaning or lifecycle, consider a post type. If it is a label applied to records, consider a taxonomy.
- How will editors work with it? A post type can provide a separate admin screen and selected editing features. A taxonomy provides term management and hierarchical or flat grouping.
- Will the value be reused? Taxonomy terms can classify multiple records and can be attached to more than one object type. A custom field generally describes an individual record.
- How should visitors find it? Decide whether the content should appear in public queries, have a post-type archive or taxonomy term pages, or remain internal. Registration settings determine public display, archives, rewrite behavior, admin UI, navigation menus, and search inclusion; existence alone does not make a type or taxonomy public.
- Should the content survive a theme change? WordPress recommends registering custom post types in a plugin when their content should remain available after switching themes.
Implementation details that prevent avoidable problems
WordPress’s register_post_type() reference says to register a custom post type on the init action. Its key can be no longer than 20 characters. The register_taxonomy() reference sets a 32-character maximum for a taxonomy key and warns about reserved identifiers and query-variable conflicts. Use unique, lowercase, prefixed names rather than generic identifiers.
Register the taxonomy with register_taxonomy() and connect it to the custom post type. The register_post_type() reference recommends declaring the connection with the taxonomies argument so the relationship is recognized consistently in query hooks. Before setting registration arguments, decide whether the content should have public display, front-end queries, archives, rewrite rules, admin menus, navigation-menu support, or search inclusion; these behaviors depend on the chosen settings and their interactions.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
