Learn the Facts

You open your site — or the admin panel — and there's nothing. No error, no message, just a blank white page. This is the "White Screen of Death" (WSOD), and it's one of the oldest, most common problems in the entire Joomla ecosystem. It's been happening since Joomla 1.5 and it still happens on Joomla 6, for the same underlying reason every time: something in the request chain is failing, and Joomla's own error handling never gets a chance to display anything about it.

The good news: it's almost always fixable in minutes once you know where to look. This guide walks through why it happens and the exact order to check things in.

What actually causes it

A blank white screen isn't one bug — it's what happens when PHP hits a fatal error before Joomla can render its own error page. The usual culprits, roughly in order of how often they're the real cause:

• An extension conflict, most often right after installing or updating one. A plugin, module, or component throws a fatal PHP error, and because it happens mid-render, nothing gets displayed at all.
• PHP memory limit too low. Joomla (especially with a heavier template or several active extensions) can exceed a restrictive memory_limit, which fails silently on many hosting configurations.
• PHP version incompatibility. An extension or a template built for an older PHP version throws a fatal error on a newer one — increasingly common right after a Joomla or PHP upgrade.
• A corrupted or misconfigured .htaccess file. Especially after a migration or a manual edit, a bad rewrite rule can break the whole site before Joomla even loads.
• Database connection failure. Wrong credentials after a server move, or a database that's hit its connection limit.
• A syntax error in a template override or custom code you or a developer edited directly.
• Disk quota or file permission issues on the hosting side, often after a backup restore or a migration.

Step 1: Turn on error reporting

This is always the first move, because right now you have no information — and everything below is faster once you can actually see the error.

If the admin panel loads: go to System → Global Configuration → Server tab, set Error Reporting to Maximum, and save. Reload the page that's showing blank.

If the admin panel is also blank: you'll need file access. Open configuration.php in your Joomla root and find the line:

public $error_reporting = 'default';

Change it to:

public $error_reporting = 'maximum';

Save and reload. You should now see an actual PHP error or warning instead of a blank page — which tells you exactly which file or extension is at fault.

If you don't have FTP set up or your host doesn't give you a File Manager, this is one of the most common moments people get stuck — you know the fix, but you can't reach the one file that needs editing. That's a solvable problem on its own; more on that at the end.

Step 2: Check the PHP error log

Even with error reporting on Maximum, some fatal errors (particularly ones that happen before Joomla fully bootstraps) won't render on the page at all — they only show up in the server's PHP error log. Ask your host where this is, or check common default locations like /logs/php_error.log or your hosting control panel's error log viewer. The most recent entries, timestamped close to when the issue started, are almost always the answer.

Step 3: Rule out the extension that was just installed or updated

If the white screen started right after you installed, updated, or configured something, that's your prime suspect — start there before anything else.

• If you can reach phpMyAdmin or another database tool, open the #__extensions table and set the suspect extension's enabled field to 0. This disables it without needing the admin panel to load.
• Alternatively, rename the extension's folder (under /plugins, /modules, or /components) via file access — Joomla will fail to find it and skip loading it, which is a quick way to confirm whether that extension is the cause.
• If disabling it fixes the site, you've found your culprit. Check for an updated, compatible version before re-enabling it.

Step 4: Increase the PHP memory limit

If nothing above points to a clear cause, memory exhaustion is the next most likely one. In php.ini, or via your hosting control panel's PHP settings, raise:

memory_limit = 256M

Some hosts also let you set this per-site via a .user.ini file or directly in configuration.php with ini_set('memory_limit', '256M'); near the top, if you don't have server-level access.

Step 5: Clear the cache

Corrupted cache files occasionally cause exactly this symptom. Delete the contents of /cache and /administrator/cache directly via file access if the admin panel's System → Clear Cache isn't reachable.

When there's truly no error, anywhere

Occasionally none of the above turns up anything — Maximum error reporting shows nothing, the PHP log is empty, and the page is just blank. This usually means the failure is happening very early, before Joomla's own error handling even initializes. In that case, the fastest path is inserting a few temporary, clearly-labeled debug markers directly into index.php and working through the request step by step — confirming the file is executing at all, then that configuration loads, then that the database connects — narrowing down which stage is actually failing. It's slower than reading a stack trace, but it works even when Joomla itself has nothing to say.

Prevention: how to avoid this next time

• Never update extensions or Joomla itself directly on a live site without a recent backup. A five-minute Akeeba Backup run is far cheaper than an emergency recovery.
• Test major updates on a staging copy first, especially jumps between major Joomla versions where extension compatibility is the most common trigger.
• Keep error reporting at "Development" or higher on a staging site, so problems surface immediately instead of as a blank page days later.

When to bring in help

If you've worked through all of the above and you're still looking at a blank screen — or you found the error but don't have the file access needed to fix it — that's usually the point where it's faster to bring in someone who's traced this exact failure pattern before than to keep guessing.