A blank white page in Zen Cart almost always means a PHP error is being silently suppressed. Enable error reporting, check your server PHP version against your Zen Cart version, then isolate the broken plugin or template file. Full steps below.
The blank white page — also called the White Screen of Death (WSOD) — is the most common Zen Cart error. The page loads but shows absolutely nothing: no header, no error message, no content. This happens because PHP is throwing a fatal error but your server is configured to suppress it rather than display it.
The good news: once you can see the actual error message, the fix is usually straightforward. Here's how to get there.
Before you can fix anything, you need to see what PHP is actually complaining about. Zen Cart has a built-in way to enable visible error reporting.
Via FTP or your hosting file manager, navigate to /includes/configure.php (and also check /admin/includes/configure.php if the admin is blank).
Look for a line containing define('STRICT_ERROR_REPORTING'. If it doesn't exist, you can add this near the top of the file:
// Add this temporarily to see PHP errors define('STRICT_ERROR_REPORTING', true); error_reporting(E_ALL); ini_set('display_errors', 1);
Remove these lines as soon as you've identified the error. Displaying errors on a live store is a security risk — it can expose file paths and server information to visitors.
Reload the blank page. You should now see an actual PHP error message. Note the file name and line number — this tells you exactly where the problem is.
The most common cause of a sudden WSOD after a hosting change or server update is a PHP version mismatch. Here's what's compatible:
To check your current PHP version, create a file called phpinfo.php in your webroot with this content, then visit it in your browser:
<?php phpinfo(); ?>
Delete phpinfo.php after you've noted the PHP version. Never leave it on a live server — it exposes your full server configuration.
If your PHP version is incompatible, contact your host to downgrade PHP (a temporary fix) or contact us to upgrade your Zen Cart version to one that supports modern PHP.
If you recently installed or updated a plugin and the WSOD appeared immediately after, the plugin is almost certainly the cause.
The error from Step 1 should point to a specific file. If it's in /includes/modules/ or /includes/languages/, that's the module causing the problem.
Via FTP, rename the suspected module folder from e.g. my_plugin to my_plugin_DISABLED. Zen Cart will no longer load it. Reload the page — if it works, you've found the culprit.
Look up the plugin on the Zen Cart plugin repository (zen-cart.com/downloads). It will list which Zen Cart versions it supports. If your store version isn't listed, the plugin needs updating or replacing.
Incorrect file permissions can cause blank pages, especially after FTP uploads or server migrations. Zen Cart files and folders need specific permissions to work correctly.
755644444 (read-only) on a live storeYou can check and fix permissions via your hosting control panel's file manager, or via SSH:
# Set all folders to 755 find /path/to/zencart -type d -exec chmod 755 {} \; # Set all files to 644 find /path/to/zencart -type f -exec chmod 644 {} \; # Lock configure.php chmod 444 includes/configure.php chmod 444 admin/includes/configure.php
Large Zen Cart stores with many products, complex templates, or several active modules can run out of PHP memory, causing a silent fatal error (and therefore a blank page).
Add this to your .htaccess file in the Zen Cart root:
php_value memory_limit 256M
If that doesn't work (some hosts don't allow .htaccess overrides), you can try adding this to the top of index.php:
<?php
ini_set('memory_limit', '256M');
If your host won't allow you to increase memory beyond a certain amount, this is a hosting limitation. Consider upgrading your hosting plan or switching to a host that allows more PHP memory.
Zen Cart writes its own error log separate from your server's Apache/PHP error log. Check this file for detailed error traces:
/logs/myDEBUG-xxxxxxx.log
If there are multiple log files, sort by date modified and open the most recent one. Look for lines marked PHP Fatal error or PHP Parse error — these will point directly to the broken file.
Consider getting professional help if:
Send us your error log and we'll diagnose it for free. Most WSOD issues are fixed within a few hours.
Get a free diagnosis