Mac backups won’t start in the browser? Chrome vs Safari vs Firefox (if/then decision tree)

Trying to start a backup from a website on your Mac—then nothing happens, it spins forever, or it keeps asking you to sign in again? The fastest way to fix it is to treat it like a browser-specific problem.

Use this if/then decision tree and stop as soon as it works.

Before you change anything: open the same backup page in a Private/Incognito window once. If it works there, your normal browser profile (cookies, extensions, cached site data) is the likely cause.

1. If the “Start backup” button does nothing (no new tab, no download, no progress)

This usually means a click is being blocked—by pop-up rules, a content blocker, or a permission prompt hidden behind the window.

• If you’re on Safari: go to Safari settings for the site and allow pop-ups (many backup tools open a separate auth or “job” window). Also check that a small permission sheet isn’t waiting behind the Safari window.
• If you’re on Chrome: check the small icon at the right side of the address bar (pop-ups blocked). Allow pop-ups for that site, then retry.
• If you’re on Firefox: look for the pop-up blocker bar at the top of the page. Choose “Allow” for the site.
• If the backup relies on a downloaded helper file: confirm your browser isn’t auto-blocking downloads from that site (Chrome is stricter than Safari here).

If you click “Start backup” and you briefly see a new tab flash and close, jump to section 3 (cookie/session loop).

2. If the backup starts, then fails immediately with “network error” (but your internet is fine)

Backups can be sensitive to privacy features that alter tracking/cookie behavior or block background requests.

• If it fails only in Safari: Safari’s cross-site tracking protections can break sign-in handoffs that a backup workflow depends on. Temporarily allow the site to use cookies (site settings) and retry. If it’s a corporate login flow, test in Chrome or Firefox to confirm it’s Safari-specific.
• If it fails only in Firefox: Enhanced Tracking Protection can block a required domain used for auth or upload. Try turning protection off for that specific site (shield icon), rerun the backup, then re-enable.
• If it fails only in Chrome: extensions (privacy, ad blockers, script blockers) are a common cause. Try a fresh Chrome profile or Incognito with extensions disabled and test again.

If it works in a private window but not a normal window, go to section 4 (extensions + cached site data).

3. If you keep getting signed out (or it loops back to sign-in when you start the backup)

A backup job often starts in one domain and completes in another (or opens a new tab to confirm permissions). If cookies are blocked or “third-party” cookies are restricted, the session can’t be carried through.

• If you’re on Chrome: check whether third-party cookies are blocked globally or for this site. If you see a cookie “eye”/privacy indicator in the address bar, use it to allow cookies for this site, then retry the backup.
• If you’re on Safari: try again after allowing cookies for the specific site (and temporarily relaxing cross-site restrictions only long enough to complete the backup). Safari is often the one that breaks “sign-in handoff” flows.
• If you’re on Firefox: disable Enhanced Tracking Protection for the site (shield icon) and retry. Some backup/auth endpoints get categorized as trackers even when they’re part of the workflow.

If changing cookie/tracking settings fixes it, you can usually re-tighten them afterwards—just keep an exception for the backup site if needed.

4. If it works in Private/Incognito but not in your normal browser profile

This points to one of three things: a bad cookie, stale cached site data, or an extension that modifies the page.

• Then first: disable extensions for the backup site (especially ad blockers, privacy blockers, password managers that autofill aggressively, “security” extensions, VPN/proxy extensions).
• Then: clear site data for only that backup site (not your whole browser history). You’re aiming to remove a broken session cookie without logging out of everything else.
• Then: sign in again, start the backup, and watch for a pop-up permission prompt or a new tab that must stay open.

If you need a quick confirmation test: create a new browser profile (Chrome/Firefox) or a new macOS user account, and try the backup once. If it works there, your main profile has the conflict.

5. If only one browser works, and you need a stable “default browser” choice

For backup workflows on a Mac, the most stable choice depends on what the backup site is doing.

• If the backup uses multiple sign-in redirects (SSO, corporate login, separate auth tabs): Chrome or Firefox tends to be more predictable than Safari because of Safari’s stricter cross-site behavior.
• If the backup triggers local-file downloads or a helper app: Safari can be simpler, but check its download and pop-up rules first.
• If you must use Safari: plan on adding a site-specific exception (cookies/pop-ups) rather than loosening privacy settings globally.

If none of the browsers work, it’s likely not “the browser” anymore—check whether a VPN, firewall, or content filter is interfering, or whether the backup service is having an outage.

Final thoughts

When a backup won’t start on macOS, testing the same workflow in Safari vs Chrome vs Firefox is a surprisingly efficient diagnostic. Differences in cookie handling, tracking protection, and extensions explain most “button does nothing” and “sign-in loop” cases.

If you want the safest approach, prefer site-specific exceptions (pop-ups/cookies) and minimal extension changes—just enough to get the backup completed.