How to fix the WordPress white screen from cPanel
The white screen appears when the site stops showing content and the browser does not display a clear error. On shared hosting, it usually happens after installing a plugin, changing a theme, updating PHP, or exhausting the assigned memory.
This guide helps you recover the site from the CMS dashboard and cPanel without root access or server commands.
Before you begin
- Have access to the CMS dashboard, if it still opens.
- Have access to cPanel to use File Manager, MultiPHP INI Editor, and, if needed, MultiPHP Manager.
- Make a copy of any files you edit, especially
wp-config.phpand folders insidewp-content. - Test changes in a private window to avoid browser cache.
Steps
- Open the site home page and the
/wp-admin/access page in a private window. - If the dashboard opens, deactivate the plugin or theme you changed right before the white screen appeared.
- If the dashboard does not open, log in to cPanel and open File Manager.
- Go to the site folder, usually
public_html, and openwp-content. - Temporarily rename the
pluginsfolder toplugins-disabledto deactivate all plugins. - Test the site. If it loads, rename the folder back to
pluginsand deactivate plugins one by one until you find the cause. - If the site is still white, go to
wp-content/themesand temporarily rename the active theme to force an available default theme. - If the problem continues, open MultiPHP INI Editor and check that
memory_limithas enough value for the CMS, for example256Mif your plan allows it. - Check
wp-config.phpand enable temporary diagnostics only while you investigate the failure. - When the site loads again, disable diagnostics, clear cache, and keep only the stable plugin or theme.
What to check in wp-config.php
| Check | What to look for | Safe action |
|---|---|---|
| Temporary diagnostics | The line define('WP_DEBUG', false); or no WP_DEBUG entry. | Temporarily change it to true to see the error and return it to false when finished. |
| Error log | The line define('WP_DEBUG_LOG', true);. | Enable it only if you need to save errors in wp-content/debug.log. |
| Public display | The line define('WP_DEBUG_DISPLAY', false);. | Keep it as false to avoid showing technical details to visitors. |
| CMS memory | The line define('WP_MEMORY_LIMIT', '256M');. | Use it if the error mentions exhausted memory and your plan allows that limit. |
Final verification
- The home page and
/wp-admin/load without staying blank. - The site keeps the correct theme and only the needed plugins active.
wp-config.phpno longer shows public diagnostics.- No new errors appear while browsing internal pages.
Common errors
- The white screen returns when activating a plugin → That plugin causes the failure or conflicts with another component → keep it deactivated and update or replace the plugin.
- The site changes to error 500 after editing files →
wp-config.phpor.htaccesshas damaged syntax → restore the copy and repeat the change carefully. - Only the dashboard stays blank → A security, cache, or page builder plugin may be failing in the dashboard → deactivate plugins from
wp-content/pluginsand test again.
When to ask for help
Open a ticket if the site stays blank after deactivating plugins and theme, if the error mentions server limits, or if you do not know which file changed. Include domain, approximate failure time, recent changes, and a screenshot or copy of the message that appears in debug.log.
Recommended reading
Still need help?
If this guide didn’t solve your issue, our team can help you via ticket.