THE SHORT ANSWER
Backward compatibility mode is how Divi 5 keeps old Divi 4 modules working. Any page that still holds one of them loads the Divi 4 framework, so it misses most of the Divi 5 speed gains. To get out, find every flagged module, swap it for a native Divi 5 module or an updated plugin version, then retest on staging.
Most agencies notice backward compatibility mode the same way: a red notice in the admin bar after a Divi 4 to Divi 5 migration, and a speed test that barely moved. The site works. It just isn’t really on Divi 5 yet.
Here is what the mode does, what it costs your clients, and the order we use to get pages out of it in 2027.
01What is backward compatibility mode?
It is a safety net. When Divi 5 finds content it can’t convert natively, such as a third-party Divi 4 module or an old layout, it loads the Divi 4 framework so that content keeps rendering and stays editable.
- It switches on automatically when Divi 5 finds legacy modules, layouts or plugins.
- A notice in the admin bar tells logged-in users that legacy content is running.
- Legacy modules can still be edited in the Visual Builder, though settings changes can trigger slower reloads.
- Visitors see a working page. Nothing looks broken.
02What does it cost?
Mostly speed, and the speed is the reason clients pay for the upgrade.
| Area | Native Divi 5 page | Page in compatibility mode |
|---|---|---|
| Framework loaded | Divi 5 only | Divi 5 plus the Divi 4 framework |
| Front-end speed | Full Divi 5 gains | Most gains lost on that page |
| Editing | Fast, all new features | Legacy modules reload slowly |
| Future updates | Supported going forward | Depends on the module’s developer |
FROM OUR DESK
The usual culprit is one small add-on module on the home page, like a fancy heading or a testimonial slider. Swap that one module and the most visited page on the site goes fully native.
03How do you find the pages that use it?
Use the Divi 5 Migrator, not guesswork. It lists incompatible pages, posts, Theme Builder templates, library items, modules and plugins.
- Run the Migrator scan on a staging copy and export or screenshot the results.
- Group the flags by module, not by page. One plugin often accounts for most of them.
- Check Theme Builder headers and footers first. A legacy module there affects every page.
- Note which pages get the most traffic. Fix those before the long tail.
04How do you get out of it?
Work through each flagged module with one of three fixes.
- Update: the plugin developer has released a Divi 5 version. Update on staging and rescan.
- Swap: a native Divi 5 module does the same job. Rebuild that section with it and match the styling with presets.
- Replace: nothing native fits. Rebuild the feature as a small custom module or with a lighter plugin.
DON’T DELETE THE PLUGIN FIRST
Removing a third-party Divi plugin before its modules are rebuilt leaves empty gaps on live pages. Rebuild the sections, check them, then deactivate the plugin.
Stuck in compatibility mode?
We rebuild flagged modules natively on staging and send a before and after speed report. Fixed quote in 24 hours.
05When is it fine to stay in it for now?
Compatibility mode is not an emergency. It is fine as a short-term state when a key plugin has a Divi 5 version on the way, or when the page gets little traffic. Keep a list, recheck it monthly, and clear the busy pages first. If you are still deciding which sites to move at all, start with our Divi 5 decision guide.
06FAQ
Does backward compatibility mode break anything?
Usually not. Its job is to keep legacy content working. The cost is speed and slower editing, not broken pages.
Is compatibility mode per page or per site?
It applies wherever legacy content loads. A legacy module in a global header or footer pulls the Divi 4 framework onto every page, so fix those first.
How long does it take to get a site fully native?
For a small site with one or two add-on modules, often a day. Sites with many third-party modules or custom code can take a week, mostly for rebuilding and testing.
Can shortcodes from other plugins stay?
Yes. Shortcodes from non-Divi plugins keep working. Test their output on staging after the move.
