Troubleshooting · Troubleshooting
How to Fix "There Has Been a Critical Error on This Website" in WordPress
Short answer
This message means PHP hit a fatal error while building the page, so WordPress stopped and showed this screen instead. Check the admin email for the recovery link, which pauses the faulty plugin or theme for your browser only. If no email arrived, turn on WP_DEBUG and WP_DEBUG_LOG, reload once, and read wp-content/debug.log to find the file at fault.
Key takeaways
- The critical error screen means a PHP fatal error stopped WordPress from building the page.
- WordPress 5.2 added recovery mode, which emails the admin a secret link to reach the dashboard.
- Recovery mode pauses the faulty plugin or theme for your browser only, not for visitors.
- The last PHP Fatal error line in wp-content/debug.log names the file and folder at fault.
- WordPress.org lists five usual causes: plugin conflicts, theme issues, PHP version, memory, and corrupt files.
- Renaming the plugins folder to plugins.hold deactivates every plugin without deleting files.
What does “There has been a critical error on this website” mean?
The message means PHP hit a fatal error while building the page, so WordPress stopped and showed this screen instead.
WordPress.org states that the message shows something in the site caused a critical error that stops WordPress from running as expected, as explained in Common WordPress Errors.
Visitors see the same screen, while the admin gets an email with a recovery link, so check the inbox first.
The message hides the real error on purpose, since showing PHP errors to visitors would leak server details.
What causes a critical error most often?
Five causes explain most critical errors: plugin conflicts, theme compatibility issues, an incompatible PHP version, a hit memory limit, and corrupted WordPress files.
| Cause | Sign | First step |
|---|---|---|
| Plugin conflict | Error starts after a plugin update | Use recovery mode to pause it |
| Theme problem | Error starts after a theme change | Switch to a default theme |
| Old PHP version | Fatal error names a PHP feature | Update PHP |
| Memory limit hit | Allowed memory size exhausted message | Raise the memory limit |
| Corrupt core files | Error after a failed update | Re-upload wp-admin and wp-includes |
WordPress.org lists the same five causes in its common errors guide, and the order above starts with the fastest to check, as shown in Common WordPress Errors.
Corrupt files usually follow a failed auto-update, so check Dashboard, then Updates for a failed core, plugin, or theme update.
PHP 8.3 or greater is the WordPress.org recommendation, while PHP 7.4 still runs but has reached end of life, as the requirements page states.
A plugin update is the most common trigger, since a new version can call a function that no longer exists.
An undefined function error often follows a bad plugin update, as our guide to the fatal error call to undefined function explains.
How do you use the recovery mode email?
Open the email WordPress sent to the site admin address and click the recovery link inside it.
- Open the inbox of the address in Settings, then General, then Administration Email Address.
- Check the spam folder if the message is not in the inbox.
- Click the recovery link, then log in to the dashboard.
- Deactivate the paused plugin or theme named in the admin notice.
Make WordPress Core explains that recovery mode places a cookie on your browser, and the faulty extension stays paused for that browser only, as described in the recovery mode announcement.
Save the recovery email until the site is fixed, since the link is the fastest way back into the dashboard.
Click Exit Recovery Mode in the admin bar when you finish, since leaving it on keeps the extension paused for you.
What if no recovery email arrived?
If no email arrived, check the spam folder, then read the debug log, since mail delivery often fails on the same server.
WordPress sends the email to the admin address, so a wrong address in Settings means the message goes nowhere.
- Confirm the admin email in Settings, then General.
- Ask the host whether the server sends mail at all.
- Use the debug log steps in the next section while you wait.
Check the admin email address in Settings, then General, since a typo there sends the recovery email nowhere.
Move on to the debug log, since it names the faulty file without any email.
How do you read the debug log to find the cause?
Turn on WP_DEBUG and WP_DEBUG_LOG in wp-config.php, reload the broken page once, then read wp-content/debug.log.
WordPress.org documents adding define( 'WP_DEBUG', true ); and define( 'WP_DEBUG_LOG', true ); to wp-config.php, which writes errors to debug.log in the content folder, as shown in Debugging in WordPress.
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Add these lines before the comment that says “That is all, stop editing!”, since lines after it never run.
Open wp-content/debug.log and find the last line that starts with PHP Fatal error, since the file path in that line names the plugin or theme folder.
The log lists errors newest last, so read from the bottom up to find the latest fatal error.
Set WP_DEBUG_DISPLAY to false so visitors never see the error text on the page.
How do you fix the faulty plugin or theme?
Once the log names the file, deactivate that plugin or switch themes, then update or replace the faulty item.
WP-CLI can deactivate one plugin or all of them with wp plugin deactivate, as the WP-CLI docs show.
- In recovery mode, deactivate the paused plugin from the dashboard.
- If you have WP-CLI, run wp plugin deactivate with the plugin folder name.
- Update the plugin or theme to the latest version and test again.
- If no update fixes it, replace it with a maintained alternative.
WordPress 7.1.5, released 18 November 2026, is the latest version, so update core too if you run an older release, according to the WordPress versions page.
PHP defaults to a 128M memory limit, so a large plugin can hit the ceiling during a heavy page, as the PHP manual shows.
If the fault is an old PHP version, our guide to updating the PHP version in WordPress walks through the change.
If the log shows a memory error, see our guide to the allowed memory size exhausted error.
Test the fix in a private window, since your logged-in session may still hold the recovery cookie.
How do you fix it when the dashboard is locked?
If you cannot reach the dashboard at all, deactivate plugins by renaming the folder over SFTP.
WordPress.org explains that renaming wp-content/plugins to plugins.hold disables all plugins, and renaming it back keeps them off until you reactivate them, as the FAQ Troubleshooting page describes.
- Connect by SFTP and open wp-content.
- Rename plugins to plugins.hold and reload the site.
- If the site loads, rename the folder back to plugins.
- Reactivate plugins one at a time in the dashboard until the error returns.
Rename the active theme folder the same way if the log points to the theme, since WordPress then falls back to a default theme.
Keep a note of which plugin you reactivated last, since the error returns with the faulty one.
Re-upload wp-admin and wp-includes from a fresh WordPress download if the log points to core files, as WordPress.org advises in Common WordPress Errors.
If the error screen shows a 500 status instead, see our guide to the 500 Internal Server Error.
How do you confirm the site is fixed?
The site is fixed when the home page and dashboard load without the critical error screen.
- Load the home page and two inner pages in a private window.
- Log in to the dashboard and open the plugin list.
- Turn off WP_DEBUG and WP_DEBUG_LOG when you finish.
- Check the site again after the next plugin update.
Back up the fixed site right away, since a working backup saves hours if the error returns. Our guide to restoring a backup with UpdraftPlus covers the restore steps.
Ask a friend on another network to load the site too, since your own browser cache can hide a broken page.
What mistakes should you avoid?
Avoid five mistakes that turn a critical error into a longer outage.
- Do not edit live files without a backup, since one typo can break the site further.
- Do not leave WP_DEBUG on after you finish, since the log file can expose error details.
- Do not delete the whole plugins folder, since renaming it is enough to test.
- Do not reinstall WordPress core over a plugin fault, since it will not fix the plugin.
- Do not ignore the debug log, since guessing at the cause wastes the most time.
Fix one cause at a time and test the site after each change, so you know exactly what solved it.
Frequently asked questions
Is a critical error the same as the white screen of death?
They share a cause, a PHP fatal error, but the critical error screen is the newer message WordPress shows since version 5.2. The white screen appears when nothing catches the crash, such as a fatal error in core files. Both point to the debug log for the cause.
Will the critical error delete my content?
No. Posts, pages, and media stay in the database, and the error only stops pages from building. Fix the faulty plugin or theme, and the same content loads again without any restore.
How long does recovery mode last?
Recovery mode lasts until you click Exit Recovery Mode in the admin bar or clear the browser cookie. The faulty extension stays paused for your browser only, while visitors keep seeing the error until you deactivate it.
Can a plugin update cause a critical error on every page?
Yes, if the plugin runs on every page load, such as a security or caching plugin. Rename the plugins folder to disable them all, then reactivate one at a time to find the one that crashes the site.
What if debug.log is empty?
The log stays empty when WP_DEBUG is off, when the constants sit after the stop-editing line, or when the host writes errors elsewhere. Check the constant placement first, then ask the host for the PHP error log.
When should I call my host?
Call your host when the error appears on a fresh install, when the log points to a server limit, or when mail and SFTP both fail. Send them the last fatal error lines from debug.log so they can act fast.
Sources
- Common WordPress Errors WordPress.org
- Debugging in WordPress WordPress Developer Resources
- FAQ Troubleshooting WordPress.org
- Fatal Error Recovery Mode in 5.2 Make WordPress Core
- WordPress Versions WordPress.org
- wp plugin deactivate Developer.WordPress.org
- Description of core php.ini directives PHP Manual
- WordPress Requirements WordPress.org
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.
