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 Not Saving Data: A Simple Guide

Advanced Custom Fields Not Saving Data: A Simple Guide

Short answer

Advanced Custom Fields usually stops saving when a long form hits the PHP max_input_vars limit, the field group location rules do not match, two fields share a name, or custom code overwrites values. Raise the input limit, review field group settings, then test for plugin, theme and block editor conflicts.

Key takeaways

  • Lost repeater rows usually mean the max_input_vars limit is too low.
  • Location rules must match the post type or template you edit.
  • Duplicate or reserved field names overwrite values.
  • Save hooks in custom code can wipe new values.
  • If the admin shows new values but the site does not, clear caches.

Why is Advanced Custom Fields not saving data?

ACF usually fails to save because the form submits more fields than PHP allows, the field group location rules do not match, field names clash, or a plugin or custom code interferes with saving.

The symptom looks the same in every case. You fill in your fields, click Update, and the page reloads with empty fields or old values. Sometimes only some fields save, which is a strong clue.

When only the later fields in a long form are lost, the cause is almost always a server limit. When nothing saves at all, look at the field group, the editor and custom code. This guide covers each cause in the order we would check them.

Before you change anything, take a backup or work on a staging copy. Our guide on setting up a staging site shows how.

Is the PHP max_input_vars limit cutting off your fields?

Yes, this is the most common cause on pages with repeaters or flexible content; PHP silently drops form inputs beyond the max_input_vars limit, so the last fields never reach WordPress.

Every field, sub field and row in your edit screen is a separate form input. A repeater with 30 rows of 5 sub fields already sends 150 inputs, plus everything else on the page. PHP's default limit is 1000.

PHP does not show an error when it drops extra inputs. The max_input_vars directive simply truncates the request. ACF only receives the inputs that made it through, so later rows vanish.

Signs this is your problem:

  • Short pages save fine, long pages lose data
  • The newest repeater rows or layouts disappear
  • Removing a few rows makes saving work again

To fix it, raise the limit. You can ask your host, or set it yourself in php.ini, .user.ini or your hosting control panel:

max_input_vars = 5000

Some hosts also run Suhosin or similar hardening, which has its own input limits. After changing settings, check the new value under Tools > Site Health > Info > Server.

Are your field group location rules correct?

Check the location rules on your field group; if they do not match the post type, template or taxonomy you are editing, the fields may appear inconsistently or not save as expected.

Open ACF > Field Groups and edit the group. Under Settings, review Location Rules. A rule like Post Type is equal to Post will not attach the fields to a page or a custom post type.

Rules based on page templates can be tricky in the block editor. If you change the template, the fields may only update after you save and reload. Save the template choice first, then fill in the fields.

Also make sure the field group is active. Inactive groups do not appear, and any values entered through other means will not be managed by them.

Could duplicate or reserved field names break saving?

Yes, two fields with the same name on one screen overwrite each other, and names that clash with WordPress reserved terms can stop values being stored correctly.

ACF saves each value under its Field Name in post meta. If two field groups on the same post both use a field called title or image, the last one wins. Your first value appears to be lost.

Avoid names that WordPress already uses for query variables or post fields. The reserved terms list includes words like name, year, page and author. Using them as field names can cause odd behavior on the front end and in queries.

A safe habit is to prefix field names, such as team_photo instead of photo. If you rename a field, existing data stays under the old name, so plan renames carefully.

Is the block editor causing the problem?

Sometimes; in the block editor, ACF fields in the meta box area save in a second request, and JavaScript errors or blocked REST API calls can stop that request from completing.

The block editor saves post content through the REST API, then saves meta boxes, including classic ACF fields, separately. If that second save fails, the post updates but your fields do not.

Check these points:

  1. Open your browser developer tools and look at the Console tab for errors while saving
  2. Look at the Network tab for failed requests to post.php or the REST API
  3. Run Tools > Site Health and check for REST API warnings

If Site Health reports a REST API problem, fix it first. Our guide on fixing the REST API error in Site Health explains the usual causes, such as security plugins and server rules.

If you use ACF Blocks, remember that block field values are stored inside the block markup, not in normal post meta. They save with the post content, so a block validation error can discard them.

Could custom code or another plugin be overwriting values?

Yes, code hooked to save_post or acf/save_post can overwrite or delete field values, and another plugin may clear meta during its own save routine.

Look for code in your theme's functions.php or in a custom plugin that runs on save. Common mistakes include:

  • Calling update_field() with an empty value on every save
  • Running code on acf/save_post before ACF has saved, then overwriting the new value
  • Using a save_post callback that calls wp_update_post() and creates a loop

ACF documents the right priorities in its acf/save_post reference. Use a priority above 10 to run after values are saved, or below 10 to run before.

Other plugins can interfere too. Import tools, translation plugins, cache plugins and page builders all touch post meta. Test by deactivating them on staging. Our plugin conflict guide walks through the process.

Do validation errors or required fields block the save?

They can; if a required field is empty or a custom validation fails, ACF stops the save and shows a message, which is easy to miss in long forms.

Scroll through the whole edit screen after clicking Update. ACF highlights fields that failed validation in red with a short message.

In the block editor, notices appear at the top of the screen and may disappear quickly. If a front-end form built with acf_form() will not save, check that acf_form_head() runs before any output on the page, as the ACF docs require.

Could caching make it look like data is not saving?

Yes, page caching, object caching or a CDN can keep serving old field values on the front end even though the new values are saved in the database.

Check the edit screen first. If the new values appear there after reloading, the data is saved and the front end is just showing a cached copy.

Clear every cache layer: your caching plugin, any server cache and your CDN. Our guide on how to clear cache in WordPress covers the common tools.

If values show in the admin but never on the page, the issue is display code, not saving. See Advanced Custom Fields not showing on page for that problem.

How do you troubleshoot ACF saving step by step?

Work through a fixed order: confirm whether data reaches the database, check input limits, review the field group, then test for code, plugin and editor conflicts.

SymptomMost likely causeFirst fix
Long repeater loses last rowsmax_input_vars limitRaise the limit to 3000 to 5000
Nothing saves on one post typeLocation rulesFix rules in the field group settings
One field keeps an old valueDuplicate field name or custom codeRename field or check save hooks
Saves in admin, old on siteCachingClear all cache layers
Fields lost only in block editorMeta box save request failedCheck console and REST API

Then follow these steps:

  1. Edit a test post, save a value, and reload the edit screen
  2. Check the value in the database or with a tool that shows post meta
  3. Raise max_input_vars if the form is long
  4. Review location rules and field names
  5. Switch to a default theme and test again
  6. Deactivate other plugins one at a time
  7. Turn on debugging and read the error log

For step 7, see how to enable debug mode in WordPress. PHP warnings in the log often point at the exact function that breaks saving.

How can you prevent ACF data loss in future?

Keep forms lean, use unique prefixed field names, keep ACF updated, and test big field group changes on staging before you edit live content.

Large flexible content layouts are powerful, but they create many inputs. Splitting content across tabs does not reduce the input count, so consider separate field groups or options pages for rarely edited data.

Keep ACF and WordPress current. Our guide on updating Advanced Custom Fields Pro explains the update process for the paid version.

If you are still learning the plugin, how to use Advanced Custom Fields covers field groups, location rules and field names from the start. You can also search the ACF support forums where many saving issues have been answered.

Frequently asked questions

Why do my ACF repeater rows disappear after saving?

Long repeaters create many form inputs, and PHP drops any beyond its max_input_vars limit without warning. Raise the limit in php.ini, .user.ini or your hosting panel, often to 3000 or more, then save again.

What should max_input_vars be for ACF?

There is no single right number. The PHP default is 1000, which large repeaters and flexible content can exceed. Many sites use 3000 to 5000. Raise it until long pages save fully, and check the value in Site Health.

Why does ACF save in the classic editor but not the block editor?

In the block editor, classic ACF field boxes save in a separate request after the post content. JavaScript errors or blocked REST API calls can stop that request. Check the browser console and Site Health for errors.

Can a caching plugin stop ACF from saving?

Caching does not stop data being saved, but it can show old values on the front end. If the edit screen shows the new value after a reload, clear your page cache, server cache and CDN.

Why does one ACF field keep reverting to an old value?

Two fields may share the same field name, or custom code hooked to save actions may overwrite the value. Rename duplicates with a unique prefix and review any save hooks in your theme or plugins.

Sources

  1. Description of core php.ini directives: max_input_vars PHP Manual
  2. acf/save_post Advanced Custom Fields
  3. Reserved Terms WordPress Codex
  4. ACF Support Forums Advanced Custom Fields

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.