Picking a Chromium browser for a Mac without losing your extensions

Read three comparison posts about the best chromium browser for mac and a strange pattern shows up. The product names differ, but the performance sections say nearly the same thing. There is a reason for that. Chrome, Edge, Brave, Vivaldi, Opera and Arc are all built on the same engine. When the engine is shared, page rendering and web standards support stop being a useful axis. What is left is narrower and more practical: what each vendor changed in the defaults, what each vendor added on top, and whether the project is still being developed.

What "Chromium" actually covers

Chromium is not a product. It is an open source browser project that other vendors build on. The project describes itself plainly:

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web.

That base includes the rendering engine, the JavaScript engine, the process isolation model that keeps one site from reading another, and the extension runtime. Whether a site loads correctly, whether a sandbox escape gets patched, whether a new CSS feature works: almost all of that is decided in this layer, and it is shared.

The practical consequence matters more than the architecture. Most business web apps are tested against Chrome. Any Chromium browser inherits that testing for free. It also means that comparing two Chromium browsers on "does this site work" produces almost no signal. They will both work, or both fail, for the same reason.

The differences live above and around the base. Brave states publicly that it makes changes and removals with every Chromium release, including proxying Google service calls through its own servers and removing several telemetry and ad-targeting APIs. So even the shared layer is not identical once it ships.

Where Chromium browsers actually differ

Three axes cover almost every real difference. Keeping them separate makes comparison posts easier to read.

Defaults. Whether ads and trackers are blocked out of the box, how third-party cookies are handled, which search engine is preselected. This is what the first hour feels like.

What sits on top. Tab grouping, workspaces, sidebars, built-in mail and calendar, an AI assistant, a VPN. This is where vendors compete, and where switching costs show up later.

Project health. Whether new development is still happening, whether the product has moved to maintenance, whether the company changed hands. For a tool that holds a working environment, this outranks the feature list.

Comparison posts usually cover only the middle axis, because it photographs well. Regret usually comes from the first and the third. Defaults are felt every day. Project health is felt three years later.

Sync and the first-run defaults are worth ten minutes

The first launch of a new browser asks two questions that are easy to click past and annoying to undo later: where settings sync to, and which search engine sits behind the address bar.

Sync is not neutral across this family. Chrome and Edge sync through a Google or Microsoft account. Brave reimplemented sync so that data is encrypted on the device and never reaches Google servers, and the sync chain is joined with a code rather than an account login. Vivaldi encrypts each item in the browser before sending it to its own servers in Iceland, where it can only be decrypted with the user's key. The practical difference shows up when a laptop is replaced: an account-based sync restores from a login, while a code-based chain needs the code, which has to be stored somewhere that survives the old machine.

The search default is the other one. It is usually the largest revenue line for a free browser, which is why it is preselected and why changing it takes two clicks rather than zero. Setting it deliberately on day one avoids weeks of results that do not match what the work needs.

The Chromium browsers available on macOS

Prices below come from each vendor's published pages.

Browser	Blocks ads by default	Main additions	Cost
Chrome	No	Profiles, tab groups	Free
Edge	No	Profiles, workspaces, sidebar	Free
Brave	Yes	Shields, Leo AI, VPN sold separately	Browser is free
Vivaldi	Optional	Workspaces, tab stacks, mail, calendar, feeds	Free
Opera	Optional	Workspaces, sidebar messengers	Free
Arc	No	Spaces, sidebar-first layout	Free

Brave is the outlier on defaults. Shields blocks trackers, cross-site cookie tracking and fingerprinting from the first launch, and Brave also strips known tracking parameters from URLs. The paid part is not the browser. Brave VPN is $9.99 per month or $99.99 per year, and one subscription covers up to 10 devices across macOS, Windows, Android and iOS. Brave Leo, the built-in assistant, has a free tier and a premium tier with more models.

Vivaldi carries the most on top. Workspaces let tabs be filed by category so only one category is visible in the window at a time, and they combine with tab stacks and split-screen tab tiling. Beyond tabs, Vivaldi ships an IMAP and POP3 mail client, a calendar and a feed reader inside the browser. All of it is free on macOS, Windows and Linux.

Arc deserves a project-health check before a feature check. The developer moved Arc to maintenance in 2025 and shifted new development to a different product. Arc still installs, still runs Chromium extensions, and still receives the underlying security updates. What it does not receive is new work.

Extensions carry over, with three things to check first

Extension compatibility is the main reason to stay inside the Chromium family. Items from the Chrome Web Store generally install and run in Edge, Brave, Vivaldi and Opera. Password managers, translation tools, screenshot tools and meeting transcribers usually move without any setup.

Three checks are worth doing before the switch, in this order.

Admin-distributed extensions come first. Extensions pushed by an IT administrator through enterprise policy are the most likely to be Chrome-only in practice, even when the code would run elsewhere.

Do not stack two ad blockers. In a browser that blocks by default, adding a blocking extension puts two filter systems on the same page. The usual symptom is not more blocking. It is a broken page, and a hard one to debug.

Run the single sign-on flow once. Login redirects are sensitive to cookie partitioning and blocking rules. A Chromium browser that renders every site perfectly can still stall on a corporate identity provider. Ten minutes of testing before a workday is cheaper than finding out during one.

Profiles solve account separation by adding windows

For anyone holding several Google accounts, the real comparison axis is not speed. It is how accounts stay apart. Every Chromium browser answers this the same way: profiles. Bookmarks, history, passwords and cookies are separated per profile, so two accounts on the same service can stay signed in at once.

The mechanism is reliable. The cost lands on window count. Profiles open in separate windows, so four accounts mean four windows, and each of those windows collects its own tabs. Separation is solved. Finding a specific screen is now a two-step search: which window, then which tab inside it. That is worse than before.

Edge, Vivaldi and Opera add workspaces on top. A workspace is a named set of tabs, and switching a workspace changes what the window shows. It is a genuine improvement for tab volume. It is not an answer to account separation, because a workspace does not carry its own login state. Two accounts on the same service still need two profiles underneath.

This is why the shape of the separation matters more than the browser name. A design that gives each service its own place, rather than filing tabs into categories, is a different answer to the same problem, and the Workspaces page lays out how that split works. The feature breakdown on the Features page is a useful way to see which of these mechanisms solves login separation and which only solves tab clutter.

Notifications are throttled at the engine level

Every Chromium browser suspends background tabs to reclaim memory. Because the behavior comes from the shared base, switching products does not change it much.

For most tabs this is correct. An open article does not need a live connection. A chat tab is different. While suspended, its connection is not maintained, and messages arrive in a batch when the tab is brought forward. A message sent before a meeting can land 30 minutes late. Pinning a tab makes suspension less likely, but the behavior varies by version and is not a guarantee.

macOS adds a second layer. A web notification needs permission from the site inside the browser and permission for the browser itself in System Settings. If the system-level permission is missing, every site in that browser goes quiet at once, which looks like a browser bug and is not. Focus modes add a third layer, and they allow or block a whole browser rather than individual services.

The conclusion is structural, not product-specific. Time-sensitive conversations held inside browser tabs will be unreliable in any Chromium browser. They belong either in a dedicated app or in a tool where each service has its own place and suspension is decided per service.

Four questions that narrow the list

Answering these in order usually leaves one or two candidates.

How many accounts are in play? Two is comfortable inside Chrome profiles. Past five, window count becomes the dominant cost and a per-service layout is worth evaluating.

How many tabs are open on a normal day? Past thirty, workspaces earn their keep, which points at Edge, Vivaldi or Opera.

Is anything time-sensitive living in a tab? If yes, decide the notification path before the browser. The browser choice follows from it.

How long is this tool expected to last? For three years or more, check project health before the feature list.

Comparison posts answer the second question and skip the other three, because the other three cannot be screenshotted. In daily use they carry more weight.

Free browsers still differ in what they cost you

Price sorting fails here. Chrome, Edge, Brave, Vivaldi and Opera are all free, so the question becomes what funds them and how far their support reaches.

Funding models vary: default search placement, an in-house ad system, separately sold subscriptions, donations. None of these is inherently better, but funding shapes defaults. A browser that blocks ads by default has a revenue model that survives blocking ads. Reading defaults as a consequence of structure rather than philosophy makes vendor messaging much easier to parse.

Coverage is the other invisible axis. In tools that keep each web app in its own place, what matters is which services are supported as first-class entries, and that list is published on the Supported apps page. For cost comparison inside that category, the free tier boundary is more informative than the monthly figure: Wavebox, for example, keeps two groups and two spaces on its free plan and charges $8.33 per month billed annually for Pro, and the Compared with Wavebox page sets that against a different way of drawing the line. Remaining edge cases tend to be covered on the FAQ page.

What to change first

Start by counting accounts and tabs on a normal workday, then answer the four questions above before opening any download page. If the count is small, a second Chrome profile ends the discussion today. If the count is large and time-sensitive messages are sitting in tabs, the fix is a layout where each service holds its own place rather than a better tab manager, which is the approach SpaceDeck takes.