You open your site and see one line: “There has been a critical error on this website.” No menu, no pages, sometimes no way into the dashboard. A WordPress critical error looks scary, but it is one of the most fixable problems in WordPress. In most cases the cause is a single plugin, theme or code snippet, and you can find it in under 30 minutes.
This guide walks you through 8 fixes in the order we recommend. Start at the top and stop as soon as your site is back.
What the WordPress critical error actually means
The message is WordPress catching a fatal PHP error. Something in your site’s code tried to do a thing PHP could not finish, so the page stopped loading. Older WordPress versions showed a blank “white screen of death.” Modern versions show the friendly message instead and email the site admin a special recovery link.
The most common causes are:
- A plugin update that conflicts with another plugin, your theme or your PHP version
- A theme update or a broken edit to functions.php
- A code snippet pasted from a tutorial with a small mistake
- An old PHP version (WordPress 7.0 and later need at least PHP 7.4, and 8.3 is recommended)
- Too little PHP memory for a heavy page or plugin
- Corrupted core files after a failed update, or, more rarely, malware
Before you change anything, take a backup if your host offers one in the control panel. If you followed our earlier backup guide, you already have one. Now let’s fix it.
1. Check your inbox for the recovery mode email
When WordPress hits a fatal error, it sends an email to the admin address with the subject “Your Site is Experiencing a Technical Issue.” Check spam and promotions folders too.
The email usually names the plugin or theme that caused the crash and includes a special login link. Click it and you enter recovery mode, a safe version of the dashboard where the broken plugin is paused just for you. Go to Plugins, deactivate the plugin it names, then click “Exit Recovery Mode” in the top bar. Visit your site in a private window to confirm it works.
No email? That is common when a site’s mail is not set up properly. Skip to the next fix.
2. Turn on the WordPress debug log
The debug log tells you exactly which file broke your site, so you stop guessing. Open your site files using your host’s File Manager or an FTP app, then edit wp-config.php in the main folder. Just above the line that says “That’s all, stop editing,” add:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );Reload your site once, then open /wp-content/debug.log. Look for a line starting with “PHP Fatal error.” It will include a file path such as /wp-content/plugins/some-plugin/… or /wp-content/themes/your-theme/functions.php. That folder name is your suspect.
When you are done, set WP_DEBUG back to false. A debug log left on can fill up disk space and expose file paths.
3. Deactivate all plugins without the dashboard
If the log points to a plugin, or you cannot read the log, disable plugins from your file manager:
- Go to /wp-content/.
- Rename the plugins folder to plugins-off.
- Reload your site.
If the site loads, a plugin was the problem. Rename the folder back to plugins. WordPress will show all plugins as inactive. Now reactivate them one at a time, checking the front end after each one. The plugin that brings the error back is your culprit. Leave it off and contact its developer, or look for an update.
Tip: if you already know the suspect from the debug log, just rename that one plugin’s folder instead of all of them.
4. Roll back the last update
Most critical errors appear right after an update. If the crash started after you updated a plugin, a theme or WordPress itself, roll that one item back to the previous version. Many plugin pages on WordPress.org list older versions under Advanced View, and most hosts can restore a single plugin folder from a daily backup.
Rolling back is a short-term fix. Check the plugin’s changelog or support forum, because the developer is often already aware and a patch usually follows within days.
5. Switch to a default theme
If plugins are not the cause, test your theme. In the file manager, rename your active theme’s folder inside /wp-content/themes/. WordPress will fall back to a default theme such as Twenty Twenty-Five if one is installed. If there is no default theme, upload a fresh one from WordPress.org first.
If the site loads with the default theme, the problem is in your theme, often in functions.php. Undo your last edit there, or restore the theme from a backup. For Elementor sites, keep a lightweight, well-maintained theme and use a child theme for any custom code so updates never wipe your changes.
6. Check your PHP version
Old PHP is a quiet cause of fatal errors, especially after plugin updates that drop support for older versions. WordPress 7.0 raised the minimum to PHP 7.4, and WordPress recommends PHP 8.3.
You can check your version in Tools, then Site Health, then Info, then Server. If you cannot reach the dashboard, look in your hosting control panel under PHP settings. Upgrading is usually one click there.
One warning: jumping from a very old PHP version straight to the newest one can also break outdated plugins. Update your plugins and theme first, then raise PHP one step at a time and test after each change.
7. Increase the PHP memory limit
If the debug log mentions “Allowed memory size exhausted,” your site ran out of memory. Add this line to wp-config.php, above the “stop editing” line:
define( 'WP_MEMORY_LIMIT', '256M' );If the error stays, your host may cap memory at the server level. Ask support to raise it. Large Elementor pages with many sections, sliders and forms can need more memory than a basic shared plan provides.
8. Reinstall WordPress core files
If none of the above works, your core files may be damaged from an interrupted update. Download a fresh copy of WordPress from WordPress.org, unzip it, delete the wp-content folder from the download (so you never overwrite your content), and upload the rest to your site, replacing existing files. Your posts, pages, media and settings stay safe because they live in the database and wp-content.
If the error still appears after this, scan for malware or ask your host to check server logs. At that point, a host’s support team can often see errors that you cannot.
Quick reference: which fix to try first
| What you see | Most likely cause | Start with |
|---|---|---|
| Error right after a plugin update | Plugin conflict | Fix 1, then Fix 3 or 4 |
| Error after editing functions.php | Theme code | Fix 2, then Fix 5 |
| “Allowed memory size exhausted” in the log | Low memory | Fix 7 |
| Error after a host or PHP change | PHP version | Fix 6 |
| No clear cause in the log | Damaged core files | Fix 8 |
How to prevent it next time
A WordPress critical error is much less stressful when you have a plan. Keep automatic daily backups. Update plugins one at a time instead of all at once, and test big updates on a staging copy first. Set up proper email delivery so the recovery email actually reaches you. Use fewer, better plugins, because every extra plugin is one more thing that can conflict.
That last point is where your Elementor addons matter. Bright Addons puts 30 free widgets in one plugin, and Pro adds 74 more plus 10 extensions in the same package, so you need fewer separate plugins to keep in sync. You can browse all widgets or check the setup docs to replace several single-purpose plugins with one.
FAQ
What does “There has been a critical error on this website” mean? It means WordPress caught a fatal PHP error, usually from a plugin, theme or code snippet. The rest of your site and content are still there. Only the code that loads the page has stopped.
Will I lose my content if I fix a WordPress critical error? No. The fixes in this guide only pause plugins, switch themes or replace core files. Your posts, pages and media live in the database and the wp-content folder, which these steps do not delete. Still, take a backup before you start.
I did not get the recovery mode email. What now? Check spam first. If it is not there, your site’s email may not be working. Turn on the debug log (Fix 2) and rename the plugins folder (Fix 3). Both work without the dashboard.
Can an Elementor addon cause a critical error? Any plugin can, including Elementor addons, especially when versions fall out of sync. Keep Elementor and your addons updated together, and choose addons that are actively maintained and tested with the latest WordPress and PHP versions.
Conclusion
A WordPress critical error feels like your site is gone, but it almost never is. Use the recovery email if you have it, read the debug log if you do not, and isolate plugins, theme and PHP one at a time. Most sites are back online after the first three fixes. Bookmark this guide so it is ready the next time an update goes wrong, and if you want a lighter, more reliable widget setup for Elementor, see our simple plans from $14 a year.
