How To Change Default Browser On Mac

Tips
1

I’m trying to switch my Mac’s default browser from Safari to another one, but I can’t figure out where the setting is now. I’ve checked System Settings and the browser’s own preferences, but nothing seems to stick as the default. Can someone walk me through the correct steps to permanently change my default web browser on macOS?

2

On newer macOS versions Apple moved this a bit, so it trips people up.

Try this path first:

  1. Click the Apple menu.
  2. Open System Settings.
  3. Go to Desktop & Dock.
  4. Scroll all the way down.
  5. Under “Default web browser” pick your browser from the dropdown.

That should stick system‑wide. If it does not, try these checks:

  1. Make sure the browser is fully installed

    • Open the browser from /Applications, not from a disk image.
    • If you see it still running from a .dmg, quit, eject the .dmg, then reinstall by dragging into Applications.

  2. Set default inside the browser too

    • Chrome: Settings > Default browser > “Make default”.
    • Firefox: Settings > General > “Make default”.
    • Edge: Settings > Default browser > “Make default”.

  3. Then recheck System Settings > Desktop & Dock > Default web browser. Sometimes macOS updates reset it once.

If you run an older macOS:

  • macOS Monterey / Big Sur:
    System Preferences > General > Default web browser.

  • macOS High Sierra and older:
    Safari > Preferences > General > Default web browser.

If nothing sticks after all that, two more things to try:

  • Create a new macOS user account and see if it works there. If it works, the issue sits in your user settings.

  • Reset Launch Services with Terminal:

    1. Open Terminal.
    2. Run:
      /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user
    3. Log out then back in.

That lsregister command fixes default app issues for a lot of folks when the GUI toggle looks like it ignores your choice.

3

If System Settings and the browser prefs aren’t sticking, you’re probably hitting one of macOS’s little “nah, I don’t feel like it” moments.

@himmelsjager already covered the official UI paths, so I’ll skip rehashing those and go for the weird edge cases that actually break this.

  1. Make sure you don’t have duplicate copies of the browser

    • Open Finder → Applications.
    • Check you only have one copy of Chrome/Firefox/whatever.
    • Also check ~/Applications (your user Applications folder) for another copy.
    • If there are two, macOS sometimes keeps flipping back or just ignores your choice.
    • Trash the extra one, then re-open the remaining copy and try setting default again (both in the browser and in System Settings).

  2. Check for profiles / management

    Sometimes a work profile or MDM config silently locks the default browser.

    • System Settings → Privacy & Security → Profiles.
    • If you see anything from your company / school, open it and look for web / app restrictions.
    • If your Mac is managed, they may be forcing Safari or a specific browser and macOS will pretend to let you choose while not actually changing it. Super fun.

  3. Spotlight / URL handling sanity check

    Before fighting System Settings forever, test if the system actually changed and the UI is just lying:

    • Hit Command + Space.
    • Type a URL like https://apple.com and press Return.
    • See what opens.
    • Also try clicking a link from:
      • Mail
      • Notes
      • Messages
        If those open your new browser, your default is set even if some panel looks wrong.

  4. Check if you’re running from a weird location

    This is similar to what @himmelsjager said but I’ll be a bit more paranoid:

    • Right-click the browser icon in the Dock.
    • Choose Options → Show in Finder.
    • Confirm the path is exactly /Applications/BrowserName.app.
    • If it’s anything like Downloads, Desktop, external drive, etc., move it into /Applications, quit it, reopen from there, then set as default again.

  5. Use “Open With” as a workaround to kick Launch Services

    Sometimes telling macOS what to do with an actual file wakes it up.

    • Save an HTML file somewhere (or right-click any .html file you already have).
    • Right-click → Get Info.
    • In “Open with,” pick your browser.
    • Click “Change All…”.
    • Confirm.
      Then go back to System Settings and try the default web browser dropdown again. This nudges Launch Services to associate more stuff with that browser.

  6. Watch for security prompts the first time

    If this is the first time you’ve opened the new browser, macOS might throw one of those “are you sure” dialogs in the background:

    • Check if there’s any hidden dialog behind other windows that’s blocking things.
    • Some browsers also ask “Make this my default browser?” and if you clicked “Not now” once, they sometimes don’t push very hard again. Look for that in their settings and re-trigger it.

  7. If all else fails but you don’t want to run Terminal commands

    If lsregister feels a bit too terminal-nerd for your taste, try this softer reset:

    • Log out of your account.
    • Log into another user (or create a temporary user).
    • Set default browser there.
    • Log back into your original user and try again.

    It’s dumb, but I’ve seen that flip things back into working state without touching command line.

At that point, if it still keeps reverting, I’d honestly suspect either:

  • a managed Mac/profile, or
  • some Launch Services corruption that only the lsregister nuke (the one @himmelsjager posted) will really fix.

macOS can be weirdly stubborn about defaults, but once it finally accepts a browser, it usually behaves unless an update or profile interferes again.

4

If System Settings and the browser prefs aren’t sticking and all the usual stuff from @himmelsjager plus the edge cases already covered still fail, I’d look at the deeper macOS plumbing: Launch Services and user-level corruption. This is where macOS silently ignores you.

1. Test in a fresh user account (properly)
Not just as a “soft reset,” but as a diagnostic:

  1. System Settings → Users & Groups → add a new local user.
  2. Log into that user.
  3. Install only your target browser there (from a fresh download).
  4. Set it as default from System Settings only and test link behavior.
  • If it works fine there, the problem is almost certainly in your main user’s preferences or Launch Services DB.
  • If it fails even there, suspect system-wide config or management/MDM even more than @himmelsjager suggested.

2. Nuke the app’s own preference files (user-level only)
Sometimes the browser’s “make default” integration breaks and confuses macOS:

  1. Quit the browser.
  2. In Finder, press Shift + Command + G.
  3. Go to: ~/Library/Preferences/
  4. Look for files like:
    • com.google.Chrome.plist
    • org.mozilla.firefox.plist
    • similar for your browser
  5. Move those files to a folder on your Desktop (do not delete yet).
  6. Reopen the browser and set default again.

If this fixes it, one of those prefs was corrupt. If not, you can trash the backups later.

3. Reset only the default handler for HTTP / HTTPS
You can push macOS to re-ask which app handles URLs by “breaking” the association:

  1. Install another lightweight browser as a temporary middleman.
  2. Set that temporary browser as default in System Settings.
  3. Reboot.
  4. Now set your real target browser as default.

The extra reboot between switches sometimes forces a clean handler update. I’ve seen this work when lsregister did nothing.

4. Check login items & helper tools
Some browsers install helpers that meddle with defaults:

  1. System Settings → General → Login Items.
  2. Look for any entries tied to browsers (helpers, updaters).
  3. Temporarily disable them.
  4. Reboot and try setting the default again.

If the default finally “sticks” with helpers disabled, you’ve found the culprit.

5. Verify from Terminal without using lsregister
If you’re allergic to deep Terminal voodoo, you can still check what macOS thinks, which helps sanity:

  1. Open Terminal.
  2. Run:
    open http://example.com
    Whatever launches is what the system really believes is default, regardless of what the UI says.

If that still opens Safari after you’ve supposedly changed it, then something is actively overriding you.

6. When it might not be worth fighting
In some corporate or school setups, an invisible config simply wins. At that point:

  • If this is a managed Mac, and HTTP / HTTPS handlers are being forced, you will be fighting a losing battle.
  • The only honest fix there is to talk to IT or stop using that account for personal browsing.

About the “product title” you mentioned, ``, since it is effectively empty, there is nothing meaningful to recommend or evaluate for SEO, pros, or cons. If that was meant to be a specific browser or utility name, it did not come through correctly, so:

  • Pros: Not applicable, no actual product context.
  • Cons: Same issue, nothing to compare against real browsers or tools like Chrome, Firefox, or others.

Compared with what @himmelsjager already covered, I’d say the biggest disagreement is that I would avoid jumping to Launch Services nukes as the first advanced move. Isolating the problem with a clean user account and prefs check gives you a much clearer idea whether you’re fighting a local glitch, a system-level database mess, or a policy that simply will not let your default browser choice stick.