WordPress Only Shows a White Page

WordPress Only Shows a White Page: How to Fix the White Screen of Death

Are you visiting your WordPress website and seeing nothing but a blank, white page? No error message, no dashboard, no content? This issue is commonly known as the White Screen of Death, or WSoD for short.

As dramatic as the name sounds: In most cases, your content, images, and settings are not lost. Usually, the website is being blocked by a PHP error, a faulty plugin, a broken theme, a memory limit issue, or a conflict after an update. With a systematic troubleshooting approach, the root cause can generally be narrowed down quite well.

What is the White Screen of Death?

The White Screen of Death describes a situation where WordPress no longer generates any visible output. Instead of the website or the dashboard, only a blank page appears. Depending on the server configuration, a message like "There has been a critical error on your website" may appear alternatively.

Typical symptoms:

• Homepage remains white,
• Dashboard no longer loads,
• Only specific subpages remain white,
• Login works, but a blank page appears right after,
• The website is unavailable after a plugin update,
• The website is blank after switching themes,
• A PHP error appears instead of the website,
• The error occurs only in the backend or only in the frontend.

The cause can often be identified by whether only the public website, only the dashboard, or both are affected.

Common Causes

1. Check Your Email Inbox

WordPress has a built-in protection mode for fatal errors. When a critical error occurs, WordPress often sends an email to the website's administrator address.

This email may contain:

• A hint regarding the faulty plugin or theme,
• A technical error message,
• A link to recovery mode,
• Information about the affected file,
• Instructions for troubleshooting.

Be sure to check your spam folder as well. However, if your website's email delivery is not properly configured via SMTP, this message might be missing.

2. Use Recovery Mode

If WordPress sends you a link to recovery mode, you should use it first. Recovery mode often allows access to the dashboard even though a plugin or theme is causing an error.

In recovery mode, you can:

• Deactivate the faulty plugin,
• Check the active theme,
• Perform updates,
• Look more closely at critical errors,
• Make your website accessible again.

If no recovery link is available, proceed with the next steps.

3. Enable Debug Mode

WordPress often hides PHP errors for security reasons. As a result, you only see a blank page. With debug mode, you can make clues about the cause visible or have them written to a log file.

How to enable debug mode via cPanel:

1. Log in to your cPanel.
2. Open the File Manager.
3. Navigate to the root directory of your WordPress installation.
4. Open the file wp-config.php.
5. Look for the line define( 'WP_DEBUG', false );.
6. Carefully change it to define( 'WP_DEBUG', true );.
7. Save the file.
8. Reload the website.

If the line does not exist, you can insert it above the line that indicates editing stops and WordPress is loaded.

4. Better Debug Configuration: Log Errors Instead of Displaying Them

On live websites, it is better not to display errors publicly, but to have them written to a log file instead. To do this, you can use the following values in wp-config.php:

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

The errors are then frequently stored in the following file:

wp-content/debug.log

After your analysis, you should disable debugging again or at least ensure that the log file is not publicly accessible.

5. How to Read Error Messages Properly

Error messages can seem complicated at first glance. However, the message usually contains a vital clue: the path to the affected file.

Example:

Fatal error: Uncaught Error in /home/user/public_html/wp-content/plugins/beispiel-plugin/plugin.php on line 123

The path here points to:

wp-content/plugins/beispiel-plugin/

This means: This plugin is very likely causing the error. If the path points to wp-content/themes/, the cause is more likely related to the theme.

6. Deactivate All Plugins for Testing

If you don't have a specific clue, a plugin conflict is often the most likely cause. You can deactivate all plugins from the outside without using the dashboard.

How to do it via the cPanel File Manager:

1. Open the File Manager in cPanel.
2. Navigate to the wp-content folder.
3. Find the folder named plugins.
4. Rename it to plugins_old.
5. Visit your website again.

If the website loads again after this, one of the plugins was very likely the trigger.

Afterward, rename the folder back to plugins. In the WordPress dashboard, you can then activate the plugins one by one until the error occurs again.

7. Deactivate a Single Plugin

If the error message already points to a specific plugin, you don't need to deactivate all plugins.

1. Open wp-content/plugins/.
2. Find the folder of the affected plugin.
3. Rename it, for example from pluginname to pluginname_deactivated.
4. Check the website again.

If the website works again, check if an update is available or if you need an alternative to the plugin.

8. Check the Theme as the Cause

If the error occurs after a theme update, theme switch, or a change to functions.php, the theme is likely the cause.

Procedure:

1. Open the folder wp-content/themes/.
2. Find the folder of your active theme.
3. Rename the folder temporarily.
4. WordPress will then attempt to fall back to an available default theme.

For this to work, a current default theme such as Twenty Twenty-Four, Twenty Twenty-Five, or another default WordPress theme should be installed.

9. Revert Errors in functions.php

If you inserted code into functions.php shortly before the error occurred, remove that change first.

Typical causes:

• Missing semicolon,
• Double-defined function,
• Incorrect bracket,
• PHP code in the wrong place,
• Snippet from an unsafe source,
• Code intended for a different WordPress version.

Open the file via cPanel or FTP and remove the last code you inserted. Save the file and test the website again.

10. Check PHP Memory Limit

If WordPress, WooCommerce, a page builder, or a backup process requires more memory than allowed, a Fatal Error can occur. Often you will then see references to "Allowed memory size exhausted".

Example:

Fatal error: Allowed memory size of 134217728 bytes exhausted

Possible solutions:

• Check the PHP memory limit in cPanel,
• Switch to a current PHP version,
• Check resource-intensive plugins,
• Optimize page builder or WooCommerce configurations,
• Check hosting resources if problems recur.

Do not raise limits blindly without looking at the root cause. If a plugin uses an unusually large amount of memory, it should be examined more closely.

11. Check PHP Version

Changing the PHP version can trigger errors if an old plugin or theme is not compatible. Conversely, a very old PHP version can also cause problems.

Check in cPanel:

• Which PHP version is active?
• Is the version compatible with WordPress?
• Are plugins and themes compatible with this PHP version?
• Did the error occur after a PHP switch?

If the error started immediately after a PHP change, you can test by reverting to the previous version and then updating or replacing the affected plugins.

12. Regenerate .htaccess

A corrupted .htaccess file more commonly leads to redirect errors or 500 errors, but it can also block a website.

How to test carefully:

1. Open the File Manager.
2. Find the .htaccess file in the WordPress root directory.
3. Rename it, for example to .htaccess_old.
4. Visit the website again.
5. If you can access the dashboard again, go to Settings > Permalinks.
6. Click Save Changes without changing anything.

WordPress will then generate a new default .htaccess, provided the file permissions allow it.

13. Clear Cache

Sometimes the actual cause has already been fixed, but a cache continues to deliver a faulty or blank page.

Clear the:

• WordPress cache,
• Caching plugin,
• Server cache, if active,
• CDN cache, if used,
• Browser cache.

Additionally, test the website in a private browser window.

14. Check Error Logs in cPanel

Server logs are often the fastest way to find the root cause. They display PHP errors, file paths, and timestamps.

Look out for:

• Fatal error,
• Parse error,
• Allowed memory size exhausted,
• Call to undefined function,
• Cannot redeclare function,
• Paths to wp-content/plugins/,
• Paths to wp-content/themes/.

If you cannot interpret the message, copy it into a support ticket. The path to the affected file is usually especially important.

15. When Only the Dashboard is White

If the public website works but the dashboard remains white, the cause is often an admin-specific plugin, a dashboard widget, a security plugin, a page builder, or a memory issue in the backend.

Check especially:

• Security plugins,
• SEO plugins with dashboard widgets,
• Statistics plugins,
• WooCommerce Admin,
• Page builders,
• PHP Memory Limit,
• Browser console.

16. When Only Specific Pages are White

If only a specific page is affected, the cause may lie with a particular block, shortcode, template, or page builder element.

Possible causes:

• Broken shortcode,
• Corrupted page builder template,
• PHP code in a widget,
• Faulty embed,
• Gallery that is too large,
• WooCommerce product issue,
• Plugin function active only on this page.

In this case, you should first check the affected page, the template used, and the plugins deployed there.

17. What You Should Not Do

• Delete WordPress files randomly.
• Edit the database without a backup.
• Delete all plugins instead of renaming them.
• Leave debug mode publicly active permanently.
• Modify theme files directly without making a copy.
• Overwrite backups before the cause is known.
• Install unknown repair plugins from unsafe sources.
• Put a WooCommerce shop back live without testing.

18. After the Repair: Test the Website Fully

Once the website loads again, you shouldn't stop immediately. Check if all important functions are working correctly again.

Test the:

• Homepage,
• Contact page,
• Forms,
• Login,
• Dashboard,
• Menus,
• Mobile display,
• WooCommerce cart and checkout, if available,
• SEO plugin,
• Caching,
• Error logs for recurring messages.

If a plugin was the cause, check if an update, an alternative, or a configuration change is needed.

19. Preventing White Screen Issues

Many white screen problems can be avoided with good maintenance.

• Perform updates regularly,
• Create a backup before making updates,
• Use staging for important websites,
• Only use well-maintained plugins,
• Delete unneeded plugins and themes,
• Use a child theme for code customizations,
• Keep the PHP version up to date,
• Check for plugin conflicts after updates,
• Store backups externally,
• Check error logs if you notice anomalies.

Recommended Troubleshooting Order

1. Check Admin Email: Is there a recovery link?
2. Check Backup: Is there a recent backup?
3. Enable Debug Log: Make errors visible or log them.
4. Read Error Message: Identify the plugin or theme path.
5. Deactivate Plugins: Rename a single plugin or the entire plugin folder.
6. Check Theme: Deactivate the active theme for testing.
7. Check PHP Memory Limit: Especially for memory errors.
8. Check PHP Version: Rule out compatibility issues.
9. Check .htaccess: In case of server or redirect errors.
10. Clear Cache: Remove the old error display.
11. Test Website: Check the frontend, backend, forms, and shop.
12. Disable Debug Again: Do not display error messages publicly.

Frequently Asked Questions about the White Screen of Death

Is my content lost?

In most cases, no. The white screen usually just means that WordPress cannot load due to an error. Content and the database are often still fully intact.

What is the most common cause?

Plugin conflicts, faulty updates, theme issues, or PHP errors in custom code adjustments are very common.

Why don't I see an error message?

Error messages are often hidden for security reasons. Enable debug logging to get clues.

Can I deactivate plugins without accessing the dashboard?

Yes. Rename the wp-content/plugins folder or the folder of a single plugin via cPanel or FTP.

What do I do with WP_DEBUG after troubleshooting?

Set WP_DEBUG back to false or disable public debug output. Debugging should not be permanently visible on live websites.

Can a theme cause the white screen?

Yes. Especially after theme updates, changes to functions.php, or due to incompatible templates, a theme can be the root cause.

What does "Allowed memory size exhausted" mean?

WordPress or a plugin requires more PHP memory than is available. Check the memory limit, plugins, and server resources.

When should I contact support?

If you cannot interpret the error message, do not have access to files, a WooCommerce shop is affected, or the website does not work despite testing plugins/themes.