White Screen in wp-admin? Fix the Admin-Only WSOD

If the front end of your WordPress site loads but /wp-admin is blank white, the problem is usually isolated to the admin side of WordPress, not the whole site. In most cases, the safest fix is to disable the conflicting plugin, switch to a default theme, clear caches, and check PHP limits before you touch anything more drastic.

Always back up first. An admin-only white screen is often recoverable without data loss, but the fastest way to turn a small problem into a bigger one is to start changing files or deleting plugins without a rollback plan.

What this symptom usually means

A white screen only in wp-admin is different from a full site white screen. Your public pages may still load because they are using cached output, a different template path, or a code path that is not hitting the broken admin-only feature.

Typical signs include:

• The homepage and posts load normally, but /wp-admin is blank.
• You may briefly see the login form, then a white page after sign-in.
• Only one admin screen fails, such as Plugins, Users, or a page builder settings panel.
• The issue started after an update, a new plugin, a theme change, or a host-side PHP change.

That pattern is useful. It usually means the site itself is not fully down, which narrows the problem to backend code, admin hooks, JavaScript in the dashboard, or server limits.

The most likely causes

When the front end still works, the most common causes are:

• A plugin conflict that only runs in admin.
• A theme function or builder extension loading in the dashboard.
• PHP memory exhaustion while WordPress builds the admin page.
• A fatal error that is hidden because error display is off.
• A broken mu-plugin or must-use integration from a host or security tool.
• Cached, stale, or minified admin assets causing the dashboard to fail to render.
• File permission or disk-space problems that affect writes in wp-admin.
• A recent update that changed how a plugin loads in the backend.

If you want a deeper look at broader update-related breakage, see WordPress Site Broke After an Update? Here's What Happened and How to Fix It. For a general recovery path when the dashboard is inaccessible, Locked Out of WordPress Admin: Why It Happens and How to Fix It is also useful.

Fix it safely, from easiest to most likely

1) Confirm it is really admin-only

Open the site in an incognito window and test a few public URLs. Then try loading /wp-admin/ directly and note exactly what happens: pure white page, partial load, spinning browser tab, or a redirect back to login.

That detail matters. A blank page is often a PHP fatal or memory issue. A redirect loop points somewhere else. A partial dashboard that never finishes loading can mean JavaScript, REST API, or plugin asset trouble.

2) Check for a hidden fatal error

WordPress often suppresses errors in production, so the white screen can hide the real cause. If you can access files safely, check the site’s error log through your host panel or server tools. Look for fatal errors around the time you tried to load wp-admin.

If you control configuration, you can temporarily enable logging rather than display. In wp-config.php, make sure errors are logged and not shown to visitors. Then reload wp-admin and inspect the log. If you are not comfortable editing configuration files, stop here and use a backup or a pro.

For step-by-step log reading on related failures, the process in There Has Been a Critical Error on This Website: What It Means and How to Fix It is a good companion guide.

3) Deactivate plugins without relying on wp-admin

Because the dashboard is broken, you may need to disable plugins from FTP, SFTP, file manager, or SSH. The safest approach is to rename the plugins folder to something like plugins-old. That deactivates all plugins at once.

Then test /wp-admin again. If it loads, one of the plugins is the cause. Rename the folder back, then move plugins out one by one or in small groups until the white screen returns. The last plugin re-enabled is the one to inspect first.

If the site uses must-use plugins, also check wp-content/mu-plugins. Those are loaded automatically and can break admin without appearing in the normal plugin list.

4) Switch to a default theme

If plugins are not the issue, the active theme or a child theme can be breaking admin output. Rename the active theme folder so WordPress falls back to a default theme such as Twenty Twenty-Four, if installed.

This is especially important if the theme adds custom admin features, page builder integrations, or dashboard widgets. A front-end theme can look fine while still crashing the backend when WordPress loads theme functions for admin requests.

5) Increase PHP memory safely

Admin pages need memory too, especially on sites with many plugins or large media libraries. A front-end page may still load if it is cached, while wp-admin fails when PHP runs out of memory during a heavier request.

Ask your host what the current PHP memory limit is. If the site is allowed to use more, raise the WordPress memory limit carefully in wp-config.php or through the host panel. Do not assume a larger limit will fix everything, though; it can hide a broken plugin and only delay the next crash.

6) Clear cache and check for broken admin assets

Some caching layers should never touch wp-admin, but badly configured performance plugins, server cache, or a CDN can still interfere with backend assets. Clear every cache you control: plugin cache, host cache, object cache, and CDN cache.

Then hard refresh the browser and test again. If the white screen is actually a dashboard that never finishes loading, open browser dev tools and check the Console and Network tabs for failed JavaScript, blocked requests, or 403/500 responses. If you see that pattern, Stop Guessing: Which CSS and JS Are Actually Blocking WordPress? may help you trace the asset problem.

7) Check for disk space and permissions problems

Low disk space can cause strange backend failures, especially when WordPress tries to write transient data, sessions, updates, or cache files. Likewise, incorrect file permissions can stop admin components from loading correctly.

Verify that the server still has room for logs, temporary files, and normal WordPress operations. Then confirm the core folders have standard permissions set by your host or deployment process. If permissions are wrong, fix them carefully and avoid making everything world-writable just to get past the error.

8) Review recent changes outside WordPress

Host-side PHP upgrades, security rules, WAF changes, or a new object cache can break admin only. A plugin update is not always the culprit. Sometimes the timing points to the host because the public site is cached while wp-admin is using the newer PHP behavior live.

If the problem started right after a host change, ask for the exact date of the change, any PHP error logs, and whether they see blocked requests to admin endpoints. That information can save hours of blind trial and error.

What not to do

Do not keep clicking around the white screen hoping it will self-heal. Do not delete plugins randomly from the WordPress admin if you can still partially access it. Do not edit core WordPress files. And do not disable security tools permanently just to test a theory unless you can restore them immediately.

Most importantly, do not keep making changes without a backup. If one fix works, you want a clean way to reverse it if another issue appears next.

How to prevent this from happening again

The best prevention is boring, repeatable maintenance: test updates on a staging copy when possible, keep backups current, and avoid stacking too many plugins that all touch the admin area. It also helps to keep PHP versions and limits aligned with the site’s actual load instead of leaving them at whatever default your host happened to set years ago.

For a practical baseline, read What a Good WordPress Maintenance Routine Looks Like. If admin issues keep returning after updates, that is usually a sign the site needs a better update workflow, not more guesswork.

When to call a professional

Call a professional if you cannot access logs, if the white screen comes back after every plugin test, if the site is mission-critical, or if you are not sure whether the issue is plugin, theme, server, or cache related. At that point, the safest move is to stop experimenting and let someone isolate the root cause with a backup-first process.

Mend handles this kind of admin-only failure every day. Our senior engineers can usually triage the problem the same day, and a free diagnosis will tell you whether it is a Quick Fix or something bigger before any work starts. If you want help without handing over passwords, you can connect securely through Mend Connect, or start with free diagnosis if you just need the cause identified first.

If the site is business-critical and you need a fast rescue, Emergency Rescue is the right path. Every paid fix comes with a plain-English report of what broke and what changed, plus a fixed-or-your-money-back guarantee.

In short: a white screen only in wp-admin is usually a contained backend problem, not a full site collapse. Work from the safest causes first—logs, plugins, theme, memory, and cache—and you can usually get the dashboard back without touching content.