BLOG

Introduction – why the white screen feels so scary

The famous White Screen of Death in WordPress is one of the most frustrating errors a site owner can encounter. From the visitor perspective there is only an empty white page, no error message, no warning and no content. In reality the posts, pages and configuration usually still exist in the database and in the file system, but the PHP execution hits a fatal error and stops producing output.

If you start changing things on the server without a plan, you can easily make the situation worse. Randomly deleting plugins, editing files or modifying the database without a backup can lead to permanent data loss. This guide focuses on a safe workflow: backup first, diagnostics second, only then come the corrective steps.

Step 1 – verify that it is not a local issue

Before touching anything on the hosting side, make sure that the problem is not limited to your own computer or browser.

• Open the site in a different browser, for example try Firefox instead of Chrome.
• Test the site on another device such as a phone or tablet.
• Switch off wifi and try loading the site over mobile data.
• Use private or incognito mode so that the browser cache does not influence the result.

If the site shows a blank white page on several devices and networks, the root cause is almost certainly on the server or inside the WordPress application, not on your local machine.

Step 2 – check whether the WordPress admin area is accessible

The next question is whether only the public part of the site is affected, or the admin dashboard as well. Try to open:

https://yourdomain.com/wp-admin

• If the admin area loads and you can log in, then the issue is usually caused by a plugin or by the active theme.
• If the admin area is also white or shows a critical error, then a deeper problem is likely, for example a broken core file, database errors or a PHP version conflict.

Step 3 – create a full backup in cPanel before doing anything else

Even if the error feels urgent, the first technical step should always be a full backup. Without it, any failed experiment can cause irreversible damage. Log in to cPanel and look for the Backup or Backup Wizard menu.

• Select the full account backup option if your hosting provider offers it.
• Start the backup and wait until the archive file is created.
• Download the backup to your own computer and store it in a clearly named folder.
• If possible, copy the file to cloud storage and to an external drive as well.

Step 4 – backup files via FTP using FileZilla

In addition to the cPanel backup, it is a good idea to download a copy of the site files via FTP. FileZilla is a popular free and open source FTP client that works on Windows, macOS and Linux.

• Start FileZilla and enter the host name, username, password and port.
• Connect to the server and browse to the main web root, usually public html or www.
• Select the entire WordPress directory and download it to a folder on your computer.

This local copy makes it easier to compare or restore files later if you need to.

Step 5 – export the database via phpMyAdmin

Most of the important WordPress data is stored in the database. Posts, pages, menus, user accounts and many plugin settings live there. In cPanel you will usually find a phpMyAdmin icon that opens a database management interface.

• Select the WordPress database from the list on the left.
• Click on the Export tab.
• Choose the quick export mode and SQL format.
• Download the resulting .sql file and store it together with your file backups.

Step 6 – inspect error logs and look for fatal errors

Once you have fresh backups, you can start investigating the root cause. In many hosting environments cPanel offers an Error log or Errors section. There you can see recent web server and PHP errors.

• Look for lines that contain the phrase Fatal error or Parse error.
• Note which file and line number they refer to.
• Check whether the path includes wp content plugins or wp content themes.

If multiple error lines point to the same plugin file or theme function, that component is a strong candidate for causing the white screen.

Step 7 – temporarily disable suspicious plugins via FTP

If the admin area is not available, you can disable plugins directly in the file system. Connect via FileZilla and open the wp content plugins directory.

• Find the folder of the plugin that you suspect.
• Rename the folder instead of deleting it, for example from contact form 7 to contact form 7 disabled.

After renaming the folder, WordPress treats the plugin as missing and deactivates it automatically. Reload the site. If the white screen disappears, you have identified the problematic plugin.

Step 8 – switch to a default WordPress theme

If disabling plugins does not help, the next suspect is the active theme. In the wp content themes directory you can temporarily rename the current theme folder. WordPress will then try to fall back to a default theme, such as Twenty Twenty Four, if it is available on the server.

If the site becomes visible with the default theme, it means that the custom theme contains broken code that needs to be reviewed and fixed by a developer.

Step 9 – review PHP version and memory settings

Another common source of white screen issues is a mismatch between the PHP version and the code used by plugins or themes. Most hosting providers offer a PHP selector in cPanel.

• Check which PHP version is currently active.
• If the problem started soon after a PHP upgrade, try switching temporarily to an older version that was known to work.
• Review the memory limit setting and increase it if possible.

A too low memory limit can cause out of memory errors when heavy page builders or large plugins run.

Step 10 – when to hand the case over to a professional

After you have created backups, inspected error logs, disabled plugins, tested themes and checked PHP settings, you have already done a lot. If the white screen still persists, it is perfectly reasonable to call in a professional who works with WordPress and servers every day.

Thanks to your preparation, that person will not start from zero. Instead, they will have:

• recent backups of both files and database,
• log excerpts that show where errors occur,
• a list of plugins and themes that have already been tested,
• information about the PHP environment and hosting setup.

This combination of careful groundwork and expert knowledge is what usually brings a stubborn white screen back to life with minimal downtime.

Official references and downloads

• Debugging in WordPress: https://wordpress.org/support/article/debugging-in-wordpress/
• FAQ Troubleshooting: https://wordpress.org/support/article/faq-troubleshooting/
• FileZilla FTP client (free): https://filezilla-project.org/
• phpMyAdmin official site: https://www.phpmyadmin.net/
• PHP manual: https://www.php.net/manual/en/