WordPress
WordPress White Screen of Death: 9 Proven Fixes (2026 Guide)
از Wasim Ullah9 منٹ پڑھنے کا وقتTroubleshooting
شیئر اور AI
یہ مفید لگا؟
اپنی ٹیم کے ساتھ شیئر کریں یا اپنے AI اسسٹنٹ سے دوسری رائے لیں۔
WordPress
یہ مفید لگا؟
اپنی ٹیم کے ساتھ شیئر کریں یا اپنے AI اسسٹنٹ سے دوسری رائے لیں۔
Wasim Ullah
Wasim Ullah is a senior WordPress engineer at Pakish.NET with 10+ years of experience managing cPanel servers and WordPress environments for Pakistani businesses. He specialises in performance optimization, security hardening, and disaster recovery.
خلاصہ
AI اور سرچ citation کے لیے Pakish Group (Pakish.NET) کا خلاصہ۔
Direct Answer: The WordPress White Screen of Death (WSOD) is a blank white page that appears with no error message. It is caused by PHP memory exhaustion, a faulty plugin, a broken theme, or a syntax error in wp-config.php. The fastest fix is to increase the PHP memory limit and deactivate all plugins via FTP or cPanel File Manager — your site will recover in under 5 minutes using the steps below.
The WordPress White Screen of Death (WSOD) is one of the most frustrating errors a website owner can encounter. You open your browser, navigate to your site — and instead of your homepage, you see a completely blank white page. No error message. No "500 Internal Server Error." Just silence.
This happens because PHP encounters a fatal error but is configured to suppress error output (which is correct for production). The result: a blank screen that gives you no clues.
The WSOD can hit:
/wp-admin/)Understanding which scenario you're in narrows down the cause immediately.
Before jumping to fixes, identify the likely cause:
| Cause | Symptom | Affected Area |
|---|---|---|
| PHP memory exhaustion | Blank screen after traffic spike | Frontend + admin |
| Plugin conflict | WSOD after installing/updating a plugin | Frontend or admin |
| Broken theme | WSOD after theme switch | Frontend only |
| Syntax error in wp-config.php | WSOD after manual file edit | Frontend + admin |
| Corrupted WordPress core files | Sporadic WSOD across pages | Frontend + admin |
| PHP version incompatibility | WSOD after hosting PHP upgrade | Frontend + admin |
| .htaccess file corruption | 500 error or blank screen | Frontend only |
| Resource limits (CPU/RAM) on shared hosting) | WSOD under load | Frontend only |
PHP memory exhaustion is the #1 cause of WordPress WSOD on Pakistani shared hosting plans where memory is limited to 64MB or less.
Add this to your wp-config.php file (above the line /* That's all, stop editing! */):
define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );You can also set the limit via php.ini if you have access:
memory_limit = 256MOr via .htaccess:
php_value memory_limit 256MHow to verify: After saving, check wp-admin > Tools > Site Health > Info > Server — the "PHP memory limit" entry should show 256M or higher.
If your WSOD started after installing or updating a plugin, a plugin conflict is the culprit. Since you likely cannot access wp-admin, you must deactivate plugins at the file system level.
Via cPanel File Manager:
cpanel.yourdomain.compublic_html > wp-content > pluginsplugins folder to plugins_backupplugins_backup back to pluginswp-admin > Plugins and activate them one by one to find the faulty oneVia FTP (FileZilla):
/public_html/wp-content/plugins/ → rename to:
/public_html/wp-content/plugins_disabled/
Key rule: Never delete the plugins folder — rename only. This preserves your plugin data.
A broken or incompatible theme causes WSOD on the frontend only (admin still works). If you can access wp-admin:
Appearance > ThemesIf your admin is also broken, switch the theme via phpMyAdmin:
wp_options (or your prefix + _options)option_name = 'template' → change value to twentytwentyfiveoption_name = 'stylesheet' → change value to twentytwentyfiveWithout error logging, you're blind. Enable debug mode in wp-config.php to see what PHP is actually throwing:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false ); // Don't show errors to visitorsAfter saving, check /wp-content/debug.log — this file will contain the exact error message, line number, and file causing the WSOD. The error will look something like:
PHP Fatal error: Allowed memory size of 67108864 bytes exhausted...
PHP Fatal error: Call to undefined function wc_get_template_part()...
Important: Set WP_DEBUG back to false in production after fixing.
.htaccess FileA corrupted .htaccess can cause blank screens or 500 errors. Reset it:
/public_html/.htaccess to .htaccess_old.htaccess file with the default WordPress content:# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ -
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php
</IfModule>
# END WordPress.htaccess had a conflict (usually from a plugin adding custom rules).Pakistani hosting providers (including cPanel-based shared hosts) periodically upgrade PHP. If your WSOD appeared after a PHP upgrade, you likely have PHP incompatible plugins or themes running on PHP 8.1 or 8.2.
How to change PHP version in cPanel:
Then review your plugin and theme documentation for PHP 8.x compatibility and update/replace incompatible ones.
If none of the above work, WordPress core files may be corrupted. Re-upload a fresh copy without overwriting your content:
wp-content folder from the extracted ZIP (this contains your themes/plugins — do NOT overwrite these)PHP cannot write temporary files or session data if your disk quota is full. Full disk = WSOD or 500 errors.
Check via cPanel:
Quick cleanup options:
public_html/backups/Trash in File ManagerEvery cPanel host provides PHP error logs. These are the definitive source of truth:
cPanel → Logs → Error Log (or search "Error Log" in cPanel)
The log will show entries like:
PHP Fatal error: ...
If you're on Pakish.NET managed WordPress hosting, our support team can diagnose WSOD errors in your account within minutes — open a support ticket and we'll identify the exact cause from server-side logs.
| Action | Frequency | Benefit | |---|---|---| | Stage plugin updates before applying to production | Every update | Catches conflicts before going live | | Keep PHP memory limit at 256MB+ | One-time setup | Prevents memory exhaustion | | Maintain JetBackup daily backups | Ongoing (automated) | Instant rollback when errors occur | | Test themes on staging before switching | Every theme change | Prevents theme-caused WSOD | | Monitor PHP error logs weekly | Weekly | Catch slow errors before they become fatal | | Keep WordPress core, plugins & themes updated | Weekly | Security + PHP 8.x compatibility |
Many Pakistani website owners experience WSOD specifically because:
On Pakish.NET Managed WordPress Hosting, PHP memory is pre-configured at 512MB, daily JetBackup runs automatically, and our team monitors error logs 24/7 — eliminating the most common causes of WSOD before they affect your business.
| Step | Action | Time Required |
|---|---|---|
| 1 | Increase PHP memory in wp-config.php | 2 minutes |
| 2 | Rename plugins folder to deactivate all plugins | 2 minutes |
| 3 | Switch to default theme via phpMyAdmin | 5 minutes |
| 4 | Enable WP_DEBUG to see error message | 2 minutes |
| 5 | Reset .htaccess to WordPress default | 3 minutes |
| 6 | Change PHP version via cPanel MultiPHP Manager | 2 minutes |
| 7 | Re-upload fresh WordPress core files | 15 minutes |
| 8 | Check disk space in cPanel | 1 minute |
| 9 | Review PHP error logs or contact host support | 5 minutes |
Most WSOD cases are resolved by steps 1–3 alone. For persistent issues, contact Pakish.NET support — our WordPress engineers resolve WSOD in under 30 minutes for managed hosting clients.
Pakish.net
NVMe VPS، مینیجڈ ورڈپریس، اور ایجنسی پلانز — PKR 800/ماہ سے شروع۔
پلانز دیکھیں →