Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →A blank WordPress page is a symptom, not a diagnosis: possible causes include a fatal PHP error, a plugin or theme conflict, incompatible PHP, a memory limit, a database error, or damaged WordPress files. Start with Recovery Mode if it is available. Otherwise, use the access you still have—wp-admin, your host’s file manager or FTP, or diagnostic logs—to isolate the problem. Back up before changing files, and avoid showing error details to site visitors.
Before you troubleshoot: choose the safest path
First note whether the blank page affects the whole site or only one page, and whether you can still sign in to wp-admin. Then check whether WordPress sent a Recovery Mode email. These clues guide the next step; none identifies the cause on its own.
As an Amazon Associate I earn from qualifying purchases.
- Recovery Mode email or notice: follow the component WordPress identifies.
- Dashboard access: isolate plugins from wp-admin, then test the theme if needed.
- No dashboard access: use Recovery Mode or your host’s file tools only if you can safely reverse the change.
- Evidence of a PHP, database, core-file, or server issue: inspect a protected error log or ask your host to help interpret it.
Before file changes, make a backup you can restore. Learn WordPress includes backups in its troubleshooting guidance: Troubleshooting Basics.
1. Look for a WordPress Recovery Mode email
For certain fatal PHP errors during a regular page load, WordPress can enter Recovery Mode and email the site administrator a special login link. Check the administrator inbox, spam folder, and any filtering rules. The message may identify the plugin or theme associated with the error.
If no email arrives, that does not rule out a fatal error. WordPress notes that server email configuration or filtering can prevent delivery. See the official Recovery Mode documentation for how the feature works and its limits.
2. Use the Recovery Mode notice to address the named component
Recovery Mode can pause a faulty plugin or theme for your administrator session, allowing you to sign in and investigate. Read the notice, then deactivate or repair the named component. If you recently edited code, undo or correct that change rather than making unrelated changes.
After addressing the issue, exit Recovery Mode and check the site again. A component being named is a useful lead, not a reason to assume every blank page has the same cause.
3. If wp-admin works, isolate plugins one at a time
A plugin conflict is one possible cause. If you can access the dashboard, deactivate plugins, then reactivate them individually, checking the affected page after each activation. If the blank screen returns after a particular plugin is enabled, that gives you a specific lead to investigate; it does not establish that plugins are generally the cause.
WordPress describes plugin isolation as a troubleshooting method in its guide to FAQ Troubleshooting.
4. If wp-admin is unavailable, temporarily disable plugins through file access
Use your hosting account’s file manager or FTP to find the WordPress plugins directory. WordPress documents temporarily renaming that directory, or a suspected plugin’s folder, as a way to test whether plugins are involved. This is a diagnostic change, not a repair: restore the original folder name after the check, then identify and reactivate plugins deliberately.
Rank #3
Changing plugin status through phpMyAdmin is another documented option, but it involves editing database values. If you are unfamiliar with the database or unsure how to reverse a change, ask your host for help instead.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →5. Test the active theme
If the problem began after a theme change, test whether the active theme is involved. Switch to an available default theme through wp-admin if you can. If the dashboard is inaccessible, WordPress documents renaming the active theme folder through FTP as a diagnostic route. Make sure an appropriate default theme is installed before relying on this test.
Changing themes can alter the site’s appearance and behavior, so treat the switch as temporary and record the original theme and folder name. WordPress Learn explains systematic plugin and theme checks in Troubleshooting Basics.
6. Enable logging to identify the error
If component isolation does not reveal the cause, WordPress debug logging may help identify the error and the file involved. In wp-config.php, the relevant settings include WP_DEBUG and WP_DEBUG_LOG; the WordPress configuration handbook explains how to configure them: Debugging in wp-config.php.
Use logging rather than displaying diagnostic errors on a public page. Error details can expose sensitive information, and depending on the site’s setup, a log file may itself be publicly accessible. Protect the log, avoid sharing it publicly, and remove or disable temporary debugging settings when finished.
7. Check PHP compatibility or memory only when clues point there
WordPress lists incompatible PHP and reaching the available memory limit among possible causes of a white screen. A recent PHP-version change or an error log naming a memory limit can help direct this investigation; without such evidence, changing settings at random can add another variable.
There is no single memory value established as the right fix for every site. Some hosts do not allow memory changes through WordPress, so check your hosting controls or ask the provider to review the limit and PHP compatibility. The wp-config.php handbook describes host-dependent configuration limits.
8. Repair core files or involve the host when evidence points beyond plugins and themes
A blank screen can also be associated with database errors or corrupted WordPress files. If the log points to those layers, address the specific error rather than repeating plugin and theme changes. Back up before replacing or upgrading files: WordPress cautions that file replacement can overwrite local modifications.
Contact your hosting provider when you lack file access, the issue appears to involve server configuration or the database, or you cannot safely interpret or reverse a change. WordPress’s Recovery Mode guidance also points site owners toward their host when they need help outside the tools available to them.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsWhat the troubleshooting result tells you
A restored page after a controlled plugin or theme change is a useful diagnostic clue. A log naming PHP, database, or core-file errors points to a different layer. WordPress documentation describes these as possible causes but does not provide percentages showing how often each one is responsible, or a fix that works for every site.
Keep a record of each change and its result. That makes it easier to undo a diagnostic step, avoid repeating failed checks, and give your host concrete information if the problem requires server-level support.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
