Route field data into blocks

Meta Field Block displays custom field values in the WordPress Block Editor. MFB Pro adds structured presentations for complex fields, so field data can appear as container content, media blocks, query results, or values bound to core blocks. This works with dynamic templates without a custom display block for common layouts.

For a field to appear in the editor, it must be available through the REST API or have its field type set to dynamic. Blocks can use post, term, or user data. They can sit inside a parent block that includes postId and postType context, such as Query Loop, WooCommerce Product Collection, or Term Query, or work as stand-alone blocks.

Groups and repeated entries

ACF Group and Flexible Content fields can render as container blocks. A Group can also use a Details block. Arrange Repeater entries in row, stack, grid, carousel, or accordion layouts. Nested fields can be displayed with the Sub Field Block or bound to core blocks. Corresponding Meta Box Group and Cloneable Group fields support similar container and repeater presentations.

Accordion layouts can organize repeated FAQ content, while a carousel can present items such as banner slides. The layout follows the field data and the structure needed by the template.

Media and related content

An ACF Image field can render as a core Image block. Gallery fields support grid, masonry, and carousel layouts. ACF File fields can render as video, picture, button, or link blocks; Link fields can render as buttons, and URL fields can render as images, buttons, links, videos, or embeds. Email fields can appear as buttons or links, and oEmbed fields as Embed blocks.

ACF Relationship and Post Object fields can appear as Query Loops. Meta Box Post fields can use a Query Loop, and taxonomy fields can use a Terms Query block. MFB Pro also supports ACF Google Map fields.

Bind fields to core blocks

Custom fields from ACF, Meta Box, core meta fields, and core options can bind directly to Heading, Paragraph, Button, Image, Video, and Embed blocks. Cover blocks can use field values for background images, video, or embeds. This lets a template send each value to the block that presents it.

Developer controls

Hook APIs allow developers to customize block output, display complex field data, or use the block as a placeholder with object_id and object_type context. Shortcode output can also be displayed, including in a Query Loop where the block can use the correct post ID. Meta Field Block displays existing field values; it does not provide field entry or saving.