One minute your WordPress site is fine. The next, you are staring at a blank white page, a “There has been a critical error” message, or a 500 error that will not go away. You did nothing dramatic. You clicked Update on a plugin. You changed one line of CSS in your theme. You switched themes to see how it looked. Now the site that took you months to build is gone, and your stomach drops.
If that is you right now, take a breath. Almost every broken WordPress site comes back. The catch is that getting it back depends on one thing most people ignore until it is too late: a backup you actually own and control.
This guide is not a product pitch. It walks through what usually breaks a site, how to confirm exactly what went wrong, and how to restore it, in order, fastest option first. If you can fix it without spending a cent, do that. If your only real fix is restoring a backup, I will show you the cleanest way to do it.
The Backup Myth That Leaves People Stranded
Here is the belief that turns a 10-minute fix into a lost weekend: “My host backs up my site, so I am covered.”
Hosts do take backups, but not for you. Those backups exist so the host can recover its own servers when hardware fails. Many keep them for a short window, some store only the database, and plenty charge a fee or open a slow support ticket before they will restore anything for you. When they do restore, it is usually all or nothing, and it can wipe the posts you published after the snapshot was taken.
The truth: a host backup is a safety net for the host. A backup sitting in your own account is a restore button for you. It is the one you can open, download, move between hosts, and run whenever you need it. If you are dealing with a break right now, knowing which kind you have changes everything about your next step.
Why This Happens
WordPress breaks in predictably boring ways. Once you know the usual suspects, the diagnosis gets much faster.
- A plugin update clashes with something. This is the number one cause. A new version conflicts with another plugin, your theme, or your PHP version, and the site throws a fatal error.
- A theme change drags your customizations away. Switching themes deactivates menus and widgets, and if you edited the parent theme directly, an update erases that work.
- Your host changed the PHP version. Older plugins written for PHP 7 can throw fatal errors when the server moves to PHP 8.2 or 8.3.
- A manual code edit went wrong. One missing semicolon in
functions.phpor a bad snippet is enough to take the whole site down. - The database is damaged or half-imported. A failed migration or a corrupted table leaves the site loading blank or stuck in a redirect loop.
- The site ran out of memory. A heavy page builder plus a long plugin list can hit a server memory limit and produce a fatal error.
How to Confirm What Actually Broke
Do not start changing things at random. Run this checklist first. It takes about five minutes and tells you which fix you actually need.
- Write down the exact symptom. A plain white screen, the words “There has been a critical error on this website,” a 500 error, a site with no styling, or an admin you cannot log into. The symptom points to the cause.
- Check your admin email. WordPress sends a message titled “Your Site is Experiencing a Technical Issue.” It includes a Recovery Mode link that can get you back in even when the front end is blank.
- Ask when it broke. If it happened right after an update, that update is your prime suspect. If it happened after you touched code or a theme, start there instead.
- Test with plugins out of the picture. In Recovery Mode, deactivate all plugins. If the site comes back, a plugin is the cause.
- Switch to a default theme. Activate Twenty Twenty-Five. If the site loads, your theme is the problem.
- Turn on debugging. Add
define('WP_DEBUG', true);anddefine('WP_DEBUG_LOG', true);towp-config.phpto see the real error inwp-content/debug.log. - Read the server error log. Your host’s file manager or control panel usually has a PHP error log that names the exact file and line that failed.
If steps 1 to 3 point at a specific plugin or theme, you can often fix the site in under ten minutes. If the database is damaged or the cause stays unclear, jump to the restore option below.
The Fix: From Free to Full Restore
Work through these in order. The first three are free and fix most breaks.
1. Free fix: use WordPress Recovery Mode
Recovery Mode has been built into WordPress since version 5.2. When a fatal error hits, WordPress emails the admin a link. Open it and you get a stripped-back admin screen where you can deactivate the plugin or theme that broke things. Once you deactivate the culprit, the site usually returns instantly. Expected result: the site loads, and you know which plugin to leave alone until it is patched.
2. Free fix: rename the plugin folder over SFTP
If you never got the recovery email, log into your host’s file manager or connect over SFTP and open wp-content/plugins. Rename the suspect plugin’s folder to something like plugin-name-off. WordPress deactivates it the moment the folder name changes. To rule the theme out, do the same in wp-content/themes. Expected result: the site is back and one suspect is confirmed.
3. Free fix: roll the plugin back one version
If a plugin update was the trigger, you rarely need to abandon the plugin. Install the free WP Rollback plugin and roll the offending plugin back to its previous version. Test the site, then wait for the developer to ship a fixed release before you update it again. Expected result: the site works and you kept the plugin.
4. The reliable fix: restore from your own backup
If the free fixes did not work, or the database itself is damaged, this is the case where restoring a backup is the fastest fix. You need a backup plugin that stores copies off your server and can put them back with one click.
UpdraftPlus is the one I use, and it is the most widely installed backup plugin on WordPress for good reason. The free version takes scheduled backups to Google Drive, Dropbox, or another cloud account, then restores your files and database in a few clicks when something goes wrong. To restore, open Settings, then UpdraftPlus Backups, find the most recent backup from before your site broke, and click Restore. You can bring back the whole site, or just the plugins, theme, database, or uploads that you need.
Expected result: your site returns to the exact state it was in before the break, customizations and all. Once you have a working backup cycle, a broken site stops being a crisis and becomes a ten-minute inconvenience.
5. Last resort: ask your host for a server-level restore
If you have no backup at all, contact your host support and ask whether they hold a server snapshot from before the break. Many do, some for only a few days. Be specific about the date and time you need. Expected result: a working site with whatever was in that snapshot, which may be missing anything published since. This is exactly why owning your own backup matters.
When It’s Worth Paying for a Backup Plugin
For a single small site, the free version of UpdraftPlus is genuinely enough. It schedules backups off-site and restores them. Do not upgrade just because a pricing page tells you to. You can also compare it against other options in my guide to the best WordPress backup plugins.
Premium starts around $70 per year for up to two sites, and it earns that money in three specific cases. You want a backup taken automatically before every update, so a bad update can never strand you. You want incremental backups, so daily copies do not fill your storage. Or you manage several sites and want site-to-site migration and priority support. One lost weekend of sales or client work costs more than the whole year.
If your hosting is the bottleneck: Kinsta keeps your site safe with automatic daily backups and one-click restore, so a bad update or a hack is a rollback, not a rebuild. Free staging environments let you test updates before they touch the live site. Their support is top tier, and 24/7 live chat is staffed by WordPress engineers who will help fix the actual problem with you, so you are not stuck waiting on your developer to reply. Plans start at $35 per month.
If your backup habit is already solid, the other half of staying safe is keeping the site from getting hit in the first place. My WordPress security fix guide covers that side, and if a bad update is slower than you would like, it helps to know how to back up WordPress the right way in the first place.
Frequently Asked Questions
Sometimes. WordPress keeps no backup of its own, so your only options are asking your host for a server snapshot from before the break, or rebuilding the parts you lost. This is the single best reason to set up a backup today, before you need it.
Open Settings, then UpdraftPlus Backups. Find the backup set from before the problem, click Restore, choose which parts you want (database, plugins, themes, uploads, or the lot), and confirm. UpdraftPlus downloads the files and applies them to your site in a few minutes.
Yes, if you restore the full database. Choosing your own backup gives you control over this. If you only need to undo a broken plugin or theme, restore just the plugins or theme and leave the database alone. That keeps your newer content intact.
Take a backup before you update, and prefer a plugin or host that backs up automatically before changes. Test big updates on a staging site first, and avoid editing parent theme files directly. Use a child theme so theme updates never wipe your customizations.
Small sites usually restore in 5 to 15 minutes. Larger sites with big media libraries take longer because the files have to download and upload again. On a host with one-click restore and staging, a rollback is close to instant.
Your Next 10 Minutes
Here is the whole thing in three steps you can run right now.
- Check your admin email for the WordPress recovery link, then deactivate the plugin or theme you last touched. This alone fixes most breaks.
- If that fails, open your backup plugin or host panel and find the most recent restore point from before the break. Restore your files and database.
- Once the site loads, set up automatic off-site backups before you change anything else, so the next break costs you ten minutes instead of a weekend.
If updates keep breaking your site, the weak link is usually a fragile theme or a bare-bones host with no staging. Moving the site to a host that includes daily backups, staging, and one-click restore removes most of that risk. Then get back to growing the site instead of rescuing it.
This post contains affiliate links. If you buy through them, I may earn a small commission at no extra cost to you.
About The Author
