Shopify Metafields in Framer: Richer Product Content Fast
Yes, a Framer storefront can read Shopify metafields. You define the metafield in Shopify, set its definition's storefront access to PUBLIC_READ, then query it through the Storefront API and render the value on your Framer product page. That keeps fabric, care, dimensions and sizing content in Shopify, where the merchant already edits it, rather than duplicated in Framer CMS where it quietly drifts out of date.
Most Framer builds get this backwards. Title, price and images arrive through the product sync, and then someone pastes the care instructions into a Framer CMS field "just for this launch." Six months on, the Shopify admin says one thing, the site says another, and nobody remembers which is right.
What is a Shopify metafield?
A metafield is a typed custom field attached to a Shopify resource — a product, variant, collection, customer or order — holding data Shopify has no built-in field for. Each one has a namespace, a key, a type and a value, and a definition that tells the admin how to render the input.
Shopify product metafields are the ones that matter for a storefront build: fabric content, care instructions, warranty length, assembly time, a reference to a size chart. Merchants can create up to 256 metafield definitions per resource type, and each installed app gets its own allowance on top. The ceiling is not your problem. Deciding what belongs where is.
Where should product content live: Shopify or Framer CMS?
Direct answer: anything the merchant edits per product belongs in Shopify. Anything that is editorial or page design belongs in Framer CMS. Here is the split that holds up in practice.
| Content | Recommended home | Who edits it | Indexable on the product page |
|---|---|---|---|
| Product spec (fabric, dimensions, weight) | Shopify product metafield | Merchant, in the product admin | Yes, if server-rendered |
| Care instructions | Shopify metaobject, referenced per product | Merchant, once per care type | Yes |
| Size chart | Shopify metaobject, referenced per product | Merchant, once per chart | Yes |
| Product FAQ | Shopify metaobject, or Framer CMS List field | Merchant for product-specific, designer for generic | Yes |
| Lookbook or campaign copy | Framer CMS | Designer or content editor | Yes |
| Badge or label ("Made in Italy") | Shopify metafield with predefined choices | Merchant, from a fixed list | Yes |
The rule behind the table: if changing the value is a merchandising decision, it is Shopify's. If changing it is a design decision, it is Framer's. A badge that appears on forty products is merchandising. A hero paragraph on one landing page is design.
How do you expose Shopify metafields to the Storefront API?
Three steps, and the first one is the one people miss.
1. Set storefront access on the definition. Create or update the metafield definition with access.storefront set to "PUBLIC_READ". A metafield with a value but no storefront access simply returns null to your Framer site, which looks identical to a missing value and wastes an afternoon.
2. Query it by namespace and key. On the product, request metafield(namespace: "specs", key: "fabric") and ask for both value and type. Alias several in one query rather than firing one request per field.
3. Render by type. The value always comes back as a string. A number_decimal needs formatting, a json needs parsing, and a metaobject_reference needs a second hop to pull the referenced record's fields.
"You can't create, update, or delete metafields with the Storefront API." — Shopify developer documentation
That constraint is the whole architecture in one line. Writes go through the Admin API or the admin UI; the storefront only reads. If your build needs writes from the front end, it needs an app or a backend, not a Framer code component.
One migration note: the old metafieldStorefrontVisibilityCreate mutation was removed as of API version 2025-01. Fields exposed that way need their definitions updated with access.storefront or they go dark. If you are auditing an older store, start there — and if you are new to querying against a live catalog, our Storefront API sync walkthrough covers the request shape in more detail.
How do you handle repeating content like size charts and FAQs?
Direct answer: use Shopify metaobjects for repeating content that several products share, and reference them from a product metafield.
A metaobject is a reusable record with its own fields — a size chart with rows, a care guide with steps, a material entry with a name and an icon. Define it once, reference it from a hundred products, edit it in one place. Shopify now allows up to 1,000,000 entries per metaobject definition, which removed the old plan-based ceilings of 64,000 and 128,000.
On the Framer side, repeating content got meaningfully easier with the CMS List field, which replaced the old pattern of duplicating Title 1, Description 1, Title 2, Description 2 across a collection. It is the right tool when the repeating content is genuinely yours — a features list on a template, an editorial FAQ. It is the wrong tool when the content is a merchant's size chart, because then the chart lives in two systems and only one of them is correct.
Which Shopify metafield types hold up on a product page?
Direct answer: typed, constrained types beat free text. single_line_text_field with predefined choices for badges, dimension and weight for specs, rich_text_field for care copy, metaobject_reference and list.metaobject_reference for shared records, file_reference for spec sheets.
The size limits are generous but real: most metafield types cap at 64KB, json at 128KB, and url and id at 2KB. The limit that actually bites is on lists — in Liquid, looping a list of references returns only the first 50 items, so a reference list is not a catalog. If you are weighing how much product data to mirror into Framer at all, the Framer CMS catalog limits are worth reading alongside this: Framer's Pro plan includes 2,500 CMS items and 10 collections, extendable with add-ons, which is plenty for editorial and thin for a catalog.
Does metafield content get indexed on a Framer product page?
Direct answer: only if it is in the HTML when the crawler arrives. A metafield value fetched client-side after hydration is invisible to most crawlers and to AI answer engines, which is exactly the content — specs, materials, sizing — that wins long-tail product queries.
Build the page so metafield-backed content is present at render, not after. Put the spec table and care copy in the initial markup, keep genuinely interactive pieces (a size calculator, a stock checker) on the client, and verify with a fetch-as-rendered check rather than trusting the browser view. FramerLink handles the sync side of this so product data lands in the page rather than in a post-load request, and the product page template guide shows the layout that tends to follow.
The payoff is unglamorous and large: one source of truth, a merchant who can update a care instruction without opening Framer, and a product page that says the same thing to a customer, a crawler and an AI assistant.
Frequently asked questions
Can a Framer site display Shopify metafields?
Yes. Create the metafield definition in Shopify with storefront access set to PUBLIC_READ, then query it through the Storefront API and render the value on your Framer product page. The merchant keeps editing the field in the Shopify admin, and the Framer page reflects the change without anyone touching the design.
What is the difference between Shopify metafields and metaobjects?
A metafield stores one custom value on one resource, such as a product's fabric content. A metaobject is a reusable record with several fields of its own, such as a size chart or a care guide, which many products can reference. Use metafields for per-product values and metaobjects for shared, repeating content.
How many metafields can a Shopify store have?
Merchants can create up to 256 metafield definitions per resource type, and each installed app gets its own allowance of 256 per resource type. Most metafield types cap the stored value at 64KB, while JSON fields cap at 128KB. In practice the definition count is rarely the constraint.
Do you need code to add metafields to a Shopify product?
No. Metafield definitions are created in the Shopify admin under Settings, then Custom data, and merchants fill in values on each product page. Code is only needed on the rendering side, when a custom storefront such as Framer queries the value through the Storefront API and decides how to display it.
Sources
- Retrieve metafields with the Storefront API — Shopify
- Metafield limits — Shopify
- Increased limits in metafield and metaobject definitions — Shopify
- CMS List Field — Framer
- Framer Pricing — Framer