ContentBite: a Shopify metafields app that makes custom fields easy to edit

If you’ve edited Shopify metafields in the admin, you know the feeling. You get a long list of fields called Heading, Subtitle, Button text, Image and Background color. You can change the values, but nothing tells you where they show up on the storefront. Is this image a background or a thumbnail? Is this heading the large one or the small one above it? What happens if you leave it empty?

The usual answer is to preview the store, ask the developer, or look for documentation that doesn’t exist. Developers get a steady stream of questions, and merchants edit by trial and error. I’ve seen this on nearly every Shopify project I’ve worked on, so we’re building ContentBite, a Shopify metafields app that fixes the editing side.

  • What it is: a Shopify app that groups metafields into named sections, like ACF field groups in WordPress.
  • Where it works: products, variants, collections, pages, blog posts and blogs.
  • How content is stored: as native Shopify metafields. No external database, nothing locked in the app.
  • Status: in development, coming to the Shopify App Store.

The problem isn’t metafields

Metafields are Shopify’s custom fields. They let developers build flexible content models for products, collections and pages without hardcoding content into the theme, and they make custom sections, landing pages and reusable components possible.

The problem is the editing experience. The admin shows a product’s metafields as one flat list of raw inputs. The connection between a field and the design it feeds exists only in the developer’s head. That gap is what ContentBite closes.

ContentBite Shopify metafields app: grouped fields with a section preview

What ContentBite does

Instead of scrolling through dozens of unrelated fields, you organize them into named groups. Everything for the Hero banner lives in the Hero group, everything for the FAQ in the FAQ group. If you’ve used Advanced Custom Fields on WordPress, it’s the same idea: this is the closest thing to ACF for Shopify that we could build on top of native metafields.

See which section you’re filling in

Each group can have a preview image of the section it fills. When an editor adds a group to a product or page, they pick from pictures of the sections, not from field names. They know where the title goes and how the image is used before they type anything.

Default values and presets

Many sections start with the same content. Default values fill a new group so editors don’t retype it every time. Presets are named sets of values, for example a Summer sale hero, that an editor applies in one click and then adjusts.

Hide a section instead of deleting it

Content often goes away for a month and then comes back. You can hide a group from the storefront and keep every value. When you show it again, it’s all still there.

Show metafields in your theme without code

ContentBite ships three theme app blocks for Online Store 2.0 themes: Content group renders one group or all of them, Description renders the product or page description with ContentBite shortcodes expanded, and Two images renders a designed image pair. The shortcodes are how you put metafields inside a product description: write [cbite-faq] in the description and the FAQ group renders at that spot.

Plain Liquid for developers

Every field is saved as its own native metafield with its real type, not as a JSON blob. Shopify resolves references for you, so Liquid gets a full product object or an image with its URL and dimensions:

{{ product.metafields.cbite.hero_title }}
{%- assign hero = product.metafields.cbite.hero_image.value -%}
{%- if hero -%}
  {{ hero | image_url: width: 1600 | image_tag: loading: 'lazy' }}
{%- endif -%}
{%- assign related = product.metafields.cbite.related_product.value -%}
{%- if related -%}
  <a href="{{ related.url }}">{{ related.title }}</a>
{%- endif -%}

Because the content is ordinary Shopify metafields, it works with the theme editor’s dynamic sources, the Admin API and any other app that reads metafields.

Set up with Sidekick

ContentBite adds tools to Shopify Sidekick. Ask it to create a group or a metafield and it opens a pre-filled form for you to confirm. It can also list your groups and find products that are missing one.

Coming after launch

Repeatable content blocks are next: duplicate a block when you need another feature card, and drag blocks into a new order. CSV export and import is planned too.

ContentBite vs editing metafields in the Shopify admin

Shopify adminContentBite
Field layoutOne flat list per product or pageNamed groups, one per section
Knowing what a field doesField name onlyPreview image of the section
Starting contentEmpty fieldsDefault values and presets
Taking content downClear the valuesHide the group, values kept
Showing it on the storefrontConnect each field in the theme editor or write LiquidTheme blocks, shortcodes, or Liquid
Where content livesNative metafieldsThe same native metafields

Built from client feedback

ContentBite didn’t start as a business idea. It started because I kept seeing the same frustration project after project. Clients didn’t struggle because they lacked technical knowledge. They struggled because the interface gave them no context. When I showed early versions to clients, they understood what they were editing without asking for an explanation, which was exactly the point.

The goal isn’t to replace Shopify metafields. It’s to make them feel the way they always should have: visual, organized and approachable for everyone who manages content. Editing a Hero section should feel like editing a Hero section.

FAQ

Is there an ACF for Shopify?

ContentBite is built to be that. It adds field groups the way Advanced Custom Fields does on WordPress: named groups of metafields per product, collection, page or blog post, with presets and default values.

How do I group metafields in the Shopify admin?

The admin lists a resource’s metafields as one list. To group them by section you need an app. In ContentBite you create a group, add the metafields it needs, and editors see that group as one block.

How do I show metafields on a Shopify product page?

In an Online Store 2.0 theme, connect a block setting to the metafield as a dynamic source, or read it in Liquid with {{ product.metafields.namespace.key }}. With ContentBite you can also add the Content group block, or place a shortcode in the product description.

Does ContentBite lock my content in?

No. Everything is stored as standard Shopify metafields in your store, readable from Liquid and the Admin API.

When is ContentBite available?

It’s in development and will be listed on the Shopify App Store. If you want to try it on a store before launch, get in touch.

Shopify app by WeBite, coming soon ContentBite

Shopify metafields grouped into sections your editors understand.

  • Named metafield groups for products, variants, collections, pages and blog posts
  • Preview image for every group
  • Default values, presets, and hide without deleting
  • Theme blocks and shortcodes, or plain Liquid
  • Stored as native Shopify metafields