Show More Than 30 Custom Fields in WordPress

Yes, you can show more than 30 custom fields in WordPress, but the limit is not a hard WordPress restriction — it is a display default in the admin screen and a common threshold in some page builders. This article explains exactly where the 30-field limit comes from, how to raise or bypass it, and the best ways to display many custom fields on your site.

Where the 30-Field Limit Comes From

WordPress itself does not impose a maximum number of custom fields you can create or store. The database can hold thousands of post meta entries per post. The “30” you see usually appears in two places:

• Admin edit screen: By default, the “Custom Fields” meta box in the post editor shows only the most recent 30 custom fields. This is a UI convenience, not a data limit.
• Page builders and plugins: Some page builders (like older versions of Elementor or certain ACF field group configurations) display only 30 fields in their dynamic tag dropdowns or query loops. Again, this is a UI setting, not a server limit.

If you are using the classic editor, you can click “Screen Options” in the top-right corner and change the number of custom fields shown per page (up to 999). The block editor (Gutenberg) does not have a built-in custom fields meta box by default, but you can enable it via the three-dot menu → Preferences → Panels → “Custom fields”.

How to Display More Than 30 Custom Fields on the Front End

Showing custom fields on the front end (your actual website) is a different task from editing them in the admin. If you are using a theme template or a plugin like ACF (Advanced Custom Fields), you can display an unlimited number of fields. Here are the most common methods:

1. PHP in your theme template: Use get_post_meta() or ACF’s the_field() to echo each field. You can loop through an array of field keys.
2. ACF Repeater or Group fields: Instead of creating 40 separate top-level fields, group them into a repeater. This keeps the admin screen clean and lets you output all rows with a simple loop.
3. Custom query with WP_Query: If you are listing posts that have a certain meta value, use meta_key and meta_value in WP_Query. The number of meta keys per post is irrelevant here.
4. Shortcode or block plugin: Plugins like “Custom Fields Shortcode” or ACF’s dynamic block allow you to insert any field by name, without a 30-item dropdown.

If you are using a page builder and the dynamic tag dropdown only shows 30 fields, the fix is usually to switch to “Custom Field” and type the field name manually, or to use a shortcode/block that accepts a field key.

Why the 30-Field Limit Exists in Some Tools

The 30 number is not a technical necessity. It is a design choice to keep interfaces fast and uncluttered. When a page builder scans all post meta for a post, it might find hundreds of fields (including internal ones like _edit_lock). Showing all of them in a dropdown would make the list unusable. So developers set a cap of 30 for the “recently used” or “most common” fields.

This can frustrate users with large data sets, but the solution is almost always to use a dedicated plugin that handles many fields gracefully. ACF, for example, does not limit the number of fields you can create in a field group. The dropdown in ACF’s “Dynamic Tags” might show a scrollable list, but it is not capped at 30.

How to Choose the Right Method for Your Site

Your choice depends on your technical comfort and the number of fields you need to display:

• 1–30 fields: Use the built-in custom fields meta box or a simple plugin like “Custom Fields Shortcode”.
• 30–100 fields: Use ACF (free version) with a repeater or group, or write a small PHP snippet in your theme’s functions.php.
• 100+ fields: Consider a custom post type with ACF field groups, or a database plugin like “WP Coda” that lets you manage meta in bulk.

If you are not comfortable editing PHP, a plugin like ACF is the safest and most maintainable path. It gives you a clean UI and avoids hardcoding field keys in templates.

Common Problems and How to Avoid Them

When displaying many custom fields, you might run into these issues:

• Performance: Each get_post_meta() call is a database query. If you call it 100 times on a page, it can slow things down. Use get_post_meta() once to fetch all meta for a post: get_post_meta( get_the_ID() ) returns an array of all fields.
• Field name collisions: Starting a meta key with an underscore (_) hides it from the default custom fields meta box. This is intentional for internal fields, but if you accidentally prefix your fields with _, they won’t appear in the admin dropdown.
• Serialized data: If you store an array in a single meta field (e.g., ACF repeater), you cannot query it with meta_value in a simple WHERE clause. Use ACF’s built-in query functions or store each sub-field separately.
• Page builder caching: Some page builders cache the field list. After adding a new field, clear the cache or reload the editor.

Comparing the Built-in Custom Fields vs. ACF

WordPress’s built-in custom fields are perfect for a few fields, but they have limitations:

• No UI for field types: You have to enter the field name exactly, and there is no date picker, image upload, or select dropdown.
• No repeatable groups: You cannot easily create a list of entries without using a plugin or custom code.
• Admin screen shows only 30: As discussed, the default meta box is limited.

ACF (or similar plugins like Pods or Meta Box) solves all these problems. It provides a field group builder, repeaters, flexible content, and a clean admin interface. The free version of ACF is enough for most sites.

Cost and Safety Considerations

Displaying more than 30 custom fields is free if you use the built-in WordPress features or the free version of ACF. Premium plugins like ACF Pro (which adds repeaters and flexible content) cost money, but they are not required for simply showing many fields — you can achieve the same with custom code.

Safety-wise, always validate and sanitize custom field data before outputting it. Use esc_html() or esc_attr() when echoing, especially if the field contains user input. If you are writing PHP in your theme, use a child theme so updates don’t overwrite your code.

Frequently Asked Questions

Can I show more than 30 custom fields in the WordPress admin?

Yes, in the classic editor, go to Screen Options and increase the number of custom fields shown per page. The block editor does not have this option, but you can install a plugin like “Custom Fields Suite” to get a better admin interface.

Why does my page builder only show 30 custom fields in the dropdown?

Page builders often limit the dynamic tag list to 30 for performance. You can usually type the field name manually instead of selecting it, or use a shortcode/block that accepts a field key.

Does having many custom fields slow down my WordPress site?

Not necessarily. The number of fields per post has little impact on speed. What matters is how many queries you run. Fetching all meta at once with get_post_meta( get_the_ID() ) is efficient.

What is the best free plugin to manage many custom fields?

Advanced Custom Fields (free) is the most popular. It allows unlimited fields and provides a clean interface. Pods and Meta Box are also good alternatives.

Can I use custom fields without a plugin?

Yes, you can use the built-in custom fields meta box in the classic editor. For front-end display, you need to edit your theme template with PHP functions like get_post_meta().

Is there a limit to the total number of custom fields in the database?

No, WordPress can store millions of meta entries. The only practical limit is your server’s database size and performance.

Related

• Load the Truck Admin Abuse Schedule?
• Azure DevOps Server: What It Is & How to Use It
• 301 vs 302 Redirects: Which to Use on WordPress