Troubleshooting · Explainer
What Causes "There Has Been a Critical Error on This Website" in WordPress?
Short answer
The message means a PHP fatal error stopped WordPress from running the page, and WordPress caught it instead of showing a blank screen. The usual causes are a plugin conflict, a theme that does not work with the current PHP or WordPress version, a memory limit hit, or damaged core files.
Key takeaways
- WordPress 5.2, released in May 2019, added fatal error protection, so a fatal error shows this message instead of a blank page.
- The five common causes are a plugin conflict, a theme problem, an incompatible PHP version, a memory limit hit, or damaged core files.
- Recovery mode pauses the failing plugin or theme for your browser only, so you can log in and turn it off.
- The recovery email names the plugin or theme that failed, with the file, line, and error message.
- The debug log in wp-content/debug.log records the exact PHP fatal error behind the message.
What does “There Has Been a Critical Error on This Website” mean?
The message means a PHP fatal error stopped WordPress, and WordPress caught the failure instead of showing a blank page.
When PHP hits a fatal error, it stops running the page at once. Before WordPress 5.2, released in May 2019, that usually left a blank white page, known as the white screen of death. Since 5.2, WordPress catches the error, shows this short message, and emails the site admin a link to recovery mode.
WordPress.org's Common WordPress Errors page quotes the full message, including the line “Please check your site admin email inbox for instructions,” and says it means something in the site caused a critical error that stops WordPress from running as expected.
The message gives no hint about which plugin, theme, or file failed. That detail lives in the recovery email or in the debug log, which is why the first step is always to read one of those two places.
The guide to fix “There Has Been a Critical Error on This Website” walks through the fix steps in order.
What are the most common causes?
The most common causes are a plugin conflict, a theme problem, an incompatible PHP version, a memory limit hit, or damaged files.
WordPress.org's Common WordPress Errors page lists exactly these five: conflicts between plugins, compatibility issues with a theme, an incompatible PHP version, hitting the memory limit, or corrupted WordPress files. A single update can trigger any of them, which is why the error so often appears right after an update.
| Cause | Usual trigger | First clue |
|---|---|---|
| Plugin conflict | A plugin update or a new plugin | Error names a plugin file in the log |
| Theme problem | A theme update or a new theme | Error appears after switching themes |
| Incompatible PHP version | A host PHP upgrade | Error names a function the PHP version lacks |
| Memory limit hit | A heavy plugin or a large import | “Allowed memory size exhausted” in the log |
| Damaged core files | A failed update | Error names a wp-admin or wp-includes file |
The cause is rarely visible from the message alone. Two sites can show the same words for two different reasons, so the log or the recovery email decides which cause you have.
How can a plugin cause a critical error?
A plugin can cause a critical error when its code calls a function that does not exist, or clashes with another plugin.
A plugin written for an older WordPress version may call a function that was removed, while a plugin written for a newer version may call a function the installed WordPress version does not have yet. Either way PHP stops with a fatal error, and WordPress shows the critical error message.
Two plugins can also clash when both define the same function or both change the same behavior in ways that conflict. The error then appears only when both are active, which is why turning plugins off one at a time finds the pair.
Make WordPress Core's Fatal Error Recovery Mode in 5.2 note says that when a fatal error occurs, an email goes to the admin address with a secret link to recovery mode.
Recovery mode pauses the failing plugin or theme for that browser only, so the admin can log in and turn it off. The guide to fix plugin conflicts explains how to find the plugin once you are back in the dashboard.
How can a theme cause a critical error?
A theme can cause a critical error when its code fails on the PHP or WordPress version the site runs.
A theme update that uses a newer PHP feature breaks on a host still running an older PHP version. A theme that calls a WordPress function removed in a recent release breaks the same way after a core update. The error then appears on every page, because the theme loads on every page.
The clue is timing: the error starts right after a theme update, a theme switch, or a WordPress core update. Switching to a default theme, such as Twenty Twenty-Five, is the fastest check, since a default theme is built to work with the current WordPress version.
WordPress.org's Common WordPress Errors page lists theme compatibility as one of the common causes, and suggests switching to a default theme to rule it out. If the site loads on the default theme, the old theme holds the fault.
The guide to fix a theme update that broke the site covers the steps for that case.
How can the PHP version cause a critical error?
The PHP version can cause a critical error when a plugin or theme needs a newer PHP than the host runs.
WordPress.org's Requirements page recommends PHP 8.3 or greater as of November 2026, and says WordPress also works with PHP 7.4 and above, though those versions have reached their official end of life. A plugin that needs PHP 8.0 features fails with a fatal error on PHP 7.4.
A host PHP upgrade can cause the same problem in reverse: old plugin code that worked on PHP 7.4 may use a feature removed in PHP 8.0 or later, and then fails after the host moves the site to the newer version. The error starts the day the PHP version changes, which is the clue.
Check the PHP version in Tools, then Site Health, then Info, in the dashboard, or ask the host which version the site runs.
The WordPress PHP compatibility guide lists which PHP versions work with current WordPress.
How can the memory limit cause a critical error?
The memory limit can cause a critical error when a page needs more memory than PHP is allowed to use.
PHP's manual lists core php.ini directives, including memory_limit with a 128M default as of November 2026. A site with many plugins, a large import, or a heavy page builder can pass that limit on one request, and PHP stops the script with an “Allowed memory size exhausted” fatal error.
WordPress.org's Common WordPress Errors page lists hitting the memory limit as a common cause of the critical error message. The log line names the limit and the amount the script tried to use, so it is easy to tell apart from a plugin conflict.
Raising the limit helps only when the job is sound and simply needs more memory. The guide to fix “Allowed Memory Size Exhausted” explains how to tell the two apart.
A plugin with a memory leak will keep growing until it hits any limit you set, so a limit that keeps needing to rise points at code, not at the setting.
How does recovery mode help you find the cause?
Recovery mode helps by pausing the failing plugin or theme so you can log in and see which one it was.
Make WordPress Core's Fatal Error Recovery Mode in 5.2 note says the email goes to the admin and super admin address, and the link places a cookie on the current browser. When in recovery mode, plugins and themes causing a fatal error are paused for that client, so the admin can reach the dashboard.
The same note says the pause applies only to the browser in recovery mode, and the site stays broken for everyone else until the cause is fixed.
After logging in, an admin notice names the paused extensions and the exact error, so you can turn the plugin off or switch the theme, then exit recovery mode from the admin bar.
The email subject reads “[Your site name] Your Site is Experiencing a Technical Issue”, and the body names the plugin or theme WordPress caught, with the file, line, and error message.
If no email arrives, check the spam folder and confirm the admin email address under Settings, then General, since WordPress can only send the link to the address it has on file.
How do you read the debug log to find the cause?
You read the debug log by turning on WP_DEBUG and WP_DEBUG_LOG, loading the broken page once, and opening wp-content/debug.log.
Developer.WordPress.org's Debugging in WordPress page shows the lines to add above the “That's all, stop editing!” comment in wp-config.php: WP_DEBUG set to true, WP_DEBUG_LOG set to true, and WP_DEBUG_DISPLAY set to false. The log is saved to debug.log in the content directory, usually wp-content/debug.log.
The same page says WP_DEBUG is false by default, and that WP_DEBUG_LOG does nothing unless WP_DEBUG is enabled. It also warns that debug tools are meant for local testing and staging installs, not live sites, so turn them off when you are done.
Look for a line starting with “PHP Fatal error” and read the file path and line number it names. The guide to fix the WordPress white screen of death covers the same log steps for blank pages.
A path inside wp-content/plugins names the plugin, a path inside wp-content/themes names the theme, and a path inside wp-includes or wp-admin points at damaged core files.
What mistakes should you avoid?
Do not turn off all plugins and leave them off without noting which one was active.
Bulk deactivation finds the fault, but if you do not record the list first, you may lose track of which plugins the site needs. Write the list down, or take a screenshot of the plugins screen before you start.
Do not leave WP_DEBUG on after you find the cause. The debug log keeps growing on a live site, and error details can sit in a file that visitors might reach. Set WP_DEBUG back to false and delete the log when the fix is confirmed.
Do not ignore the recovery email. It names the failing plugin or theme and gives the exact error, which saves the guesswork of turning plugins off one at a time. Check the admin email inbox, including spam, before you start changing files.
Frequently asked questions
Does a critical error mean my WordPress site is broken for good?
No, it means one PHP fatal error stopped the page, and WordPress caught it. The site files and database are usually still there. A plugin conflict, a theme problem, or a memory limit hit are the most common causes, and recovery mode exists so you can log in and turn off the failing plugin or theme without editing files first.
How long does it take to fix a critical error?
It depends on the cause. A plugin conflict can take minutes to fix once recovery mode names the plugin. A damaged core file takes longer, because it needs a fresh copy of WordPress uploaded and a check that the site loads cleanly. A PHP version problem can take longest, since it may need the host to change the PHP version or the plugin author to release an update.
Does recovery mode fix the site for visitors too?
Recovery mode pauses the failing plugin or theme for your browser only, so you can log in and turn it off. Visitors still see the critical error message until the plugin is turned off or fixed and you exit recovery mode. The pause is a way in, not a fix by itself.
Why did I not get a recovery mode email?
Check the admin email address under Settings, then General, and look in the spam folder. WordPress sends the email only to that address, and only when the error happens on the login page, in the dashboard, or during certain admin requests. If only the front end fails, open wp-login.php or wp-admin yourself to trigger the email.
Can an automatic update cause a critical error overnight?
Yes, if a plugin or theme update includes code that fails on your PHP or WordPress version. The error often appears within minutes of the update, which is the clue. Recovery mode names the extension that failed, and rolling back or turning off that one plugin or theme is usually enough to bring the site back.
Sources
- Common WordPress Errors WordPress.org
- Fatal Error Recovery Mode in 5.2 Make WordPress Core
- Debugging in WordPress WordPress Developer Resources
- Requirements WordPress.org
- Description of core php.ini directives PHP Manual
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.
