wp-admin loads a completely blank page in WordPress
wp-admin shows an empty white page and no errorShort answer
A blank wp-admin is a PHP or database error that is hidden. Turn on debug logging first, because debug.log names the file that failed. The usual causes are a plugin, the active theme, an exhausted memory limit, or a failed update. Rename the plugin or theme folder over FTP if you cannot open the dashboard.
Fix it fast
1Find out which cause you have
Make WordPress write the hidden error to a file, reload wp-admin once, and read the log. Add the three define lines to wp-config.php above the line that says to stop editing, then read the log.
define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', false ); # reload wp-admin once, then read the log tail -n 30 wp-content/debug.log2Match what you see, then jump to its fix
- 1
The log names a file under wp-content/plugins/A plugin crashes the adminFix - 2
The log names a file under wp-content/themes/, often right after switching or updating a themeThe active theme has a faultFix - 3
Allowed memory size of ... bytes exhausted in debug.logPHP runs out of memoryFix - 4
The blank page started right after an update ranA failed automatic update left files half writtenFix
- 1
What does the error look like?
wp-admin shows an empty white page and no errorAllowed memory size of xxxxxx bytes exhaustedA failed automatic update ends in a blank page or a PHP error
Cause 1 of 4
A plugin crashes the admin
1Check
The log path shows which plugin failed. If you cannot reach the dashboard, rename the whole plugins folder over FTP or SSH, which deactivates every plugin.
mv wp-content/plugins wp-content/plugins_old2Fix
Rename it back, then rename single plugin folders one at a time until wp-admin loads. Update or remove the plugin that breaks it.
mv wp-content/plugins_old wp-content/plugins
mv wp-content/plugins/the-broken-plugin wp-content/plugins/the-broken-plugin.off3Verify
Open /wp-admin/ again and reactivate the remaining plugins one by one.
curl -I https://example.com/wp-admin/Confirmed by developer.wordpress.org
Cause 2 of 4
The active theme has a fault
1Check
The WordPress guide says theme problems are especially likely after activating a new theme. Rename the active theme's folder; WordPress then falls back to an installed default theme.
ls wp-content/themes/2Fix
Rename the active theme's folder over FTP so a default theme takes over, then repair or reinstall the theme.
mv wp-content/themes/my-theme wp-content/themes/my-theme.off3Verify
wp-admin loads with the default theme.
curl -I https://example.com/wp-admin/Confirmed by developer.wordpress.org
Cause 3 of 4
PHP runs out of memory
1Check
The log line gives the limit that was hit and the file that hit it. The wp-config guide names this error as the one WP_MEMORY_LIMIT is for.
grep -i "memory size" wp-content/debug.log2Fix
The WordPress guide lists two fixes: raise the memory limit in wp-config.php, or raise it in php.ini (ask the host if you cannot edit php.ini).
// wp-config.php, above the "stop editing" line
define( 'WP_MEMORY_LIMIT', '96M' );
// optional: a separate limit for the admin area
define( 'WP_MAX_MEMORY_LIMIT', '128M' );3Verify
Reload wp-admin and check that the memory error is gone from the log.
tail -n 5 wp-content/debug.logConfirmed by developer.wordpress.org
Cause 4 of 4
A failed automatic update left files half written
1Check
The guide says a failed auto-update can show a white screen, caused by a connection problem or wrong file permissions during the upgrade. Check that the web server user can write to the WordPress files.
ls -la | head -202Fix
Update by hand, following the WordPress Manual Update steps, after checking file permissions.
# download the current release from wordpress.org, then replace wp-admin and wp-includes
# and the loose files in the root; leave wp-content and wp-config.php alone3Verify
wp-admin opens, and Dashboard > Updates shows the expected version.
curl -I https://example.com/wp-admin/Confirmed by developer.wordpress.org
How do I stop it coming back?
- Keep WP_DEBUG_LOG on in staging so a failure leaves a log line.
- Update plugins on a staging copy first, then on the live site.
- Keep one default theme installed so a theme fault has a fallback.
- Take a backup before each core update.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Back end
WP_DEBUG is set to true but WordPress still shows no errors
No wp-content/debug.log file appears
WP_DEBUG only switches debug mode on.
4 causes, each with a fixBack end
Android gets HTML instead of JSON from a PHP API
org.json.JSONException: Value <br of type java.lang.String cannot be converted to JSONObject
The response body is not JSON.
2 causes, each with a fixBack end
Apache returns 403 when a URL contains %3F
a request like /page%3Fname=test is refused while /page?name=test works
Recent Apache httpd blocks a rewrite when the request contains an encoded question mark (%3F) and the rewritten target has a literal ?.
2 causes, each with a fixBack end
Apache returns 500 with Premature end of script headers
500 Internal Server Error
Apache ran your script, but the script printed no valid HTTP header before its output.
3 causes, each with a fixBack end
Apache returns 503 or 504 because PHP-FPM did not answer in time
Error dispatching request
Apache sent the request to PHP-FPM and gave up waiting.
3 causes, each with a fixBack end
AWS SDK for PHP cannot get credentials from the instance profile metadata server
Error retrieving credentials from the instance profile metadata server.
The SDK tries the EC2 instance metadata service when it has no valid credentials from anywhere earlier in its chain.
4 causes, each with a fix