JetEngine vs Meta Box: Custom Fields, Listings, and Pricing

JetEngine and Meta Box both turn WordPress into a custom content platform:
custom post types, custom fields, relations between posts, and front-end
displays built on that data. They start from opposite ends. Meta Box begins
free and grows through extensions; JetEngine begins paid and arrives with
listings, filters, and forms already in the box. Which one fits your build
depends on how much of the front end you want the plugin to run for you.

This is the one-on-one version of the JetEngine question against the rival
most often recommended beside it. The sections below go through it in order:
what each tool actually is, where they differ, what each one costs, and
which we would pick for which job.

What each one actually is

JetEngine

JetEngine is the core of the Crocoblock ecosystem: custom post types,
custom fields, the Custom Content Types builder (which stores its data in
its own database tables), a visual Listing Builder for front-end loops,
relations between post types, and a query builder that reaches posts,
terms, users, and comments. Its front-end companions, JetFormBuilder for
forms and JetSmartFilters for faceted filtering, are separate plugins
inside the same subscription. It is Elementor-first, and the vendor now
lists Gutenberg, Bricks, and Divi among the editors it works with.

Meta Box

Meta Box is a custom fields framework with a free core plugin. The core
covers field types across posts, pages, taxonomies, and settings pages;
custom post types come through its free companion, CPT UI, or through
code. Around that core sits an extension catalogue: 35 products listed on
metabox.io as of 18 October 2026, adding groups, repeaters, tabs,
conditional logic, relations, custom tables, REST endpoints, and
front-end templates. Meta Box is admin-side first. Its strength is how
data is modelled and stored; its front-end tooling is a template system
rather than a visual builder.

Custom fields and post types

Both tools register custom post types and fields, and both model
relationships between content. The difference is depth versus wiring.
Meta Box has the deeper field system: groups, repeaters, tabbed groups,
and conditional logic are dedicated extensions, and MB Custom Table moves
field data into its own database tables. JetEngine’s field tooling is
simpler, but every field is wired straight into the dynamic content
layer: it can be used as a dynamic tag in listings, templates, and
queries the moment you create it.

On relations, JetEngine builds in three relation types (one-to-one,
one-to-many, many-to-many) per its own feature pages, while Meta Box
handles the same job through the MB Relationships extension. Neither has
an obvious advantage here; JetEngine bundles it, Meta Box modularises it.

The front end: listings, filters, and forms

This is where the two part ways, and it is the section that decides most
purchases. JetEngine’s Listing Builder is a visual loop builder: you
design the card, choose the query, and the front end renders, no PHP
required. Meta Box’s answer is MB Views, which its own product page
describes as building front-end templates “without touching theme files”
using Twig, HTML, CSS, JavaScript, and shortcodes, with one-click field
insertion. That is a capable template system, but you are writing
templates, not designing cards visually.

Filtering splits the same way. Crocoblock’s All-Inclusive subscription
includes JetSmartFilters, its faceted filtering plugin. Meta Box’s
product list carries no filter tool of its own; what it ships is an
integration with FacetWP, a separate third-party plugin you buy
separately. On forms, JetFormBuilder is a full form builder that writes
submissions into your post types, while MB Frontend Submission covers
front-end post submission. Both are credible; one is a form builder, the
other is a submission layer.

Scale and the learning curve

Both tools have a scale path, and both put data in custom tables when
you need it: JetEngine through Custom Content Types in the core plugin,
Meta Box through the MB Custom Table extension. For directory-scale
builds, JetEngine’s version is the default route rather than an add-on.
We have not run benchmarks on either tool, so we will not quote speed
figures; the structural point stands on its own.

The learning curves mirror the architecture. Meta Box’s core is easy for
fields, and the framework mindset arrives as the build grows: choosing
extensions, sometimes Composer, sometimes code snippets. JetEngine
rewards you quickly on the front end, the first listing is fast, but the
suite has many moving parts and the admin screens reward a guided
learning pass.

Pricing

JetEngine’s standalone license is around £57/yr (~$75) at list for one
site, and the vendor’s plugin page is currently showing it discounted to
$57 (around £43), so check the live price before you buy. The
All-Inclusive plan, which covers all 23 JetPlugins on one site, is
around £150/yr (~$199), and the Lifetime license is around £753 (~$999)
one time for unlimited sites. Crocoblock lists USD and converts at
checkout; prices from crocoblock.com, verified 18 October 2026.

Meta Box sells in USD. The core plugin is free. The Basic Bundle is
$49/yr (around £37) for one site with 12 PRO extensions, the Ultimate
Bundle is $99/yr (around £75) for three sites with all PRO extensions
and the all-in-one AIO plugin, and the Lifetime Bundle is $299 (around
£225) one time for three sites. Agency tiers run $149/yr, $229/yr, and
$699 one time for unlimited sites. Annual renewals are at regular price.
All figures from metabox.io/pricing,
verified 18 October 2026.

The price gap is real but smaller than it looks. Meta Box is free until
you need its premium extensions; JetEngine costs money from day one but
includes its premium features in the license. A directory build that
needs faceted filters and front-end forms ends up paying for Meta Box
extensions plus a separate filter plugin, and that total can pass the
All-Inclusive price. A site that only needs fields and post types pays
nothing with Meta Box.

When to reach for each

Choose Meta Box when: custom fields are the whole job;
budget is the hard constraint; you are happy assembling extensions and
writing templates; or you want a free core you can grow slowly without
a subscription.

Choose JetEngine when: the site is a directory, a
listings site, or a booking-style build; you want filters, forms, and
listings under one subscription; you build on a visual builder; or your
data volumes are heading for custom-table territory.

Our recommendation

For listings and dynamic-data builds, JetEngine is the stronger default.
The front-end layer that Meta Box asks you to assemble is included in
the box, the listing builder takes PHP out of the build, and one
subscription covers the wider toolkit. That is a verdict about the job,
not a claim that JetEngine is the better fields plugin.

Meta Box is the better buy for fields alone: a free core, a deeper field
system, and you pay only when you outgrow it. It is also the honest
answer for a client who just needs post types and fields and nothing on
the front end. Judge it on how much of the front end you need the plugin
to run, not on which product has the longer feature list.

Head-to-head comparisons

This page is the JetEngine one-on-one against Meta Box. The wider field
lives on the hub and the review:

• JetEngine alternatives: Toolset vs ACF Pro, the three-way hub
• JetEngine vs ACF Pro, the data architecture comparison
• JetEngine vs Toolset, the visual builder comparison
• JetEngine review, the complete suite verdict
• Crocoblock pricing explained, what the plans actually cost

Frequently Asked Questions

Is Meta Box really free?

Yes. The core Meta Box plugin is completely free and listed on the WordPress.org plugin repository, and its free CPT UI companion covers custom post types and taxonomies. The paid bundles start at $49/yr for the Basic Bundle (one site, 12 PRO extensions), from metabox.io/pricing, verified 18 October 2026.

Which should I use for a directory or listings site?

JetEngine, for most builds. It pairs custom post types with a visual Listing Builder, and the All-Inclusive subscription adds JetSmartFilters for faceted filtering and JetFormBuilder for front-end submission. Meta Box can do the same job through MB Views templates and a FacetWP integration, but you assemble it piece by piece.

Is Meta Box good enough for custom fields alone?

Yes, and it is the better buy for that job. The free core plus its extension catalogue (groups, repeaters, tabs, conditional logic, custom tables) is deeper than JetEngine's field tooling, and you pay nothing until you need a premium extension. Where it stops is the front end: its product list has no listing builder and no native filter tool, only an integration with FacetWP.