A Brave browser review from someone who works in ten web apps

Most reviews of Brave are written for a reader who browses. They measure page loads, count blocked trackers, and compare privacy defaults. That reader exists, but a different one has been searching the same terms lately: the person whose workday is Gmail, Slack, Notion, a CRM, a billing dashboard, two client Slacks and a design tool, all open at once, all needing to stay signed in. For that person, the interesting question is not whether Brave blocks more than Chrome. It is whether switching browsers changes anything about the day at all.

This review answers both, separately, because the answers point in different directions. Brave is a genuinely strong browser on the first question. On the second, it inherits a limit that every Chromium browser inherits, and no amount of Shields configuration moves it.

What actually changes in the first hour

Brave is built on Chromium, which means the switching cost is close to zero. Extensions from the Chrome Web Store install. Passwords and bookmarks import. Keyboard shortcuts are the same ones already in muscle memory. Nothing about the first hour feels like learning a new tool, which is unusual for a browser change and is the single biggest reason Brave retains people who try it.

What is different is what happens without being asked. Brave Shields are on for every site by default, with no list to subscribe to and no settings to configure. According to Brave's own description of Shields, the browser applies filter lists from the EasyList and EasyPrivacy projects, the uBlock Origin project, and lists Brave generates internally. It blocks third-party ads and trackers, partitions cookies so cross-site tracking breaks, randomizes the browser APIs most often used for fingerprinting, and can see through CNAME cloaking, which is the technique trackers use to disguise themselves as first-party resources.

The practical effect on a work machine is smaller than the marketing suggests and larger than skeptics expect. Internal tools and SaaS dashboards carry very few trackers, so a day spent inside Notion and a CRM looks about the same in any browser. The difference shows up on the open web: documentation sites, vendor pages, news articles, the twenty tabs opened while researching a purchase. Those load noticeably lighter, and they load that way on a fresh install with nobody configuring anything.

When a site does break, the Shields panel in the address bar turns protection off for that domain in one click. That single affordance matters more than it looks. It is the difference between a privacy tool that gets disabled entirely after the third broken checkout page and one that survives in daily use.

The premium layer, and what it costs to ignore

Brave ships several paid services alongside the free browser, and a fair review has to say what they are, because they are the reason some people find the product confusing.

Brave VPN is a subscription that runs at the device level rather than only inside the browser. Brave's VPN page states a strict no-logs policy verified through independent software and infrastructure security audits, more than 300 servers across over 40 regions, and coverage for up to 10 devices across Android, iOS, macOS and Windows on one subscription. It protects traffic from every app on the device, not just Brave.

Brave Leo is the built-in AI assistant. The free tier requires no account and no login. Brave states that conversations are not retained for model training, that chat history is stored locally on the device, and that both the free and premium tiers reach models from Mixtral, Anthropic and Meta. A feature called Bring Your Own Model connects a local or remote model instead. Premium raises usage limits and adds models.

Brave Rewards is the part that generates the most confusion. It is off until switched on. Turning it on means opting into Brave Ads, which appear as new tab images and push notifications rather than inside web pages, and which pay the viewer in Basic Attention Tokens. Those tokens can be sent to creators or exchanged. None of this activates on its own, and a person who never touches the token icon in the address bar will use Brave as an ordinary ad-blocking browser indefinitely.

The honest summary is that Brave is free and complete without any of the three. The premium layer is optional in the real sense, not the marketing sense.

The incidents that made people suspicious

A review that skips these is not a review. Two events account for most of the doubt that still shows up in search results, and Brave published its own account of both, which is the best place to read them.

In June 2020, a user noticed that typing certain crypto-exchange addresses into Brave's address bar produced a default completion with an affiliate code attached. Brave's post on the matter, published on 9 June 2020, called it a mistake in how affiliate codes were applied: the code was supposed to appear only in alternative suggestions that a user picks manually, not in the default that fires on the Enter key. The fix shipped in the 1.9.80 stable desktop release by switching the "Show Brave suggested sites in autocomplete suggestions" setting to off by default. Brave also stated that no user data was involved, that affiliate codes were never inserted into links on web pages, and that it confirmed with Binance that no revenue would be taken from the unintended completions.

Earlier, in December 2018, Brave Rewards showed creators in its tipping panel who had never signed up for the program, using their YouTube and Twitch channel images. Brave's update at the time apologised for it and changed the interface to label unregistered creators clearly and stop showing their channel images.

Both are real. Both were self-reported and fixed. What a reader does with that depends on the standard being applied: a browser that has shipped two bad defaults and corrected them publicly, or a browser that shipped two bad defaults at all. Neither reading is unreasonable, and neither has anything to do with whether the browser is good at the work in front of it.

Where a Brave review stops being about Brave

Here is the part most reviews never reach, because most reviews assume a reader with one identity.

Someone signed into three Gmail accounts, two Slack workspaces and a client's Notion cannot solve that with Shields, a VPN or an AI assistant. The constraint is the browser profile. In Chromium, and therefore in Brave, one profile holds one set of cookies. Two accounts for the same service means two profiles, which means two separate windows, two separate extension sets, two separate sets of open tabs, and a constant low-grade tax of checking which window is which before clicking a link.

Every Chromium browser has this shape. Brave does not make it worse and cannot make it better, because the profile model is inherited from upstream. Anyone whose real complaint is account juggling will switch to Brave, enjoy the cleaner pages for a week, and then notice the original problem is untouched.

That is the point at which the search term changes. The tool category that addresses it is the app aggregation browser: a browser that gives each web app its own persistent container so several accounts of the same service stay signed in at once, in one window. A walkthrough of how that model differs from profiles is in Workspaces, and the catalogue of services it covers is at Supported apps.

Brave against the two things it is usually compared with

	Brave	Chrome	App aggregation browser
Ad and tracker blocking	On by default, no setup	Extension required	Varies; not the purpose
Extensions	Chrome Web Store	Chrome Web Store	Often limited or absent
Several accounts of one service	Separate profiles, separate windows	Separate profiles, separate windows	Separate containers, one window
Notifications from many apps	Per site, scattered	Per site, scattered	Usually collected in one place
Built-in VPN	Paid subscription	No	No
Built-in AI assistant	Free tier, no account	Gemini integration	Varies
Cost	Free browser, paid extras	Free	Free tier plus paid tier

Reading down the columns makes the shape clear. Brave wins the privacy row outright and ties Chrome on almost everything else, because it is Chrome underneath. The third column wins nothing on privacy and exists entirely for the account and notification rows. These are not competing products so much as answers to different questions, which is why "should Brave replace Chrome" and "what should replace the way tabs are being used" have different answers.

Setting it up so it survives the first month

Most abandoned browser switches fail in the same two places, and both are avoidable.

The first is the import. Bringing over bookmarks and passwords but leaving the old browser as the system default produces a split brain: links clicked from Slack, Mail or a calendar invite keep opening in the old browser, and within a week half the session lives in each. Changing the default handler on the Mac at the same time as the import is what makes the switch stick.

The second is breakage blamed on the wrong thing. When a payment form, a single sign-on redirect or an embedded video fails, the instinct is to reopen the page in the old browser and conclude that the new one is unreliable. In most of those cases Shields is the cause and the fix is one click on the shield icon for that domain. Keeping a mental note of which sites needed it is worth doing, because the list is usually short and stops growing after the first fortnight.

Two settings are worth a deliberate decision rather than a default. Sync is off until a chain is created, and Brave states that unused sync chains expire after 12 months, with the associated server data eligible for permanent deletion after that. The token icon in the address bar is the entry point to Rewards, and leaving it untouched keeps the browser free of anything related to ads or tokens.

Who this browser is actually right for

Brave is a strong default for a person with one work identity who wants the open web to stop following them and does not want to maintain a filter list to get it. It is a strong default for a laptop that travels, where the VPN subscription covers the phone as well. It is a strong default for anyone who has been meaning to leave Chrome and keeps stalling because the migration looks expensive, since here it genuinely is not.

It is the wrong tool for a specific and increasingly common situation: four services, nine accounts, notifications arriving from every direction, and a window count that keeps climbing. Brave will make those windows lighter. It will not make them fewer, and window count is what the day actually costs.

Anyone in the second group who switches to Brave and feels disappointed has not chosen badly. They have solved a real problem that was not the problem they had.

What to change first

Install Brave, import from Chrome, and leave every default alone for a week. That answers the privacy question with no configuration and no reading. If at the end of the week the tab bar is still unreadable and the same three accounts are still being logged out of each other, the browser was never the variable. Compare how a per-app container model handles that against browser profiles at SpaceDeck, and decide between the two problems before spending any more time on either.