WordPress Custom Fields Not Showing: The Best Fix (2026)

You’ve added custom field data to a post, saved it, checked the front end, and… nothing shows up. WordPress custom fields not showing is almost always a template code issue rather than a data-saving problem. The value is usually sitting in the database just fine, but nothing on the front end is set up to actually display it. Here’s how to diagnose and fix it, whether you’re using Advanced Custom Fields (ACF) or WordPress’s native custom fields.

Step 1: Confirm the Data Is Actually Saved

Before troubleshooting display code, rule out the simpler possibility first.

  1. Open the post in the editor
  2. Scroll down to check if the custom field value is still there and saved correctly
  3. If using ACF, confirm you’re looking at the correct field group and that it’s actually assigned to this post type

If the value isn’t saving at all (rather than just not displaying), the issue is different check the field’s location rules (ACF) or confirm you’re not hitting a plugin conflict during save.

Step 2: Confirm Your Template Is Actually Calling the Field

This is the most common cause by far. Custom fields don’t display automatically anywhere your theme’s template file needs specific code to pull and print that value.

For native WordPress custom fields, the template needs:

php
<?php echo get_post_meta( get_the_ID(), 'your_field_name', true ); ?>

For Advanced Custom Fields (ACF), the equivalent is:

php
<?php the_field( 'your_field_name' ); ?>

or, if you want the raw value instead of directly printing it:

php
<?php $value = get_field( 'your_field_name' ); ?>

If this code simply isn’t present anywhere in your template file, the field will never display, no matter how correctly the data was saved.

Step 3: Double-Check the Field Name Matches Exactly

Field name mismatches are a very common, easy-to-miss cause. The name used in your template code must match exactly, including case sensitivity and underscores versus hyphens the field’s actual name/key as defined when it was created.

  • In ACF, check the exact Field Name (not the more human-readable Field Label) in the field group settings
  • A field labeled “Price” might actually have the field name product_price using price in your code instead would silently fail to display anythingwordpress custom fields not showing acf field group settings

Step 4: Confirm You’re Editing the Correct Template File

If your theme uses different template files for different post types or page layouts, you might be editing (or checking) the wrong file entirely.

  • Confirm which template file is actually being used for the specific post/page you’re testing on this can vary based on post type, page template selection, or theme hierarchy rules
  • If you’re using a page builder like Elementor, confirm whether custom fields need to be added through a specific dynamic content widget rather than the underlying PHP template at all

Step 5: Check ACF Field Group Location Rules

If you’re using ACF and the field editor doesn’t even show up when creating/editing a post, the field group’s location rules likely don’t include that specific post type or page.

  1. Go to Custom Fields > Field Groups in your dashboard
  2. Open the relevant field group
  3. Check the Location rules at the bottom confirm they’re set to show on the post type, specific page, or template you’re actually working with

Step 6: Check for Empty Value Handling

Sometimes a field displays “nothing” not because the code is broken, but because the field genuinely has no value for that specific post, and there’s no fallback text configured.

php
<?php
$value = get_field( 'your_field_name' );
if ( $value ) {
    echo $value;
} else {
    echo 'No value set';
}
?>

Adding this kind of conditional check helps you quickly confirm whether the issue is a genuinely empty field versus a broken display call.

Step 7: Clear Your Cache

If you’ve fixed the template code but the front end still doesn’t reflect the change, a caching plugin may be serving an old cached version of the page.

  • Clear your caching plugin’s full cache
  • Clear CDN cache if applicable
  • Test in an incognito window to confirm

Diagnostic Quick Reference of wordpress custom fields not showing

Symptom Likely Cause Fix Step
Field editor doesn’t appear at all when editing a post ACF location rules don’t match this post type Step 1
Field saves fine, nothing shows on front end Template missing display code Step 2
Display code exists, still shows nothing Field name mismatch Step 3
Works on some pages/posts, not others Wrong template file being edited Step 4
Code fixed, but front end unchanged Caching Step 5

wordpress custom fields not showing template code

Frequently Asked Questions of wordpress custom fields not showing

Why does my custom field show in the editor but not on the live page? This is the classic symptom of Step 2 the data is saved correctly, but your template simply doesn’t have the code needed to display it anywhere on the front end.

Is there a difference between ACF and native WordPress custom fields for this issue? The underlying cause (missing template code or field name mismatch) is the same for both ACF just uses slightly different function syntax (the_field() / get_field()) compared to native fields (get_post_meta()).

Can a plugin conflict cause custom fields to stop displaying? It’s less common than a template code issue, but possible particularly if a caching or optimization plugin is stripping or modifying template output unexpectedly. Rule out template code and field name issues first before suspecting a plugin conflict.

Do I need to know PHP to fix this myself? Understanding and editing the template display code (Steps 2-3) does require basic PHP comfort. If you’re using ACF with a page builder’s dynamic content feature instead of custom template code, the fix is often more visual/settings-based and doesn’t require coding.

Final Thoughts for wordpress custom fields not showing

WordPress custom fields not showing almost always comes down to either missing display code in your template or a field name mismatch between your field settings and your code the data itself is usually saved correctly. Work through the diagnostic table above to identify which applies to your specific case. If you’d rather have custom fields set up and displaying correctly without the troubleshooting, get in touch here and I’ll handle it directly.

Recommended Tools & Plugins

Every tool below is something I actually use on client projects, not a random affiliate list.

  • Hosting: Cloudways  fast, managed WordPress hosting
  • Theme: GeneratePress  lightweight, built for speed
  • Page Builder: Elementor Pro  the builder behind most of my client sites
  • Forms: WPForms  reliable, beginner-friendly form builder
  • Directory/Listing Sites: Directorist  for business directory or listing projects
  • Elementor Add-ons: Crocoblock (JetEngine)  for dynamic, database-driven sites
  • Keyword Research: Mangools is the SEO tool I use for keyword research
  • Backups: UpdraftPlus  never launch a site without a backup plan
  • Course Platform: Tutor LMS is the LMS plugin
  • Free Speed Test: Google PageSpeed Insights is the free tool I use to check real Core Web Vitals data

Leave a Reply

Your email address will not be published. Required fields are marked *