WordPress White Screen: Diagnostic method without apparent access

A WordPress white screen is especially disconcerting because it sometimes gives no clues: no message, no error code, no access to the admin. This symptom does not point to a single cause. A PHP error, a plugin, the active theme, a memory limit, or even an issue occurring before WordPress can all produce a blank page.

The right approach is therefore to work from the outside in, changing one thing at a time and noting the result. Before modifying any files, make sure you have a usable backup. If you don’t, first consult how to create a reliable automatic WordPress backup.

1. Confirm that it’s actually a WordPress-related white screen

Start by opening several addresses: the homepage, a specific page or post, /wp-login.php and /wp-admin/. Note which ones remain blank and which respond normally.

Also try a private window and from another network if possible. This check won’t fix anything, but it helps rule out a local cache, a browser extension, or a response cached by an intermediary service.

If you have access to the hosting file manager, temporarily create a small HTML file independent of WordPress in the same public directory, then open it in the browser. If it displays while the WordPress URLs remain blank, the server can deliver static files: the diagnosis should focus on WordPress and PHP execution. If it doesn’t display either, check the domain, the web server, the application firewall, or the hosting before modifying WordPress.

2. Enable a debug log without showing errors to visitors

When the admin is inaccessible, the file wp-config.php becomes the most useful entry point. It is normally located at the root of the WordPress installation and contains, among other things, the configuration of the database. The official documentation states that it is loaded on every non-cache-served display and that it can contain debug and memory constants.

First make a local copy of this file. Then add or replace the following constants before the line that contains /* That's all, stop editing! */ :

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

With this configuration, WordPress logs errors, warnings, and notices to wp-content/debug.log, without revealing them in the public HTML. The operation of WP_DEBUG_LOG and WP_DEBUG_DISPLAY is documented in the official guide Debugging in WordPress.

Reload the single white URL, then open wp-content/debug.log with the file manager or FTP. First look for the last lines: they often point to a specific file, plugin, theme, or PHP function. Do not publish this file and do not leave debugging enabled longer than necessary, as the log may contain file paths and other technical information.

If no file debug.log appears, check the PHP logs provided by your host. Their location and name vary by environment. The server PHP log may, however, contain a fatal error that occurred before WordPress could write its own log.

3. Disable all plugins via FTP or file manager

A plugin conflict is a common cause of the white screen. You don’t need to access the admin to check this.

1. Open the folder wp-content.
2. Rename plugins to plugins.hold.
3. Reload the page that was white.

This prevents WordPress from loading regular plugins while preserving their files and settings. The official WordPress troubleshooting FAQ also describes this disable-by-renaming when the admin menus are inaccessible.

If the site returns, immediately restore the name plugins, then activate plugins one at a time from the admin, testing the same page between each activation. The first plugin that recreates the white screen should remain disabled until you check its compatibility, updates, and error log.

If renaming the folder changes nothing, don’t delete plugins blindly: proceed with the active theme.

4. Test the theme without modifying its files

A white screen that appears after activating or updating a theme often points to the theme, its child theme, or a PHP customization. First check that at least one WordPress theme default is installed in wp-content/themes.

Next, rename only the folder of the currently active theme, for example by adding .hold to its name. WordPress will then attempt to fall back to an available default theme. The documentation on common errors specifically recommends this method when the admin area is inaccessible and a theme is suspected.

If the site becomes visible again, restore the folder name to preserve the files, but do not immediately reactivate the problematic theme. Inspect the debug.log, recent changes in a child theme, and customizations added in functions.php. A child theme and its parent both load their functions.php; file; duplicated or incompatible code can therefore cause a PHP error. To avoid creating a similar incident during a future intervention, also see how to update WordPress without breaking your site.

5. Check a PHP memory limit without masking the cause

A memory error can interrupt processing before WordPress outputs a full page. Look in the logs for an entry like Allowed memory size exhausted. Do not increase memory simply because of a white screen: first confirm the clue in the log.

If the error is indeed related to memory, you can temporarily request a higher limit in wp-config.php :

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

This constant asks WordPress to increase the PHP memory available to the site, but only if the hosting configuration allows it. The guide Editing wp-config.php also notes that increasing memory can hide the real problem, especially when a function or plugin is unusually resource-hungry. If the limit does not change or the error returns, pass the exact message to the host rather than trying multiple values.

White screen, 500 error, or critical error: do not confuse the symptoms

A white screen is a visual result: the browser receives an empty or nearly empty page. It can come from PHP or database errors, as WordPress documentation on common errors. reminds. By contrast, a 500 error is an explicit HTTP status sent by the server; it calls for checks more focused on server configuration and logs. In that case, consult common causes of a 500 WordPress error.

One critical WordPress error usually displays a message stating that a technical error has occurred. When such a message appears, instead follow the procedure outlined in Critical WordPress error: what to do before you panic.

Once the cause is isolated and fixed, deactivate WP_DEBUG, remove or archive the debug log according to your maintenance policy, then test the homepage, a few pieces of content, the login form, and the admin area. This final step confirms that the fix actually restores the site without leaving debug information accessible.