![\"example](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2023\/11\/Example-Domain-2.jpg\")
<\/figure><\/div>\n\n\nAlthough WordPress doesn’t tell you what causes the error, we know the common culprits. In most cases, the WordPress white screen of death comes from plugin compatibility issues, file permission misconfiguration, and other similar problems.<\/p>\n\n\n\n
In this article, we’ll go over the potential causes behind the WordPress white screen of death and show you how to troubleshoot them. \ud83d\udcbb Let’s get to it!<\/p>\n\n\n\n
\ud83d\udcda Table of contents<\/strong>:<\/p>\n\n\n\n There are several issues that can trigger the WordPress white screen of death. Some of these issues can also lead to other kinds of errors, so it pays to know how to troubleshoot them. In our experience, here are the most common causes:<\/p>\n\n\n\n Since we can’t be sure what’s causing the error on your end, you’ll need to work your way through several troubleshooting tasks to diagnose and fix the issue. Let’s talk about those tasks below.<\/p>\n\n\n It’s important to note that you might not need to go through all eight troubleshooting tasks to fix your site. Since we’re not sure what’s causing the WordPress white screen of death in your case, we’re ordering these troubleshooting methods in the order you should try them.<\/p>\n\n\n\n In some cases, the white screen of death error will go away on its own. This is rare but also worth checking for since it only takes a minute.<\/p>\n\n\n\n If not, go ahead and clear the browser cache. If you need assistance, read our guide on how to clear the cache<\/a> for all major browsers. After clearing it, try reloading your website to see if the error persists.<\/p>\n\n\n\n If there’s no change, you can try clearing the WordPress cache as well. WordPress caching plugins will create a cache and store it on the server. You can clear that cache manually by accessing the plugin’s settings:<\/p>\n\n\n The Purge Cache<\/strong><\/em> or Clear Cache<\/strong><\/em> button location depends on your caching plugin. After clearing the WordPress cache, reload the site and check if the error persists.<\/p>\n\n\n\n For those not<\/em> using a caching plugin (or those who can’t access the dashboard due to the error), go ahead and jump to the next method.<\/p>\n\n\n The WordPress recovery mode <\/a>can be your best ally when it comes to troubleshooting critical errors. If the CMS (content management system) detects an error that would prevent your site from working (such as the WordPress white screen of death), it should automatically trigger recovery mode.<\/p>\n\n\n Think about recovery mode as the “safe” mode in your operating system (OS). The WordPress recovery mode lets you access the dashboard to do things such as disabling plugins and themes. However, you won’t have full access to all features.<\/p>\n\n\n\n If recovery mode triggers, WordPress will send you an email containing a link that will enable you to log in to the dashboard.<\/p>\n\n\n\n The tough part about recovery mode is that it doesn’t always trigger when it should. If you see the WordPress white screen of death, and you don’t receive a recovery mode email, you can assume it didn’t trigger. In that case, you’ll need to proceed with other troubleshooting methods.<\/p>\n\n\n There are a lot of ways to create a backup<\/a> of your website. For this method, we’re talking about backups created by your web host (or third-party services), because the WordPress white screen of death can block access to the dashboard.<\/p>\n\n\n\n Most managed WordPress web hosts will create full-site backups automatically. If you use such a web host, you can deal with the white screen of death quickly by reverting to a backup before the error appeared. Typically, you can find your site backups in the security section of your hosting account.<\/p>\n\n\n\n If your web host lacks backup functionality – and you can’t access the WordPress Admin – you’ll need to do things the hard way. That means troubleshooting the error manually, which is what we’ll do in the upcoming steps.<\/p>\n\n\n How you approach disabling plugins will depend on whether you can log in to the WordPress dashboard<\/a> or not. Before you do anything, we recommend creating a full backup of your site in case anything else “breaks” during the troubleshooting process.<\/p>\n\n\n\n If you can access the dashboard, go to Plugins<\/strong><\/em> \u2192 Installed Plugins<\/em><\/strong> and disable the active plugins one by one. After disabling each plugin, check if the WordPress white screen of death persists.<\/p>\n\n\n Your goal here is to isolate which plugin causes compatibility issues (sometimes it’s more than one plugin). If you disable all active plugins and the error persists, it means they’re not the cause. In that case, you can re-enable them and move on.<\/p>\n\n\n\n If you don’t<\/em> have access to the dashboard, you’ll need to disable plugins manually using the File Transfer Protocol (FTP)<\/a>. You can read our guide on how to use FileZilla<\/a> if you’ve never used an FTP client before.<\/p>\n\n\n\n Once you’ve installed FileZilla<\/a> and connected your website, go into the public_html<\/em> folder. Then, locate the plugins<\/em> directory in the wp-content<\/em> folder:<\/p>\n\n\n Open the directory and you’ll see folders for each plugin on your site (both active and inactive):<\/p>\n\n\n If you right-click on a folder, you’ll see an option to rename it. Changing the name of a plugin’s folder will automatically deactivate it in WordPress.<\/p>\n\n\n\n The procedure is simple. You want to identify the active plugins on your site and rename their folders to something else, one by one. After renaming each folder, check if WordPress is still showing the error.<\/p>\n\n\n\n Remember that you’ll need to return each plugin’s folder to its original name. Otherwise, WordPress will fail to recognize the plugin and you’ll need to re-install it.<\/p>\n\n\n Just as with plugins, you have two ways to deactivate and switch themes. If you can access the dashboard, go to Appearance<\/strong> \u2192 Themes<\/strong><\/em>. Hover over the theme you want to switch to and click on Activate<\/em><\/strong>.<\/p>\n\n\n If the active theme caused the problem due to compatibility issues, switching to another option should fix it.<\/p>\n\n\n\n Sometimes, the WordPress white screen of death won’t let you access the dashboard. That means you’ll need to switch themes using the database. To do this, connect to the database using phpMyAdmin<\/a> (or whichever tool your host uses) from the hosting control panel. Once you’re in, select the WordPress database and find the wp_options<\/em> (it might have a different prefix) table in the menu to the right.<\/p>\n\n\n Open the table and click on Search<\/em><\/strong> in the navigation menu at the top of the screen. Type “template”<\/em> into the Value<\/em><\/strong> field that corresponds to the option_name<\/em> column and click on Go<\/em><\/strong>.<\/p>\n\n\n This will return a single entry from the wp_options<\/em> table. That entry tells WordPress which theme to use; the theme is twentytwenty<\/em> in our example.<\/p>\n\n\n Double-click on the name of the theme under option_value<\/em> and you can change it to something else. This needs to be a theme that’s installed on the website or you’ll run into further errors.<\/p>\n\n\n\n Some safe bets for most sites are default theme options, such as twentytwentythree<\/em> or twentytwentytwo<\/em>. When you’re done, check your website to see if the error persists.<\/p>\n\n\n Every file has a set of “permissions” or rules that govern who can read, write (edit), and execute it. In UNIX-based systems, these permissions correspond to numeric values. The values change depending on which users hold certain permissions.<\/p>\n\n\n\n Here’s a full tutorial on how file permissions work<\/a>. For now, you should know that there are optimal permission settings for WordPress files. If someone tinkers with them, the CMS might fail to execute critical files and it won’t work (hence the WordPress white screen of death).<\/p>\n\n\n\n The optimal file permission settings in WordPress are as follows:<\/p>\n\n\n\n These permission levels allow WordPress to function properly while still securing files and directories from users who shouldn’t be able to access them.<\/p>\n\n\n\n The easiest way to change file permission settings in WordPress is via FTP. Connect to the website and access the root<\/em> directory, which is usually called public<\/em> or public_html<\/em>. Inside, you can right-click on any file or folder and select the File Permissions<\/em><\/strong> option.<\/p>\n\n\n That option opens a window including a field where you can set the numeric value for the permission settings you want.<\/p>\n\n\n Before you start changing permission settings for every file and directory, check to see if they don’t already have the correct values. Start by checking critical files such as wp-config.php<\/em> and .htaccess<\/em> and move on from there. If a file or directory has incorrect permission levels, go ahead and fix them.<\/p>\n\n\n When you update WordPress, it automatically goes into “maintenance” mode. If someone happens to try and access the site during the update, they’ll see a message that says, “Briefly unavailable for scheduled maintenance. Check back in a minute.”<\/em><\/p>\n\n\n\n In practice, WordPress updates tend to be so fast that most users won’t run into that maintenance screen. After the update, WordPress will automatically delete the temporary .maintenance<\/em> file in the site’s root<\/em> directory.<\/p>\n\n\n\n Sometimes WordPress will run into an error and be unable to delete the file, which can lead to the white screen of death appearing on parts of the site.<\/p>\n\n\n\n To fix this, connect to your site via FTP and navigate to the root<\/em> directory. Open the directory and look for the .maintenance<\/em> file in the top level (near .htaccess<\/em>):<\/p>\n\n\n If you see the file, go ahead and delete it. This won’t affect your site in any way except it’ll kick WordPress out of maintenance mode and hopefully fix the white screen of death.<\/p>\n\n\n A lot of WordPress errors occur because some web hosts assign low PHP memory limits to websites. If your website hits that memory limit, it won’t function properly and you may run into the WordPress white screen of death.<\/p>\n\n\n\n This may not be an issue depending on which web host you use. Most reputable WordPress web hosts set high memory limits, so you’ll never run into errors due to a lack of PHP memory.<\/p>\n\n\n\n Before you start tinkering with your site’s settings, go to the dashboard and jump to the Tools<\/strong> \u2192 Site Health<\/strong> <\/em>tab.<\/p>\n\n\n\n Inside, click on Info<\/strong> \u2192 Server<\/strong><\/em>. This page displays information about your server’s configuration, including which version of PHP you’re using and its memory:<\/p>\n\n\n Anything above 128-256 MB is more than enough for most WordPress websites. If your memory limit is below those values, you’ll want to increase it<\/a> by contacting your host.<\/p>\n\n\n The WordPress white screen of death (who picked that name?) seems intimidating, but it’s fixable. The challenge lies in figuring out what’s causing the error on your site, and the only way to do that is by trying multiple troubleshooting methods.<\/p>\n<\/div>\n\n\n\n\n
What causes the WordPress white screen of death?<\/h2>\n\n\n\n
\n
.maintenance<\/code> file<\/li>\n\n\n\nHow to fix the WordPress white screen of death (eight ways)<\/h2>\n\n\n\n
1. Clear the browser and WordPress cache \ud83e\uddf9<\/h3>\n\n\n\n
![\"Deleting](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2023\/10\/delete-cache.png\")
<\/figure><\/div>\n\n\n2. Use the WordPress recovery mode to disable plugins and themes \ud83d\udd04<\/h3>\n\n\n\n
![\"WordPress](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2021\/09\/wordpress-recovery-mode-site-message.png\")
<\/figure><\/div>\n\n\n3. Restore a backup from your web host \ud83d\udcbe<\/h3>\n\n\n\n
4. Disable active plugins \ud83d\udd0c<\/h3>\n\n\n\n
![\"Deactivate](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2023\/10\/deactivate-plugin.png\")
<\/figure><\/div>\n\n\n![\"The](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2023\/10\/wp-content-plugins.png\")
<\/figure><\/div>\n\n\n![\"Plugin](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2023\/10\/plugins-folders.png\")
<\/figure><\/div>\n\n\n5. Switch to another WordPress theme \ud83c\udfa8<\/h3>\n\n\n\n
![\"Activating](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2023\/10\/activate-theme.png\")
<\/figure><\/div>\n\n\n![\"The](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2023\/10\/wp-options-table.png\")
<\/figure><\/div>\n\n\n![\"Searching](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2023\/10\/template-option-name.png\")
<\/figure><\/div>\n\n\n![\"The](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2023\/10\/template-value.png\")
<\/figure><\/div>\n\n\n6. Check your file permission settings \ud83d\udd30<\/h3>\n\n\n\n
\n
![\"Changing](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2023\/10\/file-permissions.png\")
<\/figure><\/div>\n\n\n![\"Setting](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2023\/10\/permission-settings.png\")
<\/figure><\/div>\n\n\n7. Check for a .maintenance<\/em> file \u231b<\/h3>\n\n\n\n
![\"Deleting](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2023\/10\/wordpress-maintenance.png\")
<\/figure><\/div>\n\n\n8. Increase the WordPress memory limit \ud83d\udea7<\/h3>\n\n\n\n
![\"Checking](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2023\/10\/php-memory-limit.png\")
<\/figure><\/div>\n\n\nConclusion \ud83e\uddd0<\/h2>\n\n\n\n