If you’re searching for how to update Divi, there’s a good chance the update badge is sitting in your dashboard right now, and you’re deciding whether it’s safe to click.
That hesitation makes sense, because a theme that controls every page, header, and form on your site can change a lot in the few seconds an update takes. And most of us have heard about a layout shift or a contact form going quiet right after one.
We’ve seen plenty of these updates go smoothly and a handful go badly, and the difference rarely came down to the Divi release itself.
It came down to what was in place before the click, which is exactly where this guide begins, and it covers every situation you might be in, whether your site is running perfectly or already showing an error.
TL;DR: Connect your Elegant Themes account, take a full backup using a reliable backup plugin, and test the update on a staging copy before the live site ever sees it. If you’re moving from Divi 4 to Divi 5, treat it as a migration with its own steps, since rolling it back gets harder the longer you wait.
Find your situation
People arrive at this question from very different places, and the right first move depends on where you’re standing. This table points you to the part of the guide that will help you fastest.
| Where you are right now | Where to go |
|---|---|
| Your site works, and you want to update safely | Read the guide from the top |
| The Divi update isn’t showing up | Fix problems after an update |
| You updated, and something looks wrong | Fix problems after an update |
| Your site shows a critical error or won’t load | Fix problems after an update |
| You’re still on Divi 4 and wondering about Divi 5 | Moving from Divi 4 to Divi 5 |
| The automatic update keeps failing | Update Divi manually |
📝 Note: If your site is down right now, skip straight to the troubleshooting section. Everything else can wait until your visitors can reach you again.
Know which Divi you have
“Updating Divi” can mean three different jobs, and mixing them up is the quickest way to end up on the wrong settings screen.
Most people run the Divi theme, which bundles the Visual Builder, and they manage its updates under Divi > Theme Options.
A smaller group runs the Divi Builder plugin on top of a different theme, and their settings live under Divi > Plugin Options instead.
The third job is the move from Divi 4 to Divi 5, the rebuilt version that launched in February 2026. That one converts your content to a new format, so it gets its own section further down, and everything before it applies to routine theme and plugin updates.
📝 Note: Not sure which version you’re on? Go to Appearance > Themes and click the Divi theme card, where WordPress lists the exact version number.
Prepare before you click
Preparation takes about ten minutes, and in the updates we’ve seen go badly, at least one of these steps was missing. Each one gives you a way back if the new version doesn’t behave, so it’s worth doing all of them before you click Update.
Skim the changelog for anything that touches your important pages. Elegant Themes publishes release notes for every version, and you only need to look for changes near your forms, your store, or any third-party Divi module you depend on. Waiting a day or two after a release also lets the Divi community groups surface any bugs before they reach you.
Find out where your custom code lives before Divi overwrites it. Any code edited directly inside Divi’s own theme files disappears the moment you update, which is exactly what happened to that missing snippet.
Code added through a child theme, the code boxes in Theme Options, or a snippets plugin survives, so move any direct edits into a child theme first.
Before moving those edits, back up your current theme files so you have a copy of the customizations you’re protecting.
Backup your files and database somewhere other than your server. A backup stored on the same server can vanish along with the site it was meant to protect. BlogVault keeps encrypted copies off your server and can restore your whole site in one click, even when the dashboard won’t load.
Create a staging copy where you can test without visitors watching. A staging site is a private clone of your website, and anything that breaks there never reaches your customers. If you use BlogVault, open the Staging section and click Add Staging, and you’ll have a copy ready to log into within minutes.
📝 Note: Your pages, layouts, and Theme Builder templates are stored in the database, so a normal update leaves them alone. The real risk is code that someone edited inside Divi’s own files.
Connect your Elegant Themes account
Divi only offers updates to sites linked to an active Elegant Themes membership, so a missing connection is the most common reason people never see the update at all. You need your Elegant Themes username and an API key, which you’ll find by logging in to the members area and opening Account > Username & API Key.
Open the Updates tab in your Divi settings. Go to Divi > Theme Options for the theme, or Divi > Plugin Options for the Builder plugin, and click Updates.
Paste your username and API key, then save. Watch for an invisible space before or after the key, since that tiny mistake causes a surprising number of failed authentications.
Older Divi sites sometimes run a separate plugin called Elegant Themes Updater, with the account fields under Settings > General. Current versions of Divi don’t need it, because they update through the regular WordPress screen once your key is saved.
📝 Note: Elegant Themes lets you create a separate, labelled API key for each website. If you ever sell or hand over a site, you can switch off that one key without touching any other site.
Update on staging and test it properly
With your account connected and a safe copy ready, the update itself takes about a minute. Log in to your staging site, go to Dashboard > Updates, click Check Again if Divi isn’t listed, then select it and click Update Themes (or Update Plugins for the Builder plugin).
The success message that follows only confirms that the files installed, so the real test is clicking through the site the way a visitor would. Open your homepage, your busiest landing pages, and your Theme Builder headers and footers on both a phone and a desktop, since responsive layouts are often the first thing to shift.
Then try the parts of the site that do something, such as sending a test form, opening a slider or tab, adding a product to the cart, or logging in as a member.
If anything breaks at this stage, stop and celebrate a little, because staging just did its job. Your live site is untouched, and the troubleshooting section below covers the usual causes.
📝 Note: Pay extra attention to pages built with third-party Divi modules. Those modules come from other developers, so they’re more likely to lag behind a new Divi release.
Take the update live
- Once staging looks right, the live update becomes the calmest part of the whole process. Take a fresh backup of the live site first, so your restore point reflects today’s orders and comments rather than last week’s.
- Push the tested copy live or repeat the update. In BlogVault, open the Staging section and click Merge to move your tested staging site to live, or simply run the same update through Dashboard > Updates on the live site.
- Run the same checks again on the live site. Your live site has real traffic, caching, and sometimes a CDN in front of it, so a quick second round of testing confirms that visitors see what you saw on staging.
📝 Note: Divi has a built-in Version Rollback button under Divi > Theme Options > Updates. It returns the theme to the version you had before, though it doesn’t undo database changes, so your backup remains the stronger safety net.
Moving from Divi 4 to Divi 5
Moving to Divi 5 deserves more care than a routine update, because it changes how your content is stored. Divi 5 replaces the old shortcode system with a new format, and a built-in tool called the Divi 5 Migrator converts your existing layouts.
There’s also no rush. Elegant Themes has said Divi 4 will be supported for at least 12 months after Divi 5 launched on February 26, 2026, and Divi 5 costs nothing extra if your membership is active. When you’re ready, run the whole move on staging first.
- Bring WordPress, your plugins, and Divi 4 fully up to date. The option to switch only appears in Divi 4.27.6 or later, and your third-party Divi extensions should be on their Divi 5-ready versions where those exist.
- Switch on Divi 5 updates and install it. Go to Divi > Dashboard, click Enable Divi 5 Updates, and run the update.
- Run the Divi 5 Migrator and check your pages. Open Divi > Divi 5 Migrator, let it convert your content, then test carefully, especially pages that use third-party modules or custom code.
Modules that haven’t caught up with Divi 5 yet keep running through a compatibility layer, though Elegant Themes notes those pages can load more slowly until the module’s developer releases an update.
📝 Note: Elegant Themes describes this move as one-way. The Migrator can restore your Divi 4 content right after migrating, but the more you edit in Divi 5, the harder a clean rollback becomes, which is why your pre-migration backup matters so much here.
Update Divi manually
If the automatic update keeps failing, you can install the new version yourself without deleting anything first. Older guides tell you to switch to another theme and delete Divi before uploading, but WordPress has handled this more safely for years.
- Download the latest Divi file from your Elegant Themes account. Save the .zip file to your computer and take a backup of your site before going further.
- Upload it and let WordPress replace the old version. Go to Appearance > Themes > Add New Theme > Upload Theme, choose the file, click Install Now, and then click Replace active with uploaded when WordPress notices the theme already exists.
WordPress swaps the files while keeping your settings and content in place, so all that’s left is to clear your caches and test the site as usual.
📝 Note: A manual upload won’t fix a broken account connection. If updates never appear because authentication failed, solve that first so future updates arrive normally.
Fix problems after an update
Most Divi update problems fall into a handful of patterns, and each one has a sensible first move. Start with the heading that matches what you’re seeing.
The update doesn’t appear
Check that you entered your username and key on the right screen, Theme Options for the theme or Plugin Options for the Builder plugin, and that your membership is still active. WordPress also caches update notices for a while, so clicking Check Again on Dashboard > Updates and giving it some time often solves the problem on its own.
Your changes aren’t showing
Stale caches cause most of these cases, so clear your browser cache along with any caching plugin or host cache. Divi also keeps its own copy of your styles, which you can reset by going to Divi > Theme Options > Builder, finding Static CSS File Generation, and clicking Clear.
The layout shifted or a module stopped working
Clear Divi’s static CSS first, because outdated styles cause a surprising share of broken layouts. If the problem stays, check whether the affected page uses a third-party module or custom code, and look for an update from that developer. A customization that vanished completely was almost certainly edited inside Divi’s own files, so restore that code from your backup into a child theme.
The site is stuck in maintenance mode
A message saying the site is briefly unavailable for maintenance usually means the update stopped partway through. WordPress leaves a file called .maintenance in your site’s main folder during updates, so delete it through your host’s file manager or FTP and then check whether Divi finished updating.
Your site shows a critical error
A critical error after an update usually means a plugin doesn’t work with the new version. Divi’s Safe Mode, found under Divi > Support Center, temporarily switches off plugins, your child theme, and custom code for your account only, which tells you quickly whether something outside Divi is to blame. If Safe Mode clears the error, turn plugins back on one at a time on staging until the error returns, and you’ve found the culprit.
If you can’t log in at all, check your admin email for a WordPress recovery mode link, which lets you sign in with the faulty plugin paused. When even that fails, restore your backup to get the site back first and investigate on staging afterward, rather than experimenting on a live site your visitors can’t reach.
Divi won’t authenticate
Recheck your username, look for that hidden space around the key, and confirm your membership is active. The problem is occasionally on Elegant Themes’ side, so trying again later is worth a shot, and you should never paste your API key into a public forum while asking for help.
📝 Note: Write down what you changed and what you saw before you start fixing things. If you end up contacting Elegant Themes support, those notes will get you a useful answer much faster.
How often to update Divi
Regular updates are part of keeping your site secure, because they carry security fixes along with bug fixes, new features, and support for new WordPress versions. Skipping several in a row makes each future update larger and more likely to cause trouble, which is the opposite of what you want.
A good rhythm for most sites is to read the changelog when a release appears, give it a day or two, test it on staging, and then update the live site. That keeps you current without making you the first person to discover a new bug.
📝 Note: If you run several WordPress sites, update and test one first. Problems tend to repeat across similar sites, so the first one becomes your early warning.
FAQs
Will updating Divi delete my pages or designs?
No, a normal update leaves your content alone. Pages, layouts, and Theme Builder templates live in the database, and only code edited inside Divi’s own theme files gets overwritten.
Can I undo a Divi update if I don’t like it?
Yes, in two ways. Divi’s Version Rollback button returns the theme to your previous version, while restoring the backup you took beforehand returns the whole site, including the database, to how it was.
What happens if my Elegant Themes membership expires?
Your site keeps working exactly as it is today. You just stop receiving Divi updates, which means missing security fixes and WordPress compatibility updates until you renew.
Do I need to update my Divi child theme?
No, you update the parent Divi theme and leave the child theme in place. After the parent update, test your site on staging and adjust the child theme’s code only if something conflicts with the new version.
Should I turn on automatic updates for Divi?
For a site that earns money or collects leads, we’d keep updates manual. Automatic updates skip your backup and staging test, which removes the exact steps that make an update safe.
Conclusion
Every smooth Divi update we’ve seen had the same quiet foundation underneath it: a backup that could be restored, a staging copy to test on, and a few minutes spent checking the pages that matter most.
With those in place, a release that misbehaves becomes a small fix on a private copy rather than a scramble on your live site. So the next time that badge appears, set up your safety net first, and the click itself will be the easiest part.
Akshat is the founder and CEO of BlogVault, MalCare, and WP Remote.
