Skip to content

What Are Metaobjects in Shopify?

Definition

Metaobjects are custom data structures in Shopify that group several related fields into a standalone object, such as a size chart, a designer profile or an FAQ. A metaobject definition sets the fields and their rules, and each entry holds one set of values. Entries can be referenced from products or published as their own storefront pages.

How metaobjects work

A metafield adds one field to something Shopify already has, such as a product. Some content does not belong to one product: a size chart shared by 200 shoes, a designer biography, a store FAQ. Metaobjects let you define custom data structures with several related fields, and each one is a standalone entity that products and other resources can reference.[1]

Every metaobject has two parts. The definition is the schema: its name, its fields and their rules. The entries are the content, one set of values per entry. In the Shopify admin you manage definitions under Settings > Custom data and entries under Content > Metaobjects.[2] Each field can carry validation, such as a character limit, a minimum and maximum value or a list of preset values.[2] Shopify's own examples include product highlights, influencer profiles, FAQs and an event history.[2]

Entries reach the storefront in three ways:

  • Through a metafield. A product gets a metafield of type metaobject reference, and the theme reads the entry through it. This is the most common route.
  • Directly in the theme editor. A section setting can connect to a metaobject as a dynamic source if the definition has storefront access and compatible fields.[3]
  • As its own page. With the Online Store capability, every entry gets a URL and a theme template (more below).

Developers can also read metaobjects in Liquid and through the Storefront API.[2] Storefront access is off by default; a definition must be set to public read before the Storefront API, used by headless storefronts, can see it.[1] Definitions can belong to the merchant, editable in the admin, or to an app, which uses the reserved $app prefix.[1]

Capabilities and limits

A definition can switch on four optional capabilities:[4]

CapabilityWhat it does
PublishableEntries are Draft or Active, which controls whether the storefront shows them
TranslatableEntries can be translated through Shopify's translation APIs
RenderableEntries carry SEO metadata, such as a page title and meta description
Online StoreEntries get a theme template and a URL, so each renders as a web page

The limits are wide enough for most stores:[5]

WhatLimit
Definitions per store128 on plans below Plus, 256 on Plus
Definitions per installed app128
Fields per definition40
Entries per definition1,000,000
Entries in one list metafield1,024
Entries in a Liquid loop50 without paginate, 250 per page with it

Metaobject pages

Metaobject pages are the feature most merchants don't know about. Turn on the Online Store capability, add a theme template, and every entry becomes a page. The template lives at templates/metaobject/{type}.json, so it is a normal Online Store 2.0 template built from sections.[6] The URL follows the handle you choose for the definition: with the handle content, an entry is served at /pages/content/{entry-handle}.[4]

In the admin the steps are: give the definition storefront access, select Publish entries as web pages, add entries, then create the template in the theme editor. You also choose which fields fill the page title and meta description.[7] Shopify recommends turning on the Renderable capability alongside Online Store, so those SEO fields can be managed.[6] Designer pages, stockists, lookbooks, recipes and ingredient glossaries all fit this pattern, and none of them needs an app.

Example: a designer directory for a furniture store

Take a hypothetical furniture store with 600 products from 24 designers. Today each designer's biography is pasted into the description of every product they designed, so a new photo or a corrected bio means editing dozens of products. We would model it like this:

Field in the Designer definitionType
NameSingle line text
PortraitFile
CountrySingle line text
BiographyRich text
WebsiteURL
CollectionCollection reference

That is 6 of the 40 fields a definition allows, and 24 entries out of a possible 1,000,000.[5] Each product gets one metafield, custom.designer, that references an entry, so a biography is edited once and changes on every product page that uses it. With the Online Store capability and the handle designers, each designer also gets a page such as /pages/designers/hanna-berg, and the collection field lists their pieces on it. A designers index page can loop over all 24 entries without pagination, because Liquid returns up to 50 entries before paginate is needed.[5]

The collection field matters: a metaobject does not know which products point to it, so the designer page needs its own link to the products. A collection, or a list of product references on the entry, solves that.

Metaobjects vs metafields

Shopify's analogy is that metafields add new columns to existing resources, while metaobjects create new kinds of data, like custom tables.[8]

MetafieldsMetaobjects
What it isAn extra field on a product, order or customerA standalone entry with its own fields
Use it forAn attribute of one resourceSomething many resources share, or that needs its own page
How they connectA metafield can reference a metaobject entryUsually reached through that metafield

FAQ

What is the difference between a metaobject definition and an entry?

The definition is the schema: the name, the fields and their validation rules. An entry is one set of values for that schema, such as one designer or one size chart. One definition can hold many entries.[1]

Can metaobjects have their own pages?

Yes. With the Online Store capability and a metaobject template in the theme, each entry renders as a web page with a URL such as /pages/content/{entry-handle}.[4]

How many metaobjects can I create?

128 definitions on plans below Plus and 256 on Plus, plus 128 per installed app. Each definition can have up to 40 fields and 1,000,000 entries.[5]

Can metaobjects be translated?

Yes, if the definition has the Translatable capability switched on. Entries can then be translated through Shopify's translation APIs.[4]

Do I need a developer to use metaobjects?

Not for the data. Definitions and entries are created in the admin, and themes that support dynamic sources can show them without code.[3] You need a developer for custom sections, such as a designer page layout or a size chart pop-up.

The bottom line

Metaobjects are Shopify's way to store content that stands on its own, with its own fields, instead of squeezing it into product descriptions. Products point to entries through a metafield, and with the Online Store capability each entry can also be a page. Use them for anything shared by many products or worth its own URL. When the theme needs sections to show that content, our Shopify theme development team builds them, and for headless storefronts we read the same entries through the Storefront API in our headless Shopify projects.

Article sources

We use primary sources only: official documentation, product pages and laws. Each link was checked on the date shown.

  1. Shopify Dev. About metaobjects. Accessed 17th Nov 2026.
  2. Shopify Help Center. Metaobjects. Accessed 17th Nov 2026.
  3. Shopify Dev. Dynamic sources. Accessed 17th Nov 2026.
  4. Shopify Dev. Use metaobject capabilities. Accessed 17th Nov 2026.
  5. Shopify Dev. Metaobject limits. Accessed 17th Nov 2026.
  6. Shopify Dev. Metaobject templates. Accessed 17th Nov 2026.
  7. Shopify Help Center. Building web pages with metaobjects. Accessed 17th Nov 2026.
  8. Shopify Dev. Data modeling with metafields and metaobjects. Accessed 17th Nov 2026.

Need this on your store?

See the service

The checklist we run before touching a client's code

Get it by email, plus a few short notes over the next two weeks: what we see most often on Shopify stores and what actually fixes it.

No spam. Unsubscribe anytime. Privacy Policy