WordPress Critical Error: How to Fix “There Has Been a Critical Error on This Website”

Key highlights

• Learn what the WordPress message “There has been a critical error on this website” means and what usually causes it.
• Follow the main steps to fix the error, including using Recovery Mode, disabling plugins, switching themes and checking debug logs.
• Understand how to identify whether the issue is caused by a plugin conflict, theme problem, low PHP memory or corrupted WordPress files.
• Find out what to do next if the error appears after an update, code change or failed installation.
• Review the final recovery options to restore your site and get it running again safely.

Seeing the message “There has been a critical error on this website” can be alarming for any WordPress user. This WordPress critical error usually means something in your site’s core files, theme or plugins has caused a PHP-related issue, preventing your site from loading properly.

The good news? You can usually fix the WordPress error quickly – even without deep technical knowledge. In this guide, we’ll walk you through a step-by-step process to fix the critical error in WordPress, using both basic and advanced troubleshooting methods.

Note: Before making changes to your WordPress files or database, create a full backup of your site. If your hosting provider offers automated backups or restore points, use them before troubleshooting. If you cannot access your site safely, contact your hosting provider for help.

TL;DR – How to fix a WordPress critical error

If your site is down, start here:

• Checking your Recovery Mode email from WordPress
• Disabling recently updated plugins or themes
• Turning on WordPress debug mode to find the exact PHP error
• Increasing the PHP memory limit if your site has run out of resources
• Replacing corrupted WordPress core files
• Restoring a backup if the error started after a recent change

If you cannot access wp-admin, you can still troubleshoot the issue using FTP or your hosting File Manager.

Quick overview – How to fix the critical error in WordPress

Use these steps to troubleshoot the WordPress critical error in a safe order, starting with the quickest fixes and moving to more advanced solutions only if needed.

Step	Action	What to do
Step 1	Check your admin email	Open the Recovery Mode email from WordPress and use the link to access your dashboard safely
Step 2	Clear cached data	Clear your browser, plugin, server and CDN cache to make sure you are not seeing an outdated error page
Step 3	Check the logs	Enable debug mode in wp-config.php and review /wp-content/debug.log for plugin, theme or PHP errors
Step 4	Deactivate plugins	Disable recently updated or problematic plugins to check for conflicts
Step 5	Switch to a default theme	Rename your active theme folder through FTP or File Manager to test whether the theme is causing the issue
Step 6	Increase PHP memory	Add WP_MEMORY_LIMIT in wp-config.php or update the setting in your hosting control panel
Step 7	Replace core files	Upload fresh wp-admin and wp-includes files from the latest WordPress version
Step 8	Repair the database	Use phpMyAdmin or WP_ALLOW_REPAIR to fix damaged database tables if needed
Step 9	Roll back recent changes	Revert a recent plugin, theme or core update if the error started after a change
Step 10	Check file permissions	Review file permissions and rename .htaccess if needed to rule out configuration issues
Step 11	Scan for malware or server issues	Check for malicious code, security issues or server-level problems that may be causing the error

The above table explains the steps you might require to fix the error. However, before diving into each step in detail, let’s first understand what this WordPress error actually means.  

What does “There has been a critical error on this website” mean?

The “There has been a critical error on this website” message appears when WordPress encounters a PHP fatal error that prevents a page from loading properly. Instead of showing a blank screen or exposing technical details, newer versions of WordPress display this general WordPress critical error message to protect sensitive information.

This usually means something has gone wrong in your WordPress core files, theme or one of your installed plugins. As a result, the site may become partially or completely inaccessible until the underlying issue – often a plugin conflict, theme problem or PHP error – is resolved.

How does WordPress handle critical errors?

When a fatal PHP error occurs, WordPress tries to protect your site by:

• Displaying a generic message instead of detailed error output
• Sending a notification to your site admin email inbox
• Activating Recovery Mode, which lets you access the WordPress admin area more safely and troubleshoot the issue without taking down the entire site

This system, introduced in WordPress 5.2, helps prevent a full site crash and makes it easier to isolate the specific file, plugin or theme causing the error.

When might you see this error?

You might see this WordPress critical error after:

• Updating WordPress, a theme or a plugin
• Installing a new plugin that is incompatible with your setup
• Editing a PHP file or custom function with invalid code
• Exceeding your PHP memory limit
• Migrating your site to a new server or hosting provider
• Running into database connection or configuration issues

In short, this error is a sign that something in your WordPress site’s code or environment has failed and needs troubleshooting. Next, let’s look at the most common causes behind it.

Common causes of the WordPress critical error

A WordPress critical error can result from several issues affecting your site’s files, code or server configuration. Identifying the cause is the first step toward restoring your WordPress website.

1. Plugin conflict or faulty updateMalware injections, incorrect file permissions or web server misconfigurations can also trigger PHP errors. These problems are often harder to spot without checking logs or reviewing recent changes to the site environment.Now that you know what usually causes this issue, the next step is to troubleshoot it safely. Let’s look at how to fix the WordPress critical error step by step.

Conflicts between WordPress plugins or a faulty update are among the most common reasons for a critical error. If a plugin introduces incompatible code or uses more resources than your site can handle, it may break part or all of your website.

2. Theme incompatibility or custom theme bug

Errors in a WordPress theme, especially after updates or custom modifications, can trigger a fatal error. This is common when a theme file contains broken code or conflicts with a plugin or WordPress version.

3. Corrupted WordPress core files

Incomplete updates or file corruption in directories like wp-admin or wp-includes can stop your site from loading properly. Core file issues may also appear after a failed update, migration or manual file change.

4. PHP version mismatch or deprecated functions

Running an outdated or unsupported PHP version can cause errors when plugins or themes rely on newer functions. This often happens when your hosting environment and WordPress setup are no longer fully compatible.

5. Insufficient memory or resource limits

When your site runs out of allocated PHP memory, it may crash with a WordPress critical error message. Memory issues are more likely on plugin-heavy sites or during updates, backups or other resource-intensive tasks.

6. Database corruption or misconfiguration

Incorrect database credentials, damaged tables or corrupted data can prevent WordPress from working normally. In some cases, the issue affects only part of the site, while in others it can bring down the entire website.

7. Server or malware issues

1. Plugin conflict or faulty updateMalware injections, incorrect file permissions or web server misconfigurations can also trigger PHP errors. These problems are often harder to spot without checking logs or reviewing recent changes to the site environment.Now that you know what usually causes this issue, the next step is to troubleshoot it safely. Let’s look at how to fix the WordPress critical error step by step.

1. Plugin conflict or faulty updateMalware injections, incorrect file permissions or web server misconfigurations can also trigger PHP errors. These problems are often harder to spot without checking logs or reviewing recent changes to the site environment.Now that you know what usually causes this issue, the next step is to troubleshoot it safely. Let’s look at how to fix the WordPress critical error step by step.

How to fix the WordPress critical error in 11 steps?

If your site shows “There has been a critical error on this website,” start with the safest troubleshooting steps first and move to more advanced fixes only if the issue continues. In most cases, the fastest way to fix a WordPress critical error is to identify the plugin, theme, file or server setting that triggered it and reverse the issue step by step.

Step 1: Check your admin email for a Recovery Mode link

When a critical error occurs, WordPress often sends an email to your site admin inbox with the subject line “Your Site is Experiencing a Technical Issue.”

This email usually includes a Recovery Mode link that lets you open the WordPress admin area more safely. From there, you can identify the plugin or theme causing the issue and deactivate it without affecting the rest of the site.

Step 2: Clear cached data

Sometimes a cached version of the error page continues to appear even after the issue has been fixed.

Clear your browser cache, plugin cache and any cache managed through your hosting control panel. If your site uses a CDN, purge that cache as well. Then reload your site to check whether the error is still active.

Step 3: Check the logs to identify the issue

If the error continues, the next step is to look for clues in your logs.

Open the wp-config.php file in your site’s root directory and add the following code before the line that says “That’s all, stop editing! Happy publishing.”

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

This enables debug mode, saves error messages to a log file and hides them from visitors.

After saving the file, reload your site and open /wp-content/debug.log. Review the latest entries to find the plugin name, theme file, PHP function or file path linked to the fatal error. You can also check your hosting dashboard for PHP and server logs if they are available.

Once you finish troubleshooting, turn debug mode off again by setting WP_DEBUG to false.

Step 4: Deactivate plugins to rule out conflicts

Plugin conflicts are one of the most common causes of a WordPress critical error.

If you can access wp-admin through Recovery Mode, deactivate recently updated or newly installed plugins first. If you cannot access the dashboard, use FTP or File Manager to rename the plugins folder temporarily and test whether the site starts loading again.

If the error disappears, reactivate your plugins one at a time until you find the one causing the issue.

Step 5: Switch to a default WordPress theme

If the issue points to a theme conflict, use FTP or File Manager to rename your active theme folder inside /wp-content/themes/.

WordPress may then fall back to a default theme such as Twenty Twenty-Five. If the site starts working again, the issue is likely within your theme files or a recent theme update.

If using Bluehost,

• Go to the account manager and select Websites.
• Select Manage and go to Plugins.
• Deactivate plugins individually.

Also read: How to Disable/Delete Themes and Plugins in WordPress

Step 6: Increase the PHP memory limit

A low PHP memory limit can trigger fatal errors, especially on plugin-heavy sites or during updates, backups or other resource-intensive tasks.

Open wp-config.php and add:

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

Save the file and reload your site. You may also be able to change this setting in your hosting control panel depending on your provider.

Step 7: Replace corrupted WordPress core files

If WordPress core files were damaged during an update, migration or malware incident, replacing them can help restore normal functionality.

Download the latest version of WordPress from wordpress.org, then upload fresh copies of the wp-admin and wp-includes folders to your site using FTP. This refreshes the core files without changing your wp-content folder or database.

Step 8: Repair the database if needed

Database corruption or configuration issues can also trigger a critical error.

You can inspect your database in phpMyAdmin and repair damaged tables if needed. Another option is to temporarily enable the WordPress repair feature by adding this line to wp-config.php:

define( 'WP_ALLOW_REPAIR', true );

Then visit:

[yourdomain].com/wp-admin/maint/repair.php

Once the repair is complete, remove the line from wp-config.php.

Step 9: Roll back a recent update

If the error started immediately after a WordPress, plugin or theme update, revert the most recent change first.

Delete or deactivate the updated plugin or theme through FTP or File Manager and reinstall a stable version if needed. If the issue began after a core update, restoring a recent backup is usually safer than manually downgrading WordPress.

Step 10: Check file permissions and configuration files

Incorrect file permissions or a broken .htaccess file can stop your site from loading properly.

Standard permissions are usually:

• Folders: 755
• Files: 644

You can also temporarily rename .htaccess and reload the site. If the site loads, generate a new .htaccess file by saving your permalink settings in WordPress once access is restored. Review any .user.ini or PHP configuration files as well if they may be affecting memory or timeout settings.

Step 11: Scan for malware or server issues

If none of the steps above work, check for malware, suspicious code injections, server misconfiguration or permission issues.

• Review your security logs from dashboard.
• Do a quick malware scan to identify bugs.
• Check with your hosting provider for server-level errors that may not appear in WordPress logs.

What if wp-admin is unavailable?

If you cannot access wp-admin, you can still troubleshoot the WordPress critical error through FTP or your hosting File Manager. This gives you direct access to your site files so you can disable plugins, switch themes, check debug logs and update configuration files safely.

What to do if the error started after an update or code change

If the WordPress critical error appeared right after an update or code edit, the timing is a strong clue. In many cases, the fastest way to fix the issue is to reverse the most recent change and test your site again.

Step 1: Identify what changed most recently

Start by checking whether the error appeared after:

• Updating WordPress
• Installing or updating a plugin
• Updating or editing your theme
• Adding custom PHP code
• Changing server or PHP settings

If the error started immediately after one of these actions, begin your troubleshooting there.

Step 2: Roll back the last plugin or theme change

If you recently installed or updated a plugin or theme, deactivate it first.

If you still have dashboard access, disable the plugin or switch the theme from wp-admin. If you cannot log in, use FTP or File Manager to rename the plugin or theme folder and test the site again.

If the error disappears, the most recent update or change is likely the cause.

Step 3: Undo recent code edits

If you added custom code to functions.php, a custom plugin or another PHP file, remove the last change and reload your site.

Even a small syntax error or incompatible function can trigger a fatal error and cause WordPress to stop loading properly.

Step 4: Check compatibility before restoring the change

Before reactivating the plugin, theme or code snippet, confirm that it is compatible with your current WordPress version, PHP version and other active tools on your site.

This helps prevent the same WordPress critical error from happening again right away.

Step 5: Restore a backup if needed

If you cannot isolate the issue quickly and the error started after a recent update or edit, restoring a recent backup may be the safest option.

Choose a backup taken before the change was made, then test your site carefully before applying updates again.

Step 6: Reapply changes one at a time

Once your site is working again, reintroduce updates or custom code one at a time.

This makes it easier to confirm which specific change triggered the error and reduces the risk of breaking the site again.

If the error still remains after these steps, the issue may be tied to your hosting environment or a deeper server-level problem. Next, let’s look at when to contact your hosting provider.

When to contact Bluehost – Your reliable hosting provider

If the WordPress critical error still remains after basic troubleshooting, the issue may be tied to your hosting environment rather than WordPress alone. If your site is hosted with us on Bluehost, our support team can help with server settings, backups, file access and error logs that may not be visible inside WordPress.

Contact our support if:

• You cannot access wp-admin, FTP or File Manager.
• The error started after a server change, migration or PHP update.
• Your debug log does not show a clear cause.
• Your site has memory limit, timeout or permission issues you cannot change yourself.
• You need help restoring a backup.
• You suspect malware, corrupted files or a server-level configuration problem.

Our 24/7 expert WordPress team is available to assist you from the first step to every troubleshooting issue you face using your website.

When contacting Bluehost support, share as much detail as possible, including:

• When the error started
• Whether it happened after an update or code change
• Any plugin, theme or file you recently modified
• The exact error message from your debug log or server log
• The troubleshooting steps you have already tried

This can help the team identify the issue faster and avoid repeating steps you have already completed.

Once your site is working again, the next step is to reduce the chances of the same issue happening again. Let’s look at a few simple ways to prevent future WordPress critical errors.

Best practices to prevent future critical errors

Once you’ve fixed the WordPress critical error, it’s essential to prevent it from happening again. Regular maintenance and smart management can protect your WordPress website from unexpected downtime or data loss.

1. Keep WordPress, plugins and themes updated

Outdated WordPress core files, plugins or themes are a common cause of critical errors.

To reduce the risk:

• Update WordPress to the latest stable version

• Regularly update installed plugins and themes to ensure compatibility with newer PHP versions.

• Remove unused plugins and themes to reduce the risk of conflicts.

Also read: WordPress PHP Versions: How to Update Your Settings

2. Use trusted plugins and themes

Poorly coded or unsupported tools often trigger fatal errors.

• Only install WordPress plugins and themes from trusted sources.
• Check reviews, last update date and compatibility before installation.
• Avoid downloading from third-party or nulled sources, which may contain malware.

3. Test changes before going live

Before applying any updates or code edits to your live site, test the changes. You can do so in a staging environment as mentioned earlier. 

This allows you to identify issues without affecting your entire website. Most hosting providers offer one-click staging or cloning tools. 

Also read: How to Create a Staging WordPress Site

4. Monitor performance and resource usage

Regularly review your site’s PHP memory limit and server health:

• Use your hosting control panel to monitor memory usage, CPU load and error logs.
• Increase the PHP memory limit if your site experiences frequent fatal errors or timeouts.
• Consider upgrading your plan if your current hosting doesn’t meet resource needs.

5. Automate backups and error monitoring

Backups are your best recovery tool during unexpected issues.

• Set up automated backups through your hosting dashboard or a plugin.
• Use error monitoring tools like WP Activity Log or Sentry to track PHP errors and debug logs in real time.

These measures ensure you can quickly restore your WordPress site if a problem arises.

Read more: How to Create a Manual Backup

6. Limit direct edits to core or theme files

Editing PHP files or core files directly can easily break your WordPress site.

Instead, use:

• Child themes for customization
• Code snippets plugins for minor code changes
• Version control systems (like Git) to track changes safely

By following these preventive measures, you’ll minimize the chances of running into another critical error message and maintain a stable, high-performing WordPress website.

Final thoughts

A WordPress critical error can be alarming, but it’s usually easy to fix. Start by checking your admin email for a recovery link, deactivate any problem plugins or themes and use debug mode to pinpoint the issue. If needed, increase PHP memory or restore a recent backup.

To prevent future hiccups, keep your WordPress, themes and plugins updated, test changes in a staging site and monitor server resources. This is where choosing the right hosting makes a real difference.

With Bluehost WordPress hosting, you’re backed by a platform built specifically for WordPress. You get automated backups, one-click staging, built-in caching for faster load times and proactive security features – all designed to simplify troubleshooting and improve stability.

As your website grows, our hosting scales with you. From flexible upgrades and consistent performance to tools that support everything from small blogs to high-traffic business sites – we got you covered. So, instead of worrying about technical issues, you can focus on running and growing your website with confidence.

FAQs