Quickfields Bulk Editor for ACF: Spreadsheet-Style Bulk Editing for WordPress Pages
If you maintain dozens of WordPress pages that share the same Advanced Custom Fields groups, opening each page in the classic editor (or ACF meta box) one by one is slow and error-prone. A content sprint that should take an afternoon stretches into days when every hero headline, CTA label, and meta blurb lives in a separate admin screen. Quickfields Bulk Editor for ACF turns that workflow into a spreadsheet: pages as rows, ACF fields as columns, with autosave as you type.
The free plugin is open source on GitHub:
https://github.com/Sameer559-code/Quick-Fields-Bulk-Editor-for-ACF
It is built and maintained by Sam Syntax. It is not affiliated with or endorsed by Advanced Custom Fields.
The problem Quickfields solves
ACF is excellent at structuring page data — hero titles, service blurbs, location addresses, pricing tiers, testimonial snippets. But the default editing experience is page-centric: open Page A, scroll to the field group, edit, save, repeat for Page B through Page Z. That model breaks down when:
- You launch a rebrand and need consistent copy updates across 30+ landing pages
- SEO or legal asks for a terminology change site-wide in custom fields
- A new field group is added and you need to populate initial values quickly
- Editors compare values side-by-side but WordPress only shows one page at a time
Spreadsheet-style bulk editing is not a novel idea — teams have hacked together CSV imports, custom admin tables, or WP-CLI scripts for years. Quickfields packages the spreadsheet mental model into a native wp-admin experience with projects, autosave, and ACF-aware field detection so you do not maintain one-off tooling per client.
Who this plugin is for
You will get the most value if you:
- Run marketing or location pages that share the same ACF field groups
- Need to update headlines, blurbs, CTAs, or SEO-adjacent copy across many pages at once
- Want a project-based workspace (group related pages, open one sheet, finish the job)
- Prefer not to build a custom admin UI or import scripts for every content sprint
- Work with agencies or in-house teams where non-developers own content but developers own ACF schema
If your content lives mostly in the block editor body and you barely use custom fields, this is not your tool — stick with core bulk edit or a page builder. Quickfields is specifically for ACF field values on WordPress pages.
When NOT to use Quickfields
- Repeater / flexible content heavy sites — complex nested fields are not editable in the sheet yet
- Post types other than pages — the current version targets pages; custom post type support may come later
- One-off single page edits — opening the classic editor is faster for a single change
- Sites without ACF — the plugin requires Advanced Custom Fields to be active
What you get in the free plugin
- Unlimited projects — group the pages you want to edit together
- Page picker — assign WordPress pages to a project
- Spreadsheet sheet view — edit text and textarea fields in place
- Field-group tabs — switch between ACF groups without leaving the sheet
- Image previews — read-only preview of image field values
- Clear text fields — wipe text across all pages in a project when you need a clean slate
- Autosave — changes persist as you type
Requirements
| Requirement | Version |
|---|---|
| WordPress | 5.8+ |
| PHP | 7.4+ |
| ACF | Free or Pro |
ACF must be installed and active. Quickfields detects fields registered through Advanced Custom Fields only — not raw post meta written outside ACF's API.
Installation from GitHub
- Clone or download the repo into
/wp-content/plugins/:
cd wp-content/plugins
git clone https://github.com/Sameer559-code/Quick-Fields-Bulk-Editor-for-ACF.git quickfields-bulk-editor-for-acf- In Plugins, activate Quickfields Bulk Editor for ACF.
- Confirm Advanced Custom Fields is active.
- Open Quickfields Bulk Editor in the admin menu and create your first project.
On Bedrock installs, add the plugin via Composer path repository or clone into web/app/plugins/ following your project's plugin layout. See Roots Bedrock for Composer-managed WordPress structure.
Typical workflow (step by step)
- Create a project — name it after the content sprint (e.g. "Q3 Service Pages Rebrand").
- Assign pages — use the page picker to add all related landing pages.
- Open the sheet — each row is a page; columns map to ACF text and textarea fields.
- Edit cells in place — tab between cells like a spreadsheet; autosave writes to the database.
- Switch field-group tabs — when pages have multiple ACF groups, tabs keep the grid manageable.
- Spot-check images — read-only image previews show missing or wrong assets without leaving the grid.
- Clear and repopulate — use "clear text fields" when you need a blank slate before a full rewrite.
Supported field types (this version)
| Type | Support |
|---|---|
| Text | Editable |
| Textarea | Editable |
| Image | Read-only preview |
| Repeater | Not supported |
| Flexible Content | Not supported |
| Relationship / Post Object | Not supported |
Repeaters, flexible content, relationships, and other complex types are not supported yet. Keep those edits in the normal ACF UI until Pro or a later free release covers them.
Quickfields vs alternatives
| Approach | Pros | Cons |
|---|---|---|
| Quickfields sheet | Native admin UI, autosave, no CSV prep | Text/textarea focus in free tier |
| ACF + WP All Import | Powerful for migrations | CSV setup overhead per sprint |
| WP-CLI custom scripts | Automatable in CI | Developer-only, no visual grid |
| Per-page ACF editing | Full field type support | Slow at scale |
Free vs Pro
The free GitHub plugin fully covers bulk text editing. CSV import/export, in-sheet image editing, and clearing image fields ship in the separate Quickfields Pro add-on — they are not paywalled inside the free plugin as fake "locked" buttons. Use free for day-to-day copy sprints; upgrade when you need CSV or image workflows.
Gotchas and best practices
- Field group location rules — only fields that ACF shows on a given page appear as columns; if a page does not match a location rule, that group's columns may be empty for that row.
- Autosave is per-cell — there is no "save all" panic button because saves happen continuously; still avoid closing the browser mid-keystroke on slow connections.
- Administrator access only — users need
manage_options; editors without that capability cannot open Quickfields. - Projects are not content — deleting a project removes the grouping, never the underlying page data.
- Test on staging first — bulk edits are real database writes; run a content sprint on staging before production.
FAQ
Does deleting a project delete page content? No. Projects are only groupings. Page content stays untouched.
Who can use it? Users with manage_options (typically administrators).
Does it work with ACF Pro? Yes — both ACF Free and ACF Pro are supported for detected field types.
Is it on WordPress.org? Check the repo README and readme.txt for the current distribution path; the source of truth for development is the GitHub repository.
Can I contribute? Issues and pull requests are welcome on GitHub. Report bugs with WordPress version, ACF version, and steps to reproduce.
How this fits a modern WP stack
Quickfields sits next to the "scaffold then ship" WordPress toolchain many teams already use:
- Theme scaffold: Roots Sage
- Project layout: Roots Bedrock
- Plugin structure: WordPress Plugin Boilerplate
- Debugging: Query Monitor
- Headless API: WPGraphQL
Once the site architecture is solid, content ops still need a fast way to update ACF values at scale — that is the gap this plugin fills. Developers ship the theme and field schema; editors finish the copy in a sheet instead of forty separate admin tabs.
Get started
Clone the repo, activate it beside ACF, create a project, and open the sheet:
github.com/Sameer559-code/Quick-Fields-Bulk-Editor-for-ACF
Want CSV and image editing? See Quickfields Pro. Full walkthrough: this post.