How to Fix the WordPress Critical Error and Get Your Site Back Online
“There has been a critical error on this website” is a PHP fatal error in WordPress. To fix it, open the recovery mode email link, enable the debug log in wp-config to read the error, then isolate the cause by deactivating all plugins, switching to a default theme, or raising the PHP memory limit.
Few messages stop a business site as completely as “There has been a critical error on this website.” The page goes blank, the WordPress dashboard may lock you out, and there is no obvious clue about what broke. The good news: a WordPress critical error is almost always a single, fixable fault — a conflicting plugin, a broken theme, an exhausted PHP memory limit, a bad PHP version, or a corrupt core file. This guide walks the recovery in the order a professional would, so you spend your time on the likely cause instead of guessing.
What “There Has Been a Critical Error on This Website” Means
The critical error message is WordPress’s safe way of saying a fatal PHP error stopped the page from finishing. Rather than show a raw white screen of death, modern WordPress catches the fatal error, halts the request, and displays a generic critical error message so visitors never see sensitive details. The real explanation is written to the error log, and — if your site can still send mail — to the site admin email inbox.
Because the wording is deliberately vague, the message itself never tells you the cause of the error. That is by design: exposing a fatal PHP error to the public could leak file paths or code. Your job is to read the log, reproduce what triggered the error, and rule causes out one at a time.
Common Causes of a WordPress Critical Error
Most critical errors trace back to a short list of culprits. Knowing them tells you where to look first:
- Plugin conflict or a broken plugin update. Incompatible or buggy plugins are the most common trigger — one plugin calls code another plugin or the WordPress core no longer provides.
- A broken or incompatible theme. A theme that expects a newer WordPress version, or an edited
functions.php, can throw a fatal error site-wide. - Exhausted PHP memory limit. When a page needs more memory to run than the server allows, PHP stops and WordPress reports a critical error.
- An outdated or wrong PHP version. Old code on a new PHP version (or the reverse) produces fatal php errors during a page load.
- Corrupt core files or a damaged database. A failed update or a half-finished upload can leave corrupted files in the WordPress core.
Keep this list in mind as a checklist: you will confirm or eliminate each one in the steps below. For deeper diagnostics across any WordPress error, our WordPress troubleshooting guide maps the full decision tree.
Before You Start: Capture the Error and Back Up
Two minutes here saves hours later. First, note exactly what you see — the critical error message, the URL where it appears, and whether the WordPress admin area is also down. Second, take a backup of your WordPress website (files and database) before you change anything, so any fix you try is reversible. If you cannot reach the dashboard, your host’s control panel or an FTP client can copy the files, and the hosting control panel usually exports the database. A current backup is also your fastest route to restore your site if a step goes wrong; see our WordPress backup strategy for business websites.
Step 1 — Check the Admin Email and Use WordPress Recovery Mode
When a fatal error occurs, WordPress sends an email to the site admin email with the subject line “Your Site is Experiencing a Technical Issue.” That email names the plugin or theme that caused the error and includes a special WordPress recovery mode link.
Open the recovery mode link and WordPress loads the dashboard with the offending plugin or theme paused, so you can log in even while the front end shows the critical error. From there you can deactivate the named plugin, update it, or switch themes, then exit recovery mode to check your site. If the email never arrived — common when the site cannot send mail — move to the debug log in Step 2.
Step 2 — Enable Debug Mode to Read the Error Log
If recovery mode is not available, turn on WordPress debug so the platform records the fatal error. Edit wp-config.php (via FTP or the hosting control panel file manager) and add these lines just above the “That’s all, stop editing” comment:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );Reload the page that shows the critical error, then open /wp-content/debug.log in the same folder via FTP. Checking the php error log gives you the file and line that triggered the error — for example, a plugin’s PHP file or a theme template. That single line usually points straight at the cause. When you finish, set WP_DEBUG back to false so the log does not grow on a live site. For the official reference, see Debugging in WordPress.
Step 3 — Deactivate All Plugins, Then Reactivate One by One
Because faulty add-ons cause critical errors more than anything else, this is the highest-value test. If you can reach the dashboard (directly or through recovery mode), deactivate every plugin at once from the Plugins screen.
If you are locked out, use FTP or the file manager: rename the /wp-content/plugins folder to plugins-off. WordPress can no longer load them, so it deactivates everything and the critical error usually clears. Rename the folder back, then reactivate each one, reloading the site after every step. Whichever add-on brings the error back is causing the issue — update it, replace it, or remove it. Working through plugins or themes this way isolates the fault without touching your content.
Step 4 — Switch to a Default Theme to Rule Out the Theme
If disabling plugins did not fix the WordPress critical error, suspect the theme. From Appearance → Themes, activate a default WordPress theme such as Twenty Twenty-Four. If the site recovers, the previous WordPress theme — or a recent edit to its functions.php — was the trigger.
Locked out of the dashboard? Over FTP, rename your active theme’s folder inside /wp-content/themes. WordPress falls back to a default theme automatically. Once the site loads, you can repair the theme, reinstall a clean copy, or restore it from backup. For a theme-specific walkthrough, see how to fix a broken theme in WordPress.
Step 5 — Increase the PHP Memory Limit or Update PHP
If the debug log mentions “allowed memory size exhausted,” the page ran out of memory to run, and our dedicated guide on how to fix the WordPress memory exhausted error covers that specific fault in depth, including how to find which plugin is consuming the memory. The quick fix is to increase the PHP memory limit by adding this line to wp-config.php:
define( 'WP_MEMORY_LIMIT', '256M' );Some hosts cap memory at the server level; if the limit will not budge, raise it in php.ini or ask your host. While you are there, confirm the site runs a supported PHP version. An end-of-life PHP version, or a plugin not yet compatible with the newest release, can both throw a fatal error. Most hosts let you update PHP from the hosting control panel in a click — test on staging first, because a version change can surface its own conflicts.
Step 6 — Restore Core Files or Reinstall WordPress
If plugins, themes, memory, and PHP all check out, the problem may be corrupt core files from a failed update. The safe fix is to reinstall WordPress core: download a fresh copy from WordPress.org and, over FTP, replace the wp-admin and wp-includes folders plus the loose files in the root — but not wp-content (your themes, plugins, and uploads) or wp-config.php. This overwrites corrupted WordPress core files without touching your content. If even that fails, restore your WordPress website from the backup you took earlier. WordPress.org documents both the message and the recovery in Common WordPress errors and Recovery Mode.
Prevent Future Critical Errors
Once you get your site back online, a little process keeps the critical error from returning:
- Test updates on staging. Apply WordPress updates, plugin updates, and PHP changes on a copy first, so a conflict never reaches visitors.
- Keep automated backups. A daily backup of your WordPress website turns any future fatal error into a quick restore instead of a crisis.
- Audit plugins and themes. Remove abandoned plugins, keep the rest current, and avoid stacking plugins that do the same job.
- Watch the error log. Periodic debug log checks surface warnings before they become a site-down critical error.
When to Call for Help
If you have worked through every step and the WordPress site still breaks, or if the critical error followed a security incident, bring in help. Contact your hosting provider first — they can see server logs, confirm the PHP version, and rule out a platform problem on their end. If the cause looks like a hack or defacement rather than a plain fatal error, follow a structured incident response after a WordPress hack instead of patching blindly. For hands-on recovery of a business-critical site, our team offers WordPress support that gets your site back online safely.
FAQ: WordPress Critical Errors
How do you fix the “There has been a critical error on this website” message?
Open the recovery mode link in the admin email, or enable the debug log in wp-config.php to read the fatal error. Then isolate the cause: deactivate all plugins, switch to a default theme, raise the PHP memory limit, and as a last resort reinstall WordPress core files or restore from backup.
What is a critical error in WordPress and what does it mean?
A critical error in WordPress is a fatal PHP error that stops a page from loading. WordPress hides the technical detail behind a generic critical error message and writes the real cause to the error log.
What are the common causes of a WordPress critical error?
The usual causes are a plugin conflict, a broken or incompatible theme, an exhausted PHP memory limit, an outdated PHP version, or corrupt core files. Most critical errors come from a plugin or theme.
What is WordPress Recovery Mode and how does it help?
Recovery mode is a safe login link WordPress emails to the site admin when a fatal error occurs. It loads the dashboard with the offending plugin or theme paused, so you can fix the cause even while the front end shows the critical error.
How do I enable debug mode to find the error?
Add define( 'WP_DEBUG', true ); and define( 'WP_DEBUG_LOG', true ); to wp-config.php, reload the broken page, then open /wp-content/debug.log to see the file and line that triggered the error.
How do I troubleshoot if I cannot access the WordPress dashboard?
Use FTP or your hosting control panel file manager. Rename the /wp-content/plugins folder to deactivate all plugins, or rename the active theme folder to force a default theme. Both let you isolate the cause without the dashboard.
How can I restore my WordPress website from a backup to fix it?
Use your backup plugin or host’s restore tool to roll the files and database back to the last working point. A recent backup is the fastest way to restore your site when a fix is risky or the cause is unclear.
When should I contact my hosting provider or a developer?
Contact your hosting provider if the steps above do not resolve the issue, if the error appears server-wide, or if you suspect corrupt core files. Call a WordPress developer when the site is business-critical or the error followed a security incident.
