WooCommerce White Screen After Update? Causes & Fix

You updated WooCommerce and the store went white — no error, no admin, nothing. That blank page is a PHP fatal error, and the log almost always names the file that caused it. Here's how to read it and get the store back.

Last updated: 16 Jul 2026 · ~7 min read

What a white screen after a WooCommerce update means

PHP hit an error it could not continue past, stopped, and sent an empty response. WordPress normally catches that and shows "There has been a critical error on your website" instead. A truly blank page means the fatal happened somewhere the handler couldn't help — very early in the load, in a must-use plugin or drop-in, or on a site where the fatal-error handler is switched off. Same underlying event, less helpful presentation.

The important part: your database is fine. Orders, products, customers and settings are all still there. One PHP file is throwing, and until you find it nothing renders. This is recoverable, and you usually don't need to restore a backup.

The most common causes (most likely first)

1. An extension fataled on the new WooCommerce versionThe log shows Uncaught Error: Call to undefined method or Call to undefined function, pointing at a file inside wp-content/plugins/ — a WooCommerce extension, not WooCommerce itself. The release you just installed removed or renamed something that extension still calls. This is the one to check first.
2. Your theme's WooCommerce template overrides are out of dateThe fatal points at a file inside your theme — often a woocommerce/ folder in the theme directory, or functions.php. The theme copied a WooCommerce template years ago and it still calls a function the new version dropped. Tell-tale: the shop is white but non-Woo pages sometimes still load.
3. PHP ran out of memory during or after the updateThe log says Allowed memory size of X bytes exhausted. Nothing is broken in code — the process simply couldn't finish. Common on hosts with a low memory_limit, and often intermittent: some pages load, some don't.
4. The store's PHP version is below what this WooCommerce release needsThe log shows a PHP Parse error: syntax error inside a WooCommerce file rather than an uncaught error — PHP literally can't read the new code. WordPress blocks updates your PHP can't run, so this usually means the update was done manually over FTP or with WP-CLI, or the host changed the PHP version separately.
5. The update didn't finish, or PHP is running stale cached codeThe log says Failed opening required, or names a class as not found when the file is plainly there on disk. Either the update was interrupted and files are half-copied, or OPcache is still serving the old compiled version. Re-upload WooCommerce from a fresh zip and restart PHP.

Where to look first

• Turn on logging first — don't guess. Over SFTP, edit wp-config.php and set WP_DEBUG to true, WP_DEBUG_LOG to true and WP_DEBUG_DISPLAY to false, above the "stop editing" line. Reload the white page, then open wp-content/debug.log and read the last entry.
• Path inside wp-content/plugins/? That's cause 1. Over SFTP, rename that plugin's folder (add -off to the end) — WordPress deactivates what it can't find, and the store should come straight back.
• Path inside your theme? That's cause 2. Rename the theme's woocommerce/ override folder so WooCommerce falls back to its own templates, or temporarily switch to a default theme by renaming the theme folder.
• "Memory exhausted" or a parse error? That's cause 3 or 4 — raise memory_limit, or check your host's PHP version against what this WooCommerce release requires.
• Store back up? Update the offending extension to a version that supports your WooCommerce release, or roll WooCommerce back until its author ships one. Don't leave it renamed and forget.

How to know you fixed it

Frequently asked