“There Has Been a Critical Error on This Website”: How to Fix It in WordPress (2026)
What the WordPress critical error and the white screen of death mean, how to use recovery mode, find the cause in the error log and get your site back online step by step.

You open your website and instead of your home page you see one sentence: “There has been a critical error on this website.” Sometimes it adds “Please check your site admin email inbox for instructions.” Sometimes there is nothing at all, just a blank white page. Customers cannot reach you, and often you cannot even log in.
The good news: in most cases your content is not lost. The error means that a piece of PHP code stopped working, usually after a plugin, theme or PHP update. This guide shows you how to find the cause and get your site back online, step by step, starting with the fastest fixes.
Key takeaways
- “There has been a critical error on this website” means a fatal PHP error. The white screen of death is the same problem with error messages turned off.
- The most common causes are a plugin or theme update, a PHP version change, custom code and too little memory.
- First check the admin email inbox (and spam) for “Your Site is Experiencing a Technical Issue”. It contains a recovery mode link that lets you log in and deactivate the faulty plugin.
- No email? Read the error log in your hosting panel or turn on WP_DEBUG_LOG. The log names the file and line that caused the error.
- If you cannot log in, deactivate plugins by renaming their folder via your hosting file manager or FTP.
- Undo the last change first: the update you just installed, the PHP version you just switched, the snippet you just added.
What the critical error actually means
WordPress is built with PHP. When a plugin, theme or snippet runs into an error that PHP cannot recover from, the page stops loading. That is a fatal error.
Since version 5.2, WordPress catches these fatal errors. Instead of a broken page, visitors see the short critical error message, and WordPress sends an email to the administrator address with details and a link to recovery mode. In recovery mode you can log in while the faulty plugin or theme is paused for you, and fix the problem from the dashboard. See the official WordPress documentation on recovery mode.
The white screen of death is the older or quieter version of the same problem: a fatal error, but with nothing shown at all. You see it on old WordPress versions, when error display is turned off, or when the error happens before WordPress can show its message.
The most common causes
| Cause | Typical trigger | How likely |
|---|---|---|
| A plugin update or a new plugin | The error appears right after updating or installing a plugin | Very common |
| A plugin conflict | Two plugins that worked alone break together | Common |
| A theme or page builder update | The front end breaks, sometimes the admin area still works | Common |
| A PHP version change | Your host or you switched PHP and old code is no longer supported | Common, especially in 2026 with the end of PHP 8.2 |
| Custom code | A snippet in functions.php or a code snippets plugin | Common |
| Not enough memory | “Allowed memory size exhausted” in the error log | Occasional |
| A failed WordPress update | The update was interrupted and core files are incomplete | Rare |
| Malware | Infected files with broken code | Rare, but serious |
The fastest question is always: what changed right before the error? In most cases the answer points straight to the cause.
Step 1: Check your email for the recovery mode link
Look in the inbox of the email address set as the WordPress administrator (and in the spam folder) for a message with the subject “Your Site is Experiencing a Technical Issue”. It tells you which plugin or theme caused the error and contains a special login link.
- Click the recovery mode link and log in.
- WordPress shows which plugin or theme is paused because of the error.
- Deactivate that plugin, or switch to a different theme.
- Exit recovery mode and check your site in a private browser window.
- Then look for an update or an alternative for the plugin, or contact its developer.
The link is only valid for a limited time. If it has expired, or the email never arrived (common when the site cannot send emails), continue with step 2.
Step 2: Find the cause in the error log
Most hosts keep a PHP error log that you can open in the hosting panel, often under PHP settings, logs or the file manager as error_log. Look for lines starting with PHP Fatal error. They name the file and line, for example a path inside wp-content/plugins/plugin-name/. The folder name tells you which plugin or theme it is.
If there is no log, turn on WordPress debug logging. Open wp-config.php in the file manager and add these lines above the line that says “That’s all, stop editing”:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Load the page again. WordPress now writes errors to wp-content/debug.log without showing them to visitors. When you have fixed the problem, set WP_DEBUG back to false. The official WordPress debugging guide explains all debug options.
Step 3: Deactivate plugins without the dashboard
If you cannot log in, deactivate plugins through the file system. WordPress treats a plugin whose folder it cannot find as deactivated.
- Open the file manager in your hosting panel, or connect with an FTP client.
- Go to
wp-content/plugins/. - If the log named a plugin, rename only its folder, for example from
plugin-nametoplugin-name-off. - If you do not know which plugin it is, rename the whole
pluginsfolder toplugins-off. All plugins are now deactivated. - Reload your site. If it works, rename the folder back to
plugins, log in and reactivate the plugins one by one until the error returns. The last one you activated is the culprit.
Renaming does not delete any plugin settings. They are still in the database when you reactivate the plugin.
Step 4: Rule out the theme
If the plugins are not the cause, test the theme. In wp-content/themes/, rename the folder of your active theme. WordPress then falls back to a default theme such as Twenty Twenty-Five, as long as one is installed. If the site loads, the problem is in your theme, a child theme or a page builder template. Rename the folder back before you continue, otherwise your design and theme settings stay switched off.
Step 5: Check the PHP version and the memory limit
If the error appeared after your host changed the PHP version, or after you switched it yourself, set the previous version again in your hosting panel. That usually fixes the site within a minute. Then find the plugin or code that is not compatible with the new version and replace or update it, because old PHP versions stop receiving security fixes. Our guide on updating the PHP version in WordPress shows how to do that safely.
If the log says “Allowed memory size of … bytes exhausted”, WordPress ran out of memory. You can raise the limit in wp-config.php:
define( 'WP_MEMORY_LIMIT', '256M' );
Your host sets the maximum. If the error comes back, a single plugin is often using far too much memory, and that plugin is the real problem. More on memory settings in the WordPress documentation on wp-config.php.
Step 6: Repair WordPress or restore a backup
If none of this helps, core files may be damaged, for example by an interrupted update. You can reinstall WordPress under Dashboard → Updates (“Re-install version”), or upload fresh copies of the wp-admin and wp-includes folders from wordpress.org. Never overwrite wp-content or wp-config.php, they contain your content and settings.
The fastest way back is often a backup from before the error. Restore it, then repeat the update that caused the problem on a staging copy to find out what went wrong. Our WordPress backup guide explains what a backup needs to be usable in a moment like this.
If you find unknown files, strange code at the top of PHP files or new admin users, the error may be caused by malware. Read our guide on what to do if your WordPress site is hacked.
The most common error messages, and what they mean
The error log usually tells you exactly what went wrong, if you know how to read it. These are the fatal errors we see most often on WordPress sites:
| Message in the log | What it means | What to do |
|---|---|---|
| Allowed memory size of … bytes exhausted | WordPress ran out of PHP memory | Raise WP_MEMORY_LIMIT, then look for the plugin that uses so much memory |
| Call to undefined function … | The code calls a function that does not exist: a plugin it depends on is missing, or the function was removed in a newer PHP version | Update or replace the plugin, or reactivate the plugin it depends on |
| Uncaught Error: Class “…” not found | A file or dependency is missing, often after an interrupted update | Reinstall the plugin or theme named in the path |
| Parse error: syntax error, unexpected … | A typo in PHP code, almost always a snippet that was just added | Remove or correct the snippet in the file and line named in the log |
| Uncaught TypeError or ArgumentCountError | PHP 8 is stricter than PHP 7, and old code passes the wrong kind of value | Update the plugin or theme. Switch PHP back only as a temporary fix |
| Maximum execution time of … seconds exceeded | A process took longer than the server allows, for example an import or a backup | Find the plugin running that process. Raise max_execution_time only if the process is legitimate |
How to read a line in the error log
A typical entry looks like this:
PHP Fatal error: Uncaught Error: Call to undefined function create_function() in /home/user/public_html/wp-content/plugins/old-slider/old-slider.php:112
- PHP Fatal error is the type. Only fatal and parse errors break the site. Warnings and notices can wait.
- Call to undefined function create_function() is the cause. This function was removed in PHP 8.0, which is why this error often shows up right after a PHP upgrade.
- /wp-content/plugins/old-slider/ tells you the culprit: the plugin in the folder
old-slider. - :112 is the line in that file. You only need it if you or a developer fix the code yourselves.
In this example, the fix is to rename the old-slider folder, then update the plugin or replace it with a maintained alternative.
Where to find the error log and the file manager at your host
The names differ from host to host, but you will usually find them here:
| Hosting panel | File manager | Error log |
|---|---|---|
| Hostinger (hPanel) | Websites → your site → Files → File Manager | Turn on error logging in the PHP configuration, then open the error_log file |
| cPanel | Files → File Manager | Metrics → Errors, or the error_log file in your site folder |
| Plesk | Websites and Domains → File Manager | Websites and Domains → Logs |
| Managed WordPress hosts | Often SFTP access instead of a file manager | A log viewer in the site dashboard |
If you cannot find either, ask your host’s support for the PHP error log of your site. They can usually see it in seconds.
Typical cases with Elementor and WooCommerce
Page builders and shops run a lot of code and depend on many add-ons, so they cause a good share of critical errors:
- Elementor and Elementor Pro out of step. If one is updated and the other is not, they can stop working together. Update both to matching versions.
- Old Elementor add-ons. Third-party widget packs that are no longer maintained often break after an Elementor update. Rename the add-on folder first, not Elementor itself.
- WooCommerce extensions. Payment gateways, subscription or shipping plugins that are behind the current WooCommerce version are a classic cause. Update the extensions together with WooCommerce, and test major WooCommerce updates on staging.
- The checkout breaks but the rest works. That is often a payment or shipping plugin. Check the log right after a test order.
When the recovery mode email does not arrive
Many WordPress sites cannot send email reliably, so the recovery email never arrives. A few things help:
- Check which address is set as the administration email under Settings → General. That is where WordPress sends the message.
- Install an SMTP plugin and send email through a real mailbox or email service. Your contact forms will benefit too.
- You can send recovery emails to a different address by adding this line to wp-config.php:
define( 'RECOVERY_MODE_EMAIL', 'you@example.com' );
If none of this helps right now, you do not need the email: the error log and the steps above work without it.
Quick diagnosis: what changed last?
| What happened right before | Most likely cause | First thing to try |
|---|---|---|
| You updated plugins | The updated plugin | Recovery mode link, or rename that plugin folder |
| You installed a new plugin | The new plugin or a conflict with it | Rename the new plugin folder |
| You updated or changed the theme | The theme or page builder | Rename the theme folder |
| Your host announced a PHP change | Old code that is not compatible | Switch back to the previous PHP version |
| You added code to functions.php | A typo or an incompatible snippet | Remove the snippet via the file manager |
| Nothing you know of | Automatic update, PHP change by the host or malware | Read the error log |
How to prevent the next critical error
- Backup before every update. Then a broken update costs minutes, not days.
- Update in the right order and not everything blindly at once. Our guide on updating WordPress safely explains how.
- Test big updates and PHP upgrades on staging before they reach the live site.
- Check your pages after every update. Not every error is a critical error: a broken layout or a missing form does not show a message at all.
- Monitor your site. If your site goes down at night, you want to know before your customers do.
- Remove plugins you do not use. Less code means fewer conflicts.
Updates that do not break your site.WP Beekeeper makes a full backup before every update, installs updates in the right order, compares your pages before and after and flags anything that looks different. From 29 euros per site and month.
See how it works →Sources and further reading
- Recovery Mode, WordPress.org documentation
- Debugging in WordPress, Advanced Administration Handbook
- Common WordPress errors, Advanced Administration Handbook
- Editing wp-config.php, Advanced Administration Handbook
- Supported PHP versions, php.net
Frequently asked questions
What does “There has been a critical error on this website” mean?
It means a fatal PHP error stopped WordPress from loading the page. It is usually caused by a plugin, a theme, custom code or a PHP version change. Your content is normally not lost.
How do I fix the critical error if I cannot log in?
Check the admin email inbox for the recovery mode link. Without it, open your hosting file manager or FTP, go to wp-content/plugins and rename the folder of the plugin that causes the error, or the whole plugins folder, to deactivate plugins.
I did not get the recovery mode email. What now?
Check the spam folder and make sure you look at the email address set as WordPress administrator. If the site cannot send emails, read the PHP error log in your hosting panel or turn on WP_DEBUG_LOG to find the faulty file.
What is the WordPress white screen of death?
It is a blank white page without any message. It has the same causes as the critical error, a fatal PHP error, but the error is not shown. The same steps fix it: error log, plugins, theme, PHP version and memory.
Can a PHP update cause a critical error?
Yes. Old plugins, themes or custom code can use PHP features that newer versions removed. Switch back to the previous PHP version to get the site online, then update or replace the incompatible code.
Will I lose my content if I deactivate plugins?
No. Renaming a plugin folder only deactivates the plugin. Its settings stay in the database and are back when you reactivate it.
How can I prevent critical errors?
Make a backup before every update, update in the right order, test big updates and PHP upgrades on staging, check your pages afterwards and monitor your site so you notice problems quickly.
Conclusion
The critical error looks alarming, but it is usually a single plugin, theme or code change that stopped working. Use the recovery mode email if you have it, otherwise the error log, then deactivate plugins and the theme through the file manager, check the PHP version and memory, and restore a backup if nothing else helps. Once your site is back, make sure the next update starts with a backup and ends with a check of your pages.
Let your WordPress maintenance run itself.Backup first, updates in the right order, a visual check of every page and a clear monthly report. Try WP Beekeeper free for 14 days, no credit card needed.
Start free trial →

