How to delete metafields in bulk
Removing metafields one at a time is fine for a handful of records. Once you are looking at dozens, hundreds, or many thousands of them, you need a bulk workflow. Metafields Guru gives you three, and the right one depends on two things: how many metafields you are removing and how precisely you can describe them.
Clearing a metafield's value is how you delete it. Every method below works by clearing values and letting the app remove the now-empty metafields when you save or import.
Quick comparison
| Excel-like editor | Bulk editor | Export + import | |
|---|---|---|---|
| Best for | A dozen metafields across mixed resources, no clear pattern | One known metafield (up to 5) across a filtered set of resources | Large clean-ups, entire namespaces, or selections you cannot express as a filter |
| Scale | Up to 50 resources per page, reviewed by hand | Any number of resources per run - no limit | Bounded only by CSV file size |
| You must know | Nothing precise - you filter and eyeball the grid | The exact namespace and key of each metafield | Only the namespace(s) - keys can be anything, including auto-generated ones |
| How you select | Manually, cell by cell | Filter rules (simple or advanced) | Filter at export time, then edit the CSV |
| Review before delete | Full - you see every value | Preview of matched resources | Full - in your spreadsheet editor |
| Undo | Discard before saving - irreversible once saved | Re-import the auto-generated Backup file from History | Re-import the original export file, kept in History |
| Detailed guide | Excel-like editor | With the bulk editor | With data import |
Method 1 - Excel-like editor: point-and-delete a handful
Use it when you need to remove a small number of metafields (roughly up to a dozen) that do not share a clean rule - a few products here, a stray value on one collection, a wrong entry on a single customer.
The Excel-like editor loads your resources into a spreadsheet-style grid. You add the metafield columns you care about, filter or search down to the rows you need, and clear individual cells. Because Shopify does not allow empty metafields, every cell you clear is deleted when you press Save.
- Open Metafields Guru → Excel-like editor and press Open editor.
- Pick the resource type (products, collections, orders, and so on).
- Press Select columns and add the metafields you want to inspect.
- Use search and the advanced filters to narrow the grid down to the resources in question.
- Click a cell and clear it - the ✕ (clear) button on the active cell, or the
Del/Backspacekey. Highlight several cells to clear them at once. - If your selection spans several pages, press Save before turning the page - page navigation is disabled while there are unsaved changes. Save, move to the next page, repeat. Once your changes are saved, the cleared metafields are removed.
The Excel-like editor does not generate a backup. You can discard unsaved changes, but once you press Save the deletion is final. Before a large clean-up, export the metafields so you have something to re-import.
Full walkthrough: Everything you need to know about the Excel-like editor.
Not the tool for thousands of resources (you would page through 50 at a time), or for "delete everything in this namespace" (you still add columns key by key).
Method 2 - Bulk editor: one rule, any number of resources
Use it when you can describe exactly which resources (as a filter) and which metafield (namespace + key) - no matter how many resources match.
The bulk editor filters resources by any criteria you can build - tags, vendor, saved searches, or a full AND/OR condition tree in the advanced filter - and then removes one specific metafield from every match in a single run.
- Open Metafields Guru → Bulk Actions → Bulk Editor.
- Choose the resource type and build your selection with the simple filters or the advanced filter. Press Show filtered … to preview the matches.
- Press Edit filtered ….
- In the action drop-down, choose Delete metafield.
- Press Select metafield and specify it - from a definition/set, copied from another resource, or by typing the namespace / key / type manually. Remove the type condition to delete every metafield with that namespace/key combination regardless of its type.
- Need to remove more than one metafield? Press Add new action - up to 5 delete actions run together.
- Launch the bulk edit.
Every bulk action automatically generates a Backup file with the data as it was before the run. Find it under Bulk Actions → History and re-import it to undo the deletion. A run usually produces a single backup file; only when some of its actions overwrite the results of earlier ones is the backup split into several files (one per action) - import those in reverse order, from the last action to the first.
Full walkthrough: How to delete metafields in bulk with the bulk editor.
Not the tool for clearing a whole namespace that has many (or auto-generated) keys - you would have to name each key, and you are capped at 5 per run. That is Method 3.
Method 3 - Export + import: bulk clean-ups and whole namespaces
Use it when you are removing a lot of metafields at once, you want to delete an entire namespace no matter what the keys are, or your selection cannot be expressed as a filter.
The idea: export the metafields you might want to delete, open the CSV in any spreadsheet editor, clear the values of the ones you actually want gone, and re-import the file with the delete empty metafields option enabled. Every row you blanked out becomes a deletion.
Why this beats Methods 1 and 2 for namespace-wide clean-ups: exporting in rows mode lets you list up to 10 namespaces and pulls every metafield in them regardless of key - including auto-generated keys you could never type out by hand. Clearing a whole column of values in a spreadsheet is a couple of clicks, and the import removes them all in one pass.
👉 How to delete metafields in bulk with data import - the full step-by-step, including the whole-namespace workflow.
Which method should I use?
- A few metafields, scattered, no pattern → Excel-like editor.
- A clear filter plus a known metafield (up to 5 of them), at any scale → Bulk editor.
- Many metafields, a whole namespace, or no filterable pattern → Export + import with delete empty metafields.
Frequently asked questions
Does deleting a metafield value also delete its definition?
No. These methods delete metafield values on resources. Metafield definitions and metafield sets stay in place - remove those separately from Shopify's Settings → Custom data screen or from the app's definitions screen.
Can I recover metafields after a bulk delete?
It depends on the method:
- Excel-like editor - no automatic backup. Discard works only before you save; a saved deletion is irreversible. Export the metafields first if the edit is large.
- Bulk editor - every bulk action automatically produces a Backup file under Bulk Actions → History. Download it and re-import it with the CSV import feature to revert the changes. A run usually has one backup file; only when some of its actions overwrite earlier ones is the backup split per action - then import those in reverse order, from the last action to the first.
- Export + import - the export file you started from is the backup. It stays in Bulk Actions → History; re-import it to restore the values the import changed.
Why do I clear values instead of pressing a "delete" button?
Shopify's API has no concept of an empty metafield. Clearing the value and then saving (Methods 1 and 2) or importing with delete empty metafields (Method 3) is the delete operation.
How many resources can each method handle?
The Excel-like editor shows 50 resources per page, reviewed manually. The bulk editor has no resource cap - a single filter can cover your entire catalog. Export + import is bounded only by the CSV size limit of your plan (50 MB on Rookie and Adept, 250 MB on Guru, 500 MB on Guru Plus).
How do I delete every metafield in a namespace?
Use Method 3. Export in rows mode with the namespace (or up to 10 namespaces) specified, clear the value column in your spreadsheet editor, and re-import with delete empty metafields enabled. See the step-by-step guide.