Troubleshooting
Advanced Custom Fields Not Showing on Page: Causes and How to Fix It

Short answer
ACF fields usually do not show because the field group's location rules do not match the screen, the theme never outputs the values, the code uses the field label instead of the field name, or the wrong post ID is read. Check location rules for the editor and template code for the front end.
Key takeaways
- ACF saves data but does not display it on the front end by itself.
- Location rules in one group use AND, separate groups use OR.
- Code must use the field name, not the field label.
- Pass an explicit post ID outside the main loop or for options pages.
- Recent ACF versions escape unsafe HTML and may disable the shortcode by default.
Why are Advanced Custom Fields not showing on your page?
ACF fields usually do not show because the field group's location rules do not match, the theme never outputs the fields, the code uses the wrong field name or post ID, or the field is empty.
Advanced Custom Fields stores extra data on posts, pages and other content. It does not print that data on the front end by itself. Something, usually your theme template, a block or a page builder, has to display it.
That gives you two different problems to check:
| Where fields are missing | Likely cause |
|---|---|
| In the editor screen | Location rules, inactive group, Screen Options |
| On the live page | Template code, field name, post ID, empty values, caching |
Work out which one you have first. The fixes are different.
If you are new to ACF, our guide on how to use Advanced Custom Fields covers setup from scratch.
Do the field group location rules match the page?
Open the field group under ACF > Field Groups and check its Location rules, because fields only appear on screens that match every rule in a group.
Location rules decide where a field group shows in the editor. A rule such as Post Type is equal to Post will not show the group on pages.
Common mistakes:
- The rule targets a post type you are not editing
- A Page Template is equal to rule points to a template the page does not use
- Several rules in one group use AND, so all must match at once
- The rule targets a specific page that was later replaced
Rules in the same group are combined with AND. Rules in separate groups, added with the or button, are combined with OR. If you meant show on posts or pages, use two rule groups.
Also check the field group is active. An inactive group does not appear anywhere.
Is the field group hidden by Screen Options?
In the classic editor, a field group can be hidden through Screen Options, so open that tab at the top of the edit screen and make sure the group is ticked.
In the block editor, look in the editor's preferences for panels. Field groups appear as meta boxes below the content or in the sidebar, depending on the group's position setting.
If the group's position is set to side, check the sidebar rather than below the content. People often miss it there.
Does your theme actually display the fields?
ACF only saves the data, so your theme template, a block or a shortcode must output it, otherwise the values exist in the database but never appear on the page.
This is the most common front-end cause. Adding a field group and filling it in does nothing visible until something displays it.
Ways to display fields:
- Theme template code using the_field or get_field
- ACF Blocks if you build custom blocks with ACF
- Page builder dynamic tags, such as Elementor Pro's ACF dynamic tags
- The ACF shortcode, where enabled
ACF documents the two main functions: get_field returns a value, and the_field prints it.
If you edit theme files, use a child theme. Changes to a parent theme are lost when it updates.
Are you using the right field name?
ACF functions need the field name, not the field label, so check the exact name in the field group, since a small typo returns nothing.
Each field has a Field Label, shown to editors, and a Field Name, used in code. A label of Hero Title might have the name hero_title. Code that asks for Hero Title gets an empty result.
Open the field group, click the field, and copy the name exactly. Names are case-sensitive and use underscores rather than spaces by default.
For fields inside a group, repeater or flexible content field, the way you reach the value changes. Sub fields use the_sub_field or get_sub_field inside a loop over the parent field.
Is the code looking at the right post?
Outside the main loop, or on archive and option pages, ACF may read the wrong post, so pass the correct post ID or the word option as the second argument.
ACF functions default to the current post in The Loop. In headers, footers, sidebars and custom queries, the current post may not be the one you expect.
Fixes by situation:
- Custom WP_Query. Call the_post inside your loop so ACF sees each post, then reset post data afterwards.
- Options page. Pass option as the post ID.
- Taxonomy terms. Pass the term object or a string like term_ followed by the term ID.
- Users. Pass user_ followed by the user ID.
When in doubt, pass the ID explicitly. It removes guesswork.
Is the field value empty or in an unexpected format?
Empty fields print nothing, and fields like images, links and relationships return arrays or objects, so printing them directly shows nothing useful.
First confirm the post actually has a value saved. Open it in the editor and look at the field.
Then check the field's Return Format. An image field can return an array, a URL or an ID. If it returns an array and your code echoes it, you get the word Array or nothing at all.
To see what ACF returns, temporarily dump the value with PHP's var_dump on a staging site. Remove the debug line once you know the format.
Could ACF's HTML escaping hide your content?
Yes, recent ACF versions escape unsafe HTML when the_field prints values, so scripts, iframes or some tags saved in a field may be stripped from the output.
ACF made this change for security. Most text and normal formatting still prints fine. Embeds, script tags and some attributes may be removed.
If a field that used to show embedded code now looks empty, this is a likely cause. Read ACF's release notes and documentation on escaping before changing anything. Allowing raw output can open security holes, so only do it for trusted fields.
Could the ACF shortcode be turned off?
Yes, newer ACF versions turn the ACF shortcode off by default on new installs, so a shortcode that prints nothing may simply be disabled.
If you rely on the shortcode, check ACF's documentation for how to enable it in your version. Where possible, prefer template code, ACF Blocks or a page builder's dynamic tags, which are more flexible.
Shortcodes also do not work in every place. Some page builder fields and widget areas need specific settings before shortcodes run.
Could caching or a conflict be the cause?
Yes, page caches can serve an old version without your new field values, and other plugins or themes can break ACF output.
Clear your caching plugin, host cache and CDN after editing fields. Our guide on how to clear cache in WordPress lists each layer.
If values still do not show, test for a conflict on a staging copy. Our guide on fixing a plugin conflict shows the method.
How do you debug ACF problems quickly?
Turn on WordPress debug logging, check for PHP errors in your template, and test the field with a simple get_field call on a single post.
Steps that find most problems fast:
- Enable debug logging and reload the page
- Read the log for errors in your theme files
- Add a temporary get_field call with an explicit post ID
- Compare the field name in code with the field group
- Check the return format
Our guide on enabling debug mode in WordPress explains the settings. ACF's documentation hub has examples for every field type.
For a broader look at custom fields, including WordPress's built-in option, see how to add custom fields in WordPress.
Frequently asked questions
Why do ACF fields show in the editor but not on the site?
ACF stores the values but your theme must print them. Add template code with the_field or get_field, use a page builder's ACF dynamic tags, or use ACF Blocks. Without one of these, the data never appears on the page.
Why is my ACF field group not showing in the editor?
Check the group's location rules, make sure the group is active, and look in Screen Options or editor preferences. A group positioned in the sidebar is also easy to miss.
Why does get_field return null?
The field name may be wrong, the post may have no saved value, or the code is reading a different post. Use the exact field name and pass the post ID explicitly to test.
Why does my ACF image field show Array?
The image field's return format is set to array, and your code printed it directly. Use the array's url key, or change the return format to URL in the field settings.
Does the ACF shortcode still work?
It can, but newer ACF versions disable it by default on new installs for security. Check ACF's documentation for how to enable it, or use template code or dynamic tags instead.
Sources
- Advanced Custom Fields plugin WordPress.org Plugins
- get_field() Advanced Custom Fields
- the_field() Advanced Custom Fields
- The Loop WordPress Developer Resources
- var_dump PHP Manual
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


