JetEngine for Divi 5: Complete Feature Guide

JetEngine is now compatible with Divi, bringing powerful dynamic content capabilities. It definitely can take your development workflow to the next level.

While Divi 5 has introduced a dynamic feature – Loop Builder – it remains a builder rather than a true dynamic content tool, and the latter is essential for websites that go beyond simple landing pages.

Many Divi users have historically relied on ACF, as one of the earliest custom fields solutions, while JetEngine offers a broader range of functionality, from simply creating CPTs and custom fields to enabling use cases like headless setups or AI-driven front ends via the REST API. 

Before the Divi 5 and the full integration introduction, you actually could use JetEngine just like you do ACF – without dedicated front-end modules, but the basic functionality was still there – to create custom posts, fields, and taxonomies, and then display the values on the front end using the Dynamic Content tool. 

But now, dozens of new features are available, along with the dedicated modules to display dynamic content, but that’s only the beginning, as JetEngine can replace over 10 Pro plugins.

JetEngine Major Features: Brief Overview

There are built-in features and modules that you can switch on and off for better performance. Here are just the most important and popular of them. 

For creating custom post types, fields, and taxonomies (data modeling)

• Custom Post Types (CPT) tool to create custom post types with all the meta fields you need them to have.
  There, you can find extra tools to make working with posts effective, such as quick edit support, admin columns editor, and others.  

You can choose custom meta storage for your CPTs, for better performance, to store certain post type fields in custom database tables. 

• Custom Taxonomies tool – for creating custom taxonomies – to add categories and tags. 
• Meta Boxes tool – you can add custom fields when creating new CPTs, but you can also create reusable custom field groups that can be added to posts, taxonomy terms, and users. 
• Custom Content Type – a JetEngine-specific way to store data that doesn’t require single templates and is great for performance. 

For displaying dynamic content on the front end (rendering and display)

• Listing Template editor – a dynamic loop editor to create repeatable loop templates to be used in a grid, slider, calendar, map, or in a dynamic table. 
• Dynamic modules – using them, you can display any dynamic content on the front end, modify them using filter callbacks, and use other flexible advantages of these modules created specifically for JetEngine’s dynamic data. 
• Interactive Calendars – to display date-related content.
• Dynamic Tables and Charts – will be added in future releases.
• Map listing – display location-based data on the map. 
• Dynamic visibility – adds content visibility control based on a huge list of static and dynamic conditions – will be added in future releases.
• Twig integration – you can build listing (loop) templates using pure HTML and CSS, adding dynamic fields there, and then incorporate them into Divi pages. Great for an uncluttered DOM and performance. 

Advanced tools for dynamic content (data querying and interactions)

• Query Builder – a unique feature for querying content from a database without coding and SQL queries, that supports even the most complex combinations of criteria. 
• Data Store – allows storing data in cookies, sessions, or user meta – great for Add to Favorites functionality or even notifications – will be added in future releases.  
• Relations – allows for creating additional layers of connections between different content types, such as CPTs, users, and taxonomies.
• REST API tool  – sending and receiving data from remote websites, headless builts, or any other application. 
• Profile Builder – a powerful functionality for creating advanced front-end user profiles – will be added in future releases. 

AI tools (integrations and APIs)

• AI Website Structure Builder – creates CPTs, custom fields, relations, taxonomies, loop templates, and filters according to your prompts. Creates a centralized dashboard to reach any content entity fast. It’s a trained built-in model that understands your prompts very well and doesn’t require your paid AI tool API.  
• MCP server and Command Center – using it, you can connect your AI tool using API and curate the website with agentic AI.  
• SQL query assistant – helps you build SQL queries, if needed. 

Additional tools

• Shortcode generator – create shortcodes to display custom content across the site.
• Glossaries – a tool for creating reusable data lists to use in dynamic fields. 
• Option pages – to create global data pages available on any page and controlled from one place. 

Typical Workflow When Working With JetEngine and Divi

There are definitely many ways to use JetEngine, but it usually starts with creating and displaying CPTs. So, we have these steps:

1. creating a custom post type; 
2. adding custom fields;
3. creating a Single template for this CPT;
4. adding actual content (or demo content);
5. fetching particular data;
6. creating a loop template called listing template in JetEngine and displaying it on the front end. 

With Crocoblock Divi integration, you get not only JetEngine but JetSmartFilters as well, so you can add filters to your content loop as well. 

This is how the whole process looks: 

📌 For a detailed guide on how to create content loops, check this guide. 
📌 To learn how to add filters, read this article. 

Want to make websites
powered by Divi-5 dynamic?

Check out how

Divi 5 Loop Builder vs. JetEngine

Divi 5 is now supporting a loop builder natively. So let’s see why you actually need JetEngine and the advantages it has.

How Divi’s Loop Builder works

The concept is straightforward: you take any Divi container, a section, row, column, or module, enable the Loop option on it, and Divi starts repeating that container for every item that matches your query. You design one card, wire up dynamic fields like post title, featured image, or excerpt, set how many items to show, and you’re done. It’s entirely visual, lives inside the Divi builder, and requires no code.

For querying, you get post type, terms, and users. You can include or exclude specific posts, filter by category or tag, set an offset, and order results by date, title, or ID. Additionally, you can select a content entity with a particular meta field value – to do it, you should type the meta field name and the value. 

Pagination is handled by a dedicated Pagination module that you drop onto the page and point at the loop.

It’s a decent solution, and for standard use cases, blogs, product grids, event listings, and team pages, it works cleanly and keeps everything inside one tool.

How JetEngine Loop Builder (Listing Grid) handles the same workflow

JetEngine separates the process into distinct steps, each with its own dedicated tool.

1. Query data using the Query Builder. Instead of a handful of options inside a container’s settings panel, you get a standalone query editor where you can build conditions across custom fields, meta values, relation data, taxonomic hierarchies, and user-specific data. You can query posts, users, comments, relations – basically any data type on your website.
   
   Talking about query conditions, you also have all existing options. For example, display only posts published within a particular time frame, with a certain combination of meta fields, with over a specific number of comments, posted by the user who has certain words in their bio.
   You can combine conditions with AND/OR logic, compare numeric ranges, filter by relationship connections between post types, and save queries to reuse across the site.
   This is a fundamentally different level of control compared to Divi’s tool.

2. Loop template. Now, you design the loop item inside a dedicated Listing Template editor powered by Divi Builder. Every element inside it is designed to connect to dynamic data, including data from related post types, user meta, option pages, or calculated values. You’re not adapting a general-purpose layout tool to handle dynamic content, but working in an environment built for it from the ground up.

3. Displaying all posts on the page. Now, you place the result on the page using a Listing Grid module. This is where things open up considerably. The same listing template can be dropped into a grid, a slider, a map, a calendar, a chart, or a filterable table, just by choosing a different module. The template stays the same, the data stays the same, only the presentation changes.
   On the contrary, in the native Divi loop, the loop and its container are the same thing, so switching from a grid to a map would mean rebuilding the whole setup.

Filtering

Filtering is powered by JetSmartFilters, which is another plugin but is included in the Crocoblock Divi package. 

So, Divi currently offers basic pagination and ordering. JetSmartFilters, in its turn, is a powerful AJAX-powered filter plugin that offers a variety of filter types. 

📌 Read more about JetSmartFilters integration for Divi here. 

So, which loop builder do you need in Divi 5?

If your content is standard WordPress posts, products, or taxonomy terms, and your loop is a grid or a list with basic sorting and pagination, Divi’s Loop Builder can be enough. 

If your content has a custom structure, if you need to query across relationships, filter results dynamically on the front end, or display the same data in multiple formats depending on context, JetEngine is doing work that Divi’s Loop Builder was never designed to do. And crucially, the two don’t conflict. JetEngine’s listing templates and modules sit inside Divi pages just like any other element, so you’re not choosing one tool over the other; you’re using each for what it’s actually built for.

Why Divi Needs JetEngine?

In the previous section, I talked particularly about the loop builder functionality of both tools. But let’s have a look at the bigger picture and take a simple example of a job board website. 

There, you will need Companies and Jobs CPTs, with jobs linked to companies. Each CPT has its own set of custom fields, like Salary Range, Location, etc. 

Divi’s Loop Builder can display jobs once everything is set up, but it has no tools to create that data structure or define those relationships. You’d be pulling in multiple separate plugins to fill each gap.

JetEngine covers that entire chain. You build the post types and fields inside it, define how Companies and Jobs relate to each other, set up the query logic with conditions as complex as your project needs, and then create the listing template that displays the result.

Now let’s go feature by feature.

• Data structure. Divi’s Loop Builder works with whatever post types and fields already exist in WordPress. It doesn’t create or manage them. JetEngine lets you build the entire content model from scratch, custom post types, custom fields, custom taxonomies, and relationships between them, all without touching code.

• Query logic. Divi gives you the standard WordPress query options: post type, category, tag, date, author, and a handful of others. JetEngine’s Query Builder lets you combine conditions across custom fields, meta values, relations, and user data, covering cases that would otherwise require custom WP_Query code.
• Relations. Divi has none. JetEngine lets you create all types of relationships between any content types, so a property can belong to an agent, an agent can manage multiple offices, and an office can have multiple amenities, all connected and queryable.
• Dynamic visibility. Divi has basic show/hide conditions. JetEngine lets you control the visibility of any element based on dynamic conditions, user roles, meta values, relation data, or custom callbacks.

So, the main idea here is that Divi and its Loop Builder, in particular, and JetEngine aren’t really competing but open new possibilities for Divi users, never available before. 

JetEngine and Divi: Performance

JetEngine doesn’t affect the Divi website performance negatively, as it doesn’t add heavy scripts or unnecessary front-end assets by default. Instead, it follows a modular architecture where you can enable only the features you actually use. This means no extra load from unused modules, which is a key difference compared to many all-in-one plugins.

On the front end, JetEngine outputs clean, structured data and works natively with Divi modules, avoiding redundant wrappers or deeply nested DOM elements. In case you want to achieve the most lightweight DOM structure, you can use Twig for listing templates and then use it in a Listing Grid in Divi.

From a database perspective, JetEngine gives you more control than most plugins. Features like Custom Content Types and Custom Meta Storage allow you to reduce reliance on the default WordPress postmeta table, which can become a bottleneck on large-scale sites. 

Properly structured data queries through the Query Builder are also more efficient than multiple WP_Query loops or poorly optimized third-party solutions.

However, performance still depends on how you build your project. Complex queries with multiple conditions, relations, and filters can increase server load if not optimized. The same applies to large datasets displayed without pagination or lazy loading. This isn’t a limitation of JetEngine itself, but rather how dynamic content systems work in general.

To keep things fast and scalable, I recommend:

• enable only the JetEngine modules you need;
• use Custom Content Types and Custom Meta Storage for CPTs where possible for large datasets;
• optimize queries and avoid unnecessary conditions;
• implement pagination, AJAX loading, or caching for listings;
• switch off unused views and select the Optimized DOM mode in JetEngine > JetEngine > Performance tab;
• combine JetEngine with proper hosting and caching. 

So, in real-world projects, if configured correctly, JetEngine can actually replace multiple plugins, which rather improves overall performance by reducing plugin bloat and conflicts.

FAQ

Wrapping Up

JetEngine transforms Divi 5 from a visual builder into a full dynamic content system. Instead of relying on multiple plugins, you can manage custom post types, advanced queries, dynamic visibility, and even AI-assisted workflows in one place. JetEngine offers a very flexible and modular approach, being at the same time an incredibly powerful plugin, but not slowing down your website and replacing many other plugins, thus saving your money and time.