You loaded your site and got a blank white page. Or an error message. Or a spinning wheel that never stops.
Your WordPress site crashed, and right now every other thought is on hold. How long has it been down. How many sales you’re missing. Whether you can fix it before a customer notices.
Here’s the good news. Most WordPress crashes come from a short list of causes, and a fair number of them you can fix yourself in the next twenty minutes. The rest need someone who does this for a living. The real skill is knowing which situation you’re in before you start changing things.
This guide goes in order: confirm the site is genuinely down, work out what kind of crash you’re looking at, try the fixes that are safe to do yourself, and recognise the exact point where carrying on does more harm than good.
Let’s get your site back.
First, make sure your site is actually down
Before you touch anything, spend sixty seconds ruling out a false alarm. A surprising number of “my site crashed” moments aren’t crashes at all.
Try these:
- Open your site on your phone using mobile data instead of wifi. If it loads there, the problem is your network or device, not your site.
- Open it in a private or incognito window. That skips your browser cache.
- Check a service like downforeveryoneorjustme.com, which tells you whether your site is down for everyone or just you.
If the site loads for everyone except you, clear your browser cache along with any caching plugin or CDN cache, and you’re probably done. No emergency.
If it’s genuinely down for everyone, keep reading.
Work out what kind of crash you’re dealing with
“Crashed” looks different depending on what broke. The screen in front of you is your first real clue, so match it to one of these:
A blank white screen. No text, no error, just white. This is the white screen of death, usually a PHP error coming from a plugin or theme.
“There has been a critical error on this website.” WordPress hit a fatal error and stopped. If WordPress emailed you about it, that email often names the exact plugin. We cover this one step by step in our guide to fixing the WordPress critical error.
An HTTP 500 error. A server-side error. Often a corrupted .htaccess file, a PHP problem, or memory running out.
“Briefly unavailable for scheduled maintenance.” Your site got stuck in maintenance mode because an update was interrupted partway through. This one is usually a quick fix.
“Error establishing a database connection.” WordPress can’t reach its database. Either the database is down, overloaded, or the login details in your config have changed.
The site loads, but it’s broken. Layout scrambled, images missing, a feature dead. Often a theme conflict, a failed update, or a caching problem. If something like your theme has stopped displaying properly, our post on a theme not showing on your site goes deeper.
Note what you’re seeing. It decides what you try next.
The fixes you can safely try yourself
These are steps a non-developer can do without much risk. Work through them in order and stop the moment your site comes back.
- Undo your last change. Think back. Did the site break right after you updated a plugin, installed a theme, or changed a setting? If so, that’s almost certainly your cause. If you can still reach your WordPress dashboard, deactivate that plugin or switch the theme back. Crashes rarely come out of nowhere. Something changed.
- Clear every cache. Browser cache, caching plugin, hosting cache, CDN. A site can look broken simply because visitors are being served an old, broken copy. This is quick, it never makes things worse, and it’s always worth doing first.
- Deactivate your plugins. Plugin conflicts are the most common cause of a crash. If you can get into your dashboard, deactivate all your plugins, check whether the site returns, then reactivate them one at a time until it breaks again. The last one you switched on is your culprit. If you can’t get into your dashboard, this step means logging into your hosting file manager and renaming the plugins folder. That’s doable, but it’s the edge of safe DIY. If that sentence already lost you, skip to the next section.
- Switch to a default theme. If plugins aren’t the problem, your theme might be. Temporarily switching to a default WordPress theme such as Twenty Twenty-Four tells you whether the theme is at fault.
- Restore a recent backup. If you have a backup from before the crash, restoring it is the fastest route back online. One caveat: you’ll lose anything that happened since that backup, including new orders, form entries, and comments. If your site takes orders, that matters, so weigh it up before you restore.
If one of those brought your site back, good. Now find out why it happened, because a crash you don’t understand is a crash waiting to repeat.
Know when to stop
Here’s the part most crash guides skip.
Every fix above is reversible and low-risk. But WordPress troubleshooting has a cliff edge, and it’s worth naming exactly where it sits. Stop doing it yourself the moment a “solution” asks you to:
- Edit core files like wp-config.php or functions.php
- Add or change code snippets
- Touch the database directly through phpMyAdmin
- Run command-line tools
- Change file permissions
These things are all learnable. The problem is the margin for error. One wrong character in the wrong file turns a single-plugin problem into a site-wide one, and at that point you’re not fixing a crash, you’re rebuilding. The same caution applies to any crash you’ve already spent more than an hour on, anything involving malware or a hack, and a database connection error that clearing the cache didn’t solve.
When you reach that line, the genuinely cheap move is to hand the site to someone who fixes WordPress every day. More on that below.
Why WordPress sites crash in the first place
Once your site is back, it helps to understand what knocked it over. Crashes almost never have one tidy cause. Usually it’s one of these:
Plugin conflicts. Two plugins try to do the same job, or one ships an update written for a newer version of WordPress than the one you’re running. Something throws a fatal error and the site stops.
Theme and PHP mismatches. Your theme ran fine on WordPress 6.3, then 6.4 changed something it relied on. Or your host bumped your PHP version and older code couldn’t keep up.
Memory exhaustion. Your site tries to do too much at once, like a traffic spike during a sale or a heavy import, and runs out of the memory your hosting plan allows.
Database corruption. An update fails partway through and leaves the database in a state WordPress can’t read.
Malware. A security hole lets malicious code in, and that code crashes the site or hijacks your visitors.
The pattern worth noticing: most of these trace back to updates and to security gaps. Which is also where prevention lives.
How to stop the next crash before it happens
You can’t make a WordPress site crash-proof. You can make crashes rare and boring instead of frequent and expensive.
- Test updates on a staging site first. A staging site is a private copy of your live site. Run the update there, confirm nothing breaks, then push it live. This alone prevents most update-driven crashes.
- Keep real backups. Automatic, stored off-site, and frequent enough that restoring one wouldn’t cost you a day of data.
- Update on a schedule, not in a panic. Plugins, themes, and core, reviewed regularly rather than all at once at midnight.
- Watch for trouble. Uptime and security monitoring catches problems while they’re still small.
None of this is complicated. It’s just steady, and steady is the thing that slips first when you’re busy running a business. If keeping on top of it isn’t realistic, that’s exactly what ongoing WordPress maintenance is for.
Get your site fixed today, without touching a line of code
If you’ve hit the cliff edge, or you’d simply rather not spend your evening inside a hosting file manager, this is what WP Relieve does.
You send us the problem. A WordPress developer who has seen this exact crash before diagnoses it, fixes it properly, and tells you in plain language what went wrong. You don’t open FTP. You don’t google error messages. You don’t gamble with your live site.
It’s one flat fee, $147 a month, for unlimited fixes and ongoing maintenance. No hourly billing, no surprise invoice after an emergency. Crashes and security issues get 24/7 emergency cover, and most standard tasks are completed within one business day. If it turns out not to be for you, there’s a 7-day money-back guarantee, no questions asked.
More than 328 businesses and agencies already run their sites this way.
“I have had an awesome experience using WP Relieve. They help me redesign things, fix pesky bugs, and are prompt and kind technicians. I highly recommend their services.”
— Stephanie Anne
“Very efficient and affordable services. I like that you guys can pick up even the most complex WordPress requests and deliver in no time.”
— Kelvin Mwangi
The team that fixes today’s crash is the same team that keeps the next one from happening. You can see the kinds of tasks we handle, or get started and have your site sorted.
WordPress crash FAQ
Why did my WordPress site suddenly crash?
Most sudden crashes follow a change: a plugin or theme update, a new install, or a PHP version bump from your host. Plugin conflicts are the most common single cause. If your site broke right after you updated something, start your troubleshooting there.
How do I fix the WordPress white screen of death?
The white screen is usually a PHP error from a plugin or theme. Clear all caches first. If you can reach your dashboard, deactivate plugins one by one and switch to a default theme to find the cause. If you can’t reach the dashboard, the fix involves your hosting file manager, which is the point to consider expert help.
My WordPress site crashed after a plugin update. What do I do?
Deactivate that plugin. If you can log into WordPress, do it from the Plugins page. If the update locked you out, you’ll need to rename the plugin’s folder through your host’s file manager. Once the site is back, check whether a newer version of the plugin has fixed the bug before you reactivate it.
Can I fix a crashed WordPress site without a developer?
Often, yes. Clearing caches, deactivating plugins, switching themes, and restoring a backup are all safe to do yourself. The line is code. Once a fix asks you to edit files, run commands, or touch the database, the risk of making things worse outweighs the saving.
How long does it take to fix a crashed WordPress site?
A simple cause like a single plugin conflict can be sorted in minutes. A database problem, a hack, or a crash with no obvious trigger takes longer to diagnose. With WP Relieve, crash and security emergencies are handled around the clock, and most standard fixes are completed within one business day.
How do I get into WordPress admin when the whole site is down?
If wp-admin won’t load, you usually can’t fix anything from the dashboard at all. Access then happens through your hosting control panel or file manager: renaming the plugins folder, swapping the theme, checking error logs. If that’s unfamiliar territory, it’s a safer use of your time to pass it to someone who works in there daily.
A crashed site feels like a disaster while you’re staring at it. Most of the time it isn’t. Work through the safe steps above, and if the next move involves editing code, treat that as your signal to hand it over. Doing that early is what keeps a bad afternoon from turning into a bad week.
