Running Brave on a Mac as your work browser

Installing Brave on a Mac takes about a minute. Deciding how to actually work in it takes longer, and most guides stop at the install. The hard part shows up on day three, when a client dashboard stops responding because the blocker is too aggressive, or when two Gmail accounts have to be open at once, or when the twenty web apps that were annoying in Chrome turn out to be exactly as annoying in Brave. The browser change fixed one class of problem and left another class untouched. Knowing which is which before committing saves a week.

What changes, and what does not

Brave is built on Chromium. That means the extensions, bookmarks, and saved passwords from Chrome carry over, the keyboard shortcuts are the same, and pages render identically. The switching cost is genuinely low.

What changes is the blocking. Ad and tracker blocking is compiled into the browser rather than added as an extension, which has a consequence beyond page speed. Brave describes the arrangement this way:

Since Shields are patched directly onto the open-source Chromium codebase, they don't rely on MV2 or MV3. Source: brave.com

Extension formats change. Chrome retired Manifest V2 and a lot of blocking extensions went with it. A blocker that lives in the browser itself is not exposed to that. Pages also load faster, which is real but small: a fraction of a second per page.

What does not change is the shape of the day. Twenty web apps stacked in a tab strip behave the same in every Chromium browser. Tabs shrink as the count rises, and past roughly ten the labels stop being readable. Once three Slack tabs sit side by side there is no way to tell them apart by looking. That problem comes from the container, not the brand, so it survives the switch intact. Treating these as two separate problems, with two separate fixes, is the whole trick.

Importing from Chrome without importing the mess

The import dialog offers bookmarks, history, saved passwords, and extensions in one pass, and taking all of it is the default behaviour. It is also how a browser switch ends up feeling like no change at all. The bookmark bar that was already unusable arrives unusable. The forty extensions accumulated over four years arrive too, including the three that stopped being maintained and the two that overlap with blocking that is now built in.

A more useful sequence is to import bookmarks and passwords, skip extensions entirely, and then add extensions back one at a time as a specific task demands one. Most people finish the week with four or five instead of forty, and the ones that never got re-added turn out not to have been missed. This also removes a common source of confusion during a trial: when a page misbehaves in a fresh browser with no extensions, the cause is the browser or the site, and the diagnosis takes two minutes instead of an afternoon of disabling things one by one.

History is the one import worth thinking about separately. It is useful for finding that article from last Tuesday and it is also the thing most likely to autocomplete a personal URL in front of a client during a screen share. On a machine used for both work and personal browsing, leaving history behind and starting clean is a defensible choice.

Three settings worth deciding on day one

The settings screen is long and reading it top to bottom is a waste of an afternoon. Three decisions cover the working setup.

Blocking strength, adjusted per site. The lion icon in the address bar controls blocking for the site currently open. Older internal tools, timesheet systems, and client admin panels sometimes have buttons that stop responding when trackers are blocked, because the button and the tracker are the same script. The durable pattern is to leave the global setting strong and lower it only for the specific sites that break. Lowering the global setting to fix one page removes the reason for the switch.

The default search engine. Brave ships its own search as the default and it can be changed in settings. If a team shares search links, or a workflow depends on a particular engine's operators, set this on the first day rather than discovering the mismatch mid-task.

What opens at launch. Either restore the previous session or pin a fixed set of pages. Skipping this decision means the first few minutes of every morning go to hunting for yesterday's tabs.

One more item is worth settling early: whether Brave becomes the system default browser. Leave it unset and links clicked from Mail or Slack open in the old browser, which quietly produces a state where the same service is logged in under different accounts in two different browsers. On a client dashboard that gets confusing fast. During a trial period, keeping the old default and opening Brave manually is the cleaner arrangement.

Two accounts on the same service

This is where most work setups actually fail, and no amount of settings tuning touches it. Two Gmail accounts, two Slack workspaces, a client's admin panel and a personal login on the same platform: these need separate storage, not separate settings.

Brave added containers in July 2026. The official description is narrow and worth reading literally:

cookies and storage are not shared outside of the container, even when visiting the same site Source: brave.com

Containers are built into Brave 1.92 on Windows, macOS, and Linux, with Personal, Work, Social, and School included by default. A tab is assigned to a container by right-clicking it and choosing one. Profiles, the older Chromium mechanism, are also available and work differently: a profile gets its own window, its own Dock behaviour, and its own everything.

	Containers	Profiles
Unit	A tab	A window
Separate window	No	Yes
Separate extensions and settings	No	Yes
Risk of acting under the wrong account	Higher, both live in one window	Lower, windows are visually distinct
Best for	Two or three logins, occasional use	Full separation of work and personal

The practical rule: if sending a message from the wrong account would be embarrassing or expensive, use profiles, because the visual separation is doing safety work that a tab badge cannot do. For casual splits, containers are lighter. A workable hybrid exists: one profile for work and one for personal, with containers used inside the work profile to keep individual client logins apart. That gives hard separation where the consequences are real and cheap separation where they are not.

Sync has no account, and that cuts both ways

There is no Brave account to sign into. Devices are joined into a sync chain instead. Enabling sync on the first machine produces a 24 word code, and entering that code on a second machine, or scanning a QR code, joins them. Bookmarks, passwords, and open tabs are then shared. Encryption happens on the device, with the key held by the user, so the sync servers are not able to read the contents.

Two consequences matter in practice.

Losing the code means losing the way back in. No account means no password reset. If every device on a chain is wiped, the chain is gone. Any still-connected device can redisplay the code, so recovering it is possible right up until the last one is reset. Storing it somewhere other than the devices themselves is the obvious precaution.

Sync is sharing, not backup. Deleting a bookmark on a laptop deletes it on the desktop. Tidying a bookmark folder at home at night and finding it missing at the office the next morning is the standard version of this surprise. Nothing about the feature is broken; it just means every cleanup is a cleanup everywhere.

What is free and what is not

Brave is free, and several bundled services are not. Knowing the line in advance avoids planning around something that turns out to be paid.

Feature	Free tier	Paid
Ad and tracker blocking	Unlimited	No paid tier
Sync	Unlimited	No paid tier
AI assistant	Basic use is free	Premium tier exists
Video calls	Hosting up to 4 people, unlimited calls and length	5 or more participants, recording
VPN and firewall	Not included	9.99 USD per month or 99.99 USD per year

Video calls are usable for small internal check-ins at no cost: four participants, with no cap on how many calls or how long they run. Recording and larger meetings require the paid tier. Four is enough for a standup and not enough for a client presentation, which is a fair description of where that line sits.

The VPN is device-wide rather than browser-only, and one subscription covers up to 10 devices across Android, iOS, macOS, and Windows. That is a different product category from the proxy features some browsers bundle for free, and it duplicates whatever corporate VPN may already be in place. Worth checking before paying for it twice.

Notifications end up managed in two places

On macOS, browser notifications are governed twice: once by the permission granted to the site inside the browser, and once by the notification settings for the browser app in System Settings. A permission granted months ago and forgotten is the usual reason something keeps making noise after it was supposedly silenced, and a Focus mode is the usual reason an important alert never arrived.

Brave prompts for permission the first time a site asks. Approving reflexively builds a permissions list that is unreadable within a few months. Reviewing the site permissions list and keeping only what should genuinely interrupt is the maintenance task nobody schedules and everybody eventually needs.

There is a second effect worth planning around. Background tabs get throttled to save resources, so a chat or monitoring dashboard buried deep in the tab strip may deliver late or reload on return. The tools that most need to be live are precisely the ones that should not be sitting in a tab.

The cleanest test of whether notifications are configured correctly takes one day. Note every alert that arrives and mark whether it caused an action or an interruption. Anything that never causes an action has its permission revoked at the site level rather than muted at the operating system level, because a muted alert still costs the browser the work of delivering it and still sits waiting in the notification centre.

What to change first

Set blocking strong and lower it per site, decide how two accounts get separated before the first mix-up rather than after, and write the sync code down somewhere that is not a device. Then count the web apps returned to more than ten times a day: everything on that list is being managed by a container macOS does not recognise, since Mission Control and the app switcher operate on windows, not tabs. Moving those into windows of their own is what Workspaces and Features describe, and SpaceDeck lists what that costs.