Meta Field Block – Display Custom Fields for ACF, Meta Box and More
by Phi Phan · Blocks
Also makes 7 other plugins · 26.8K+ installs across the portfolio →
A single block to display custom fields in the Block Editor. It supports ACF, MetaBox, WooCommerce, meta, rest field, shortcode and more.
Try it live opens a temporary test site in your browser, which can take about 20 seconds to load. Plugins that rely on outside services or a full server may not work completely there.
Health
A 91/100
no flags
Active installs
10K+
≈18K estimated
Momentum
-23%
downloads vs prior 30d
Biggest opportunity: Swap “block” for “display”. “block” isn't earning its slot: you're not in the first 24 results for its own search. “display” sits at #5 untagged, close enough for a declared tag to move it up. All five slots are taken, so one has to go.
91 health vs 71 average across 2,531 Blocks plugins
Install conversion
How it's measured →5.0%
of downloads still active
At least 10K of 199.8K lifetime downloads are still running, above its category: the median Blocks plugin keeps 2.1%, across 1,584 plugins.
Downloads count every update, not just first installs, so older and more frequently released plugins read lower. Compare against other Blocks plugins, not across the directory. wp.org reports active installs as the bottom of a band, so the real rate is this or higher.
This plugin shipped 8 releases in the last 12 months, and every existing install that updated counted as another download. wp.org publishes no split between first installs and updates, so we show the raw rate rather than guess at one.
Details
Directory ranking optimization
How it's scored →How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.
Excellent listing optimization
Well tuned across the board
Updated 14 days ago
Tested up to WordPress 7.1.4, the current branch or newer
5.0★ over 57 reviews, weighted for review count to 4.6★
5 of 5 tags set · short description in place
2 of 2 support threads resolved in the last 2 months
Search visibility
How it's tracked →Directory searches this plugin turns up in, and which way each one is moving. WordPress.org publishes no history of search positions, so this starts the day we first tracked a keyword and never backfills.
47
Momentum
Holding steady
+0.6
Velocity
places per keyword, 28d
39%
Breadth
of keywords climbing, 28d
-0.8
Acceleration
recent half vs earlier
wp.org is where the directory puts the plugin for that search. On merit is where it would sit if results were ranked on rating, support and updates, without the install boost. The last column is how far the wp.org position moved, from our first reading in the last 90 days to the latest.
| Keyword | wp.org | On merit | wp.org move, 90 days |
|---|---|---|---|
| meta field your tag | #1 | #1 | up 1 |
| meta field block | #1 | #1 | 0 |
| meta box | #2 | #2 | 0 |
| acf field your tag | #3 | #3 | up 1 |
| display custom fields | #4 | #4 | — |
| display | #5 | #4 | up 3 |
| field | #5 | #5 | 0 |
| display meta | #2 | #2 | 0 |
| display field value | #2 | #3 | up 1 |
| meta | #6 | #6 | up 2 |
| custom field your tag | #7 | #7 | up 2 |
| custom meta box | #3 | #5 | 0 |
| acf image field | #3 | #3 | 0 |
| metabox | #7 | #7 | up 3 |
| as metabox | #3 | #4 | down 1 |
| display more | #4 | #5 | up 1 |
| meta fields | #4 | #4 | up 1 |
| custom meta field | #4 | #4 | — |
| display id | #4 | #2 | up 2 |
| acf get field | #4 | #5 | up 1 |
| block your tag | Not in the top 24 | ||
355 searches this plugin appeared in over the last 90 days, 20 listed. 288 left out as unrelated or noise (years, numbers, stray words). 1 of its tags isn't in the top 24 for their own search.
What to do about it
- Swap “block” for “display”. “block” isn't earning its slot: you're not in the first 24 results for its own search. “display” sits at #5 untagged, close enough for a declared tag to move it up. All five slots are taken, so one has to go.
- One page off on “acf”. #15 puts you just past the first ten results, where almost all the clicks stop. The gap to close is small.
Daily downloads
Since 5 Oct 2022 · 1,491 days · wp.org + Plugin Pulse archive
30-day downloads
Rolling 30-day volume · peak 15K · peaks are release surges
Directory rank vs rivals
wp.org popularity rank over time · higher is better · when a rival's line climbs above yours, they've overtaken you
Health trend
Composite health score, snapshotted daily
Update activity
How busy the existing users are, measured as downloads in the last 30 days for every 1,000 active sites. A spike means a new release everyone's pulling; a long, slow decline means an aging user base that updates less.
Release cadence
Actively maintainedHow often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.
8
releases in the last 12 months
14d ago
latest release · v1.6.2 · 20 Oct 2026
49
tagged releases on record
Recent releases
What its installed base runs
via wordpress.orgShare of active installs on each version of this plugin. Green is the current release; a big slice on older versions is a user base that has stopped updating.
Estimated active installs
The public count shows “10K+”. Our estimate pins where the real number sits.
Crossed into this band 10 months ago; a band this size takes about a year or more to cross, which places it about 80% of the way through.
Install history since 28 Sep 2022
Recent reviews
All reviews on wp.org ↗- ★★★★★ markcarrara4mo ago
Well I did code back before classes and objects, so you know that was a while ago. While the plug in works fine, the support has been more than awesome. I didn’t understand a few concepts, once I got that fixed with the help of Phi, I was good to go. The pro version was worth the small cost and it helps out the developer. I purchased it before I needed the features Pro offers.
Read on wp.org ↗ - ★★★★★ Cyrille Sanson7mo ago
Meta Field Block is the perfect tool to display customs fields.Work perfectly in a loop, where shortcode are not effective.
Read on wp.org ↗ - ★★★★★ Oligraph9mo ago
Meta Field Block feels like the natural born sibling of ACF. It makes working with CPTs a breeze. And Phi’s support is extraterrestrial (stellar?).
Read on wp.org ↗ - ★★★★★ natebald12mo ago
This is an awesome plugin, but to be fair, the support is even better. I reached out with more questions on possible customizations or specific application of the product and the development team came back with spot on answers. I wish all WordPress projects were like this one!
Read on wp.org ↗ - ★★★★★ beatty671.1y ago
We love Meta Field Block. Client wanted to leave his Divi & Elementor website behind for something better and easier – and a WordPress theme w Gutenberg was the way to go. We amped it up some with custom post types (ACF) and with the newish Full Site Editing switch, we wanted to get started with the blocks and ACF with minimal hassle. Meta Field Blocks allowed us to set up page templates that use Gutenberg blocks / native WordPress features while also including custom field groups and custom post types, all together now. The free version of MFB is terrific. I wanted more features so happily paid for the Pro. Support from Phi is fantastic. My client loves his new site. Loves using the blocks, and loves that his site is organized via ACF and Meta Field Blocks. 1000% highly recommended. Just get the plugin already!
Read on wp.org ↗ - ★★★★★ demonboy1.2y ago
I hit the infamous shortcode problem in my html block theme recently. I wasn’t aware there was an issue but doing some research I ended up on a Git forum and came across this plugin. I was already using an ACF plugin for my images but this plugin is more flexible and solved the shortcode issue for post ID as well. I was attempting to build my site with minimal plugins, and even tried vibe coding a solution to post ID myself, but I would say Meta Field Blocks is essential if you’re trying to call complex dynamic content in your query loop. Excellent work and superb support to boot. Thank you!
Read on wp.org ↗ - ★★★★★ kuweb11.4y ago
Really useful and well working plugin for displaying ACF fields in templates including repeater fields. Awesone friendly and quick support!
Read on wp.org ↗ - ★★★★★ jhnpldng1.5y ago
Wow – been a couple of years since I logged into wp.org This plugin is just the thing needed to display custom fields on the front end without messing with php templates or dealing with the bloat of a page builder. I’m looking forward to getting the Pro version.
Read on wp.org ↗
Latest updates
via wp.org changelogRecent releases and news for this plugin
- — Version 1.5.3 Release Date – 28 April 2026 Added – Support for width and height in WordPress 7.0 Added – (MFB Pro) Render oEmbed fields as core/embed blocks Added – (MFB Pro) Render URL fields as video or embed blocks Added – (MFB Pro 1.5.3
- — Version 1.5.2 Release Date – 02 March 2026 Added – New “Enable Strict Mode” setting. When enabled, only custom fields exposed via the REST API can be displayed on the frontend Security – Restricted access to private user custom fields 1.5.2
- — Version 1.5.1 Release Date – 19 January 2026 Fixed – (MFB Pro) Bound blocks were not displayed in the pattern preview Fixed – (MFB Pro) Context data was not available when using a block inside a pattern 1.5.1
- — Version 1.5.0 Release Date – 15 January 2026 Added – Display subfields for the Terms Query block. Added – (MFB Pro) Display taxonomy fields as a Terms Query. Improved – Handle field context based on the loop context. Improved – Displa 1.5.0
- — Version 1.4.6 Release Date – 18 November 2025 Improved – Removed _source names from the suggested list for Secure Custom Field (SCF) Improved – Passed block settings to the meta_field_block_get_acf_field and meta_field_block_get_mb_fi 1.4.6
- — Version 1.4.5 Release Date – 10 September 2025 Improved – Refactored the code to support additional add-ons. Fixed – Double formatting issue on ACF textarea fields. 1.4.5
Security history
via Wordfence IntelligenceAll 4 disclosed vulnerabilities are patched in the current version (1.6.2). Sites still on an older version should update.
- Patched Medium · 6.5 Meta Field Block <= 1.5.1 - Insecure Direct Object Reference to Authenticated (Contributor+) Arbitrary User Meta Exposure ↗2026-05-27 CVE-2026-3173 Authorization Bypass Through User-Controlled Key Affects <= 1.5.1 Patched in 1.5.2
- Patched Medium · 6.4 Meta Field Block <= 1.5.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'tagName' Block Attribute ↗2026-05-13 CVE-2026-6252 Improper Neutralization of Input During Web Page Generation Affects <= 1.5.2 Patched in 1.5.3
- Patched Medium · 6.1 Freemius <= 2.10.1 - Reflected DOM-Based Cross-Site Scripting via url Parameter ↗2026-04-30 CVE-2024-13362 Improper Neutralization of Input During Web Page Generation Affects <= 1.3.3 Patched in 1.3.4
- Patched Medium · 6.4 Meta Field Block <= 1.2.13 - Authenticated (Contributor+) Stored Cross-Site Scripting ↗2024-08-16 CVE-2024-43278 Improper Neutralization of Input During Web Page Generation Affects <= 1.2.13 Patched in 1.2.14
Vulnerability records provided by Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. License and terms.
CVE records: Copyright 1999-2026 The MITRE Corporation. CVE terms of use.
Languages
via translate.wordpress.orgTranslated into 8 languages, 4 at 90% or more
AI assistants
How it's measured →Whether ChatGPT and Claude name this plugin when asked the category question, and whether the readme gives them something to quote.
This plugin’s searches fall outside the topics measured so far. See the topics measured so far.
Readme readiness
8 of 8 pass · checked 28 Oct 2026Can an assistant quote this readme? Eight deterministic checks over the wp.org listing, no model involved.
- ✓ Says what it does "A single block to display custom fields in the Block Editor. It supports ACF, MetaBox, WooCommerce, meta, r..."
- ✓ Has a FAQ 9 questions in the FAQ.
- ✓ FAQ asks real questions 9 of 9 read like questions a user would type.
- ✓ Names who it is for Names its audience or use cases ("use it", "use this", "use cases").
- ✓ Names what it works with Mentions WooCommerce, Gutenberg, Block editor, Advanced Custom Fields and 2 more.
- ✓ Headings and lists 9 headings and 6 lists.
- ✓ Enough to quote 16,629 characters of description.
- ✓ Tags match the text All 5 tags appear in the text.
Growth timeline
Install-tier crossings we have observed, and how long each tier took to outgrow
- 2026-01-15 9K+ → 10K+ up after 96 days in tier
- 2025-10-11 8K+ → 9K+ up after 101 days in tier
- 2025-07-02 7K+ → 8K+ up after 91 days in tier
- 2025-04-02 6K+ → 7K+ up after 61 days in tier
- 2025-01-31 5K+ → 6K+ up after 120 days in tier
- 2024-10-03 4K+ → 5K+ up after 104 days in tier
- 2024-06-21 3K+ → 4K+ up after 105 days in tier
- 2024-03-08 2K+ → 3K+ up after 128 days in tier
Competes with
The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).
-
Blocks for ACF Fields — Display Custom Fields in the Block Editor 2K+ installs · 4.4★ · 3 shared tags A - S Smart Custom Fields 50K+ installs · 4.5★ · 2 shared tags A
-
Advanced Custom Fields: Typography Field 3K+ installs · 4.1★ · 2 shared tags A - A Advanced Custom Fields – Taxonomy Field add-on 1K+ installs · 4.1★ · 2 shared tags D
-
Advanced Custom Fields (ACF®) 2M+ installs · 4.5★ · 1 shared tag A -
PDF Embedder – PDF Viewer & Embed PDF Files for WordPress 300K+ installs · 4.7★ · 1 shared tag A
Embed this report card
Drop a live Pulse card for Meta Field Block – Display Custom Fields for ACF, Meta Box and More into a readme, a review or a deck. It updates itself.
<iframe src="https://plugins.wpmayor.com/embed/display-a-meta-field-as-block" width="480" height="300" style="border:0" loading="lazy" title="Meta Field Block – Display Custom Fields for ACF, Meta Box and More — Plugin Pulse"></iframe> Meta Field Block – Display Custom Fields for ACF, Meta Box and More: 10K+ active installs, 5.0★ (57 reviews). Plugin Pulse (WP Mayor), as of 2026-11-03. https://plugins.wpmayor.com/plugin/display-a-meta-field-as-block
Spotted a number that looks wrong? Report a data issue and we'll check it against the source.