How to Update Elementor and Elementor Pro Safely

Elementor is on millions of WordPress sites, and it updates often. Most updates are uneventful. Some are not: a section loses its styling, a widget disappears, the editor will not load, or a popup stops opening. Because Elementor controls your layout, an Elementor update going wrong is visible on every page at once.

This guide gives you a safe routine for updating Elementor and Elementor Pro, the one rule about the two plugins that causes most problems, how to roll back when an update goes wrong, and how to know within minutes whether an update changed anything on your live pages.

Why Elementor updates break sites more often than other plugins#

• It renders your layout. A change in how Elementor outputs HTML or CSS shows up on every page built with it.
• Two plugins, one system. Elementor (free) and Elementor Pro are separate plugins that must stay compatible with each other.
• A large add-on ecosystem. Third-party widget packs and themes hook deep into Elementor. When Elementor changes, add-ons that have not caught up can break.
• Generated CSS files. Elementor saves page styles as CSS files. After an update, stale files or caches can make pages look broken even when nothing is actually wrong.
• Big version jumps. Major releases, such as Elementor 4.0 and its Atomic Editor in March 2026, change a lot at once.

Before you update: the 5-minute checklist#

1. Take a full backup of files and database. Your host's backup or a plugin such as UpdraftPlus works. See our WordPress maintenance checklist for a routine.
2. Read the changelog. Open the Elementor and Elementor Pro changelogs and look for words like "breaking", "deprecated", "requires" or anything about your widgets.
3. Check your add-ons. Elementor shows a compatibility notice on the Plugins screen for add-ons that have not declared support for the new version. Update add-ons first if they have newer versions, or wait if they have not caught up.
4. Note your current versions of Elementor and Elementor Pro. You need them if you have to roll back.
5. Pick a quiet time. Not right before a sale, a launch or a newsletter send.

The one rule: keep Elementor and Elementor Pro in step#

Most "Elementor update broke my site" stories come from updating one of the two plugins and not the other. Elementor Pro depends on the free Elementor plugin and expects a matching version range.

• Update both in the same session, free Elementor first, then Elementor Pro.
• Make sure your Pro license is active (Elementor > License), otherwise Pro updates will not appear in your dashboard.
• Do not leave auto-updates on for only one of them. If you use automatic updates, enable them for both or for neither. Our guide to WordPress automatic updates explains how to control them per plugin.

How to update Elementor step by step#

1. Test on staging first (recommended for big updates)#

Create a staging copy with your host's one-click staging or a plugin, update there, and check your pages. Our WordPress staging site guide shows how. For minor releases on a simple site you can skip staging, as long as you have a backup and check afterwards.

2. Update the plugins#

1. Go to Dashboard > Updates or Plugins > Installed Plugins.
2. Update Elementor first.
3. Update Elementor Pro right after.
4. Update any Elementor add-ons that have new versions.

If Elementor asks you to run a database update after updating, back up first if you have not already, then run it. This step migrates data to the new version's format.

3. Clear generated files and caches#

1. In wp-admin, go to Elementor > Tools and click Clear Files & Data (called Regenerate Files & Data in older versions). This rebuilds Elementor's CSS files.
2. Clear your caching plugin's cache and, if you use one, your CDN cache (Cloudflare and similar).
3. Clear your browser cache or use a private window before you judge the result.

4. Check what matters, not just the home page#

Open your most important pages in a private window: home page, key landing pages, pricing, contact form, cart and checkout if you run WooCommerce. Check on desktop and mobile. Look for:

• Missing sections, widgets or images.
• Broken spacing, fonts or colors.
• Menus, popups, sliders and forms that do not respond.
• Header and footer templates (Theme Builder) still showing.

Open the Elementor editor on one page too, to make sure it loads.

How to roll back Elementor after a bad update#

If an update breaks something you cannot fix quickly, roll back first and investigate later.

Use Elementor's built-in rollback#

1. Go to Elementor > Tools > Version Control.
2. Under Rollback Version, choose the version you had before and click Reinstall.
3. Do the same for Elementor Pro if you updated it too, so the two stay in step.
4. Clear Elementor's files and your caches again, then check your pages.

Other ways to roll back#

• Download a previous version from the Elementor plugin's Advanced View page on WordPress.org and upload it under Plugins > Add New > Upload Plugin, choosing to replace the current version.
• Use WP-CLI: wp plugin install elementor --version=x.y.z --force.
• Restore the backup you took before updating. This is the safest option when the update ran a database migration.

After rolling back, turn off auto-updates for Elementor until a fixed version is out. For more detail, read how to roll back a WordPress plugin.

Should you update to Elementor 4 and the Atomic Editor?#

Elementor 4.0 (released March 30, 2026) introduced the Atomic Editor, a new way of building with atomic elements, classes and components. Elementor's guidance is that existing designs keep working as before, while the new atomic elements are what new builds use.

That makes the switch lower risk than it sounds, but it is still a major update:

• Test it on staging first, especially if you rely on third-party Elementor add-ons.
• Update add-ons before or together with Elementor 4.
• Expect to learn new controls before rebuilding existing pages with atomic elements. There is no need to convert pages that work.

Updating Elementor on many sites (agencies)#

If you manage client sites, the risk multiplies. A routine that scales:

1. Update one low-traffic site first and wait a day.
2. Update the rest in batches, never all at once.
3. Check each site's key pages after updating, or use monitoring that does it for you.
4. Keep a note of which sites use which add-ons, so you know where a known add-on problem will hit.

Know within minutes if an Elementor update changed your site#

The hard part of Elementor updates is not clicking Update. It is noticing that the button on page 14 lost its styling, or that a popup stopped opening, before a customer does. The free MyKavo WordPress plugin is built for exactly that:

• Every update recorded and checked. Elementor, Elementor Pro, add-ons, themes and core, including automatic updates at night. On paid plans, from Starter, MyKavo checks your key pages right after each update and labels any change with the update behind it: "Appeared after: Updated Elementor 3.x to 4.x".
• Before-and-after screenshots. Drag a slider across the old and new version of a page to see exactly what moved.
• Snapshots of premium plugins (free). Right before WordPress updates a plugin, MyKavo saves a copy, so even Elementor Pro, which is not on WordPress.org, can be rolled back in one click for seven days.
• "Did it crash?" check (free). About ten seconds after an update, the site checks its own home page and up to three monitored pages for server errors, the critical error page and PHP fatal errors.
• Safe Update All (free). Update plugins one at a time with a check after each, and automatically roll back any update that breaks the site.

Summary#

Back up, read the changelog and check your add-ons. Update Elementor and Elementor Pro together, free first, ideally on staging. Then clear Elementor's files and every cache, and check your important pages on desktop and mobile. If something breaks, roll back with Elementor's Version Control tool, keep both plugins in step, and pause auto-updates until a fix is out. For anything still misbehaving, see Elementor not working.