You hit your bookmark for /wp-admin, expecting the dashboard, and instead the screen goes blank. No error message, no login form, just white. If your wp-admin is showing a white screen right now, take a breath. The fix is almost always quick once you know which of the seven common causes is hitting you.
This guide walks through the exact 7 fixes I use, in the order I try them. Most readers solve the issue inside 10 minutes without touching any code. We will cover plugin conflicts, theme problems, PHP memory limits, debug logging, file permissions, and how to recover even if you cannot log in at all.
What causes the WordPress white screen on wp-admin
The white screen of death (WSOD) on wp-admin almost always points to a fatal PHP error that WordPress is hiding from view. WordPress stops loading, the page sends back nothing, and your browser shows a blank page. The trigger is usually one of these:
- A plugin update that broke compatibility with your PHP version or another plugin
- A theme function calling code that no longer exists
- The PHP memory limit being too low to load the dashboard
- A corrupt or partially uploaded core file from a failed update
- File permissions that block WordPress from reading or writing
- A conflicting cache layer (object cache, page cache, or CDN)
- A malware infection or hacked file in wp-includes or wp-content
The good news: each cause has a clean fix you can apply yourself. You only need cPanel or FTP access to your hosting account.
Fix 1: Increase the PHP memory limit
If your dashboard is partially loading then dying, memory is the prime suspect. WordPress ships with a low default and any heavy plugin (page builder, security suite, WooCommerce) can blow past it. Edit wp-config.php in your site root and add this line just above the comment that says “stop editing”:
define('WP_MEMORY_LIMIT', '256M');
define('WP_MAX_MEMORY_LIMIT', '512M');Save the file and reload wp-admin. If your host caps memory at the server level, you may need to also add php_value memory_limit 256M to your .htaccess, or open a ticket with your host. On Hostinger and most managed Indian hosts, 256M is the safe baseline for any non-trivial site.
Fix 2: Disable all plugins via FTP
This is the single fastest test. If a plugin is the culprit, you will know in 60 seconds.
- Open your hosting File Manager or FTP client
- Go to
/wp-content/ - Rename the
pluginsfolder toplugins-off - Try to load wp-admin in a fresh browser tab
If the dashboard loads now, a plugin was the problem. Rename the folder back to plugins, then go inside it and rename each plugin folder one at a time, reloading wp-admin between each rename. The plugin you renamed when the screen comes back working is the broken one. Delete it, find a replacement, or contact the developer.
Fix 3: Switch to a default theme
If plugins are not the cause, your theme is next. Inside /wp-content/themes/, rename your active theme folder. WordPress will fall back to the latest default theme like Twenty Twenty Five if it is present. If no default theme exists, install one through your host’s File Manager by uploading the theme zip.
Reload wp-admin. If it works, your theme has a fatal error. Reinstall the theme fresh from the developer’s site, or roll back to the previous version if you keep backups.
Fix 4: Turn on WP_DEBUG to see the real error
If the white screen is still there, you need to see what PHP is choking on. Open wp-config.php and replace any existing debug lines with:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors', 0);Reload wp-admin. WordPress will write errors to /wp-content/debug.log. Open that file and look at the most recent lines. You will usually see a fatal error pointing to a specific plugin file or line. That tells you exactly what to remove or fix. Once resolved, set WP_DEBUG back to false so logs do not pile up.
Fix 5: Clear every layer of cache
A surprising number of WSOD reports turn out to be a stale cache showing an old broken state. Clear in this order: browser cache (Ctrl+Shift+Del), any page cache plugin (LiteSpeed, WP Rocket, W3 Total Cache), your CDN (Cloudflare in particular), and finally your host’s server cache. On Hostinger, that is the LiteSpeed cache button inside hPanel. After each clear, reload wp-admin in incognito.
Fix 6: Check file and folder permissions
WordPress needs the right permissions to read its own files. Wrong permissions can make wp-admin blank. Use your File Manager to confirm:
- Folders: 755
- Files: 644
wp-config.php: 600 or 644
If you recently restored from backup or migrated hosts, permissions sometimes break. Most cPanel and Hostinger File Managers have a “Fix permissions” or “Change permissions” right-click option that handles this in one click.
Fix 7: Restore from backup as the last resort
If nothing else worked, your install has a deeper problem, possibly malware, a broken core update, or a corrupt database. Restore the most recent clean backup from your host. Hostinger, Bluehost, and SiteGround all keep daily backups for at least 7 days on shared plans. After restoring, immediately update everything, change every admin password, and run a malware scan with Wordfence or Sucuri.
If you do not have backups, this is your wake-up call to set them up. Read our complete WordPress backup guide next.
How to prevent WSOD from happening again
Three habits keep the white screen away for good. First, never update plugins one by one in production without a staging copy. Use a staging environment (Hostinger and Cloudways both offer this free) and test there first. Second, keep automatic daily backups on. Third, watch your PHP version. WordPress 6.x runs best on PHP 8.1 or 8.2. If your host is still on 7.4, plugins increasingly break in confusing ways.
FAQ
Why is wp-admin white but the front end works?
The front end uses a smaller subset of plugins and theme functions. wp-admin loads almost everything at once, so it hits memory ceilings or fatal errors first. Increase memory and check the debug log to find the real cause.
How do I disable plugins if I cannot log in?
Use FTP or your host’s File Manager. Rename /wp-content/plugins to plugins-off. WordPress automatically deactivates everything inside. Rename it back and re-enable plugins one by one to identify the bad one.
Will I lose data if I rename the plugins folder?
No. Renaming only deactivates the plugins. Settings stored in the database remain. When you rename the folder back, you can reactivate each plugin and your settings return.
Can a Cloudflare setting cause a WordPress white screen?
Yes. An aggressive Cloudflare cache or Rocket Loader can serve stale broken JavaScript that blanks out the dashboard. Pause Cloudflare for 5 minutes from the dashboard to test. If wp-admin starts loading, you have your answer.
Is WSOD a sign that my site was hacked?
Sometimes, yes. Malware injections often break PHP execution. After fixing, scan with Wordfence, change all passwords, and check for unfamiliar admin users in the Users screen.
How long should the dashboard take to start loading after a fix?
A clean WordPress dashboard should respond in under 2 seconds. If yours takes 8 to 15 seconds even after fixing the white screen, you have a separate performance issue. Look at heavy plugins and unoptimised images.
Final word
The WordPress white screen of death on wp-admin feels scary the first time, but it is one of the most fixable WordPress errors. Work through these seven fixes in order and you will almost always find the cause inside 10 minutes. Bookmark this guide, set up daily backups today, and you will never lose more than a coffee break to a WSOD again.