What Is the White Screen Error?
If you open your WordPress site or admin panel and are met with a completely blank white page without any error message, you are facing the issue known as the "White Screen of Death" (WSOD). Because it gives you no information at all, it is one of the most frustrating errors at first glance; however, its cause almost always comes down to one of a few known sources and can be resolved with a systematic approach.
The Most Common Causes
The white screen usually stems from one of the following: a plugin conflict (the most frequent cause), a theme-related error, the PHP memory limit being exhausted, or code incompatibility that appears after a plugin/theme update. An important clue: sometimes only part of the site (for example, just the admin panel or a single page) goes white; this helps you narrow down the problem.
Solution 1: Enable Debug Mode
To see the real error behind the blank page, first enable debugging. Open the wp-config.php file via FTP and find the WP_DEBUG line (add it if it is missing):
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);When you refresh the page, the source of the problem (which plugin/file, which line) appears on the screen or in the wp-content/debug.log file. This is half of the solution. Once you have fixed the problem, set these lines back to false.
Solution 2: Disable All Plugins
The most frequent cause of the white screen is plugins. If you cannot access the panel, you can disable plugins via FTP:
- Open the wp-content folder via FTP.
- Temporarily rename the plugins folder to plugins-old.
- Refresh your site.
If the site loads, the problem is a plugin. Now rename the folder back to plugins, then rename the plugins one by one to find which one is causing the issue. Once you find the culprit plugin, update it, delete it, or install an alternative.
Solution 3: Switch to the Default Theme
If the plugins are fine, the theme may be next. Go to the wp-content/themes folder via FTP and rename your active theme's folder. WordPress automatically falls back to a default theme (for example, Twenty Twenty-Four). If the site loads, the problem is in your theme; update the theme or contact its developer.
Solution 4: Increase the PHP Memory Limit
The site may show a white screen when it exceeds the allocated memory. You can increase the memory limit by adding this line to the wp-config.php file:
define('WP_MEMORY_LIMIT', '256M');If this does not work, you may need to raise the memory_limit value from the PHP settings in your hosting panel, or ask your hosting provider to do it.
Solution 5: Clear the Cache
If the white screen persists even though the problem has been fixed, clear the cache of your browser and of any caching plugin you may have. Sometimes the old, broken version of the now-fixed page continues to be served from the cache.
Solution 6: Undo the Last Change
The white screen often appears as "it was working yesterday, it's not working today." In this case, the fastest diagnostic method is to remember what you last changed. Did you install a new plugin? Did you update a theme? Did you add a piece of code? The white screen is almost always the result of a recent change. That is why the most practical way to fix the error is to undo the last change: deactivate the plugin you just installed, revert the updated theme to its previous version, or remove the code you added. If you take regular backups, restoring the backup from before the problematic change also delivers results within seconds.
Solution 7: Fix functions.php Errors
A common cause of the white screen in WordPress is faulty code snippets added to the theme's functions.php file. A small syntax error (a missing parenthesis or semicolon) made while pasting a snippet you found on the internet into this file can crash the entire site. If you cannot access the panel, open the wp-content/themes/yourtheme/functions.php file via FTP and delete the code you most recently added. When you enable WP_DEBUG, the error message usually gives you the exact line number of the problematic line, which makes the fix easier. Always making such edits through a child theme also prevents your code from being lost during main theme updates.
Tip for Narrowing Down the Problem
The most practical way to quickly locate the error is to observe where the white screen appears. If both the site's front end and the admin panel (wp-admin) are white, the problem is most likely a plugin affecting the entire site or the PHP memory limit. If only the front end is white but the panel opens, the culprit is usually the active theme. If only a single page is white, a shortcode, page builder element, or content component specific to that page is faulty. By answering this "where is it white?" question, you can head straight for the most likely source instead of eliminating solutions one by one, saving yourself time.
Frequently Asked Questions (FAQ)
I can't access the panel, how do I disable plugins?
Go to the wp-content folder via FTP and temporarily rename the plugins folder to something like plugins-old. This disables all plugins at once. If the site loads, the problem is a plugin; by renaming the folder back to plugins you can then test the plugins one by one.
Why does the white screen not show any error message?
By default, WordPress does not show error messages to visitors. By setting WP_DEBUG to true in the wp-config.php file, you can see the hidden error on the screen or in the wp-content/debug.log file. This is the fastest way to find the source of the problem.
Only one page is white, the rest works. Why?
The fact that the problem appears in only one section helps you narrow down the source. Usually a plugin, shortcode, or page builder element specific to that page is faulty. When you enable WP_DEBUG and refresh that page, the problematic component usually appears in the error log.
Conclusion
Although the white screen error is scary at first, it almost always comes down to one of a few known causes. First enable WP_DEBUG to see the real error, then eliminate plugins and the theme in turn to find the culprit. Increasing the memory limit and undoing your last change also work in most cases. When you proceed systematically, you can solve this problem in a few minutes.