Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

Advanced Custom Fields Pro Not Showing: Causes and How to Fix It

Advanced Custom Fields Pro Not Showing: Causes and How to Fix It

Short answer

Advanced Custom Fields Pro usually seems missing because a field group's location rules do not match the screen, the group is inactive, or the block editor has its panel turned off. If values are missing on the live site, your template is not calling get_field or is reading the wrong post.

Key takeaways

  • Name the symptom first: missing plugin, PRO fields, field group or front-end value.
  • Location rules and the Active toggle cause most missing field groups.
  • The block editor puts ACF groups at the bottom and can hide them in Preferences.
  • Front-end values need get_field or the_field in a template.
  • Newer ACF versions escape unsafe HTML output from the_field.

Why is Advanced Custom Fields Pro not showing?

ACF Pro usually seems missing because a field group's location rules do not match the screen, the field group is inactive, the editor has hidden the meta box, or your template never outputs the value.

The phrase not showing covers several different problems. It helps to name yours before you start fixing things:

  • The ACF menu or ACF Pro plugin itself is missing from the dashboard.
  • PRO field types such as Repeater or Flexible Content are missing.
  • A field group does not appear when you edit a post or page.
  • Fields appear in the editor, but values do not show on the live site.

Each has different causes. The sections below go through them in the order most people hit them.

Before you change anything, take a backup. Some fixes involve deactivating plugins or editing theme files.

Why is the ACF Pro plugin or menu missing?

The ACF menu disappears when the plugin is deactivated, when a failed update removed its folder, or when your user role does not have permission to manage fields.

Go to Plugins > Installed Plugins and look for Advanced Custom Fields PRO. If it is listed but inactive, activate it.

If it is not listed at all, the plugin folder may be gone. This can happen after a failed update or a migration that skipped some plugins. Download the latest ACF PRO zip from your account on the ACF website and upload it again.

The ACF settings menu only shows to users who can manage options, usually administrators. If you are logged in as an editor, ask an administrator to check.

A theme or plugin can also hide the menu on purpose using the acf/settings/show_admin filter. Agencies sometimes do this on client sites. Search your theme's functions file for that filter if the plugin is active but the menu is gone.

Why are PRO field types not available?

PRO fields like Repeater, Flexible Content, Gallery and Clone are missing when the free Advanced Custom Fields plugin is running instead of ACF PRO, or when the PRO license needs attention.

ACF PRO includes everything in the free version. When you activate PRO, it should deactivate the free plugin automatically, because the two cannot run together.

Check the plugin list again. If you only see Advanced Custom Fields without PRO, you are on the free version from the WordPress.org plugin directory. Install the PRO zip to get those field types.

Next, check the license screen in the ACF menu. If the license key is missing or expired, ACF PRO shows an admin notice. The vendor's current terms decide what keeps working without an active license, so read the notice and the ACF account page carefully.

On staging or local copies, the license may be tied to the production URL. Activate it on the copy, or follow ACF's guidance for development sites.

Why does the field group not appear on the edit screen?

A field group stays hidden when its location rules do not match the post type, template or user you are editing, or when the group is switched to inactive.

Open ACF > Field Groups and edit the group. Check these settings:

  1. Active: the group must be switched on. Inactive groups never show.
  2. Location rules: read each rule. Post Type is equal to Post will not show on pages or products.
  3. AND versus OR: rules inside one group are AND conditions. Separate rule groups are OR conditions.
  4. Page template rules: if the rule checks for a template, the page must actually use that template.

A common mistake is a rule like Page Template is equal to Contact on a page that still uses the default template. The group only appears after you pick that template and update or reload.

Location rules for taxonomy terms, user profiles, menus and options pages work the same way. The group only appears on that exact screen.

ACF's resources section documents each location rule and field type.

Is the block editor hiding your fields?

Yes, it often is, because the block editor shows ACF field groups as meta boxes at the bottom of the screen, and these panels can be collapsed or turned off in Preferences.

Scroll to the very bottom of the editor. ACF groups set to Normal or High position appear under the content in a collapsible area.

If the panel is not there, open the three dot menu, choose Preferences, and check the Panels section. Meta boxes from plugins are listed there and can be toggled on.

Groups set to Side position appear in the settings sidebar on the right, below the document settings.

If you use the classic editor, open Screen Options at the top right of the edit screen and make sure your field group is ticked.

Could a sync or code issue be hiding the field group?

Yes, field groups loaded from local JSON or registered with PHP may not appear in the admin list, and JSON groups can show as Sync available until you sync them.

ACF can save field groups as JSON files in an acf-json folder inside your theme. This is called local JSON, and it is popular for version control.

If you deploy a theme with newer JSON files, the admin may show a Sync available notice. Click it to sync the changes into the database.

Field groups registered in PHP with acf_add_local_field_group() work on edit screens, but you cannot edit them in the admin. If someone tells you a group exists but you cannot see it in the list, search the theme and plugins for that function.

Switching themes can also remove field groups if they lived only in the old theme's acf-json folder or functions file.

Why do field values not show on the front end?

Values usually fail to show on the front end because the template never calls get_field() or the_field(), the field name is wrong, or the code is looking at the wrong post.

ACF stores data, but your theme decides where to print it. A new field does nothing on the live site until a template or block outputs it.

Check these common causes:

  • Field name versus label: code must use the field name, such as hero_title, not the label Hero Title.
  • Wrong post ID: outside the main loop, pass the post ID as the second argument.
  • Options page values: use get_field( 'name', 'option' ) for fields on an ACF options page.
  • Return format: an image field set to return an array prints nothing useful if you echo it directly.
  • Empty values: the post may have been saved before the field existed, so it has no value yet.

The get_field documentation shows the correct arguments for posts, terms, users and options.

$title = get_field( 'hero_title', get_the_ID() );
if ( $title ) {
    echo esc_html( $title );
}

Use var_dump( get_field( 'hero_title' ) ); temporarily to see what ACF returns. The PHP var_dump manual explains the output. Remove the line once you know the answer.

Why does HTML inside an ACF field not show?

Newer ACF versions escape unsafe HTML when you use the_field() or ACF shortcodes, so tags like script or iframe can be stripped from the output.

This change arrived as a security fix in ACF 6.2.5. If an embed code or form snippet stopped showing after an update, escaping is the likely reason.

The safer fix is to use a field type that suits the content, such as the oEmbed field for videos. ACF's documentation explains the escaping change and the filters that control it.

Only allow raw HTML from fields that trusted administrators fill in. Escaping exists to stop stored scripts from untrusted users.

Could a plugin, theme or cache be the cause?

Yes, conflicts and caching are common causes, especially after updates, so test with other plugins disabled and caches cleared before you change field settings.

Page builders often need their own setup to show ACF data. Dynamic tags in some builders are a paid feature, and a builder template may override the theme file you edited.

Caching can also hide fresh values. Clear your page cache, object cache and CDN after editing fields. Our guide on clearing cache in WordPress covers the usual places.

To rule out a conflict, follow our plugin conflict guide. Deactivate plugins one at a time on a staging copy, keeping ACF PRO active.

If the edit screen shows a PHP error or turns blank, turn on debug mode and check the log. The WordPress debugging handbook explains each debug constant.

Which fix matches your symptom?

Match what you see to the most likely cause first, then work down the list if that does not solve it.

SymptomMost likely causeFirst fix
ACF menu missingPlugin inactive or hidden by filterActivate plugin, check show_admin filter
No Repeater or Flexible ContentFree version activeInstall ACF PRO
Group missing on edit screenLocation rule mismatch or inactive groupReview rules and Active toggle
Group missing in block editorPanel turned offEnable it in Preferences > Panels
Group missing from admin listLocal JSON or PHP registrationSync JSON or find the PHP code
Value missing on live siteTemplate not outputting fieldAdd get_field to the template
Embed HTML strippedOutput escapingUse oEmbed field or review ACF escaping docs

How do you stop ACF fields disappearing again?

Keep field groups in version control with local JSON, update on staging first, and document which templates output which fields.

Small habits prevent most repeat problems:

  • Save field groups to an acf-json folder in a child theme.
  • Test ACF updates on staging before the live site.
  • Keep your license active on production so updates keep arriving.
  • Name fields clearly and consistently, like section_heading.

If you are newer to ACF, our guide on how to use Advanced Custom Fields covers building field groups and printing values from scratch.

For a lighter approach without a plugin, see how to add custom fields in WordPress.

Frequently asked questions

Why can I not see Repeater fields in ACF?

Repeater, Flexible Content, Gallery and Clone are PRO field types. If you only have the free Advanced Custom Fields plugin, they will not appear. Install and activate ACF PRO, which replaces the free plugin and adds those field types.

Why does my ACF field group not show on pages?

Check the location rules. A rule such as Post Type is equal to Post only targets posts. Add a rule for pages, or change the rule, and make sure the group is set to active. Then reload the page editor.

Where do ACF fields appear in the block editor?

Field groups with Normal or High position appear in a panel at the bottom of the editor, under the content. Side position groups appear in the right sidebar. If neither shows, enable the panel under Preferences in the editor menu.

Why do my ACF values not show on the website?

ACF saves values, but your theme must print them. Add get_field or the_field to the right template, use the field name rather than the label, and pass the post ID when you are outside the main loop.

Does an expired ACF PRO license break my site?

Check ACF's current licensing terms, as they decide what continues to work. An inactive license stops updates and shows an admin notice. Keep the license active on production so you receive security fixes.

Sources

  1. ACF resources Advanced Custom Fields
  2. get_field() Advanced Custom Fields
  3. Local JSON Advanced Custom Fields
  4. Advanced Custom Fields plugin WordPress.org
  5. Debugging in WordPress WordPress Developer Resources

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.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.