A completely white screen in WordPress, also known as the ‘blank screen of death’, is usually caused by a critical PHP error that isn’t made visible. The most common causes are insufficient PHP memory, a conflicting plugin, a corrupted theme, or an outdated PHP version. By enabling debug mode and checking plugins, theme, and settings step by step, you’ll usually find the cause within minutes.
What causes the white screen
WordPress shows a blank screen when a PHP error occurs that normally stays hidden because error display is off by default. The main causes are:
- PHP memory: a plugin or theme requests more memory than is allocated.
- Plugin conflicts: two plugins use the same function or clash with each other.
- Theme issues: a corrupted file or an outdated template function.
- PHP version incompatibility: code that doesn’t work on an older or too new PHP version.
- Timeouts: a script that runs longer than the configured execution time.
Step-by-step solution
Enable debug mode
Open wp-config.php via FTP or the file manager and add before ‘That’s all, stop editing!’: define('WP_DEBUG', true); define('WP_DEBUG_LOG', true); define('WP_DEBUG_DISPLAY', false); Error messages will now appear in /wp-content/debug.log.
Increase PHP memory
Add define('WP_MEMORY_LIMIT', '256M'); to wp-config.php. In Plesk, also adjust the memory_limit under ‘PHP Settings’ to 256MB or higher.
Disable all plugins
Rename the /wp-content/plugins folder via FTP to, for example, /wp-content/plugins-old. If the site works again, rename the plugin folders back one by one until you find the culprit plugin.
Check the PHP version
Use a recent, supported PHP version. You can view and change the active version in Plesk under ‘PHP Versions’.
Switch themes
If plugins aren’t the cause, the theme may be corrupted. Via phpMyAdmin in Plesk, use a query to change the ‘template’ and ‘stylesheet’ values in the wp_options table to a default theme.
Advanced debugging
If the screen stays blank, try these extra steps:
- Increase execution time: add to .htaccess:
php_value max_execution_time 300 - Restore a backup: if you have a recent backup, restore it via Plesk’s backup function. This gets you back online quickly without further searching.
- Check php.ini: check in Plesk under ‘PHP Settings’ whether max_execution_time, upload_max_filesize, and post_max_size are sufficiently generous.
- Check file permissions: wp-content must be writable (755 for folders, 644 for files), otherwise debug.log won’t be created.
More background articles on management and technology can be found in the knowledge base.
Preventing the white screen
The best approach is prevention rather than cure. Keep plugins and themes up to date, use a supported PHP version, and set sufficient memory. Also ensure up-to-date backups, so you can quickly switch back to a working version if problems arise. If you’re still considering switching providers, a smooth switch to Tandata will help you get there without downtime, including reliable web hosting with daily backups.
Frequently Asked Questions
Can I prevent the white screen?
Yes, by making regular backups, keeping plugins up to date, using a supported PHP version, and setting sufficient memory.
The debug.log file stays empty or isn’t created
Check whether wp-content has write permissions (755 for folders, 644 for files) via FTP or the file manager in Plesk.
Does the site work in the admin panel but not on the front end?
This usually indicates a theme issue. Switch the theme via the database or enable WP_DEBUG to see the exact error.
How much memory does WordPress need?
WordPress recommends at least 64MB, but with many plugins, 256MB or more is advisable.
Conclusion
A white screen in WordPress is annoying but usually quick to resolve. Start with debug mode, increase memory, and rule out plugins and theme as the cause. With a stable hosting environment, you prevent this kind of error from taking your site down for a long time.