WordPress white screen: causes and what to do first

If your WordPress website shows a completely blank white page, with no error message, no logo and no content, something has stopped the page from being built before anything could be displayed.

This is often called the "white screen of death". The name sounds dramatic, but the problem is usually less serious than it looks. In most cases the content of the website is still there: WordPress simply stopped while preparing the page.

The difficulty is that a white screen gives no clue about the cause. It can affect the whole website, only the dashboard or only a few pages, and it can come from a plugin, the theme, a server limit or even a cache that saved a blank page.

This guide explains what a white screen usually means, the most common causes, what you can check safely and when to ask for help.

What does a white screen mean?

When someone opens a page, WordPress loads its own code, the active plugins and the theme, reads the content from the database and assembles the page.

If one of these steps fails badly enough, PHP, the programming language WordPress is written in, stops. If the error is not shown on screen, which is normal and safer on a live website, the visitor receives an empty page.

Recent versions of WordPress usually catch these failures and show the message "There has been a critical error on this website" instead. If you see that message, our guide on the WordPress critical error is the better starting point. A white screen can still appear in several situations, for example when the error happens in a way WordPress cannot catch, when the protection has been turned off, or when the blank page comes from a cache rather than from WordPress itself.

What are the most common causes?

A PHP fatal error

This is the classic cause. A piece of code fails and PHP stops. Typical reasons include:

a plugin update that is not compatible with your WordPress or PHP version
a conflict between two plugins
a theme update or an edit to the theme files
custom code added to the theme or a snippets plugin
a change of PHP version by you or by the hosting provider
an update that was interrupted, leaving files incomplete

The error is hidden from visitors, but it is usually recorded in a log. Finding that log entry is often the fastest way to the cause.

The website ran out of memory

PHP gives each request a maximum amount of memory. If a plugin, an import, a page builder or a large page needs more, the request stops and may leave a blank page.

Raising the memory limit can help, but it is not always the real solution. It is worth understanding why the website suddenly needs more memory than before.

A plugin or the theme

Even without a visible error message, plugins and themes are the most frequent source of a white screen, especially right after an update, an installation or an activation.

A cache serving a blank page

Caching saves a copy of each page to make the website faster. If the website failed for a moment while a page was being saved, the cache may keep showing that blank copy even after the real problem has gone.

Caches can exist in several places:

a caching plugin in WordPress
the hosting provider's server cache
a CDN or proxy such as Cloudflare
the visitor's own browser

Does the white screen affect the whole site?

Where the white screen appears tells you a lot.

The whole website is blank

Both public pages and the dashboard are white. This points to something loaded everywhere: a plugin, the theme, a memory limit or a server problem.

Only the dashboard is blank

The public website works, but /wp-admin/ shows a white page. This often points to:

a plugin that runs mainly in the dashboard
a memory limit reached in the admin area, which usually does more work than public pages
a problem appearing only for logged-in users

Only some pages are blank

The homepage works, but certain pages, posts or products are white. This often points to:

a specific page template in the theme
a shortcode, block or page builder element used only on those pages
a plugin that runs only on certain page types, such as the shop or the cart
a very large page that exceeds the memory limit

Only you see it, or only visitors see it

If you see a white page but a colleague does not, or the other way round, a cache is a likely factor. Try opening the page in a private window, on another device or on mobile data instead of your office network.

What should you check first?

Think about what changed

Before touching anything, ask:

Was a plugin, theme or WordPress updated?
Was a new plugin installed or activated?
Did someone edit the theme or add custom code?
Did the hosting provider change the PHP version?
Was the website migrated or restored?
Was a caching plugin installed or reconfigured?

A white screen that appears right after a specific change is usually connected to that change.

Check the WordPress administrator email

When WordPress detects a fatal error, it may email the administrator address with details and a link to recovery mode. Check the inbox and the spam folder of the address used for the website. Treat the recovery link as sensitive and do not share it publicly.

Try to clear the cache

If you have access to the dashboard or to your caching or CDN service, clearing the cache is a safe and reversible step. Then reload the page in a private window. If the page reappears, the cache was showing an old blank copy, but it is still worth checking why the page failed in the first place.

What can you safely try?

Contact whoever made the last change

If an agency, developer or colleague recently updated or edited the website, ask them first. They may be able to reverse their change quickly.

Ask your hosting provider for the error log

Hosting providers can usually check PHP error logs and tell you whether:

a fatal error was recorded at the time the problem started
the memory limit was reached
the PHP version changed recently
the server had other problems

The error message often names the plugin or theme involved.

Deactivate the suspected plugin from the dashboard

If the dashboard still works and you strongly suspect one plugin, for example because the white screen started right after updating it, deactivate only that plugin from Plugins → Installed Plugins and reload the affected page.

Remember that plugins may handle payments, forms, security or translations. A website that loads again is not necessarily fully working, so test the important functions afterwards.

What should you avoid doing?

Avoid:

updating or deleting all plugins at once
deleting plugin or theme folders
reinstalling WordPress at random
restoring an old backup without checking what newer data it would overwrite
changing the PHP version several times in a row
leaving error messages displayed publicly on the live website
copying code from forums into wp-config.php or the theme without understanding it

Change one thing at a time and write down what you did. If something you tried did not help, undo it before trying the next step.

When should you ask for technical support?

Ask for help when:

the whole website is blank and you cannot access the dashboard
the website sells products, takes bookings or manages subscriptions
the white screen returns after a temporary fix
you cannot find any clear error in the logs
custom code or a heavily customized theme is involved
the problem appeared after a migration or a PHP change
you are not comfortable editing files or using SSH

You do not need to diagnose the problem yourself before asking. Describe what you see, where it appears and what changed.

What information should you collect?

Useful details include:

the website URL and the addresses of affected pages
whether the dashboard works
when the white screen started
what changed just before
any email received from WordPress
the name of the hosting provider
whether a cache plugin or a CDN is used
whether a recent backup is available

Do not send passwords by ordinary email. D4Hub can explain which access is needed and how to share it safely.

How D4Hub can help

The goal is to find the real cause, not only to make the page appear again.

Depending on the situation, D4Hub can help with:

finding and reading the error behind the white screen
identifying the plugin, theme or custom code involved
checking compatibility between WordPress, plugins and PHP
investigating memory problems and why they started
clearing and reviewing cache configuration on the website, server and CDN
restoring damaged or incomplete files
evaluating whether a backup restore is appropriate
testing checkout, forms, login and other key functions afterwards

You can ask for support at any stage, from the first blank page to a fix that only partly worked.

Open a support ticket

For hands-on users: finding the cause of a white screen

These checks are for people comfortable with SFTP or SSH, wp-config.php and WP-CLI.

Before making changes, back up the website files and the database, or at least make a copy of any file you are going to edit. Never publish logs or wp-config.php contents, as they may include sensitive information.

Check what the server actually returns

From a terminal, check the HTTP status code of the page:

curl -I https://example.com/

A 500 status usually means a server or PHP error. A 200 status with an empty page can point to a cache, a theme template that outputs nothing or an error that was handled silently.

Enable the WordPress debug log

Open wp-config.php and add these lines before the line that says "That's all, stop editing":

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

If any of these constants is already defined in the file, change the existing line instead of adding a second one.

With these settings, errors are written to a file instead of being shown to visitors. Reload the blank page once, then open:

wp-content/debug.log

Look at the most recent lines. A fatal error usually names a file path, such as wp-content/plugins/plugin-name/... or wp-content/themes/theme-name/..., which tells you which component failed. A message like "Allowed memory size exhausted" points to a memory limit.

When you have the information, set WP_DEBUG back to false and delete debug.log. The file sits in a public folder, so it should not be left on a live website.

Disable all plugins by renaming the folder

If you cannot reach the dashboard and do not know which plugin is involved:

Connect through SFTP or the hosting file manager.
Open wp-content/.
Rename plugins to something like plugins-disabled.
Reload the website.

If the website works again, a plugin is involved. Rename the folder back to plugins. WordPress may then show the plugins as deactivated, so reactivate them one at a time, checking the website after each one, until the white screen returns.

Keep in mind that while plugins are off, features such as payments, forms and security are off too.

Disable a single plugin

If the log or the timing points to one plugin, rename only its folder inside wp-content/plugins/, for example from plugin-name to plugin-name-disabled. Do not delete it.

With WP-CLI you can do the same:

wp plugin deactivate plugin-name --skip-plugins --skip-themes

Use WP-CLI without loading plugins and themes

If a plugin or theme causes a fatal error, WP-CLI commands may fail too. The --skip-plugins and --skip-themes options let WP-CLI run without loading them:

wp plugin list --skip-plugins --skip-themes
wp theme list --skip-plugins --skip-themes

This lets you see which plugins and themes are active, and their versions, even while the website is blank.

Switch to a default theme

If the problem seems to be in the theme, check which themes are installed and activate a default WordPress theme, if one is present:

wp theme list --skip-plugins --skip-themes
wp theme activate twentytwentyfive --skip-plugins --skip-themes

Use the name of a default theme that actually appears in your list. Switching theme changes how the website looks and may affect menus and widgets, so treat it as a diagnostic step and switch back once you know more.

Check the memory limit

If the log mentions memory, ask your hosting provider what the PHP memory limit is. WordPress also has its own setting, which you can raise in wp-config.php:

define( 'WP_MEMORY_LIMIT', '256M' );

WordPress cannot go above the limit set by the server. If the website needs much more memory than before, find out what changed rather than raising the limit repeatedly.

D4Hub can help you read the log, identify the component involved and plan a safe fix.

FAQFrequently asked questions

Usually not. A white screen means the page could not be built, not that the content was deleted. Once the cause is fixed, the website normally returns as it was.

Both are often caused by a PHP error. Recent WordPress versions usually show a critical error message, while a white screen means nothing was shown at all, sometimes because the error could not be caught or because a cache kept a blank page.

The dashboard loads code and does work that public pages do not. A plugin that runs only in the admin area, or a memory limit reached there, can break the dashboard while the website still works for visitors.

The visible symptom is gone, but the cache only kept a blank page because something failed at some point. Check the error logs or ask for help to make sure the problem will not return.

It may help if the log shows a memory error, but it treats the symptom. If the website suddenly needs more memory, a plugin, an import or a change may be the real cause.

Not as the first step. A restore may overwrite newer orders, form entries or content. It is usually better to find the cause first, then decide whether a restore is needed.

Yes. Tell us what you tried and what happened after each step. That information helps reconstruct the problem and choose the next safe action.

Why is my WordPress site showing a white screen?