A WordPress white screen means PHP stopped executing before it could render anything. The usual causes are a fatal error in a plugin or theme, an exhausted memory limit, or a corrupted core file. WordPress hides errors in production by default, which is why you see nothing at all rather than a message — finding what it is hiding is most of the work.
Before you buy, one quick check
This tells you whether it is a plugin. It does not fix anything, and nothing is deleted.
Over SFTP, go to wp-content and rename the plugins folder to plugins-off. Load your site.
Site comes back — it is a plugin. Rename the folder back to plugins straight away; everything reactivates as it was. You now know what to tell us, and we will find which one.
Site is still blank — it is the theme, a core file, or a server limit. Rename it back and buy this fix; that is exactly what we diagnose.
Leave the folder renamed only as long as the test takes. A few plugins clear temporary data while inactive, so do not leave it that way overnight.
White screen of death — diagnosis & fix
Your site loads a completely blank page with no error message. We enable logging, find the fatal error WordPress is hiding, fix it, and verify every template loads.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| Blank page, but you can still log in | Likely a theme or template issue, not this |
| Browser shows a 500 error, not a blank page | HTTP 500 internal server error |
| Blank page and locked out of admin | This fix covers it |
| Went blank right after moving hosts | Broken after host migration |
| Blank page with spam text in view source | Security remediation, not this |
What you are seeing
- A completely blank page with no error text, on some or all URLs
- wp-admin is blank too, or loads but dies on one screen
- It started right after an update, a new plugin, or a change at your host
- A hard refresh and a different browser make no difference
- View source shows an empty page, or one that stops mid-render
Common causes
- A plugin or theme threw a PHP fatal error that is not being displayed
- The PHP memory limit was exhausted by a heavy query or an image operation
- A core file was corrupted by an interrupted or failed update
- Your host changed the PHP version and something is not compatible
- A syntax error in a code snippet or a direct edit to a theme file
What we do
- Take a full backup before touching anything
- Enable error logging and capture the actual fatal error, without exposing it to visitors
- Isolate the failing plugin, theme or core file by staged deactivation
- Fix, roll back or replace the failing component, and raise limits if that is the cause
- Load-test every template — home, archive, single post, admin, and checkout if you have one
- Restore your original error-display settings and send you the incident note
What is included
- A working site, verified on every template type
- A short incident note naming the exact cause and what we changed
- The pre-fix backup, kept for 30 days
- A free 9-layer scan of the site with anything else we found
Not included
- Rebuilding a site with no working backup and no recoverable database
- Malware removal or hacked-site recovery — that is a separate service
- Replacing a nulled plugin with a licensed copy, which we quote separately
- Custom development to add functionality the failing plugin never had
- Design changes or content work of any kind
Questions about this fix
My site is blank but I can still reach wp-admin. Is this the right fix?
Probably not. If the admin loads, PHP is running fine and the problem is more likely in the theme or a specific template. Run the free scan and it will point you at the right one. If you have already bought this, we tell you before doing the work and refund or re-scope.
I have 40-odd plugins. Will you have to disable all of them?
Only briefly, and only to isolate the fault. Staged deactivation narrows it down by halves rather than one at a time, so it is usually four or five steps rather than forty. Everything is reactivated in the same state it was in, with the same settings.
Can you tell me which plugin caused it?
Yes, and that is in the incident note. It matters more than the fix itself, because it tells you what to watch on the next update. If the plugin is abandoned we say so and suggest what to replace it with.
Could it break again after you fix it?
If the cause was a bad update, yes — the same update can break it again next time. The incident note tells you what to hold back. If it keeps happening, staging-tested updates are the actual fix, and that is what a care plan does.
Why can I not just see the error myself?
WordPress deliberately hides PHP errors on live sites so visitors never see a stack trace. Turning that display on safely, capturing the real error, and turning it back off is most of the work. The fix itself is often seconds once you know what broke.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.