Elementor "There Has Been a Critical Error": Real Fix (2026)
Quick answer
The Elementor "There has been a critical error on this website" message usually means a PHP fatal error inside Elementor or an add-on plugin. Fix in order: (1) raise WP_MEMORY_LIMIT to 512M in wp-config.php, (2) check /wp-content/debug.log for the exact file that crashed, (3) roll back Elementor with WP Rollback if the error started after an update, (4) deactivate Elementor add-ons (Essential Addons, Crocoblock, etc.) one at a time.
What Elementor's critical error really means
The generic message hides a PHP fatal that happened inside Elementor, an add-on plugin, or a theme integration. WordPress catches the fatal, saves the site from a total white screen, and emails the site admin a debug link — but the fix requires reading the underlying error.
Check your admin email (or wp-admin → Site Health → Info → Fatal Errors) for the crash details WordPress logged. That's step zero.
Fix #1 — Raise memory to 512M
Elementor is memory-hungry, especially with Elementor Pro and multiple add-ons. Edit wp-config.php:
define('WP_MEMORY_LIMIT', '512M'); define('WP_MAX_MEMORY_LIMIT', '768M');
Reload the editor. Memory exhaustion is behind about 30% of Elementor critical errors, especially on shared hosting.
Fix #2 — Roll back Elementor after a bad update
If the critical error started immediately after an Elementor update, install WP Rollback. Plugins → find Elementor → Rollback → pick the previous stable version.
Elementor publishes a rollback tool inside the plugin itself: Elementor → Tools → Version Control → Rollback to Previous Version. Use this if you have wp-admin access.
Prefer we just fix it?
This exact error is what our flat-fee website repair service resolves — most fixes ship in under 60 minutes, no retainer, no lock-in. Learn more about flat-fee website repair or grab a slot below.
Fix #3 — Isolate the add-on plugin
Elementor add-ons (Essential Addons, Ultimate Addons, Crocoblock JetElements, ElementsKit) can register broken widgets or hooks. Deactivate them one at a time via wp-admin — or via SFTP by renaming each plugin's folder to <name>-off.
Load the page that showed the critical error after each deactivation. The one that fixes it is your culprit.
Fix #4 — Theme integration or PHP version mismatch
Some themes hook deeply into Elementor and break when either updates. Switch to Hello Elementor (the official lightweight theme). If the site loads, your theme's Elementor integration is the issue.
Also check your PHP version — Elementor 3.19+ requires PHP 7.4 minimum, and drops support for older versions each year. Update PHP via your host panel to at least 8.1 for best compatibility.
When to call for help
If memory is at 512M, Elementor is rolled back, add-ons are off, and the site is still throwing critical errors — the issue is usually a corrupted Elementor cache or a database entry with malformed serialized data. Elementor → Tools → Regenerate CSS & Data fixes many of these.
For Elementor emergencies on WooCommerce stores or client sites, our rescue starts at $149 with typical resolution in under 30 minutes.
Common questions
Why does Elementor say "there has been a critical error on this website"?+
A PHP fatal error inside Elementor, an add-on plugin, or the theme's Elementor integration. Enable WP_DEBUG_LOG in wp-config.php and check /wp-content/debug.log — the fatal line names the exact file. The top three causes are PHP memory exhaustion, an incompatible add-on, and a version mismatch between Elementor and Elementor Pro.
How do I fix Elementor critical error after update?+
Roll back Elementor to the previous version. Use Elementor → Tools → Version Control → Rollback (if you have wp-admin access), or install WP Rollback and roll back the plugin from Plugins page. Wait for the next Elementor release with the fix, then update.
How much memory does Elementor need?+
512M is the safe minimum for Elementor Pro with a few add-ons. 256M is the absolute minimum for basic Elementor sites. WooCommerce + Elementor together often need 768M on the admin side. Set WP_MEMORY_LIMIT and WP_MAX_MEMORY_LIMIT in wp-config.php.
Does the Elementor critical error affect only the editor or the whole site?+
It depends on where the fatal fires. A broken widget in the editor only breaks the editor. A broken hook in Elementor's init breaks the whole site. Read the debug log to know which — and whether the fix needs to be urgent (public-facing outage) or routine (editor only).
Want help with this?
The pages below go deeper, by service and by city.
Services
Want this handled for you?
Book a call and we will review your site before recommending anything.