Shopify Metafields and Metaobjects, Explained for Store Owners

Shopify metafields let you store the details your products need, like size charts, care instructions, specs and ingredient lists, in proper fields instead of pasting them into every description. Metaobjects go further: you build a reusable piece of content once and attach it wherever it applies. Below I explain both in plain English, how to set them up so your theme can show them, examples you can copy, and the mistakes I see most often.

What Shopify metafields are, and why descriptions aren’t enough

A metafield is an extra field attached to part of your store. Products, variants, collections, customers, orders, pages and blog posts can all have them. Shopify’s product form covers the basics, such as title, price and weight. Metafields cover everything specific to your business: fabric, fit, burn time, wattage, ingredients, a care guide.

You could put all of that in the description, and many stores do. The trouble shows up later:

• The same information is typed slightly differently on every product, so it can’t be filtered.
• Changing one detail, like a care instruction, means editing dozens of products.
• Your theme can’t place the information anywhere except inside the description.
• Reports can’t group or filter sales by it.

Structured fields fix all four, and Shopify keeps building on them. Since February 2026, metafields can be used as dimensions and filters in Analytics once you allow it in the definition, and in June 2026 Shopify added a product disclosures field, for warnings like California Proposition 65 notices, that is stored as metafields.

Set up metafield definitions properly

A definition tells Shopify what a metafield holds and where it applies. Without one, a metafield is “unstructured”: usually created by an app, without the same validation, and harder to use. Create definitions under Settings, Metafields and metaobjects (some of Shopify’s help pages still call this Custom data). For each one you choose:

1. Name and description. Write the description for the person filling it in, for example “Hand wash cold. One sentence per step.”
2. Namespace and key. Shopify generates it from the name, like custom.care_guide. Your theme and apps refer to it, so treat it as permanent.
3. Type. Single line text, rich text, integer, decimal, date, true or false, color, file, measurements such as weight or dimension, references to products, pages or metaobjects, and more. Pick the narrowest type that fits.
4. One value or a list. A list suits details like “suitable for” or several materials.
5. Validation. Limits such as a minimum and maximum, or preset choices for single line text, keep the data clean.

Before creating a custom definition, check two shortcuts. Standard definitions, such as Product subtitle, Care guide and Product rating, are set up by Shopify and supported across themes and apps. Category metafields, such as color, size and fabric, come from Shopify’s product taxonomy, and the color one is what powers swatches on product pages and in filters. Shopify’s guide to creating metafield definitions walks through each screen.

Show metafields on your store with dynamic sources

On an Online Store 2.0 theme you don’t need code to display a metafield. In the theme editor, open the product template, add or select a block such as a text block or collapsible row, and click the connect dynamic source icon next to a setting. Pick the metafield, save, and every product shows its own value in that spot. Product templates can use product metafields, and collection templates can use collection metafields.

Three things to test before you publish:

• A product with no value. Depending on the theme, an empty metafield can leave a blank gap or a heading with nothing under it.
• Variants. If you use variant metafields, switch between variants and check that the value updates.
• Formatting. Rich text and lists can look different from the description, so check them on a phone.

Vintage themes don’t support dynamic sources, and some layouts, such as a proper size table built from several fields, need a custom block. That’s a small, one-time job I often handle as part of my Shopify development service.

Metaobjects: reusable content you build once

A metafield holds one value. A metaobject is a small content type you design yourself, with several fields. You create the definition, meaning the fields, on the same settings page, then add entries under Content, Metaobjects. To attach an entry to a product, create a product metafield of the metaobject reference type and pick the right entry on each product.

Shopify’s own examples include product highlights with an icon, title and text, FAQs, and influencer profiles. The point is reuse: edit an entry once and every product that references it updates. Entries can also be published as their own web pages through a metaobject template, and since December 2025 you can create and edit metaobjects from the theme editor. One caution: deleting a metaobject definition deletes all of its entries, and that can’t be undone.

Practical examples you can copy

Size charts

Create a Size chart metaobject with fields for the chart and a short fit note, add one entry per chart (women’s tops, men’s pants), and reference the right entry from each product. Change a measurement once and every product using that chart updates. Rich text metafields don’t offer tables the way the page editor does, so a common workaround for table-style charts is to keep each one on a page and reference that page instead.

Care instructions

Use the standard Care guide definition, or a Care metaobject with one entry per fabric if many products share the same instructions.

Specifications

Use measurement types for dimensions, weight and volume so units stay consistent. If shoppers need to filter by a number, such as wattage, use an integer or decimal field instead, since measurement types aren’t on Shopify’s list of filterable types.

Ingredient lists

For a simple list, use a list of single line text. If each ingredient deserves its own description or page, make Ingredient a metaobject and reference a list of entries. That also works as a filter, so shoppers can find every product with a given ingredient.

Mistakes I see on real stores

• No definitions. Unstructured metafields left by old apps can’t be filtered and are easy to forget. Shopify builds every metafield filter on a definition.
• The wrong type. Multi-line text for something that should be a list, or text for a number, blocks filtering later. Only single line text, integer, decimal, true or false and metaobject reference fields can be filters.
• Careless deleting. When you delete a definition, Shopify asks whether to keep the saved values or delete them too. If the metafield is connected to your live theme, deleting it can cause display errors for customers.
• One-off fields everywhere. Twenty definitions that each serve three products are a maintenance problem. Group related details into a metaobject.
• Typing everything by hand. The bulk editor handles metafields for products, variants, collections and customers, and product CSV files include product metafields once they’re defined. Variant metafields aren’t in the product CSV, so use the variant bulk editor for those.

With hundreds of products to fill in, part of the work can be automated, for example by turning supplier spec sheets into draft values that a person checks before import. That’s the kind of workflow I build in my AI automation service.

What to do next

1. List the product details customers ask about that your product form doesn’t cover.
2. Check standard definitions and category metafields before creating custom ones.
3. Create definitions with the narrowest type, a clear description and validation.
4. Move anything shared by many products into a metaobject.
5. Connect the fields in the theme editor, then test empty values, variants and long text on a phone.
6. Fill in values with the bulk editor or a CSV, spot-check them, and add filters for the fields shoppers choose by.

Related reading: Shopify Abandoned Cart Recovery That Brings Buyers Back and Shopify Plus vs Advanced: When the Upgrade Is Actually Worth It.

FAQ

What is the difference between metafields and metaobjects?

A metafield adds one field to something that already exists, such as a product. A metaobject is a new type of content with its own fields, which you attach to products through a metafield.

Do I need an app to use metafields?

No. Definitions, values, dynamic sources and metaobjects are all built into Shopify. Apps help with very large catalogs or special cases.

Will my metafields survive a theme change?

Yes. The values belong to your products, not the theme. You’ll need to reconnect them in the new theme’s editor, but nothing is lost.

Can customers filter products by metafields?

Yes, through the Search & Discovery app, as long as the metafield has a definition and a supported type: single line text, integer, decimal, true or false, or a metaobject reference.

Product details scattered across descriptions, tags and old apps? Ask for a free review of your product data and I’ll show you which details belong in metafields and how to move them without breaking your pages.