Magento White Screen FAQ
All 12 answers
What is the Magento white screen of death (WSOD)?
The white screen of death is a completely blank page Magento serves when a PHP Fatal error happens but display_errors is off (the default in production mode). PHP stops, sends no output, and the browser shows nothing. The real error is not gone, it is written to var/log/exception.log, var/report/, or the PHP-FPM error log. The first job is to surface that hidden message; the fix follows from there.
How much does it cost to fix a Magento white screen?
Every project gets a fixed written quote. Send a short brief on WhatsApp and I reply with scope, price and timeline.
It depends on the cause:
- Quick Fix: one well-defined blank page or route with a clear fatal.
- Bug-Fix Sprint: a gnarly root cause (post-deploy WSOD, multiple blank routes, module conflict) plus regression tests.
- Emergency / Retainer: custom, available on request; a stabilization sprint is available for high-risk stores.
You get a fixed estimate before any work starts.
How fast can you fix a blank Magento page?
Emergencies are triaged during my working hours (10 AM to 7 PM IST, Monday to Saturday). The first step is surfacing the hidden fatal; the fix may be quick (regenerate generated/, reset OPcache) or take longer (isolate a broken module, trace memory exhaustion). We give you a realistic ETA right after we see the error.
How do you find the error behind a blank page?
We make the hidden fatal visible without exposing it to your customers. On a staging clone we run bin/magento deploy:mode:set developer (or set display_errors = On) so the page shows the real message. In parallel we read var/log/exception.log, var/log/system.log, var/log/debug.log, the newest file in var/report/, and the PHP-FPM / nginx error logs. Between the on-screen fatal and the logs, the cause is usually obvious.
Can you fix it without breaking my live store?
Yes. We reproduce the white screen on a staging clone first, fix it there, and only deploy once it is verified. We never turn on display_errors on a live production store where customers could see a stack trace. Every change is reversible, if a deploy misbehaves we roll it back, so you are never stuck on a dead page.
My store went white right after a deploy, what causes that?
Post-deploy white screens are usually one of: (1) missing generated/ code, setup:di:compile did not run or failed, so classes like …\Interceptor or …\Proxy do not exist; (2) stale OPcache still serving old bytecode against new files; (3) wrong ownership on var/, generated/, or pub/static so PHP-FPM cannot write. We check the deploy log, regenerate code cleanly, reset OPcache, and fix permissions for your stack.
I see “Allowed memory size exhausted”, how do you fix it?
PHP Fatal error: Allowed memory size of N bytes exhausted means a page blew past PHP’s memory_limit and died blank. Raising the limit alone is a band-aid, we trace why it ran out: an unbounded collection load, a runaway loop, a heavy import, or a leaky third-party block. We fix the offending code path so the page stays under a sane limit, then set memory_limit to a value that fits real traffic.
A new extension made every page blank. Can you fix it?
Yes, this is one of the most common WSOD causes. A freshly installed or version-incompatible module throws an uncaught fatal during bootstrap, whiting out the whole site. We read the log to identify the exact class and module, disable it safely with bin/magento module:disable, get your store back up, then decide whether to patch the module, pin a compatible version, or replace it with a working alternative.
My admin login is blank but the frontend works, why?
A blank admin (or blank login screen) while the storefront loads usually points to an adminhtml-area fatal: a broken admin module, a corrupt generated/ for the admin area, a session/Redis issue, or an OPcache mismatch. The diagnostic is the same, surface the fatal from var/log and the report file, then fix the specific cause. We also confirm your admin URL and session storage are configured correctly.
Do you work on staging or directly on live?
We prefer to work on a staging clone so we can safely enable developer mode and reproduce the white screen without exposing errors to customers. If you do not have staging, we can spin up a quick clone or, for genuine emergencies, work carefully on live with display_errors kept off and errors read only from the logs. Either way the live deploy happens only after the fix is verified.
Can wrong file permissions cause a white screen?
Yes. If PHP-FPM cannot write to var/, generated/, or pub/static, usually from a wrong owner or a too-strict umask after a git pull or scp, Magento fails to bootstrap and the page renders blank. We reset ownership to your web user, apply the correct directory and file modes, and confirm Magento can write its cache, generated code, and static assets. After that the page renders normally.
Is there a guarantee the white screen stays fixed?
Yes. Every fix is verified against the real page before we close it. The 14-day bug-fix warranty on production deployments covers regressions in delivered scope. We also hand you a short root-cause note so you (or your host) can avoid the same trigger on the next deploy. For stores that cannot risk repeat downtime, a retainer adds a response window agreed in writing.
Related FAQ topics
All FAQ topics-
Magento Upgrade
Common questions about upgrading Adobe Commerce / Magento Open Source. -
Hyvä Development
Common questions about Hyvä theme development, migration from Luma, and Hyvä Checkout.
-
Magento Performance
Common questions about Magento performance optimization, Lighthouse... -
Emergency Bug Fixing
Common questions about emergency e-commerce bug fixing across... -
Hiring a Freelance Magento Developer
Questions about Magento project scope, quotes, start dates... -
Magento B2B Development
Common questions about Adobe Commerce B2B, Magento B2B development...