Should You Update to Divi 5?

Whether you should update to Divi 5 comes down to one question that Elegant Themes’ own Migrator answers for you in about a minute: does your site contain modules Divi 5 cannot render natively? If the scan is clean, update — the performance work is the entire point of the rewrite. If it flags legacy or third-party modules, those specific pages will quietly load the old Divi 4 framework after you migrate, and you will have paid the migration cost without collecting the benefit.

That is the decision in one paragraph. The rest of this page is the detail behind it: what actually changed, what was removed, what the one-way migration means in practice, and the page-level trap that is easy to trigger before you have migrated anything at all.

The three outcomes of a Divi 5 Migrator scan. Built from Elegant Themes’ migration and backward-compatibility documentation, read 30 August 2026.

Should you update to Divi 5? Start with the Migrator scan

Elegant Themes ships a scanner rather than asking you to guess. In the WordPress dashboard, Divi → Divi 5 Migrator runs a compatibility scan across pages, posts, custom post types, theme templates, WooCommerce products, library items, widgets and presets. It reports which of those contain modules Divi 5 supports natively and which do not.

The scan is the decision. Read it this way:

• Nothing flagged. Migrate. Every page moves to the Divi 5 rendering path and you get the performance work the rewrite was for.
• A handful of pages flagged. Migrate a staging copy, fix or replace the modules on those pages, then migrate production. The flagged pages are the only ones that lose out.
• Most of the site flagged, or the flagged modules come from a Divi Marketplace extension with no Divi 5 support yet. Wait. You would be migrating into backward-compatibility mode across the board, which is the worst of both worlds.

Before the scan, Elegant Themes asks for three things in its migration guide: back up “your entire Divi 4 website first — including the database, uploads directory, and all theme and plugin files”; create a staging site; and “update WordPress, Divi, and all plugins before you migrate. Running the migration on outdated software increases the chance of conflicts.” It also asks you to check each Divi Marketplace extension’s product page for a “Compatibility with Divi 5” tag.

What actually changed in Divi 5

Divi 5 is a rewrite, not a feature release. The headline is that the shortcode-based storage format is gone — the thing every Divi review, including our own Divi theme review, spent years warning readers about as a lock-in risk. Content is no longer stored as nested shortcodes in the post body.

Since the 26 February 2026 release, Elegant Themes has been shipping into 5.x steadily rather than treating the launch as the finish line. From its published Divi 5 update status page, read on 30 August 2026:

Version	Released	Notable in that release
5.11.1	19 Aug 2026	Improvements and bug fixes — current release
5.11	13 Aug 2026	Gravity Forms module, Charts module
5.10.1	9 Aug 2026	Bug fixes only
5.10.0	7 Aug 2026	New features, improvements, bug fixes
5.9.0	9 Jul 2026	Grid Editor
5.8.0	19 Jun 2026	Tooltip module
5.7.4	12 Jun 2026	Workspace management system

Two things are worth reading out of that table rather than skimming past it. The first is cadence: eleven minor releases in roughly six months, with two bug-fix-only releases landing on the same day in June. That is an actively maintained product, not a launch-and-leave. The second is that modules people expected at launch — a Gravity Forms module, a Charts module, the Grid Editor — arrived through the spring and summer. If you evaluated Divi 5 in March and concluded it was missing things, the version you evaluated is five months and nine releases out of date.

One thing has not arrived. Elegant Themes describes Full Site Editing as “nearly complete and will be released following Divi 5’s official release.” It publishes no date for it.

What Divi 5 removed, and what that costs you

Two features are being deprecated: Quick Action and Split Testing.

Quick Action is a keyboard-driven command palette, and Divi 5 has introduced its own command interface, so the loss there is a change of habit rather than a change of capability.

Split Testing is different, and it is the strongest single argument for staying on Divi 4 right now. Divi’s built-in A/B testing let you test module-level variants — a different button colour, a different headline — without a third-party tool, and Elegant Themes names no replacement for it. If you are running live tests through it, migrating means either giving up the tests or moving them to an external testing tool and rebuilding them. That is real work with a real cost, and no page-one result for this query mentions it.

Child themes and custom CSS are a softer case. Elegant Themes says they “should continue to work,” while noting that “some code adjustments may be necessary.” That is a vendor hedging on other people’s code, which is fair enough, but it means a heavily customised site should be treated as a stage-first site regardless of what the Migrator scan says. If your customisation is mostly child-theme templates rather than module code — the pattern in most of the setups covered in our roundup of Divi blog child themes and modules — you are on the safer side of that line.

Backward compatibility is not the safety net it sounds like

This is the part most coverage gets wrong, because “backward compatible” sounds like “nothing breaks” and stops there. Nothing does break. Something quieter happens instead.

When a page contains a module Divi 5 does not support natively, Divi loads the Divi 4 framework to render it. In Elegant Themes’ own words, from its backward compatibility documentation: “pages using these legacy modules will not benefit from Divi 5’s performance enhancements.” The scope is per-page, not site-wide — “Only pages with unsupported Divi 4 modules will experience slowdowns due to the Divi 4 framework being loaded,” while “Pages using modules fully supported by Divi 5 will maintain optimal performance without any impact on speed.”

So a migrated site can end up with two classes of page: fast ones on the new rendering path, and slow ones still dragging the old framework, with nothing on the front end to tell them apart. Divi does flag it — “For pages utilizing unsupported Divi 4 modules, a notification will appear in the WordPress Admin bar” — but only for a logged-in user viewing that page. Visitors see the slow page and nothing else.

There is an editing cost too. Working on a legacy module inside the Divi 5 builder “will require an Ajax reload after any setting is changed.” If you have ever wondered why a Divi site feels slow in the builder, an Ajax round-trip on every setting change is exactly the kind of thing that produces that feeling — and here it is a documented consequence of migrating with legacy modules still in place rather than a misconfiguration you can fix.

Elegant Themes publishes no figures quantifying the performance gap between the two paths. The direction is stated plainly in its documentation; the size of it is not.

The one-way migration, and the trap before it

“Switching from Divi 4 to Divi 5 is a one-way update via the Migrator.” Rollback exists — Elegant Themes publishes a rollback guide and the Migrator automatically creates content backups — but the guidance is candid about it degrading: “the longer you run Divi 5 and edit content, the harder a clean rollback becomes.”

The trap sits earlier than that, and it is the single most useful sentence in the whole migration guide: “Opening a page before migrating causes Divi 5 to convert it immediately without the option to roll it back.”

Read that carefully. It means the dangerous moment is not clicking the migrate button. It is installing Divi 5, deciding to “just have a quick look at how one page renders,” and opening that page in the builder. That page is now converted, individually, outside the Migrator, with no rollback for it. On a site where you were still deciding, you have just made the decision for one page and lost the ability to compare.

The practical rule that follows: after installing Divi 5 and before running the Migrator, do not open anything in the builder. Run the scan, read it, then either migrate or roll back — but do not browse.

Staying on Divi 4: what you keep and what you give up

Staying is a legitimate choice, and Elegant Themes treats it as one. Divi 4 “will be fully supported for at least 12 months” after the 26 February 2026 release, receiving “security patches and critical bug fixes.” What it does not receive is new development: “No new features are being developed for it.”

That framing matters because “at least 12 months” is a floor with no stated ceiling, announced in February. It is not a deadline you need to act on this month, but it is also not an open-ended commitment. Anyone choosing to stay should treat the decision as revisitable rather than settled.

	Divi 4	Divi 5
New features	None being developed	Shipping continuously — 11 minor releases since February
Support window	Security and critical fixes, at least 12 months from 26 Feb 2026	Current product
Split Testing	Available	Deprecated, no stated replacement
Third-party modules	Work normally	Native if updated; otherwise legacy mode, per page
Reversibility	n/a	One-way; rollback degrades with use
Full Site Editing	No	“Nearly complete”, no published date

Cost: what the update to Divi 5 does and does not add to your bill

Nothing. Elegant Themes states it directly in its Divi 5 FAQ: “No, Divi 5 will be available free of charge to any Elegant Themes user with an active subscription.” There is no Divi 5 upgrade SKU and no paid migration tier.

If your membership has lapsed and you are pricing a return, the figures as listed on Elegant Themes’ own pricing pages on 30 August 2026 are $89 billed yearly, $249 for Divi Lifetime, $277 a year for Divi Pro, and $297 today then $212 a year for Divi Lifetime + Pro. Refunds are 30 days, no questions asked. We go through what the marketing calls a discount — and what it actually is — on our Elegant Themes coupon page.

See current Divi pricing at Elegant Themes

That is an affiliate link — if you buy through it, WPNeon earns a commission at no extra cost to you. It does not change what this page says about Split Testing or the one-way migration.

If you are choosing Divi for the first time

Everything above assumes an existing Divi 4 site. If you are starting fresh, none of it applies: there is nothing to migrate, no legacy modules, no one-way decision. You install Divi 5 and build on the current rendering path.

The first-time question is a different one — whether Divi is the right builder at all. That comparison is worth making against Beaver Builder and against Themify Ultra, both of which trade differently on lock-in and learning curve. If you want to see what people actually ship with it, our collection of Divi theme examples is a better guide to the ceiling than any feature list, and the Divi Theme Builder WooCommerce walkthrough covers the case where Divi’s template control earns its keep. The membership also carries Bloom, which is worth factoring into the price rather than treating as a bonus.

Divi is not listed in the WordPress.org theme directory, so there is no independent active-install count, rating or “tested up to” figure for it the way there is for a free theme. Every usage number published about Divi originates with Elegant Themes. We say where each figure comes from and when we read it, which is the standard set out in how WPNeon reviews WordPress products — the same approach we take to fast-moving areas like WordPress MCP servers, where vendor claims outnumber independent checks by a wide margin, and to the security trade-offs each MCP setup exposes.

Frequently asked questions

Is the update to Divi 5 free?

Yes. Elegant Themes states that “Divi 5 will be available free of charge to any Elegant Themes user with an active subscription.” There is no upgrade fee, no separate Divi 5 licence and no paid migration service. An active membership is the only requirement, and lapsed members pay the normal renewal price.

Can I roll back from Divi 5 to Divi 4?

Yes, immediately after migrating, using Elegant Themes’ rollback guide and the content backups the Migrator creates automatically. It gets worse with time: Elegant Themes warns that “the longer you run Divi 5 and edit content, the harder a clean rollback becomes.” Treat rollback as a same-day option, not a standing one.

Will my third-party Divi modules break?

They will not break, but unsupported ones force Divi to load the Divi 4 framework on any page that uses them, so those pages get none of Divi 5’s performance work. Editing them also requires an Ajax reload after every setting change. Check each extension’s Divi Marketplace page for a Divi 5 compatibility tag first.

What is the latest version of Divi?

Divi 5.11.1, released 19 August 2026 according to Elegant Themes’ update status page, read on 30 August 2026. Divi 5 reached official release on 26 February 2026 and has shipped eleven minor versions since, including the Gravity Forms and Charts modules in 5.11 and the Grid Editor in 5.9.

How long will Divi 4 keep working?

Elegant Themes commits to full support for “at least 12 months” from the 26 February 2026 Divi 5 release, covering security patches and critical bug fixes. No new features are being developed for Divi 4. The twelve months is a stated floor rather than an end date, so plan to revisit the decision rather than assume indefinite support.

Should I update to Divi 5 on a live site directly?

Only if the Migrator scan is completely clean and you have a current backup. Otherwise migrate a staging copy first. Critically, after installing Divi 5 do not open any page in the builder before running the Migrator — doing so converts that page immediately with no rollback available for it.