If you’ve landed on this page because your WordPress website suddenly displays the message “There has been a critical error on this website”, don’t panic. This error is one of the most common WordPress problems, and in most cases, it can be fixed without rebuilding your website or losing your data.

In this step-by-step guide, you’ll learn what causes the WordPress Critical Error, how to identify the root problem, and 12 proven solutions that work for beginners and advanced users alike.

Whether the error appeared after installing a plugin, updating your theme, upgrading WordPress, or making changes to PHP files, this guide will help you restore your website safely.

Quick Answer

The WordPress Critical Error usually occurs when a fatal PHP error prevents WordPress from loading properly. The most common causes include:

• Plugin conflicts
• Broken themes
• Corrupted WordPress core files
• PHP memory limit exhaustion
• Outdated PHP version
• Faulty custom code
• Database issues

In most situations, the error can be fixed by disabling plugins, switching themes, increasing PHP memory, enabling WordPress debugging, or restoring a recent backup.

Table of Contents

1. What Is the WordPress Critical Error?
2. Why Does It Happen?
3. How to Identify the Cause
4. 12 Proven Ways to Fix It
5. How to Prevent It
6. Frequently Asked Questions
7. Final Thoughts

What Is the WordPress Critical Error?

The WordPress Critical Error is a fatal error that stops WordPress from loading properly. Instead of displaying your website, WordPress shows a message similar to:

“There has been a critical error on this website. Please check your site admin email inbox for instructions.”

This message replaced the traditional “White Screen of Death” beginning with WordPress 5.2. The new system is designed to make troubleshooting easier by sending recovery information to the administrator’s email address.

Unlike simple warnings or notices, a critical error prevents PHP from completing execution. Because WordPress relies heavily on PHP, even a single fatal error can stop your entire website from working.

How to Identify the Real Cause

Before attempting any fix, identify what changed immediately before the error appeared.

Ask yourself:

• Did I install a new plugin?
• Did I update WordPress?
• Did I update my theme?
• Did I edit PHP files?
• Did my hosting provider change PHP versions?
• Did I restore an old backup?

If the answer is yes to any of these questions, you’ve already narrowed down the likely cause.

The next step is to troubleshoot each possibility methodically instead of making random changes.

What’s Next?

Now that you understand what causes the WordPress Critical Error, it’s time to fix it.

In the next section, you’ll learn the 12 proven solutions, including how to disable plugins without access to the WordPress dashboard, enable debugging, increase PHP memory, repair corrupted files, and recover your website safely.

12 Proven Ways to Fix the WordPress Critical Error

Now that you understand what causes the error, it’s time to fix it. Start with the first solution below and continue in order until your website starts working again.

Fix #1: Enable WordPress Debug Mode

The fastest way to discover the real cause of the critical error is by enabling WordPress Debug Mode.

Instead of guessing, WordPress will generate an error log showing exactly which file, plugin, or theme is causing the issue.

Why This Works

When Debug Mode is enabled, WordPress records PHP errors inside a log file instead of hiding them.

How to Enable Debug Mode

1. Login to your hosting File Manager or connect using FTP.
2. Open the wp-config.php file.
3. Find this line:

define('WP_DEBUG', false);

Replace it with:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

Save the file.

Now visit your website again.

WordPress will generate a log file here:

/wp-content/debug.log

Example

Fatal error:
Call to undefined function abc_function()
in /wp-content/plugins/example-plugin/functions.php

This tells you exactly which plugin is causing the problem.

Fix #2: Disable All Plugins

Plugin conflicts are responsible for a large percentage of WordPress Critical Errors.

If you cannot access your WordPress dashboard, you can still disable every plugin manually.

Method 1: Using File Manager

1. Open File Manager in your hosting account.
2. Go to:

/wp-content/

Rename the folder:

plugins

to

plugins-disabled

WordPress automatically disables every plugin.

Now refresh your website.

If the Website Starts Working

One of your plugins caused the error.

Rename the folder back to plugins.

Then activate plugins one by one until the error returns.

The last activated plugin is the culprit.

Example

Now you’ve identified the problematic plugin.

Fix #3: Switch to a Default WordPress Theme

Sometimes the issue isn’t a plugin—it’s your theme.

This is especially common after updating premium themes or editing the functions.php file.

How to Change Themes Without Dashboard Access

Go to:

/wp-content/themes/

Rename your current theme.

Example:

astra

Rename it to:

astra-old

If a default theme such as Twenty Twenty-Five is installed, WordPress automatically activates it.

If Your Website Starts Working

Your theme contains the problem.

This could be:

• Broken functions.php
• Outdated theme files
• Compatibility issues
• Incorrect custom code

Fix #4: Increase PHP Memory Limit

Many WordPress websites crash because PHP runs out of available memory.

This usually happens on shared hosting.

Symptoms

• Critical Error
• Blank White Screen
• 500 Error
• Website crashes while importing data

Increase Memory Using wp-config.php

Add this line before:

/* That's all, stop editing! */

Add:

define('WP_MEMORY_LIMIT', '256M');

Some hosting providers allow:

512M

Why It Works

More memory allows WordPress, Elementor, WooCommerce and large plugins to execute properly.

Recommended Memory Limits

Fix #5: Reinstall WordPress Core Files

WordPress core files can become corrupted after failed updates or malware attacks.

Fortunately, reinstalling WordPress does not delete your posts or database.

Steps

1. Download the latest version of WordPress.
2. Extract the ZIP file.
3. Upload everything except:

• wp-content
• wp-config.php

Overwrite existing files.

Why This Works

Corrupted system files are replaced with clean versions.

Your database, media library, plugins and themes remain intact.

Fix #6: Update Your PHP Version

Running an outdated PHP version is one of the most overlooked causes of the WordPress Critical Error.

Modern plugins often require PHP 8.x.

How to Check PHP Version

Most hosting control panels include a PHP Version Manager.

Examples:

• cPanel
• Plesk
• Cloudways
• SiteGround Site Tools
• Hostinger hPanel

Recommended Versions

Example

You update WooCommerce.

The new version requires PHP 8.1.

Your hosting is still using PHP 7.4.

Immediately after the update, your website displays the WordPress Critical Error.

Upgrading PHP fixes the problem instantly.

Quick Troubleshooting Checklist

Fix #7: Check and Repair Your WordPress Database

A corrupted database can also trigger the WordPress Critical Error. This usually happens after interrupted updates, failed migrations, server crashes, or malware infections.

Common Symptoms

• Error establishing a database connection
• Critical Error after updating WordPress
• Missing posts or pages
• Dashboard not loading correctly

Enable Database Repair

Open your wp-config.php file and add the following line before the “That’s all, stop editing!” comment:

define('WP_ALLOW_REPAIR', true);

Now visit:

https://yourdomain.com/wp-admin/maint/repair.php

Select Repair Database or Repair and Optimize Database.

Fix #8: Verify File Permissions

Incorrect file permissions can prevent WordPress from loading essential files, resulting in a Critical Error.

Recommended Permissions

How to Check

1. Login to cPanel or your hosting File Manager.
2. Right-click a folder or file.
3. Select Permissions.
4. Correct the values if necessary.

Incorrect permissions often occur after migrating websites between servers.

Fix #9: Restore a Recent Backup

If the error appeared immediately after making changes, restoring a backup is often the quickest solution.

Restore If You Recently:

• Updated plugins
• Updated themes
• Updated WordPress
• Modified PHP files
• Migrated your website

Most Hosting Providers Offer One-Click Backups

• SiteGround
• Hostinger
• Bluehost
• Cloudways
• Kinsta
• WP Engine

If you use backup plugins like UpdraftPlus or BlogVault, restoring your latest backup usually takes only a few minutes.

Fix #10: Scan Your Website for Malware

Malicious code injected into your website can break WordPress and trigger fatal PHP errors.

Signs of Malware

• Unexpected redirects
• Spam pages indexed in Google
• Unknown administrator accounts
• Modified core files
• Suspicious PHP files

Recommended Security Plugins

• Wordfence Security
• Solid Security (formerly iThemes Security)
• Sucuri Security
• MalCare

Run a complete scan and remove any infected files.

If core files are infected, reinstall WordPress after cleaning the malware.

Fix #11: Use WordPress Recovery Mode

Starting with WordPress 5.2, Recovery Mode helps administrators regain access when a plugin or theme causes a fatal error.

How Recovery Mode Works

When WordPress detects a fatal error, it sends an email to the site administrator containing a special recovery link.

The email usually includes:

• The plugin causing the error
• The affected PHP file
• A secure Recovery Mode login link

After logging in through Recovery Mode, you can deactivate the faulty plugin or theme without affecting the rest of your website.

Fix #12: Contact Your Hosting Provider

If none of the previous fixes work, the issue may be server-related rather than WordPress itself.

Your Hosting Provider Can Check:

• Server error logs
• PHP configuration
• Memory allocation
• CPU limits
• File system errors
• Database corruption
• Firewall restrictions

Many managed WordPress hosts can identify the exact cause within minutes using server logs that are not accessible to website owners.

Information to Provide

• When the error started
• Recent changes made to the website
• Error messages from debug.log
• Your WordPress version
• Your PHP version

Providing these details helps support engineers diagnose the issue much faster.

Summary of All 12 Fixes

These 12 solutions resolve the majority of WordPress Critical Errors.

However, if your website still isn’t working, don’t worry. The next section covers six more advanced fixes, including repairing the database, checking file permissions, restoring backups, identifying malware infections, contacting your hosting provider, and using Recovery Mode to bring your website back online.