Wavebox on a Mac, and who it actually suits

Two searches lead here. The first comes from someone with forty tabs and six logins who has just heard the phrase "app browser" and wants to know whether Wavebox is the thing that fixes it. The second comes from someone already running it on a Mac, who has hit the free tier ceiling, or the account screen, or the annual price, and wants to know whether the next step is upgrading or leaving.

Both questions have the same answer underneath: Wavebox is a specific set of trade-offs, and whether they land well depends on three things that have nothing to do with the feature list.

What Wavebox is, in one paragraph

Wavebox is a Chromium browser rebuilt around apps instead of pages. Gmail, Slack, Notion, Asana and anything else with a URL become entries in a sidebar rather than tabs in a strip. It runs on macOS, Windows and Linux, and it keeps each group of apps in its own cookie container, so several accounts of the same service can stay signed in at once without private windows or profile juggling.

Because it is Chromium underneath, the parts that make Chrome familiar are still there. Chrome extensions install, the developer tools are the ones already known, and rendering behaves the way the rest of the web expects. What changes is the shell around the page: a persistent left rail, groups, a unified notification path, and a set of controls that assume the same app will be open all day rather than visited once.

The thing that makes it an app browser rather than a skin is the cookie container. Everything else on the feature list is arrangement. That one mechanism is what lets a work Gmail and a personal Gmail exist at the same time without either one noticing.

The account, and why it matters more than it looks

Wavebox creates an account during installation. Setup asks for an email address before the browser is usable, and that account is also what carries Profile Sync on the paid plans.

For a lot of people this is a non-issue. For some it is the whole decision. A vendor account means a second identity to manage, a second place a password ends up, and, if the setup is synced, browsing configuration held on someone else's servers. Companies with rules about where work data lives sometimes stop here. Individuals who have watched several products in this category get acquired sometimes stop here too.

Worth separating two different questions that get merged in reviews. The first is whether an account is needed to start. The second is where the setup lives once it exists. Wavebox answers the first with yes and the second with its own cloud, on Pro and above. Other products in the category answer differently: some need no account at all, some sync through storage the user already owns, and some, like Ferdium, are open source and can sync through a self hosted server or plain backups.

Neither answer is wrong. The mistake is discovering it in month three.

What the free tier actually allows

The free tier is where most evaluations end, so the numbers are worth stating plainly. Wavebox's free plan covers 2 spaces, with 2 apps in each, one extension, and one dashboard. Paid is 99 USD per year, which works out at roughly 8.33 USD per month, with a Teams plan at 12.50 USD per user per month.

Four apps total is a real constraint. A typical starting set is one email, one chat, one document tool and one project tracker, which fills the free tier exactly and leaves no room for the second account that started the search. Anyone whose actual problem is three Gmails will be looking at the paid plan on day one.

That is not a criticism, it is a scoping decision, and it is the correct one to understand before installing. The useful comparison is not free versus paid within one product. It is what 99 USD per year buys here against what the same money buys elsewhere, given the specific set of apps and accounts in play.

Setting it up on a Mac without doing it twice

Most first attempts in this category fail the same way. Everything gets added at once, the sidebar becomes a second tab strip, and a week later the browser is back. A setup that survives is built in a different order.

Start from accounts, not apps. Write down every identity that has to stay signed in during a normal day: work Gmail, personal Gmail, the client's Google Workspace, two Slacks on different emails. That list is the real requirement, and it is what decides whether a free tier is viable before anything is installed.

Then group by context rather than by vendor. A group holds one cookie container, so everything inside it shares a session. Putting the work Gmail and the personal Gmail in the same group defeats the mechanism. Putting the work Gmail, the work Slack and the work Notion together matches how a working hour actually runs, and switching groups then switches the whole context at once.

Add apps in the order they get opened, and stop at the free ceiling deliberately. Two spaces with two apps each is enough to test the thing that matters, which is whether two accounts of one service genuinely stay separate. That test takes an afternoon and answers the question the reviews cannot.

Leave link handling until last. The single behaviour that decides whether the setup holds is what happens when a link arrives from outside the browser. A shared document link opened under the wrong identity produces a permission error, and after enough of those the habit of pasting URLs into the right window comes back. Any app browser worth keeping routes links into the app and the session that own them, and that behaviour is worth testing on purpose during a trial rather than discovering later.

Finally, decide the sync question before importing anything, because moving a configured setup between products later is the part nobody enjoys.

Where the daily friction tends to show up

Three patterns come up repeatedly when people who have used it for a while describe what they changed.

Cross-platform by design

Wavebox ships for macOS, Windows and Linux from one codebase. That is a genuine advantage for anyone moving between a Mac at home and a Windows machine at work, and it is dead weight for anyone who only uses a Mac. Cross-platform Chromium builds tend to bring their own window chrome and their own conventions rather than leaning on macOS behaviours. Whether that reads as consistency or as friction depends entirely on how many operating systems are in the picture.

Customizing an app's appearance

Wavebox's official material does not state a setting for injecting custom CSS or JavaScript into an app. It publishes Wavebox Flow, a tool for building an extension of one's own, which is a more capable route and a longer one. For someone who wants to hide one noisy sidebar in one web app, the gap between "paste four lines of CSS" and "build an extension" is the gap between doing it and never doing it.

The terminal question

There is no built-in terminal stated in Wavebox's own material. For most people this is irrelevant. For developers running commands against the same service they have open in a tab, it means the day is still split across two applications, and the app browser has consolidated everything except the window that gets used most.

Wavebox next to the alternatives

Figures reflect what each vendor states on its own site as of August 2026. Prices and terms change, so confirm before buying.

Product	Platforms	Account to start	Free tier	Paid	Sync
Wavebox	macOS, Windows, Linux	Yes, created during install	2 spaces, 2 apps each, 1 extension	99 USD per year	Their cloud, Pro and up
Shift	macOS, Windows	Only to buy the paid plan	5 spaces, 10 apps each	19.99 USD per month, 199.99 USD per year	Their cloud
Rambox	macOS, Windows, Linux	Yes	Unlimited apps, no workspaces or multi login	7 USD per month, 70 USD per year	Their cloud
Ferdium	macOS, Windows, Linux, FreeBSD	No	No limit, Apache-2.0 open source	None	Own server or manual backup
Sidekick	macOS, Windows, Linux	Yes	Shut down	Shut down	Their cloud

The Sidekick row is the one to read twice. It was acquired by Perplexity and has shut down, with its site now forwarding to Comet. Recommendations for it are still ranking in search results. Confirming that a product is still taking new signups belongs at the start of any shortlist in this category, not at the end.

Read the free tier column as the real comparison. Ferdium's has no cap and no vendor account, and the trade is community support rather than a company. Shift's is the most generous among the commercial options at 50 apps across five spaces, and its paid plan is the most expensive on the list. Rambox does not cap apps but keeps workspaces and multi login behind Pro, which puts the deciding feature on the paid side.

Who it fits, and who it does not

It fits someone on more than one operating system who wants the same setup on each, is comfortable with a vendor account, mostly needs organization rather than deep customization, and can live inside four apps for free or is happy to pay annually.

It fits less well in three cases. A Mac only user pays for portability that never gets used. Someone who wants to reshape how a web app looks finds the route runs through building an extension. Someone who wants no vendor account at all is stopped at the installer.

There is a fourth case that shows up less often in reviews and more often in practice. Someone whose day alternates between a web app and a command line spends it in two applications regardless of how well the browser is organized, because the terminal is not one of the things being gathered. Consolidating nine web apps and leaving the tenth window untouched is still a real improvement, but it caps how much the switching cost can fall.

None of those are defects. They are the shape of the product, and the shape is stated openly enough to check in advance. The full row by row breakdown, including platforms, account requirements and sync, is set out in the comparison with Wavebox, and the underlying mechanism that all of these products depend on is explained on the Workspaces page.

What to change first

Write down the number of accounts that must stay signed in at once, the number of operating systems in daily use, and whether a vendor account is acceptable. Those three lines eliminate most of this category in a couple of minutes, well before any trial is installed. Then read the free tier row on each remaining candidate, including SpaceDeck, and test the shortlist with the actual accounts rather than a sample set.