A WordPress critical error means a plugin, theme, custom code snippet, or server setting caused a PHP fatal error and stopped the page from loading. To fix it, open the recovery mode email or the debug log to find the faulty file, then deactivate that plugin, switch themes, or adjust PHP settings.

Many business owners describe the same afternoon (this is a composite of common cases). The owner of a small landscaping company asks a freelancer to add a quote form, and an hour later the homepage shows one plain line: there has been a critical error on this website. The owner has spring bookings coming in through that site, and he worries every lead will go to a competitor. On his first call with a web team, he admits he does not understand the error. The developer asks him to forward one email from his inbox, reads the error details inside it, and finds a single broken line of code. He realizes the fix starts with information he already had.

What Does “There Has Been a Critical Error on This Website” Mean?

“There has been a critical error on this website” means WordPress hit a PHP fatal error and stopped loading the page to protect the site. WordPress 5.2 introduced the message, which replaces the old blank white screen for most fatal errors.

Short Answer: The WordPress critical error is a safety screen, not a sign of lost data. PHP stopped running because one piece of code failed, and your posts, pages, and orders stay in the database. Find the file named in the error details, disable it, and the site loads again.

What Visitors and Admins See

Visitors see only the short critical error line. Logged-in administrators usually see an extra sentence asking them to check the site admin email inbox for instructions, because WordPress sends the error details to the administration email address.

Common Causes

Here are the causes that trigger the message most often:

A plugin that conflicts with another plugin, your theme, or your PHP version
A broken theme update, functions.php edit, or custom code snippet
A host that upgraded the PHP version, leaving an older plugin incompatible
A script that ran out of PHP memory
Corrupted WordPress core files from a failed update

How Do You Use the Recovery Mode Email?

The recovery mode email gives you two tools: a description of the error and a special login link that pauses the faulty plugin or theme for your session. WordPress sends the email to the administration email address under Settings, then General.

Look for a subject line similar to “Your Site is Experiencing a Technical Issue.” Here is how to use the email:

Scroll to the Error Details section. It usually names the error type, the file path, and the line number.
Note the folder name in that file path, such as wp-content/plugins/plugin-name. That folder names the cause.
Click the recovery mode link, log in, and deactivate or update the paused plugin or theme.
Click Exit Recovery Mode in the admin toolbar and check the site.

If the email never arrives, check spam and confirm the admin address still works. If the link shows an error, our guide to fixing “Recovery Mode not initialized” explains why and what to do instead.

How Do You Find the Error With WordPress Debug Mode?

WordPress debug mode writes every PHP error to a log file, so you can read the exact cause even without the recovery email. You turn it on in wp-config.php, the main settings file in your site’s root folder.

Short Answer: In wp-config.php, set WP_DEBUG to true, WP_DEBUG_LOG to true, and WP_DEBUG_DISPLAY to false. Reload the broken page, then open wp-content/debug.log and read the last “PHP Fatal error” line. That line names the file and folder that crashed.

The WordPress debugging guide explains each setting. Turn the settings off once you finish.

Many cPanel hosts also keep a server log named error_log inside public_html, with the newest entry at the bottom. Read either log like this:

“Allowed memory size of 134217728 bytes exhausted” means the site ran out of its 128 MB memory limit.
“Call to undefined function” usually points to a plugin that needs a newer or older PHP version.
“Syntax error, unexpected” points to a typo in custom code or functions.php.

How Do You Fix a WordPress Critical Error Without wp-admin?

You fix a WordPress critical error without wp-admin by working in your hosting file manager or an FTP client. Renaming a plugin or theme folder makes WordPress deactivate it, and editing wp-config.php changes memory settings.

Work through these fixes in order:

Deactivate Plugins via FTP

Open wp-content/plugins and rename the folder that the log or email named, for example from booking-form to booking-form-off. If nothing names a plugin, rename the whole plugins folder to plugins-off to deactivate plugins all at once. Rename it back, then reactivate plugins one at a time from the Plugins screen until the error returns.

Switch to a Default Theme

Open wp-content/themes and rename your active theme’s folder. WordPress falls back to an installed default theme such as Twenty Twenty-Five. If the log points to functions.php, open that file and remove the last snippet you added instead of switching themes.

Raise the PHP Memory Limit

Add define( ‘WP_MEMORY_LIMIT’, ‘256M’ ); to wp-config.php when the log shows a memory error. Your hosting plan sets the real maximum, so ask support to raise the server limit if the error returns.

What If the Critical Error Started Without Any Update?

A critical error that appears with no update usually comes from a change on the server, such as a host switching PHP versions, corrupted core files, or wrong file permissions. Less often, malware changes site files and breaks them.

Here is what to check:

PHP version: Ask your host whether they changed it, or check the PHP selector in your hosting panel. Switch back to the previous version temporarily, then update the plugin that failed.
Core files: Open Dashboard, then Updates, and click Re-install. Without dashboard access, upload fresh wp-admin and wp-includes folders from the same WordPress version.
File permissions: Folders usually need 755 and files 644.
Malware: Unknown files, strange redirects, or admin users you did not create point to a hack. Website security services can clean the site and close the hole.

When the error appeared right after a plugin, theme, or core update, follow our guide to the WordPress white screen after an update, which covers maintenance mode and rollbacks.

How Do You Prevent Critical Errors in WordPress?

You prevent most critical errors by testing changes on a staging site, updating one plugin at a time, and keeping fresh backups. The WordPress common errors guide covers the most frequent WordPress errors and their usual causes.

These habits make the biggest difference:

Add custom code through a child theme or a snippets plugin, never the live theme editor.
Check plugin compatibility before your host upgrades PHP.
Keep the administration email address current so recovery emails reach a real person.

Our website maintenance checklist turns these habits into weekly, monthly, and yearly tasks.

If you would rather not handle updates yourself, ongoing website maintenance covers plugin, theme, and core updates and fixes errors as they appear.

Conclusion

The critical error message looks alarming, but it protects your site and keeps your content safe. Start with the recovery mode email, because its error details often name the plugin or theme at fault. If the email never arrives, turn on debug mode and read the last fatal error in debug.log. Then rename the faulty plugin or theme folder, raise the memory limit, or check your PHP version.

If you want a hand reading the error and getting the site back, reach out to our team for a plain-language conversation.

Frequently Asked Questions

Did the critical error delete my website content?

No. The critical error means PHP stopped running before WordPress could finish the page. Your posts, pages, products, and orders stay in the database. Once you deactivate or fix the plugin, theme, or code that crashed, everything appears again. Take a full backup of your files and database before you start the repair.

Why didn’t I get the recovery mode email?

WordPress sends the recovery mode email to the administration email address in Settings, then General. If that address is old, nobody sees the email. The email can also land in spam, or fail when your server cannot send mail. In that case, turn on debug mode in wp-config.php or read your host’s error_log file instead.

Can a PHP update cause a WordPress critical error?

Yes. Hosts upgrade PHP to keep servers secure, and an older plugin or theme can stop working on the new version. The error log often shows “Call to undefined function” or a similar message. Switch back to the previous PHP version in your hosting panel for now, then update or replace the plugin before you upgrade again.

Do visitors see the critical error message?

Yes. Visitors see a short notice that the site has a critical error, with no details about the cause. Logged-in administrators see an extra line pointing them to the admin email inbox. Because customers see a broken page, fix the error quickly or restore a working backup while you investigate.

There Has Been a Critical Error on This Website: How to Fix It in WordPress