An Opera browser review for people who work in the browser all day

Most Opera reviews are written for someone choosing a browser to read the web with. That is a different job from the one being done here. If eight hours a day are spent inside Gmail, Slack, Notion, a CRM and two admin consoles, the questions that decide the outcome are narrow: does the tab strip stay readable at forty tabs, can two accounts on the same service be open at once, and does a notification still arrive when the tab has been idle since morning. This review answers those questions and skips the page load benchmarks, because at this workload the renderer is almost never the bottleneck.

What Opera actually ships, stated plainly

Opera is a free desktop browser from Opera Norway, available for macOS, Windows, Linux, iOS, Android and Chromebook. Under the surface it is the same engine family as Chrome. Opera's own developer documentation states it directly:

Opera is based on Chromium, which means it is possible to run CRX files in Opera. Source: dev.opera.com

That single sentence settles a lot. Sites that render correctly in Chrome render correctly here. Extensions built for Chrome install here. The company's own product page puts the catalogue at over 2,500 Opera add-ons in addition to Chrome extensions. So the reason to move is not compatibility and not speed. It is the set of features Opera layers on top, which is unusually large for a browser that costs nothing.

The desktop lineup is worth knowing before downloading, because the names are close together. The main Opera browser is the one this review covers. Opera GX is aimed at gaming. Opera Air is a separate build. Opera Neon is positioned around agents and automated tasks rather than ordinary browsing. Opera Mini is mobile. Installing the wrong one and concluding that Opera is not a work browser is a common way to waste an afternoon.

Workspaces, and what they do and do not separate

Workspaces are the feature most often cited in Opera reviews aimed at professionals, and they are genuinely useful. Each workspace holds its own set of tabs. Switching is a click in the sidebar, and a hotkey can be assigned. Each one takes a name and an icon, and a workspace can be hidden from view without being deleted. The description on Opera's feature page is precise about the scope:

Keep tabs in separate workspaces and organize your browsing the way you want. Source: opera.com

Read that carefully, because the limit hides in it. Workspaces organise tabs. Nothing in the feature is described as giving each workspace its own cookie jar, and in practice it does not. Two workspaces named Client A and Client B share one logged-in identity per service. Opening the same dashboard under two accounts still requires two Chrome-style profiles, which means two separate browser sessions with separate windows anyway.

This matters because the two problems get conflated constantly. Workspaces solve visual clutter: forty tabs become four groups of ten, and the nine unrelated tabs stop competing for attention. They do not solve account separation. Anyone who searched for an Opera review because of the second problem will find Workspaces satisfying for about a week and then hit the wall.

Tab Islands sit underneath all of it

Tab Islands is the newer layer and it runs by default. Open a link from a page and the child tab joins an island with its parent, so a research detour stays visually attached to what started it. Islands collapse and expand, take names and colours, and can be created manually with the plus button to the right of the tab strip. The setting to turn the automatic behaviour off lives in Easy setup, under the toggle for automatically creating tab islands, which is worth knowing on day one because automatic grouping is divisive.

The honest assessment is that islands help enormously with research and very little with operations. Chasing a question across fifteen pages is exactly what they were built for. Returning to the same eight tools every single day is not, because those tools have no parent tab and no natural grouping. They just accumulate.

The sidebar messengers are the real differentiator

This is the part of Opera that has no equivalent in a default Chrome install. Messaging and social services are pinned into the sidebar and open in a panel alongside the page, rather than as tabs. Opera's Mac page lists the set:

Chat with friends while browsing. Facebook Messenger, WhatsApp, Discord, Bluesky, Slack and Telegram, right in your sidebar. Source: opera.com

For a certain shape of work day this is transformative. Slack stops being a tab that gets buried, and checking it does not cost the current page. The panel is narrow, which suits chat and suits nothing else.

The constraint is the same one as everywhere else in this browser: one account per service, tied to the current profile. A contractor in three client Slack workspaces gets one in the sidebar and the rest back in tabs. Instagram and X are offered on the same terms, which is fine for a personal account and awkward for anyone running accounts for clients.

Notifications and sleeping tabs, which is where work actually gets lost

Tab organisation gets all the attention in reviews, and background behaviour causes most of the real damage. Every Chromium browser throttles tabs that have been out of view for a while, and each one ships some form of deliberate deactivation to reclaim memory. The visible symptom is identical everywhere: a tab that was left open all morning reloads when clicked, and whatever was half typed into it is gone.

Opera inherits that architecture. Tab snoozing appears in its own help index alongside the duplicate tab highlighter and the battery saver, which is a strong hint about which lever is being pulled when a long-idle page comes back blank. For research tabs this is exactly right and costs nothing. For a support console with a half-written reply in it, or a form that took twenty minutes to fill, it is the single most expensive behaviour in the browser.

The workaround inside any tab-based browser is the same three steps. Find the sleep or memory setting, identify the two or three services that must never be reloaded without warning, and exclude them by site. Then check that notifications from those services still arrive after the machine has been idle, because a throttled tab can stay silent while appearing perfectly awake. Testing that takes five minutes and is worth doing before trusting any browser with a queue that people are waiting on.

The sidebar messengers change this calculation in a useful way. A panel pinned to the sidebar is not a background tab, so chat tends to keep delivering when tabs have gone quiet. That is a real argument for putting the one chat tool that matters most into the sidebar rather than leaving it in the strip, regardless of which browser is in use. It is also the reason some people end up running their busiest services as separate windows or separate applications entirely: a window that is always a window never gets treated as a tab that can be discarded.

Where Opera stops, compared with the alternatives

Three approaches exist for keeping many work apps usable at once, and they fail in different places.

Approach	Separates tabs	Separates logins	Survives a restart	Cost
Opera Workspaces and Tab Islands	Yes	No	Yes	Free
Chrome profiles	Yes, one window each	Yes	Yes, if windows are reopened	Free
A browser that gives each web app its own window	Yes	Yes	Yes	Paid, varies

Chrome profiles are the usual fallback for the account problem, and Google's help describes what they hold: bookmarks, history, passwords and other settings kept separate per profile. The price is that each profile is a whole browser window with its own tab strip, so the clutter comes back one level up. Running four profiles means four windows that all look identical in the app switcher.

The third row is the category that a tool like this one belongs to, where each service gets a window and a session of its own rather than a tab. The trade is money and a different mental model, described on Features and in more detail under Workspaces. Nothing here is free of trade-offs. The point of the table is that Opera occupies one specific cell, and choosing it while needing a different cell is the main way these decisions go wrong.

The features that are not about work, and whether they get in the way

Opera ships a built-in ad blocker and a free VPN, both on by default or one toggle away, plus a paid VPN Pro tier that covers the whole device. It also ships a music player, a cashback feature for shopping, tab emojis, a volume booster, a unit converter, a personalised news feed on the start page and a built-in AI assistant that is free to use.

For a work machine, the relevant question is whether that surface area costs anything. Mostly it does not, because unused panels can be removed from the sidebar and the start page can be emptied. The ad blocker is a genuine benefit on ad-heavy internal tools and knowledge bases. The free VPN is useful for checking how a page looks from elsewhere, though routing an entire work session through it is a conversation to have with whoever owns the security policy, not a default to leave on.

The one real cost is attention. A browser that offers a news feed and a shopping feature every time a new tab opens is working against the person trying to stay in one task. That is a configuration problem rather than a flaw, but it does need ten minutes of configuration.

Who should move and who should not

Move if the day is one identity across many services and the pain is visual: too many tabs, no structure, chat buried three windows deep. Workspaces plus sidebar messengers address that directly, at no cost, on a browser where every existing extension continues to work.

Do not move if the pain is accounts. Two Google identities, three client Slacks, or a personal and a work profile that must never cross will not be fixed by grouping tabs, and discovering that after importing every bookmark is a bad week. The same applies if the pain is state loss, where a reloaded tab wipes a half-finished form, because that is governed by how background tabs are put to sleep rather than by how they are grouped.

Anyone in the second group is looking at profiles, containers, or a browser built around windows per app. Comparisons of that category are laid out under Compared with Wavebox and Compared with Sidekick, which are the closest neighbours in terms of what they try to solve.

What to change first

Install Opera alongside the current browser rather than replacing it, then move one workspace of tabs into it for a week and leave everything else where it is. If the complaint after that week is still "the right tab is hard to find", Opera solved it and the move is worth completing. If the complaint is "the second account still has no home", the next thing to read is Pricing on a tool built for that, such as SpaceDeck, because no amount of tab grouping reaches that problem.