You clicked update, and now there's a white screen, a fatal error, or a layout in pieces. It happens after almost every WordPress release, and it is nearly always one plugin — An add-on that extends your CMS; outdated or abandoned plugins are the most common way sites get hacked. or theme that wasn't ready — not WordPress itself. The good news: if you move carefully and have a copy to fall back on, a broken update is one of the most recoverable problems a site can have. The bad news: poking at it without a backup — A tested copy of your site you can restore from; an untested backup is a hope, not a plan. is how a five-minute rollback turns into a rebuild.
Check these first, yourself
Take a full backup first — files and database — Where your site stores its content and user data; overloaded or corrupted, it throws errors instead of pages.. Rolling back without one turns a fixable problem into a permanent one.
Read the exact error: turn on WP_DEBUG or check the host's error log, and it will usually name the plugin or theme that failed.
Disable the suspect at the source: rename its folder over SFTP (for example wp-content/plugins/that-plugin → that-plugin.off) and reload.
If a theme update broke it, switch to a default theme like Twenty Twenty-Four to confirm, then restore the last good copy.
Should you fix it yourself or call a rescue?
Still have questions?
Can I just reinstall WordPress to fix it?
Reinstalling core rarely helps and can make it worse. The break is almost always a plugin or theme, so you roll back the suspect — not the whole platform.
Will I lose content if I roll back?
No. Restoring the last good files and database brings back exactly what you had. The only thing you would re-add is anything published after that point.