Codiffy (codiffy.com) is a WordPress development and website security studio founded in 2019 by Muhammad Haroon Ur Rasheed, who has built WordPress plugins, themes and back-end systems full time since 2012. Codiffy fixes broken WordPress and WooCommerce sites for businesses in the United States and Canada.
The WordPress white screen of death is a blank white page with no error message. It means PHP stopped before it could show anything, usually because of a plugin or theme error, too little memory, a full disk or a mistake in an edited file. Clear any cache first, then find the real error in the log and fix the plugin, theme or setting it points to. Take a backup before you change anything.
Site blank right now? Call +1 (347) 474-0387. We respond within 15 minutes, 24/7, and fix it the same day. You get the price before we start.
What the white screen means
WordPress builds every page with PHP. When PHP hits a fatal error and error messages are switched off, which is right for a live site, the visitor gets nothing: a blank white page.
Since version 5.2 WordPress usually catches these errors and shows “There has been a critical error on this website” instead. You still see a plain white page when the error happens before WordPress can catch it, when the server itself runs out of memory or disk space, or when a cache keeps serving a blank copy of the page. The causes and the fixes are the same, so our guide to the critical error helps here too.
How to fix the white screen of death
- Clear the cache and check where the page is blank.
- Find the real error in the log.
- Raise the memory limit if PHP ran out.
- Switch off the plugin or theme at fault.
- Check the disk space on the server.
- Undo a recent edit to a site file.
- Restore a backup, as a last resort.
Step 1: Clear the cache and check where the page is blank
- Open the site in a private window and on your phone’s mobile data. If it works there, your browser cached the blank page.
- Clear your site’s cache: the caching plugin, your host’s cache and any CDN such as Cloudflare. A cache can keep serving a blank page long after the cause is fixed.
- Open yourdomain.com/wp-admin/. If the admin area works but the front of the site is blank, the theme is the likely cause. If both are blank, look at plugins, memory and disk space.
- Check your email for WordPress’s “Your Site is Experiencing a Technical Issue” message. If it arrived, it names the plugin or theme at fault and gives you a recovery mode link.
Step 2: Find the real error in the log
A blank page hides the error, so you need the log:
- Your hosting control panel’s error log, or a file named
error_login the site’s folders. - WordPress’s debug log. Add these lines to
wp-config.php, above “That’s all, stop editing”, then load the blank page again and openwp-content/debug.log:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Look for “PHP Fatal error” or “Allowed memory size”. The file path names the plugin or theme at fault. When you are done, remove the lines and delete debug.log, because anyone who finds it can read it.
Step 3: Raise the memory limit if PHP ran out
If the log says something like this:
Allowed memory size of 134217728 bytes exhausted
PHP ran out of memory. 134217728 bytes is a 128 MB limit, and this exact line is one our monitoring caught on a client site. Add this line to wp-config.php:
define( 'WP_MEMORY_LIMIT', '256M' );
If the server’s own PHP limit is lower, WordPress cannot go above it, so ask your host to raise memory_limit too. If the error comes back even with more memory, a plugin is using far too much and needs fixing or replacing.
Step 4: Switch off the plugin or theme at fault
If you can open the admin area, switch the plugin off from the Plugins screen. If you cannot:
- One plugin: in your hosting file manager or over SFTP, rename its folder in
wp-content/plugins/, for example toplugin-name-off. WordPress switches off a plugin whose folder it cannot find. - Not sure which: rename the whole
pluginsfolder, check the site, then rename it back and switch the plugins on one at a time until the page goes blank again. - The theme: rename the active theme’s folder in
wp-content/themes/. WordPress falls back to a default theme, if one is installed.
Then update, roll back or replace the plugin or theme before you switch it back on.
Step 5: Check the disk space on the server
When the disk is full, PHP cannot write its temporary files or session data, and pages crash or come out blank.
A real case: in August 2025 an online store we look after started crashing at checkout. The server had run out of disk space. Old staging copies of the site were taking up the space, and they also contained malware, so we deleted them. That freed the space and removed the malware in one step, and checkout worked again.
Check the disk usage in your hosting control panel. The usual space-eaters are old backups and staging copies, large log files, and cache folders that are never cleared.
Step 6: Undo a recent edit to a site file
A single typo in wp-config.php or in a theme’s functions.php, such as a missing semicolon or a stray space before <?php, can blank the whole site. If the white screen started right after someone edited a file, put back the previous version of that file from a backup or your host’s file history.
If WordPress core files were damaged, for example by an update that stopped halfway, upload fresh copies of the wp-admin and wp-includes folders from the same WordPress version. Leave wp-content and wp-config.php alone.
Step 7: Restore a backup, as a last resort
If nothing above finds the cause, restore the most recent backup from before the page went blank. Save a copy of the current site first, so recent orders, form entries and content changes are not lost.
How to stop it happening again
- Test updates on a staging copy before they reach the live site.
- Never edit theme or config files on the live site without a backup.
- Watch the disk space, and delete old backups and staging copies you no longer need.
- Use monitoring that alerts you to fatal errors and outages, so you hear before your customers do.
A WordPress maintenance plan covers all of this, with monitoring by Guardian Shield Lite, our own security plugin.
When to call a developer
Call for help if:
- The log is empty or you cannot reach it.
- The page is blank even with every plugin switched off and a default theme.
- The white screen keeps coming back.
- Your site is an online store and checkout is affected.
Codiffy responds within 15 minutes, 24/7, and fixes broken sites the same day. You get the price before we start. Call +1 (347) 474-0387 or email haroon@codiffy.com. Ecommerce troubleshooting and fixes
Frequently asked questions
Why is only the admin area blank?
Some plugins load code only in the admin area. When that code fails, visitors still see the site while wp-admin is blank or shows an error. Find the plugin in the log and switch it off by renaming its folder.
Why is only one page blank?
That page uses something the others do not: a page-builder element, a shortcode or a form. Check the log while you load that page, and look at the plugin behind the element.
Will I lose my content?
No. The white screen stops the page from being built; your pages, posts and orders stay in the database. Take a backup before you change anything all the same.
Can a hack cause a white screen?
Yes, sometimes. Badly written malware can break PHP and blank the site. If the log points to files you never installed, or the site also shows spam or redirects, read what to do if your website is hacked.
About the author
Muhammad Haroon Ur Rasheed founded Codiffy in 2019. He has been a full-time WordPress and back-end developer since 2012 and has fixed broken, slow and hacked WordPress and WooCommerce sites for businesses across the United States and Canada. Codiffy works from Rawalpindi, Pakistan, in US and Canadian business hours.

