Troubleshooting · Troubleshooting
How to Fix the Elementor Critical Error
Short answer
To fix the Elementor critical error, use the Recovery Mode link in the admin email to reach the dashboard, read wp-content/debug.log to find the failing plugin, deactivate that plugin, and raise the PHP memory limit to 512M. If the error started after an update, match Elementor and Elementor Pro versions or roll Elementor back to the previous version.
Key takeaways
- The critical error means a PHP fatal error stopped WordPress from finishing the page.
- Recovery Mode, introduced in WordPress 5.2, pauses the faulty plugin for your session only.
- Elementor needs at least 256 MB of PHP memory, and 512 MB is recommended for complex sites.
- The debug log at wp-content/debug.log names the exact file and line behind the error.
- Elementor and Elementor Pro must be updated together, or a version mismatch can crash the site.
- Roll back Elementor from Elementor > Tools > Version Control when an update causes the error.
What does the Elementor critical error mean?
The Elementor critical error means a PHP fatal error stopped WordPress from finishing a page, so WordPress shows “There has been a critical error on this website” instead of the page.
A fatal error is a PHP error that stops the script at once. WordPress hides the technical detail from visitors, but it records the cause for the site admin.
WordPress.org's Common WordPress Errors page says the message means something in your site caused a critical error that prevents WordPress from running as expected.
The error can hit the front end, the dashboard, or only pages built with Elementor. Where it appears tells you where to start looking.
| What you see | What it usually means |
|---|---|
| Whole site shows the message | A plugin, theme, or core file fails on every page load |
| Only Elementor pages fail | Elementor, Elementor Pro, or an Elementor add-on fails |
| Only the dashboard fails | A plugin that loads in wp-admin fails |
| Message after an update | The new version conflicts with another plugin or with PHP |
What causes the Elementor critical error?
The most common causes are a plugin conflict, low PHP memory, an Elementor and Elementor Pro version mismatch, an old PHP version, or a damaged file.
WordPress.org lists plugin conflicts, theme compatibility issues, an incompatible PHP version, hitting the memory limit, and corrupted WordPress files as the usual causes.
Elementor adds its own triggers. A third-party Elementor add-on can call a function that no longer exists after an update, and two versions of Elementor that do not match can fail together.
- A plugin conflict: another plugin loads code that clashes with Elementor.
- Low memory: the page needs more PHP memory than the server allows.
- Version mismatch: Elementor and Elementor Pro were updated at different times.
- Old PHP: the server runs a PHP version Elementor no longer supports.
- A damaged file: an update stopped halfway and left a broken file.
Check what changed just before the error appeared. An update, a new plugin, or a host change points at the cause.
How do you get back into WordPress with Recovery Mode?
Open the recovery email WordPress sent to the site admin address, click its link, log in, and WordPress pauses the faulty plugin or theme for your session only.
Recovery Mode is a built-in WordPress feature introduced in WordPress 5.2. It lets you reach the dashboard when a fatal error would otherwise lock you out.
WordPress.org's Recovery Mode page says the faulty plugin or theme is paused just for your admin session, so you can log in safely.
- Open the inbox for the site admin email address.
- Find the message about the technical issue and open it.
- Click the recovery link in the message.
- Log in to WordPress when asked.
- Look for the notice at the top of the dashboard that says Recovery Mode is active.
Once inside, go to “Plugins > Installed Plugins” and look for the paused plugin. Deactivate it, then exit Recovery Mode from the admin bar and reload the site.
If no email arrived, check the spam folder. The mail may also fail if the site cannot send email, so move on to the debug log step below.
How do you find the real error in the debug log?
Turn on WP_DEBUG and WP_DEBUG_LOG in wp-config.php, reload the broken page once, then read wp-content/debug.log to find the line that starts with “PHP Fatal error”.
The generic message hides the cause on purpose. The debug log shows the exact file, line, and message behind it.
WordPress's Debugging in WordPress guide says the log is saved to debug.log in the content directory, usually wp-content/debug.log.
- Back up the site, then open wp-config.php in the site root with FTP or your host file manager.
- Add these 3 lines above the line that reads
/* That's all, stop editing! Happy blogging. */:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
- Save the file and reload the broken page once.
- Open wp-content/debug.log and read the newest lines at the end.
The last “PHP Fatal error” line names the file that failed. A path with wp-content/plugins/elementor points at Elementor, while a path with another plugin folder names that plugin.
Turn WP_DEBUG back to false when you finish. Leaving it on writes errors to a file on a live site.
How do you fix a plugin conflict that causes the critical error?
Deactivate every plugin except Elementor and Elementor Pro, check the site, then reactivate plugins one by one until the error returns.
This test finds the exact plugin that clashes with Elementor. Elementor's own help page gives the same method for isolating a conflict.
If you can reach the dashboard, use “Plugins > Installed Plugins”. Select every active plugin except Elementor and Elementor Pro, choose “Deactivate” from the Bulk Actions menu, and click “Apply”.
If the dashboard is locked, use FTP or your host file manager instead. WordPress.org says to rename the wp-content/plugins folder to plugins_old, which deactivates all plugins at once.
- Rename the folder of the plugin named in the debug log first.
- Reload the site to see if the error is gone.
- If it is gone, rename the other plugin folders back one at a time.
- Reload the site after each rename until the error returns.
- Leave the plugin that brings the error back deactivated.
Elementor's preview error guide says that if the editor loads in Safe Mode, an active plugin or theme is causing the conflict.
Safe Mode is at “Elementor > Tools > General” in the dashboard. Set “Safe Mode” to “Enable” and click “Save Changes”, then open the page in Elementor again.
If plugins are not the cause, switch to a default theme such as Hello Elementor or Twenty Twenty-Five at “Appearance > Themes”. A theme that fails with Elementor needs an update or a replacement.
How do you raise the PHP memory limit for Elementor?
Add define( 'WP_MEMORY_LIMIT', '512M' ); to wp-config.php above the stop-editing line, save the file, and reload the site.
Elementor needs a minimum of 256 MB of PHP memory, and 512 MB is recommended for complex sites, according to Elementor's help pages.
PHP's own manual says the memory_limit setting caps how much memory a script may allocate, and it lists the default as 128M. That default is too low for a page builder with many plugins.
| Setting | Value | Source |
|---|---|---|
| Elementor minimum memory | 256 MB | Elementor requirements |
| Elementor recommended memory | 512 MB | Elementor requirements |
| Elementor best performance memory | 768 MB | Elementor requirements |
| PHP manual default memory_limit | 128M | PHP manual |
- Open wp-config.php in the site root with FTP or your host file manager.
- Add
define( 'WP_MEMORY_LIMIT', '512M' );just above the line that reads/* That's all, stop editing! Happy publishing. */. - Save the file and reload the broken page.
If the error still says “Allowed memory size exhausted”, the server cap in php.ini may be lower than 512M. WordPress cannot use more memory than the server allows, so ask your host to raise the server limit.
Our guide to the memory exhausted error covers the same fix in more detail.
How do you fix an Elementor and Elementor Pro version mismatch?
Update Elementor and Elementor Pro to their latest matching versions, then clear caches and reload the site.
Elementor and Elementor Pro are two plugins that must work as a pair. When one updates and the other stays old, a function one expects may be missing from the other.
Elementor's requirements page, checked in November 2026, says Elementor works with WordPress 6.8 or greater and PHP 7.4 or greater. An old PHP version can make a new Elementor release fail the same way.
- Go to “Dashboard > Updates” and update WordPress core first if an update is waiting.
- Go to “Plugins > Installed Plugins” and update Elementor.
- Update Elementor Pro in the same visit.
- Update Elementor add-ons, such as widgets packs, to versions made for the new Elementor release.
- Go to “Elementor > Tools” and click “Regenerate Files & Data” to rebuild Elementor's files.
Check the version numbers on the Plugins screen after the update. Both plugins should show a recent release date, not one from months ago.
If your host runs an old PHP version, update it before you update Elementor again. Our guide on how to update the PHP version walks through that change.
How do you roll back Elementor after a bad update?
Use Elementor's Version Control tool to reinstall the previous version, then check the site before you update again.
Roll back only when the error started right after an Elementor update. A rollback is a short-term fix, not a cure for a plugin conflict or low memory.
Elementor's rollback guide says to back up the site before rolling back to a previous version.
- Go to “Elementor > Tools” in the dashboard.
- Click the “Version Control” tab.
- Leave “Rollback Version” on the previous version, or pick an earlier version from the dropdown.
- Click “Reinstall” to install that version.
- Reload the front end and the Elementor editor to check the error is gone.
If the dashboard is locked, you cannot use Version Control. Rename the elementor folder in wp-content/plugins over FTP to deactivate it, regain access, then reinstall the older version from the Plugins screen.
Report the broken update to Elementor support after you roll back. Staying on an old version leaves you without security fixes and new features.
How do you check the error is fixed?
Reload the front end in a private browser window, open the dashboard, and open one Elementor page in the editor.
A fix is only real when all 3 checks pass. A page that loads for you may still fail for a logged-out visitor if a cache hides the error.
- Load the home page and 2 Elementor pages as a logged-out visitor.
- Log in to the dashboard and confirm no critical error notice appears.
- Open a page with “Edit with Elementor” and confirm the editor loads.
- Check wp-content/debug.log for new “PHP Fatal error” lines.
Clear every cache layer before you judge the result. Clear the browser cache, the caching plugin, and the server cache, then reload.
Cloudflare can also hide or cause script errors. Cloudflare's Rocket Loader docs say to disable Rocket Loader and retest if you see JavaScript or jQuery issues.
If the error returns only on one page, the problem sits in that page. Rebuild its Elementor content or restore that page from a backup made before the error started.
When should you contact your host?
Contact your host when the error stays after you have deactivated plugins, raised the memory limit, and matched Elementor versions, or when you cannot edit server files.
Some fixes need server access you may not have. Your host can raise the PHP memory limit, change the PHP version, and read the server error log.
Ask your host these 4 questions, and send them the newest lines from wp-content/debug.log:
- What is the PHP version and the server memory_limit on this site?
- Can you raise the memory limit to 512M?
- Does the server error log show a fatal error for this site?
- Is a server firewall rule blocking Elementor requests?
WordPress.org says to contact your host when the database has met its quota or the server is down. The same advice fits here when the site fails even with all plugins off.
If your host finds a server fault, ask for the fix in writing and the time it was applied. That record helps if the error returns.
What mistakes should you avoid?
Do not edit files without a backup, do not leave debug mode on, and do not delete Elementor to fix a crash.
Deleting Elementor removes the builder, but it leaves its content in the database. That step can break pages further, so use the safer steps in this guide first.
- Editing wp-config.php without a backup can lock you out if you mistype a line.
- Leaving WP_DEBUG on writes errors to a public file on a live site.
- Updating only Elementor Pro while Elementor stays old keeps the mismatch.
- Raising the memory limit to a huge value hides a plugin that uses too much memory.
- Ignoring the debug log and guessing at fixes wastes time and can break more pages.
If you are unsure about a step, stop and ask your host or a developer. A backup made before you start lets you undo any change in minutes.
Our guide to removing Elementor safely explains the right way to take Elementor off a site if you decide to stop using it.
Frequently asked questions
Why does my Elementor site show a critical error only on some pages?
Only the pages that load the failing code show the error. A page that uses a broken Elementor widget or add-on fails, while pages without that widget load fine. Read the debug log to find which file fails, then deactivate the add-on or rebuild that page.
Can I fix the Elementor critical error without FTP access?
Yes, if the Recovery Mode email arrives. Click its link to log in with the faulty plugin paused, then deactivate the plugin from the dashboard. If no email arrives and the dashboard is locked, you need FTP or your host file manager to rename the plugin folder.
Will raising the PHP memory limit always fix the critical error?
No. Raising the limit to 512M only fixes errors caused by exhausted memory. If a plugin conflict or a version mismatch is the cause, the error returns until you deactivate the conflicting plugin or match the Elementor versions. Check the debug log first so you fix the real cause.
Is it safe to roll back Elementor to an older version?
Rolling back is safe as a short-term fix if you back up the site first. It restores the version that worked before the bad update. Do not stay on the old version for long, because you miss security fixes. Report the problem and update again once a fixed release is out.
How long does it take to fix the Elementor critical error?
Most fixes take 15 to 30 minutes once you know the cause. Reading the debug log takes a few minutes, deactivating plugins takes a few more, and raising the memory limit is one line in wp-config.php. If the cause is unclear or the host must change server settings, it can take longer.
Sources
- Common WordPress Errors WordPress.org
- Debugging in WordPress WordPress Developer Resources
- Recovery Mode WordPress.org
- How to Fix the 'Preview Could Not Be Loaded' Error Elementor
- System Requirements to Use Elementor Elementor
- Rollback to a previous version of Elementor Elementor
- Runtime Configuration: memory_limit PHP
- Rocket Loader Cloudflare
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
