Opera Workspaces: Organizing Tabs by Context Without Extra Windows
Opera Workspaces group tabs into named, switchable contexts in one window. Here's how to set them up, what they actually isolate (and don't), and the mistakes to avoid.
14 Jun 2026, 01:46 UTC

If your tab bar regularly degenerates into a row of unreadable favicons, Opera's Workspaces feature is the built-in fix: named, color-coded tab groups that live in one window and switch with a single click. The useful takeaway up front: Workspaces are excellent for separating long-lived contexts (work, personal, a research project), but they are a visual organization layer only — they do not isolate cookies, logins, or memory, and hidden tabs keep consuming resources.
What Workspaces actually do
A workspace is a named tab set shown as an icon at the top of Opera's tab bar. Clicking a workspace icon instantly hides the current set of tabs and shows the tabs belonging to the selected workspace. Only one workspace is visible at a time, which is the entire point: your 30 research tabs stop cluttering the view while you answer email.
Key mechanics to understand:
- All workspaces share one window, one profile, one history, and one set of extensions.
- Tabs in hidden workspaces stay open in the background. They are not automatically suspended.
- Workspaces and their tabs persist across restarts when session restore is enabled, so they suit long-lived project contexts rather than throwaway grouping.
A worked configuration: separating Work, Personal, and Research
Here is a concrete setup you can replicate in a few minutes. Menu names and placement vary slightly across Opera versions and platforms, so treat labels as approximate.
- Create the workspaces. Right-click an empty area of the tab bar and choose the option to create a workspace (wording like "Create Workspace" or a "+" on the workspace strip). Make three: Work, Personal, and Research.
- Name and color-code them. Give each a distinct icon and color. The color matters more than you'd expect — it lets you confirm at a glance which context you're in before typing credentials or clicking links.
- Move existing tabs. Drag a tab onto a workspace icon, or right-click the tab and use its context menu to move it to a workspace. New tabs you open while a workspace is active belong to that workspace automatically.
- Learn one fast-switch method. Clicking the workspace icon works, but check Settings for configurable keyboard shortcuts for switching workspaces — a hotkey is where most of the productivity gain comes from, since you never break typing flow to manage windows.
- Enable session restore. In Opera's settings, confirm the startup option is set to reopen your previous session. Without it, your carefully organized workspaces won't survive a restart.
To verify the setup worked: switch between two workspaces and confirm the tab strip changes completely; restart the browser and confirm all three workspaces and their tabs return.
Workspaces vs. alternatives
| Approach | Windows | Cookie/login isolation | Memory behavior | Best for |
|---|---|---|---|---|
| Workspaces | One | No (shared profile) | All tabs stay loaded | Visual context separation |
| Separate windows | Many | No (shared profile) | All tabs stay loaded | Multi-monitor setups |
| Separate profiles | One or more | Yes | All tabs stay loaded | Separating identities/accounts |
The comparison makes the trade-off clear: if you need to be logged into two different accounts on the same site, or you want a security boundary between contexts, Workspaces are the wrong tool — use separate browser profiles. If you just want fewer visible tabs, Workspaces are lighter-weight than juggling windows.
Limits and common mistakes
Hidden does not mean suspended
The most common misconception: moving tabs to another workspace does not free memory. Background tabs keep running. You can confirm this yourself with Opera's built-in task manager (Menu > Developer > Task Manager, on desktop builds) — tabs from hidden workspaces still appear with live memory and CPU figures. If RAM pressure is your actual problem, close heavy tabs or use Opera's tab-snoozing/discarding features rather than hiding them.
Not a privacy or security boundary
Because workspaces share one profile, a site open in your Personal workspace can read the same cookies and storage as one in Work. Don't treat workspace separation as isolation for sensitive browsing.
Version drift
Opera has changed the workspace UI placement, default shortcuts, and menu wording across releases. If a step above doesn't match what you see, right-click the tab bar and look for workspace-related entries, or search "workspace" in Settings — the feature itself is stable, but its chrome moves around.
Over-grouping
More than about five workspaces tends to recreate the original problem: you forget which context holds the tab you want. Keep the count small and the names action-oriented.
Practical check
After configuring, run this three-part sanity check: (1) toggle between workspaces and confirm only the active set is visible; (2) open the task manager and confirm hidden tabs still consume memory, so you know hiding isn't cleanup; (3) restart with session restore on and confirm everything persists. If all three behave as described, Workspaces are working as intended and the remaining discipline — actually closing tabs you're done with — is on you.
0 replies
A thoughtful contribution can make all the difference. Be the first to share one.