Skip to content

Why does WordPress show a critical error?

A WordPress critical error (or white screen of death) means PHP execution failed before WordPress could render the page. It usually happens after updates, plugin changes, theme edits, PHP version changes, server limits (memory/timeouts), or a conflict inside the plugin stack. This page is for urgent incidents where the site is unusable or revenue/enquiries are at risk. We treat it as a rescue job: isolate the fault, stabilise the site, and verify it’s safe to run again.

Process

How We Fix a WordPress Critical Error

A controlled recovery process (no trial-and-error).


  • Diagnosis: We capture the real error from logs (server/PHP/WordPress debug), reproduce the failure, and identify the trigger (plugin, theme, update, or server change).

  • Stabilisation: We restore access using the minimum safe change (disable the conflict, rollback safely, fix compatibility, or adjust limits) without breaking other journeys.

  • Verification: We confirm key pages load, wp-admin works, and business-critical flows (forms/checkout) behave normally before closing the incident.

WordPress critical error recovery process showing diagnosis from logs, safe stabilisation, and verification of key site flows

Common causes

Most Common Causes of a WordPress Critical Error

What breaks WordPress (and what we check first).


  • Plugin conflict or update: a new plugin version triggers a fatal error, hooks conflict, or deprecated code breaks on newer PHP.

  • Theme override / custom code: functions.php edits, outdated templates, or custom snippets fail after WordPress/WooCommerce updates.

  • PHP version / server limits: incompatible PHP version, memory exhaustion, timeouts, or OPcache issues can crash requests before pages render.

  • Corruption or file issues: partial update, missing files, permissions problems, or failed deployments can trigger white screens.

Illustration showing common causes of a WordPress critical error including plugin conflicts, theme code issues, PHP limits, and file corruption
When the site crashes, the priority is safe recovery and stability — not random changes.

How WPAssistant Works: Rescue Principles

Isometric 3D illustration of a magnifying glass identifying a bug in a code document, with a log file beside it, representing root-cause diagnosis and technical troubleshooting

Root-cause diagnosis

We trace the real failure point using logs and controlled testing, not assumptions.

isometric 3d illustration of a control panel with a single slider being adjusted by a wrench and gear, shield icon representing safety, and a small before and after comparison card, symbolising minimal safe changes and controlled website fixes

Minimum safe change

We apply the smallest reliable fix that restores the site without introducing new problems.

Isometric 3D illustration showing end-to-end checkout verification with a checklist, shopping cart, and email confirmation connected in a single workflow, representing complete purchase journey testing and order validation

Business-critical testing

We verify wp-admin, key pages, forms, checkout, and integrations before closing the incident.

Isometric 3D illustration of a report document with simple charts, a speech bubble, and a handshake symbol connected together, representing clear communication, reporting, and handoff verification in a digital workflow.

Clear handover

You get a short summary of what broke, what we changed, and what to do next.

WordPress Critical Error / White Screen: What We Fix

A critical error can hit the front-end, wp-admin, or both. Sometimes the site looks “blank” with no message. Sometimes WordPress shows the critical error screen or sends an email to the admin address.

Typical rescue outcomes

We restore site access, isolate the failing plugin/theme/code path, and fix the root cause (compatibility, conflict, memory/timeouts, broken deployment, permissions). We then verify key journeys: important pages load, forms submit, and checkout/payment still works where applicable.

Related rescue pages (recommended)

If the critical error is part of a wider outage, these pages cover common neighbouring causes:

Site Down (Incident Response) · Checkout Issues Hub · Site Broke After Migration · Rescue Packages & Pricing

No open-ended billing. Scope is agreed before work begins. If the issue is bigger than expected, you’ll know before any additional work is done.

 

  • Fast stabilisation: restore access and stop the crash quickly and safely.
  • Root-cause fixes: plugin/theme/code conflicts identified from logs, not guesswork.
  • Safe changes only: minimum fix required to restore stability without collateral damage.
  • Verification: confirm wp-admin, key pages, and business journeys work again.
  • Clear next steps: what caused it, what we changed, and how to prevent repeats.

Critical Error FAQs: Quick Answers

Short answers to the most common questions when WordPress shows a critical error or white screen.
What is the WordPress white screen of death?

It’s when WordPress fails before rendering output, so the page loads blank. The cause is usually a PHP fatal error, memory exhaustion, or a plugin/theme conflict.

Why did WordPress start showing a critical error after an update?

Updates can introduce compatibility issues (PHP changes, deprecated functions), trigger plugin conflicts, or break theme overrides and custom code. We confirm the trigger from logs and apply a safe fix.

Can you fix it if I can’t access wp-admin?

Yes. We can diagnose from hosting/server access and logs, disable the conflict safely, restore access, then fix the root cause properly.

Do you work on live or staging?

Where possible we use the safest approach available for your setup. The method depends on urgency, access, and whether a staging environment exists.

Do you guarantee the issue will be fixed?

We provide best-effort incident response. We diagnose the root cause and apply the minimum safe change to restore stability where possible. Outcomes can’t be guaranteed due to hosting and third-party factors.

Need help now?

Start a WordPress Rescue

If your site is down, unstable, or something broke after an update, plugin change, or migration, tell us what’s happening. We’ll review the details and confirm the next steps before any work starts.

Include your website URL, what changed before the issue, and any error message or screenshot. That helps us move faster.

Start a WordPress rescue request