Divi 5 Honest Review: Top Issues, Wins & What’s Next

I've Been Waiting for Divi 5 for Years — Here's My Honest Take

Let me be upfront with you. I've been building websites with Divi for a long time. It's the backbone of a lot of the work I do here at Ravenous Raven Design, and I've watched the Divi 5 development cycle unfold from the very beginning — the 2022 announcement, the alpha phases, the beta, the "we're releasing before end of year" promises that slipped into 2026. I've been patient. And for the most part, that patience has been worth it.

But I'm not going to sit here and tell you Divi 5 is perfect. It's not. There are real issues that real designers are dealing with right now — and some of them have cost me time on client projects. At the same time, there are things about Divi 5 that genuinely excite me, things I've been asking for since Divi 4 launched, and things that make me believe the long-term future of this builder is actually bright.

This isn't a sponsored post. This isn't a polished marketing overview. This is my real, working-designer perspective on where Divi 5 stands right now, what's broken, what's brilliant, and what I'm hoping Elegant Themes delivers in future releases. Let's get into it.

First — What Divi 5 Actually Is (And Why It Matters)

Divi 5 is not just an update. It's a complete rewrite of the builder from the ground up. Elegant Themes moved away from the old shortcode-based architecture that Divi 4 was built on — a system that worked, but had real ceilings when it came to performance and scalability — and rebuilt everything on a modern React-based framework. That's a massive undertaking. Like, genuinely massive. And it's the reason the release took years longer than anyone expected.

The shortcode system in Divi 4 was the source of a lot of the performance complaints over the years. Pages would get bloated, load times would suffer on complex builds, and the code output was notoriously messy. Divi 5's new architecture addresses all of that at the foundation level. That's the right call. It's the kind of foundational work that pays dividends for the next decade, even if it's painful to wait for.

By February 26, 2026, Elegant Themes officially removed the beta label. So Divi 5 is now the live, production version. About 40% of Divi users were already building on it before the official release. And while I'd been testing it in staging environments for months, I want to share the five issues that have been the most significant — and my workarounds for each one.

Issue #1: Third-Party Plugin Compatibility Is Still a Real Problem

This one hits hardest for anyone who has built out a client site with a solid ecosystem of third-party Divi plugins — DiviEngine modules, Divi Supreme, DiviFlash, custom marketplace extensions, you name it. The new Divi 5 API is a completely different architecture from Divi 4. That means every single third-party plugin had to be rebuilt from scratch to work natively with Divi 5. And most of them weren't ready at launch.

Elegant Themes built a backward compatibility system to bridge this gap — and credit where it's due, it mostly works. Unsupported modules run in "compatibility mode," which means they still display correctly on the frontend. But here's the catch: any page that contains a legacy module has to load the entire Divi 4 framework alongside the Divi 5 framework. You lose all of the performance benefits of Divi 5 on that page. Every. Single. Page. That has a legacy module.

For client sites with dozens of pages and multiple third-party modules on each one, this is not a minor issue. It's the difference between a site that loads in 1.5 seconds and one that loads in 3.5 seconds. That affects user experience, bounce rate, and SEO. It's frustrating — especially because some third-party developers were late to get access to the final Divi 5 API specs, which wasn't entirely their fault.

My Workaround

For new client projects, I've started auditing every third-party plugin before I even begin a build. I check the developer's Divi 5 compatibility roadmap — most reputable ones have them published — and if a plugin isn't fully rebuilt yet, I either find a native Divi 5 alternative or I plan the build without it. For existing client sites, I'm not rushing the migration. I'm watching the plugin ecosystem mature first, staging everything before touching a live site, and migrating in phases. Patience here is not weakness — it's the right strategy.

Issue #2: Migrating Existing Divi 4 Sites Is Nerve-Wracking

I want to give credit to Elegant Themes for building a migration system at all. Most major page builder rewrites at this scale have essentially said "sorry, start fresh." The Divi 5 migrator scans your site, converts compatible content, and flags what it can't handle. That's genuinely impressive work. But — and this is a big but — the migration process is still stressful, especially on complex, heavily customized client sites.

Responsive positioning settings that were configured in Divi 4 don't always carry over correctly. Custom CSS in child themes that referenced Divi 4-specific selectors breaks or behaves unexpectedly. Preset configurations need to be rebuilt in the new system. If your site has custom PHP hooks that relied on the Divi 4 API, those need to be rewritten. For a site with a hundred pages and years of accumulated customization, this is a significant undertaking.

There's also the psychological weight of it. Running a migration on a client's live site — even with a backup — carries real risk. And clients don't care about the technical explanation. They care that their website works. That pressure is real.

My Workaround

I don't migrate anything live without a full staging environment test first. That's non-negotiable. I run the migration on a staging clone, walk through every page manually, test every form and interactive element, check every responsive breakpoint on real devices — not just browser resize — and document every issue before I even think about touching the production site. It adds time to the project. I build that time into my quotes now. No exceptions.

Issue #3: The Builder Interface Has a Learning Curve — Even for Experienced Users

The Divi 5 interface is genuinely different from Divi 4. Not just visually — structurally. The way modules are added, the way presets work, the way the settings panels are organized, the new Command Center — it's all been redesigned. For someone coming from Divi 4 with years of muscle memory, the first few weeks feel slower than they should. Things you could do in three clicks before now take five, because you're searching for where Elegant Themes moved them.

The top bar UI, for instance, was recently reorganized because the original Divi 5 interface crammed too many tools into the same visual level. Finding the preview button, the history panel, the canvas switcher — it wasn't intuitive, and that's not me being picky. That's a UX problem that Elegant Themes acknowledged and is actively fixing. The updated top bar is cleaner. But the fact that these interface refinements are still rolling out in incremental updates means the experience is inconsistent right now depending on which version you're running.

For clients I've trained on managing their own Divi 4 sites, I'm also being careful about when to bring them into Divi 5. The workflow changes are significant enough that previous training sessions don't fully apply. That's an education overhead cost that falls on me.

My Workaround

I blocked out dedicated time to just play in Divi 5 — not on a client project, on a sandbox site where I could explore without consequences. I went through the new preset system, the Variable Manager, the Canvases feature, the Command Center. I rebuilt a few familiar layouts from scratch just to retrain my hands. That investment paid off. I'd recommend doing the same before you commit to a client build. And for client training, I've started creating updated screen recordings specific to Divi 5 — tailored to exactly what each client actually needs to manage on their own site.

Issue #4: Some Divi 4 Features Were Quietly Swapped Out

This one surprised me more than it should have. In early 2025, Elegant Themes published what they called the "Divi 5 Feature Swap" — an announcement that certain Divi 4 features wouldn't be making it into Divi 5's initial release. The reasoning was logical: instead of delaying Divi 5 further to rebuild every rarely-used legacy feature, they'd swap them out for new, more-requested features like flexbox grids, customizable breakpoints, and nested rows.

I get the decision. From a product strategy standpoint, it makes sense to prioritize what the majority actually uses. But for the minority that depended on those specific features — like the old Quick Actions workflow or certain Extend Styles configurations — this was a real disruption. No warning, no migration path for those specific workflows, just a post explaining why they were gone and a promise that some might return eventually.

The communication around this could have been better. A heads-up in the changelog before it happened — or a community vote with more transparency — would have reduced the frustration significantly. Instead, some users discovered missing features mid-project. That's not a good experience.

My Workaround

Before starting any new project in Divi 5, I audit which Divi 4 features I was relying on and confirm whether they exist in Divi 5, whether they've been replaced by a new feature, or whether they've been removed. The new Presets system replaces a lot of what Extend Styles did — often more powerfully — once you understand how it works. The new Variable Manager handles global fonts in a way that's actually cleaner than the old system. Most things I relied on have equivalents; I just had to find them. But you have to know to look.

Issue #5: The Release Timeline Eroded Trust in the Community

I'll say this as fairly as I can. The Divi 5 development cycle started with an announcement in November 2022. The stated goal was to release before the end of 2025. The beta label wasn't removed until February 26, 2026. That's over three years of development, multiple missed target dates, and a lot of "we're almost there" updates in between.

For solo designers and small agencies that plan their tech stack around tools like Divi, that uncertainty has a real cost. Decisions about whether to start new client projects on Divi 5, whether to migrate existing sites, whether to invest time learning the new system — all of those decisions were on hold in a kind of extended limbo. I've seen real frustration in the Divi community around this, and I understand it.

That said — and I mean this — building a complete rewrite of a page builder used by millions of sites worldwide is not a small task. I'd rather they took the time to do it right than rush it and ship something broken at scale. The backward compatibility system alone was a multi-year engineering challenge. So I hold both things at once: the frustration was valid, and the care that went into the product was also real.

My Take Going Forward

What I'd love to see from Elegant Themes is a more transparent, milestone-based communication cadence rather than calendar-based release estimates that slip. Tell me "we'll release when X, Y, and Z are stable" — not "we'll release by Q4." One is honest and specific. The other sets up disappointment. I think their community deserves that level of honesty, and I think it would actually restore a lot of goodwill.

What I Genuinely Love About Divi 5

Okay. I've been honest about the problems. Now let me be equally honest about why I'm sticking with Divi 5 and why I think it's the right long-term foundation for my business.

The Performance Gains Are Real

On pages that use only native Divi 5 modules — no legacy compatibility mode — the performance difference compared to Divi 4 is genuinely significant. Cleaner code output, faster server rendering, better Core Web Vitals scores. For clients where I've been able to build clean Divi 5 pages from scratch, the speed improvements have been measurable and meaningful. This is the payoff for all those years of foundational work, and it's exactly what I was hoping for.

The New Presets System Is a Game Changer for Agency Work

The stacked and nested presets in Divi 5 are something I've wanted for years. The ability to create reusable design configurations at the element, section, and sitewide level — and have them actually update across a site when you change the preset — is the kind of system that makes agency work scalable. In Divi 4, changing a global design decision meant hunting through individual modules. In Divi 5, it's one update that cascades. That's not a minor improvement. That's a workflow transformation.

Customizable Breakpoints Are Finally Here

I cannot overstate how much I've wanted this. The ability to set custom pixel widths for responsive breakpoints — beyond just the three fixed points of Divi 4 — means I can finally design for the actual device landscape instead of squeezing everything into three buckets. Phone, Phone Wide, Tablet, Tablet Wide, Widescreen, Ultra-Wide. Real, configurable breakpoints. This alone makes Divi 5 worth it for any designer who takes responsive design seriously.

The Command Center Is Genuinely Useful Once You Know It

The new Command Center — essentially a keyboard-driven shortcut system for adding, moving, and managing elements in the builder — is the kind of power-user feature that makes experienced Divi designers significantly faster. Once I built the muscle memory for it, my builder workflow got noticeably more efficient. It's one of those features that seems overwhelming at first and becomes something you can't work without after a couple of weeks.

The Foundation Is Finally Right

This might be the most important thing. Divi 4 was built on a codebase that had accumulated years of legacy debt. It worked — remarkably well, honestly — but there were real ceilings on what it could do without a complete rebuild. Divi 5's React-based foundation means that future features can be built faster, deployed more reliably, and maintained more easily. The pace of updates since the beta launch has already been noticeably faster than what we saw in the final years of Divi 4. That momentum is exactly what the community needed to see.

Divi 4 vs. Divi 5: Where Things Stand Right Now

Factor	Divi 4	Divi 5
Architecture	Shortcode-based (legacy)	React-based (modern framework)
Frontend performance (native modules)	Moderate — known bloat issues	Significantly faster, cleaner code output
Third-party plugin compatibility	Broad, mature ecosystem	Still maturing — compatibility mode for legacy modules
Responsive breakpoints	Three fixed breakpoints only	Fully customizable — 6 configurable breakpoints
Preset system	Global presets (limited)	Stacked and nested presets — sitewide design control
Migration from Divi 4	N/A	Available — staging test strongly recommended
Builder interface	Familiar, mature, well-documented	Redesigned — learning curve for experienced users
Feature parity with Divi 4	Complete	Near-complete — some legacy features swapped out
Update velocity	Slower in later years	Updates released every two weeks
Recommended for new builds?	Only if heavy plugin dependency	Yes — for native module builds
Recommended for existing site migration?	Stay if heavily plugin-dependent	Stage first, migrate in phases

What I Hope to See in Future Divi 5 Releases

Now that the beta label is off and the real-world build-and-iterate phase has begun, here's my honest wish list for where I hope Elegant Themes takes Divi 5 next.

A Fully Mature Third-Party Ecosystem — Sooner Than Later

This is the biggest one for me. The power of Divi has always been the ecosystem around it. If the third-party developers who build the extensions, modules, and child themes that expand Divi's capabilities don't have fully rebuilt, native Divi 5 products available soon, the platform loses one of its core competitive advantages. Elegant Themes needs to treat third-party developer support as a first-class priority — not an afterthought. More direct API support, faster responses to developer questions, and a more collaborative relationship with the ecosystem builders would go a long way.

Better Native Form and Dynamic Content Capabilities

Right now, complex forms, conditional logic, and dynamic content delivery in Divi still largely depend on third-party plugins. As those plugins mature into Divi 5, this will improve. But I'd love to see Elegant Themes build more native dynamic content capabilities directly into Divi 5 — custom field integration, more flexible loop builders, better conditional display options. The foundation is there. The content and data flexibility needs to catch up.

Improved Global Design Controls

The Variable Manager is a great step forward for managing global fonts and colors. But sitewide design decisions — spacing scales, typography hierarchies, global component libraries — still require more manual work than they should. A more robust design token system built into Divi 5 would make it genuinely competitive with headless and block-based approaches that offer deeper global design control. This is where I think Divi 5 has real room to grow.

Transparent, Milestone-Based Roadmap Communication

I said this earlier and I'll say it again: I'd love a public roadmap that tracks specific capabilities and stability milestones rather than calendar dates. "We'll release X feature when conditions A, B, and C are met" is more trustworthy and more actionable for designers trying to plan their work around Divi's capabilities. The community has been patient. Rewarding that patience with genuine transparency would strengthen the relationship between Elegant Themes and the people who have built their businesses on this platform.

Frequently Asked Questions

Should I migrate my existing Divi 4 site to Divi 5 right now?

It depends entirely on your plugin stack. If you're building with mostly native Divi modules and your third-party plugins have confirmed Divi 5 compatibility, the migration is worth doing — and the performance gains on native pages are real. But if your site relies heavily on third-party modules that are still in compatibility mode, I'd wait until those plugins have fully rebuilt Divi 5 versions. Running in compatibility mode means loading both frameworks, which eliminates the performance benefits of Divi 5 on those pages. The right move is to audit your plugin dependencies first, stage the migration thoroughly, and never touch a live site without a verified backup and rollback plan.

Is Divi 5 actually faster than Divi 4?

Yes — but with an important condition. Pages built entirely with native Divi 5 modules see meaningful performance improvements: faster server rendering, leaner code output, better Core Web Vitals scores. Pages that include any module running in backward compatibility mode load both the Divi 4 and Divi 5 frameworks simultaneously, which actually makes those pages slower than a clean Divi 4 build would have been. The performance story of Divi 5 is genuinely compelling — but only when you're running fully on the new system. Mixed-framework pages are a temporary regression, not a feature.

Can I still roll back to Divi 4 if something breaks after migrating?

Yes — Elegant Themes built a rollback option into the migration system specifically for this scenario. If you migrate and encounter serious issues, you can restore your Divi 4 content. However, this is not a perfect safety net, and it's not a substitute for a proper staging process. Complex customizations, custom PHP in child themes, and third-party plugin configurations may not roll back cleanly. Treat the rollback option as an emergency brake, not a reason to skip staging. Do the staging test. Always.

Is Divi 5 worth it for new website builds starting today?

For new builds that don't rely on legacy third-party modules, yes — I'd recommend starting on Divi 5. The new preset system, the customizable breakpoints, the Command Center, and the faster native performance all make it a stronger foundation for a new site than Divi 4 was. The caveat is the plugin ecosystem. Before you start, confirm that every third-party plugin you plan to use has a native Divi 5 version available. If it doesn't, build a plan around native alternatives until it does. Going in with clear eyes about what's available now versus what's coming makes the decision a lot cleaner.

Bottom Line: Divi 5 Is the Right Bet — Just Go In With Your Eyes Open

Here's where I land after all of this. Divi 5 is the right foundation. The architectural decisions that Elegant Themes made — ditching shortcodes, rebuilding on React, investing in backward compatibility, overhauling the preset system — those are the right calls for the long-term health of the platform. The features I've been asking for since Divi 4 are either already here or visibly on the way. The update velocity since the official release has been encouraging.

But the issues are also real. The third-party ecosystem isn't fully there yet. Migration on complex existing sites requires serious care and time. The interface has a real learning curve for experienced Divi 4 users. Some legacy features were quietly removed without enough communication. And the years of delayed timelines have cost Elegant Themes some community trust that they'll need to earn back through execution, not announcements.

My advice? Start using Divi 5 on new projects now, especially if you're building with native modules. Monitor the third-party plugin ecosystem closely and migrate existing sites in a controlled, staged process when your specific plugins are fully ready. Don't rush migration just because the official release is live. And give yourself real time to learn the new workflow before you're on a client deadline.

The long game here is good. I'm in. I just think the community deserves an honest picture of where things actually stand — not just the highlight reel.

If you're a Spokane-area business owner wondering how your website's platform affects your performance, SEO, and long-term maintenance costs, that's a conversation I'm always happy to have. Ravenous Raven Design builds and manages WordPress websites that are designed to perform — not just look good. Check out our web design prices, explore our web design portfolio, or WordPress Management options if you need someone to handle the technical side so you can focus on running your business. And if you want the unfiltered take on whether Divi 5 is right for your specific site, just reach out — I'll tell you exactly what I think.