Apps
Safari keeps crashing or quitting unexpectedly? Here's why — and how to fix it
By the Noah team·Updated August 19, 2026·5 min read
Short answerSafari crashing over and over is usually one of these, each with a clean fix:
- A bad extension — an add-on built for an older Safari can bring the whole browser down. The most common cause.
- A corrupt cache — the temporary files Safari keeps to load sites faster can get damaged and choke it.
- One heavy or broken page — a single site can crash the tab (or the browser) every time it loads.
Start in Safari's
Settings > Extensions — turn them all off. If that stops it, switch them back on one at a time to find the culprit. The steps below cover the cache and stuck-page cases too.
Safari bounces in the Dock and disappears, or it opens fine until you visit one site and then quits. Annoying — but it's almost never your Mac at large. It's usually one add-on, or the local files Safari keeps to speed things up. Both are safe to reset.
Below are the causes, most common first. Do it by hand, or let Noah find the crash report, name what's failing, and clear the right thing on your approval (more at the end).
A bad extension is bringing it down
Crashing started after you installed an add-on, or after a macOS update, and you use one or more Safari extensions.
A Safari extension is a third-party add-on that runs inside the browser — an ad blocker, a password tool, a shopping helper. When one is built for an older version of Safari, it can crash the whole browser, not just itself. This is the first thing to rule out.
Fixopen Safari > Settings > Extensions and turn them all off. If the crashing stops, switch them back on one at a time, using Safari normally between each, until it crashes again — the last one you enabled is the culprit. Remove it, or update it from the App Store.
NoahNoah reads the crash report Safari leaves behind, tells you whether an extension is named in it, and points to the exact one — instead of leaving you to toggle add-ons and guess.
The cache is corrupt
Safari crashes at launch or across many sites, with no single extension or page to blame.
Safari keeps a cache — copies of images and page data — so sites load faster next time. If those files get damaged, Safari can choke on them. Clearing the cache is safe: it only removes the temporary copies, and sites rebuild them.
Fixin Safari > Settings > Privacy > Manage Website Data, click Remove All. For a deeper clear, enable the Develop menu (Settings > Advanced > “Show features for web developers”) and choose Develop > Empty Caches. Note this signs you out of most sites, which is normal.
One site crashes it
Safari is fine until you open one particular website, then it dies every time.
A single broken or very heavy page — a runaway script, a bad ad — can crash the tab or the whole browser whenever it loads. The tell is that the crash is tied to one site.
Fixclear just that site's data (Settings > Privacy > Manage Website Data, search the site, Remove), then reload. If it still crashes, open the page in a Private window — which ignores your cache and most extensions — to confirm it's the page and not your setup.
If it still crashes: a clean slate
If none of the above sticks, move Safari's saved state aside so it opens fresh. Quit Safari first, then in Finder press ⌘ ⇧ G and go to ~/Library/Saved Application State/; drag com.apple.Safari.savedState to the Desktop. Reopen Safari — it forgets its last session (and the stuck tab that may have been crashing it) and starts clean.
Frequently asked questions
Why does Safari keep quitting unexpectedly on my Mac?
Almost always a bad extension, a corrupt cache, or one broken page. Turn off all extensions first (Safari > Settings > Extensions); if that stops it, re-enable them one at a time to find the culprit. If not, clear website data and test any site that crashes it in a Private window.
Will clearing Safari's cache delete my bookmarks or passwords?
No. Clearing the cache and website data removes temporary files and signs you out of sites, but your bookmarks, history, and saved passwords are stored separately and stay put.
How do I find out which Safari extension is crashing it?
Disable every extension, then turn them back on one at a time, using Safari normally between each. The one that brings the crash back is the culprit — remove or update it. Noah can also read the crash report and name it directly.
Safari crashes the instant I open it — what do I do?
You can't reach the menus, so reset its saved session: quit Safari, go to ~/Library/Saved Application State/ in Finder, and move com.apple.Safari.savedState to your Desktop. Safari reopens without the tab that was crashing it.
Could a Safari crash be a virus?
Very unlikely. Repeated Safari crashes are almost always an extension, cache, or page issue — not malware. Work through those first. Noah can confirm by reading the crash report.
Commands in this guide are standard, read-only macOS diagnostics unless noted; anything that changes your system is called out. When in doubt, back up first with Time Machine.