Divi 5 is a ground-up rebuild of Divi, not a facelift. The shortcode-based page structure is gone, replaced by a block-style JSON format; the builder runs on a new rendering engine that is dramatically faster; and old Divi 4 workflows — child themes, custom CSS targets, third-party modules — all need a compatibility check. Here's what actually changed and what it means for a working site.
The big change: no more shortcode soup
Divi 4 stored every page as a wall of nested shortcodes. It worked, but it made content brittle — deactivate the theme and your content became tag salad. Divi 5 stores layouts in a structured format the builder can parse reliably. In practice: cleaner markup, faster saves, and far fewer "the builder timed out" afternoons.
What does Divi 5 mean for site speed?
This is the headline most owners care about. Divi 4's front end carried years of legacy CSS and JavaScript; Divi 5 renders leaner output and stops shipping styles for modules a page doesn't use. Sites I've rebuilt have gone from "optimize it with three plugins and hope" to passing Core Web Vitals with just sane image sizes and page caching. The theme is no longer the bottleneck — which, for Divi, is genuinely new.
What breaks when you switch?
- Third-party Divi modules built for Divi 4's API don't load until their developers ship Divi 5 versions. Inventory yours before migrating, not after.
- Child themes that override Divi 4 templates or hook its internals can fail quietly — the site runs, but customizations vanish. CSS-only child themes usually survive.
- Custom CSS targeting Divi 4's class names may need new selectors, because the rendered markup changed.
Should you migrate an existing site right now?
If your site is simple — standard modules, light customization — the migration is closer to routine than scary, and the speed payoff is worth scheduling it. If you depend on third-party modules or a heavily customized child theme, audit first and migrate on staging. That audit process is exactly what the next post in this series covers.
Frequently asked questions
Is Divi 5 stable enough for client sites?
Yes, with the usual caveat: stability is about your specific stack, not the theme in isolation. Test your plugin list on staging. I build new client sites on Divi 5 by default now.
Do Divi 4 layouts import into Divi 5?
Divi 5 converts Divi 4 layouts on migration. Standard layouts convert cleanly; layouts leaning on third-party modules convert with holes where those modules were. That's the main thing to check page by page.
Will Divi 4 keep getting updates?
Elegant Themes has maintained security support through the transition, but feature development lives in Divi 5. Staying on Divi 4 indefinitely is a slowly narrowing road — plan the move on your schedule rather than an emergency's.