Categories: Wordpress Tutorials

How to Fix the WordPress White Screen of Death

The wordpress white screen of death usually means a PHP fatal error, plugin or theme conflict, memory limit, or incomplete update stopped WordPress before it could render the page. Follow these steps in order and you can usually identify the failing component from DirectAdmin File Manager, even when both the website and wp-admin are blank.

What causes the white screen

The blank page is a symptom, not a diagnosis. WordPress documentation lists plugin conflicts, theme problems, incompatible PHP versions, exhausted memory, database errors and damaged files among the common causes. A recent plugin, theme, PHP or WordPress update is a useful clue, but do not assume the newest change is the only possible cause.

The problem may affect the whole website, only wp-admin, one post, or one PHP-heavy action such as uploading an image. First test the home page and /wp-admin/ in a private browser window. Note exactly which URLs are blank and whether the issue started after an update.

What you need before starting

You need access to your hosting account’s DirectAdmin panel, its File Manager and, if possible, a recent WordPress backup. You do not need SSH for the steps below. If the dashboard still opens, keep a second tab open for it; if not, use File Manager for the recovery work.

Take a backup before editing wp-config.php, renaming folders or restoring anything. Use your hosting account’s self-service backup tools to keep a copy of the WordPress files and database. Also download a copy of wp-config.php before changing it, because a missing quote or semicolon can create a second error.

Step 1: Turn on safe WordPress debugging

Why this helps: the log often names the plugin, theme file or memory problem that caused the blank page.

  1. Open DirectAdmin and go to File Manager.
  2. Open the document root for the affected domain, usually the folder containing wp-admin, wp-content and wp-includes.
  3. Make a copy of wp-config.php, then edit the original.
  4. Find the line that says /* That’s all, stop editing! Happy blogging. */. Add the following lines immediately before it. If any of these constants already exist, edit their values instead of adding duplicates.

~~~php define( ‘WP_DEBUG’, true ); define( ‘WP_DEBUG_LOG’, true ); define( ‘WP_DEBUG_DISPLAY’, false ); @ini_set( ‘display_errors’, 0 ); ~~~

  1. Save the file and load the blank URL once. Then open wp-content/debug.log in File Manager.
  2. Read the newest entry at the bottom. Look for a PHP Fatal error, Allowed memory size exhausted, an unfamiliar plugin directory, or a theme file path.

Success looks like a new log entry that points to a component or error class. If the log does not appear, check that WP_DEBUG_LOG is inside wp-config.php, that you edited the correct WordPress installation, and that File Manager is showing hidden files where required.

The official WordPress debugging guide recommends logging errors while keeping them off the page. After you finish troubleshooting, change WP_DEBUG to false, remove the temporary log if it contains sensitive paths, and do not leave debugging enabled on the live site.

Step 2: Disable every plugin from File Manager

Why this helps: one incompatible plugin can stop WordPress before the login screen is generated, so the dashboard may be unavailable even though the files are intact.

  1. In the WordPress document root, open wp-content.
  2. Rename the folder plugins to plugins.disabled.
  3. Open the home page and /wp-admin/ in a private window.

Success means the site loads or the login screen returns. WordPress cannot find the original plugin directory, so it treats the plugins as inactive without deleting their files.

If the site is working, rename plugins.disabled back to plugins. In the dashboard, activate plugins one at a time and reload the affected page after each activation. The plugin that brings the blank screen back is the likely cause; leave it inactive while you update, replace or reconfigure it.

If renaming the folder makes no difference, keep its original name and continue. Do not delete the plugin folder during diagnosis because its settings and content may still be needed.

Step 3: Switch to a default theme

Why this helps: a PHP error in functions.php, a template, a page builder integration or a child theme can prevent WordPress from rendering any page.

If the dashboard works, go to Appearance > Themes and activate an installed WordPress default theme. If the dashboard is blank, open wp-content/themes in File Manager and identify the active theme folder from the debug log or the theme name you recently changed.

Rename that active theme folder, for example from my-theme to my-theme.disabled. WordPress can fall back only if another usable default theme is installed, so do not remove the last available theme. If no default theme is present, upload a clean copy of a current default theme from the official WordPress source before testing.

Success means the front end or dashboard returns with the default design. That confirms the failure is in the original theme or its custom code. Restore the original folder name after testing, then fix the theme on a staging copy or replace the damaged file with a clean version from its developer.

If a child theme is active, test its parent and child separately. Custom code in the child theme’s functions.php is a common reason for a blank page after a small edit.

Step 4: Raise the WordPress memory request carefully

Why this helps: an error such as Allowed memory size exhausted means the PHP request ran out of the memory available to it; raising a WordPress request can help when the hosting limit permits it.

Edit wp-config.php again and add these lines before the stop-editing comment. WordPress documents 128M as a practical front-end value and 256M as the usual administrative value, but the hosting account may cap the real PHP limit.

~~~php define( ‘WP_MEMORY_LIMIT’, ‘128M’ ); define( ‘WP_MAX_MEMORY_LIMIT’, ‘256M’ ); ~~~

If the constants already exist, change their values rather than creating a second copy. Save the file, reload the failing URL and check debug.log again.

Success means the memory error disappears and the page renders. If the same error remains, the server-level PHP memory_limit may be lower than the WordPress request. Do not keep increasing numbers blindly: deactivate the component named in the log and ask the host whether the account limit can be changed.

Memory is often a symptom of a plugin or theme doing too much work. Once the site is available, reduce the number of active plugins, update compatible components and test heavy tools such as page builders or importers separately. See the related guide on increasing the WordPress memory limit for the configuration details.

Step 5: Check the PHP version in DirectAdmin

Why this helps: WordPress may load correctly on one PHP version while an old plugin or theme fails on another.

Open DirectAdmin’s PHP version selector for the affected domain. Record the current version, then choose a PHP version supported by your current WordPress release and compatible with your active plugins and theme. Change one setting at a time and test both the website and /wp-admin/ after each change.

Success means the same URL loads without a new fatal error in the log. If changing PHP fixes the site, update or replace the component that is not compatible before making the version change permanent. If it makes the problem worse, return to the recorded version and use the debug log to identify the incompatible code.

Do not treat a PHP switch as a substitute for updating an abandoned plugin. WordPress’s PHP guidance explains why version changes can improve security and performance while still exposing old code to compatibility errors.

Step 6: Remove a stuck maintenance file and test rewrite rules

Why this helps: an interrupted update can leave WordPress in maintenance mode, while a damaged rewrite file can produce a blank or server error before the normal page loads.

In the WordPress document root, enable hidden files in File Manager. If a file named .maintenance is present and you are not currently running an update, rename it to .maintenance.old. Reload the site.

If the page is still blank, make a copy of .htaccess and rename the original to .htaccess.old. Test the site again. If it loads, sign in to WordPress, open Settings > Permalinks, and click Save Changes to let WordPress write fresh rewrite rules. Restore or remove the old copy only after you have verified the new file.

Success is a working front end after one of these files is isolated. If neither change helps, restore the original filename before moving on so you do not leave the site with incomplete configuration.

Step 7: Restore a known-good backup

Why this helps: if the error began after a failed update or a file edit and the cause is not clear, a matching files-and-database restore is safer than deleting WordPress folders at random.

Use DirectAdmin’s backup or restore tool and choose the most recent backup from before the white screen started. Restore the WordPress files and database from the same point in time when the tool allows separate selections. Do not restore only the files if the database was changed at the same time.

Success means the original page and /wp-admin/ return, and your latest posts, orders or form submissions are present as expected. Test the home page, one older post, the login screen and any important form before making new changes. If you do not have a usable backup, do not reinstall WordPress over the top until you have copied wp-content and exported the database; a reinstall can overwrite evidence or custom files.

For a site that is being moved after recovery, follow HostKarle’s guide to migrate a WordPress website manually. If you would rather start a clean installation, HostKarle WordPress hosting includes one-click WordPress setup and a PHP version selector through the DirectAdmin plans.

Verify the fix

Run this short check before calling the problem solved:

  1. Load the home page in a private browser window.
  2. Open /wp-admin/ and sign in.
  3. Visit a post, a page and the media library.
  4. Check that the active plugins and theme are the intended ones.
  5. Open wp-content/debug.log, record the useful error, then disable debugging and remove the temporary log.
  6. Make one small test change, such as saving a draft, and confirm it persists after a refresh.

If the site works only with all plugins disabled or a default theme active, the white screen is fixed temporarily, not permanently. Keep the failing component isolated and repair it before reactivating it on the live website.

Troubleshooting when the page is still blank

Only wp-admin is blank: use the plugin and theme isolation steps first. If the front end works, the error may be limited to an admin-only plugin, dashboard widget or memory-intensive task.

Only one post or page is blank: inspect the debug log after loading that exact URL. A template, shortcode or block supplied by one plugin may be failing only on that content.

The browser shows a critical error instead of white: treat it as the same troubleshooting path and check the recovery email sent by WordPress. Recovery Mode can give an administrator a temporary login that isolates the faulty plugin or theme; see the official Recovery Mode documentation.

The log points to the database: check the database credentials and database connection error separately. Do not delete or repair tables without a backup; compare the error with HostKarle’s guide to fixing a WordPress database connection error.

The log names wp-admin or wp-includes: copy wp-content, wp-config.php and your uploads first, then replace only the damaged core files with a clean copy of the same WordPress release. Avoid overwriting wp-content or wp-config.php while doing this.

FAQ

What is the WordPress white screen of death?

It is a blank page shown when WordPress stops before it can render normal output. PHP fatal errors, plugin or theme conflicts, memory limits, database problems and incomplete updates can all produce it.

How do I fix a WordPress blank page without access to wp-admin?

Open your hosting File Manager and rename wp-content/plugins to another name to disable every plugin. If that does not help, test the active theme, enable safe debug logging in wp-config.php, and read wp-content/debug.log.

Does increasing the WordPress memory limit fix a white screen?

It can fix a blank page caused by an exhausted PHP memory limit, but it will not repair a broken plugin or theme. Use the error log to confirm the cause, and remember that the hosting account may cap the actual PHP limit.

Why is my WordPress site blank after changing PHP versions?

An active plugin or theme may use code that is incompatible with the selected PHP version. Switch back to the recorded version if needed, read the debug log, and update or replace the component before testing a compatible version again.

Should I reinstall WordPress to fix the white screen?

Reinstalling is rarely the first step because it can remove useful evidence and will not fix a plugin, theme or database problem. Back up wp-content, wp-config.php and the database first; replace core files only when the log points to damaged core files.

Samrat Ghosh

Samrat Ghosh writes hands-on guides about web hosting, WordPress, domains and email for Indian small businesses, students and freelancers - the practical documentation he wishes had existed when he set up his first website.

Share
Published by
Samrat Ghosh

Recent Posts

Zoho Mail Alternatives for Indian Businesses (2026)

Compare zoho mail alternatives for Indian businesses by rupee cost, IMAP access and mailbox limits,…

3 hours ago

Best Wix Alternatives in India for Small Businesses

Compare Wix alternatives for Indian small businesses: see 3-year rupee costs, WordPress hosting, migration limits,…

14 hours ago

Titan Email Price in India: Cost per Mailbox Explained

Titan email price in India explained with mailbox costs, features, team totals and a comparison…

20 hours ago

HostKarle vs Bluehost India: Price, Renewal and Panel

HostKarle vs Bluehost compares Indian shared hosting prices, renewal bills, email, SSL, backups, panels and…

1 day ago

Hindi Blog Kaise Banaye: WordPress Step-by-Step Guide

Learn how to write blog in hindi with WordPress, Hindi typing tools, domain and hosting…

2 days ago

Google Workspace Alternatives in India for Small Teams

Compare Google Workspace alternatives in India by yearly rupee cost, email features and migration effort…

2 days ago

This website uses cookies.