Setting up Opera on a Mac for work

Downloading Opera on a Mac takes two minutes. Making it better than whatever it is replacing takes about twenty, and most of that time goes into four settings that are off by default or hidden behind a menu nobody opens. Skipping that step is why so many trials end with the browser sitting unused in the dock after a week. This guide covers what to change on day one, what to put in the sidebar, how to stop tabs from quietly discarding work, and the one problem that no amount of configuration in this browser will solve.

Before installing: check which Opera is being downloaded

Opera publishes several desktop builds and the names sit close together. The main Opera browser is the one this guide covers. Opera GX is aimed at gaming. Opera Air is a separate build. Opera Neon is positioned around agents and automated tasks. Opera Mini is mobile only.

Installing the gaming build, finding it loud, and concluding that Opera is not a work browser is a common and avoidable waste of an afternoon. The download page separates them clearly, so the only requirement is reading before clicking.

One more thing to know before starting. Opera is built on Chromium, and its developer documentation states that CRX packages, the format Chrome extensions ship in, run inside it. That means the sites and extensions in use today will almost certainly work, and the trial can be judged on features rather than on compatibility.

The four settings to change on day one

Vertical tabs. This is the highest-value change on a work machine and it is one toggle. Opera's own documentation describes turning on the vertical tab strip from Easy Setup, or by right-clicking any tab, and notes that the layout can be switched back at any time. Horizontal tabs shrink as they multiply, and past roughly ten open pages the titles become unreadable. Vertical tabs keep the title visible no matter how many are open, which matters most when six tabs belong to the same service and look identical.

Automatic tab grouping. Tab Islands is on by default. Opening a link from a page puts the new tab in the same island as its parent, so a chain of research stays visually connected. The toggle for automatically creating tab islands lives in Easy Setup, reachable from the three-line icon at the top right. Deciding whether to keep it within the first few days is worth doing deliberately, because automatic grouping is the feature people either rely on or actively resent.

Workspaces. Create three or four, name them, and give each an icon. They appear at the top of the sidebar, switch in one click, and a hotkey can be assigned. Workspaces can also be hidden rather than deleted, which is useful for a context that comes back once a month.

Default browser status. Not making Opera the system default is a legitimate choice. Keeping the old browser as the default means links from Mail and Slack open there, and Opera stays a dedicated work surface rather than a catch-all. That separation is easier to maintain than a rule about which tabs belong where.

How to divide Workspaces so they stay useful

The instinct is to create one workspace per client or per project. That usually fails within two weeks, because every client involves the same mixture of communication, production and admin, so switching contexts does not actually remove anything from view.

Dividing by type of work holds up better. Communication, production, research, and billing are four categories where the hands do genuinely different things, and switching between them clears the screen of everything irrelevant. A workspace that still feels cluttered after switching is usually a sign it was divided along the wrong axis.

Three or four is the practical ceiling. Each additional workspace adds a thing to remember, and remembering which of seven containers holds a particular tab is its own tax. Assigning switching hotkeys is worth doing only after the number has settled, since the muscle memory is what makes them pay off.

Islands sit inside workspaces, so the two layers stack. A research workspace can hold five islands, each collapsed behind a coloured handle, expanded only when needed. Naming and colouring an island is done by hovering its handle, and clicking the handle collapses it.

What belongs in the sidebar, and what does not

The sidebar messenger panels are the part of Opera with no equivalent in a stock Chrome install. Opera's Mac page lists Facebook Messenger, WhatsApp, Discord, Bluesky, Slack and Telegram as services that can be pinned there and used alongside the current page.

The rule that makes this useful is restraint. Put exactly one service in the sidebar: the one checked most often during the day. Chat kept in the tab strip gets pushed aside as tabs accumulate, and every check costs the page currently in view. A pinned panel costs neither. Adding a second and third panel undoes the benefit, because the decision of which panel to open reintroduces the hesitation that was just removed.

What does not belong there is anything wide. The panel is narrow by design, which suits a message list and suits tables, dashboards and admin consoles very badly. Panels that go unused should be removed from the sidebar entirely so the remaining one is unambiguous.

The constraint to plan around is accounts. One account per service, per profile. Three client Slack workspaces produce one panel and two tabs, and no setting changes that.

Stopping tabs from throwing away work

This is the setting that prevents actual damage, and it is the one most people never touch. Chromium-based browsers throttle tabs that have been out of view and eventually deactivate them to reclaim memory. Opera's help index lists tab snoozing and a battery saver among its features, which is the same mechanism under a different name. The symptom is identical everywhere: a tab left open since morning reloads on click, and anything typed into it is gone.

The fix is three steps. Find the sleep or memory setting. Pick the two or three services that must never reload without warning, usually anything with a text box in it, and exclude them by site. Then leave the machine alone for an hour and check that a message sent to one of those services actually produces a notification, because a throttled tab can appear awake while delivering nothing.

Power settings matter here too, and they are easy to mistake for a browser problem. If the slowdown only happens on battery, the cause is the Mac's energy settings rather than the browser, and changing browsers will not touch it. Checking the system energy settings and the browser's own battery saver together takes less time than a migration.

Notifications pass through two gates on macOS

A web notification has to clear two separate permissions before it reaches the screen. The first is per-site, granted inside the browser. The second is per-application, granted in the Mac's system notification settings, where each browser appears under its own name. If either is closed, nothing arrives, and the screen gives no clue about which one is responsible.

Two situations catch people out. The first is switching browsers: site permissions belong to the old browser, so every service has to grant permission again in the new one, and the silence that follows looks like a bug. The second is a focus mode left switched on, which no amount of browser configuration will fix.

Granting notification permission to everything is worse than granting it to nothing. When product updates and marketing sit in the same stream as a client waiting for an answer, the important one gets missed. Permit only the services where a slow reply keeps someone waiting, and check the rest deliberately. That short list also answers the earlier question of which service belongs in the sidebar.

Ten minutes of pruning, which most trials skip

Opera arrives with a lot switched on: an ad blocker, a free VPN, a music player, a shopping cashback feature, a unit converter, tab emojis, a personalised news feed on the start page and a built-in AI assistant. On a personal machine that variety is part of the appeal. On a work machine it needs a pass with the pruning shears, and the pass is short.

Keep the ad blocker. It needs no maintenance and it cuts page weight on documentation sites, knowledge bases and anything ad-supported that gets opened dozens of times a day. Keep the VPN available but switched off unless there is a reason, and check with whoever owns the security policy before routing a work session through it, since that is a decision with consequences beyond the browser.

Empty the start page. A new tab that offers news headlines and shopping deals is working directly against someone trying to stay inside one task, and the feed is configurable rather than fixed. This single change has more effect on concentration than any grouping feature.

Remove sidebar panels that are not being used. The sidebar is the fastest surface in the browser precisely because it holds one or two things, and every additional icon dilutes that. The same applies to the AI assistant panel: leave it if it gets used, remove it if it does not, rather than letting it occupy the slot by default.

None of this is a criticism of a browser that costs nothing and includes a great deal. It is simply the difference between a browser configured for browsing and one configured for work. Ten minutes spent here is what decides whether the trial ends with a browser that feels calmer than the previous one or noisier, and noisier is what most abandoned trials actually report.

Where this setup stops

Everything above addresses one class of problem: too many tabs, hard to find, losing state. It does not address accounts. Workspaces separate tabs, not sessions, so two accounts on the same service cannot be signed in at once no matter how the workspaces are named.

The usual free workaround is separate browser profiles, which do separate the session. The cost is that each profile is a full window, so four contexts produce four identical-looking windows in the app switcher, and macOS window management cannot tell them apart. Mission Control, Stage Manager and the application switcher all operate on windows, and none of them can see tabs at all, which is the structural reason a heavily-tabbed browser never feels organised on a Mac no matter how tidy the strip looks.

The alternative is giving each web app its own window and its own session from the start, which is the arrangement described under Workspaces and detailed on Features. Which services are supported is listed on Supported apps, and Compared with Wavebox is the fastest way to see how tools in this category differ on notifications and price.

What to change first

Turn on vertical tabs, create three workspaces divided by type of work rather than by client, put one chat service in the sidebar, and exclude two sites from sleeping. Run that for a week without migrating anything else. If the remaining complaint is about finding tabs, the setup solved it at no cost. If the remaining complaint is that a second account still has nowhere to live, that is the boundary of what settings can do, and SpaceDeck shows what the next step costs.