How to Bulk Edit ACF Fields in WordPress Posts and Custom Post Types

You can bulk edit ACF fields in WOLF without any ACF add-on: Advanced Custom Fields keeps every value as an ordinary custom field (post meta) of the post, and WOLF edits the meta of posts, pages and custom post types. What needs attention is the format. Each ACF field type stores its value in its own way, and that format decides which view you choose in WOLF and what you type into a cell. Below is how ACF stores values, how to turn the fields into columns, the right settings for every common field type, and why a field sometimes cannot be found.

How ACF stores field values

When a post with a field named price is saved, ACF writes two rows to the post's meta:

• price holds the value, for example 1200;
• _price holds the field key, for example field_650c1a2b3d4e5: a reference that tells ACF which field definition the value belongs to.

WOLF edits the first row. Its meta key is the Field Name from the field group, not the Field Label and not the field_ key. Three cases change the name or the place:

• Fields inside a Group are stored as group name, underscore, field name: hero_title.
• Repeater and Flexible Content sub fields get one key per row: team_0_name, team_1_name, while the parent key team records the rows: their number for a Repeater, the list of layouts for Flexible Content. You can edit an existing row across many posts, for example the first row with team_0_name, but you cannot add or remove rows: ACF reads only as many rows as the parent key says.
• Options pages, taxonomy terms and users keep their ACF values in the options, term meta and user meta tables. These are not post meta, so they are not available in WOLF.

Add ACF fields as columns

1. Open a post where the ACF fields are filled in and saved, and note its ID (the number after post= in the address).
2. In WOLF, select the post type in the post type switcher, open the Meta Fields tab, enter the ID under Get meta keys from any post by its ID and click Get.
3. The list shows every meta key of that post: each ACF field twice (price and _price) plus WordPress's own keys such as _edit_lock. Delete what you do not need, including the underscore copies of the ACF fields.
4. Give each remaining key a readable title, choose its view and type from the table below, and click Save meta fields.
5. In the Settings tab, find the new columns with the columns finder, enable them and click Save all settings.

If you know the field name, you can also enter it under Add Custom key by hands. The Meta Fields documentation describes the tab in detail.

Which view and type to use for each ACF field type

Choices: type the value, not the label

Choices in ACF are written as red : Red. The part before the colon is stored, the part after it is only shown. Enter red in WOLF. A value that is not in the list of choices is saved anyway, but the ACF edit screen then shows nothing selected.

Dates: do not use the calendar view

ACF stores a Date Picker value as Ymd, whatever display format you chose: 9 October 2026 is 20261009. WOLF's calendar view works with Unix timestamps, so it would show such values as dates in 1970 and save a timestamp instead of Ymd. That breaks every query and sort order that relies on the Ymd format, such as a list of upcoming events. Use textinput with type number and type dates as 20261009. The number type gives you a from/to filter, so 20261001 to 20261031 finds every post dated in October. Do not use increase by value on these numbers: 20261031 plus 1 is not a date. Date Time and Time Picker values are edited as text in exactly the stored format.

Images, files, galleries and relationships are IDs

An Image or File field stores only the attachment ID, so the column shows a number and there is no file picker in the cell. To change the file, enter the ID of another attachment: in the Media Library it is the number after item= (grid view) or post= (list view) when you open the file. Posts, pages and users in Post Object, Relationship and User fields work the same way.

For an ACF Gallery choose the array view, not WOLF's own gallery view. The gallery view writes a comma-separated list such as 12,34,56, while ACF expects a serialized list and does not read a comma-separated string as a gallery.

Lists of values in the array popup

The array view shows a button in the cell that opens a popup with one row per item: a key and a value. For ACF lists the keys are 0, 1, 2 in order and the values are option values or IDs. Add an item with Append array key/value, give it the next number as key, and click Apply. In the Bulk Edit tab the list you compose replaces the field on every selected post; it does not add one item to the lists that are already there. More in bulk editing serialized meta data.

Filter and bulk edit ACF fields

Enabled meta columns appear in the Filters and Bulk Edit tabs like built-in fields:

• Text fields filter with LIKE, EXACT (=), NOT EXACT (!=), NOT LIKE, Empty and NOT Empty, and take new, append, prepend and replace in bulk.
• Number fields filter by a from/to range and take set new, increase by value, decrease by value, increase by % and decrease by %.
• True / False fields filter and bulk edit as Yes/No.
• Array fields filter as text against the stored list. Search with LIKE for the option value in double quotes, "red", to find the posts where that option is selected without also matching reddish.

To copy one field into another, use the {meta:field_name} syntax described in copying data between meta fields. Every change is recorded and can be reverted in the History tab.

Filling a field on posts that never had it

A typical bulk job is filling a newly added field on hundreds of existing posts. Those posts were never saved with the field, so they have no _price reference row. WOLF writes the value correctly and the ACF edit screen shows it, but get_field() in the theme cannot link the value to its field definition and returns it unformatted. For text and numbers that changes nothing; for fields with a Return Format (dates, images, files, galleries, post objects) the theme gets the raw value, such as an image ID instead of an image array or URL.

WOLF can add the references too:

1. Add _price as a meta field with view textinput and type string, and enable its column.
2. Copy its value, the field_… key, from any post that was saved with the field.
3. Filter _price by Empty and bulk edit it with new and the copied key.

ACF field not found or not showing: checklist

• The sample post does not have the field yet. ACF writes a field, even an empty one, only when a post is saved, and Get lists only keys that exist on that post. Use a post saved after the field was added, or add the name by hand.
• Wrong name. You used the Field Label or the field_ key instead of the Field Name, or a sub field without its group or repeater prefix.
• Not post meta. The field belongs to an options page, a taxonomy term or a user.
• Another post type. With Separate columns and meta for post types set to Yes, meta fields belong to the post type that was selected when you added them.
• Not enabled. The field was saved in Meta Fields but its column was not enabled in Settings.
• Numbers or "Array" in the cell. That is how the field is stored: IDs for files and relations, the array view for lists.

If a field still behaves differently from the table above, open a topic on the WOLF support forum with the field type, its name and the ID of a post that has a value.