Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting · Troubleshooting

How to Fix wp-admin Not Loading in WordPress

Short answer

A wp-admin that will not load is usually a plugin conflict, a PHP fatal error, or a memory limit hit only in the admin. Turn on WP_DEBUG_LOG in wp-config.php, read wp-content/debug.log, rename the plugins folder by SFTP to rule out plugins, then raise WP_MEMORY_LIMIT to 256M.

Key takeaways

  • A blank wp-admin usually means PHP hit a fatal error before it sent any output.
  • WP_DEBUG_LOG writes the real error to wp-content/debug.log.
  • Renaming wp-content/plugins switches every plugin off without the dashboard.
  • WordPress 5.2 added Recovery Mode, which emails the admin a login link after a fatal error.
  • PHP's memory_limit defaults to 128M, and the admin needs more than the front end.
  • A bad .htaccess rule in wp-admin can block the dashboard while the site works.

What does “wp-admin not loading” look like?

The login form accepts your password, then the dashboard shows a blank page, a spinner that never ends, or a 500 error.

What you seeMost likely causeFirst move
Blank white pagePHP fatal error or memory limitTurn on WP_DEBUG_LOG and read debug.log
Critical error screenFatal error caught by Recovery ModeOpen the recovery email link
Plain text, no stylingAdmin CSS blockedCheck the site address and exclude wp-admin from minifiers
Too many redirectsBad .htaccess rule or wrong site URLRename .htaccess and check the URLs
403 ForbiddenServer or security rule blocks wp-adminCheck .htaccess and the host firewall

A blank page means PHP stopped on a fatal error before it sent any output. The front end can still work, since the admin loads code the public site never runs.

Plain, unstyled text means the admin CSS never loaded, which points to mixed content or a minifier rather than a crash. That case has a different fix from a blank page.

Check whether wp-login.php loads while wp-admin does not. If the login form itself is blank, the fault is wider than the dashboard, and the same log will name it.

How do you find the real error?

Turn on WP_DEBUG_LOG in wp-config.php and read wp-content/debug.log after reloading wp-admin.

WordPress's Debugging in WordPress guide says WP_DEBUG_LOG writes errors to wp-content/debug.log, and WP_DEBUG must be true for it to work.

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

Keep WP_DEBUG_DISPLAY false on a live site. The same guide warns that showing errors on screen can expose file paths to visitors.

Put the lines above the comment that says stop editing. The Editing wp-config.php guide says WordPress does not read constants placed below that line.

The log names the file and line that failed. If it names a plugin, go to the plugin section; if it names the theme, go to the theme section.

If the log is empty, the error may sit in the server log instead. Ask your host for the PHP error log, or check the host panel for a log viewer.

How do you use Recovery Mode?

Open the email WordPress sent to the admin address and click its recovery-mode link to log in with the faulty code paused.

Recovery Mode arrived in WordPress 5.2. WordPress's Recovery Mode guide says it pauses the faulty plugin or theme for your admin session only, so visitors still see the error page.

If the email never arrives, check the spam folder first. A plugin that changes how WordPress sends mail may not load when the fatal error strikes early.

A critical error screen with no email needs the file-system route instead. See How to Fix “There Has Been a Critical Error on This Website” in WordPress.

How do you rule out a plugin conflict?

Rename the wp-content/plugins folder by SFTP to switch every plugin off, then reload wp-admin.

If the dashboard loads, rename the folder back and switch plugins on one at a time inside wp-admin. The one that breaks the dashboard again is the cause.

With WP-CLI, wp plugin deactivate --all does the same job without renaming folders. Switch plugins back on one at a time from the command line.

A plugin conflict is the most common cause of a dead dashboard, and the order matters. See How to Fix Plugin Conflicts in WordPress for the full isolation steps.

Keep a note of which plugin was active when the dashboard broke. An update to that plugin is the most likely trigger, and its changelog may name the fix.

How do you rule out the theme?

Switch to a default theme such as Twenty Twenty-Five and reload wp-admin.

Use WP-CLI or rename the active theme's folder by SFTP; WordPress falls back to a default theme when the active one is missing. If the dashboard loads, the theme holds the fault.

A bad theme update can break the whole site, not just the dashboard. See How to Fix the WordPress White Screen of Death in WordPress if the front end is blank too.

How do you fix a memory limit?

Raise WP_MEMORY_LIMIT to 256M in wp-config.php, above the stop-editing line.

WordPress asks PHP for 40M on a single site and 64M on multisite by default, while admin tasks get a higher ceiling of 256M. The Editing wp-config.php guide documents both constants.

PHP's own memory_limit defaults to 128M, and it is the hard ceiling WordPress cannot pass. The PHP manual says the limit caps how much memory one script may use, and setting it to -1 removes the cap.

If the host locks the PHP limit, raising the WordPress constants changes nothing. Ask the host to raise memory_limit, or move the heavy plugin off the site.

The memory error names the limit in the log, such as Allowed memory size of 134217728 bytes exhausted. That number is 128M in bytes, and it tells you the ceiling that was hit.

How do you check .htaccess and login rules?

Look for a stray .htaccess file inside wp-admin, or a password-protection rule left by a security plugin.

A .htaccess file applies its rules to its own folder and every folder below it. Apache's .htaccess tutorial says the file changes settings per directory without touching the main server config.

Apache ignores .htaccess files entirely unless AllowOverride is set for the directory. The same tutorial says the default value of AllowOverride is None.

Rename the wp-admin .htaccess file, then reload the dashboard. If it loads, the file held a bad rule; rebuild it from a clean copy.

A login loop that keeps sending you back to the login form is usually a redirect or cookie problem. See How to Fix ERR_TOO_MANY_REDIRECTS in WordPress.

A permissions message after login means your user role changed, not that the dashboard crashed. See How to Fix “Sorry, You Are Not Allowed to Access This Page” in WordPress.

Also check for a password prompt on wp-admin: a leftover .htpasswd rule from a security plugin asks for a second login. Remove that rule if the prompt never accepts your password.

How do you confirm the dashboard is fixed?

Reload wp-admin, open a few screens, and save a test post to prove writes work.

Turn WP_DEBUG and WP_DEBUG_LOG back to false when you finish. Leaving them on fills the log file and can expose errors on a live site.

Delete or shrink wp-content/debug.log after the fix. The file grows with every error, and an old log hides new ones.

Switch the plugins back on one at a time and reload wp-admin after each one. If the dashboard breaks again, the last plugin you switched on is the cause.

What mistakes should you avoid?

Do not reinstall WordPress first, and do not leave debug mode on after the fix.

  • Reinstalling core before reading the log: most dashboard failures reverse with one renamed folder.
  • Turning WP_DEBUG_DISPLAY on live: visitors see file paths and server details.
  • Raising the memory limit past what the host allows: the change silently fails.
  • Deleting the plugins folder instead of renaming it: renaming is reversible, deleting is not.
  • Editing wp-config.php below the stop-editing line: WordPress never reads those constants.

Frequently asked questions

Why does the front end work but wp-admin is blank?

The admin loads extra code the public site never runs: admin hooks, dashboard widgets, and update checks. A plugin or theme error that only fires in admin breaks wp-admin while visitors see nothing wrong.

Can I fix wp-admin without SFTP access?

Yes, if the Recovery Mode email arrives: its link logs you in with the faulty plugin paused. Without that email or file access, only your host can rename the plugin folder for you.

How much memory does wp-admin need?

WordPress asks PHP for 40M by default, with a 256M ceiling for admin tasks, but heavy builders and security plugins need more. Set WP_MEMORY_LIMIT to 256M and ask your host to raise the PHP limit if that fails.

Will switching themes delete my content?

No. Content lives in the database, and switching themes only changes the design. Widgets and menus may move, but posts, pages, and media stay in place.

What if wp-admin loads but is very slow?

Slow admin screens point to heavy dashboard widgets, slow update checks, or a plugin making slow background requests. Rule out the fatal-error causes first, then look at what loads on each admin screen.

Sources

  1. Debugging in WordPress WordPress Developer Resources
  2. Editing wp-config.php WordPress Developer Resources
  3. Recovery Mode WordPress.org
  4. Description of core php.ini directives PHP.net
  5. Apache HTTP Server Tutorial: .htaccess files Apache HTTP Server

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test