Custom fields are great for storing structured data - movie ratings, event dates, author bios, site-wide CTAs. But storing data is only half the story. You still need a clean way to show that data on the front end.

Table of Contents hide

1. Why use block bindings?
2. Quick setup
3. What you get with Meta Box
4. Where to go next

For a long time, Gutenberg users had fewer options than page builder users. In Elementor or Bricks, you open dynamic data, pick a Meta Box field, and the element displays it. In the block editor, you often fell back to PHP templates, shortcodes, MB Views, or a custom block.

That gap is closing. Meta Box now supports WordPress block bindings, so you can connect custom fields to core blocks the same way you would with dynamic data in a page builder - without writing template code.

Why use block bindings?

Block themes and full site editing put more of the layout in Gutenberg: post content, templates, and synced patterns. If your structured data still lives only in PHP or a shortcode, the editor experience feels split in two - design in blocks, data somewhere else.

Block bindings keep everything in one place:

Editors fill in Meta Box fields as usual.
Designers (or the same editors) place Paragraph, Heading, Image, or Button blocks and bind them to those fields.
Update the field once, and every bound block reflects the change on the front end.

You keep one source of truth for the data, and you keep native block styling for typography, spacing, and layout. No need to build a custom Gutenberg block just to print a subtitle or a cover image URL.

In short: Meta Box stays your field layer. Block bindings become the bridge into Gutenberg.

Quick setup

Create your fields with MB Builder as usual - they are available for bindings by default.

Then bind a block:

Select a block that supports bindings (Paragraph, Heading, Button, Image, …).
Open Attributes in the sidebar and choose the attribute (Content, URL, …).
Pick a Meta Box source (for example Meta Box Post Field), then choose your field.

Click to Attributes to connect Gutenberg block with Meta Box field

That is it - the block uses the field value on the front end. (Requires WordPress 6.5+; the Attributes UI needs 6.9+).

What you get with Meta Box

Meta Box registers a source for each object type:

Source	Label	Available with
`meta-box/post-field`	Meta Box Post Field	Meta Box (posts and custom post types)
`meta-box/term-field`	Meta Box Term Field	MB Term Meta
`meta-box/author-field`	Meta Box Author Field	MB User Meta
`meta-box/setting-field`	Meta Box Setting Field	MB Settings Page

You can bind blocks to post and CPT fields, term meta, author (user meta) fields, and settings page fields. Structured fields go further - for example an image field can bind URL, alt, title, caption, and description separately.

Where to go next

Block bindings will not replace every display method. Complex layouts, repeaters, and advanced templates are still a great fit for MB Views, MB Blocks, PHP helpers, or page builders.

For everyday Gutenberg work - show a field in a heading, an image, a button - block bindings are the missing link between Meta Box and the block editor.

Full details, code examples, and the structured-field property list are in the docs: Block bindings.