Opera One browser joins the vertical tab club, expands Google Lens integration

**Opera** announced two desktop features for **Opera One** today: optional **vertical tabs** and expanded **Google Lens** integration, as reported by **9to5Mac**. The browser is joining the set of desktop clients that treat the tab strip as a side rail instead of only a top bar, and it is pushing visual search deeper into the browsing chrome rather than leaving it as a one-off sidebar experiment.

Optional **vertical tabs** change how the tab list is laid out and managed: tabs stack along a side panel instead of competing for horizontal space in a single row. That layout usually pairs with clearer title visibility, easier scanning of long sessions, and less compression when many pages stay open. The **Google Lens** expansion extends image-based lookup from selected content or page visuals into more of the browser surface, so reverse image search, object recognition, and on-page visual queries sit closer to normal navigation instead of a separate tool hop.

For engineers and builders, the news is about session density and in-browser research loops. Side-mounted tabs matter when you keep docs, dashboards, PRs, and staging environments open in parallel; less title truncation and a scannable list reduce the cost of context switching. Deeper **Lens** hooks matter when work depends on screenshots, design comps, product UIs, or error dialogs—visual search becomes part of the same window rather than an export-to-another-app step.

Market-wise, **Opera One** is aligning with a pattern already established by other desktop browsers that treat vertical tabs as a first-class layout option rather than a power-user extension. Pairing that with **Google Lens** also ties Opera’s desktop product more tightly to Google’s visual-search stack, using a known capability as a differentiator instead of inventing a separate reverse-image system. The move is less about inventing a new category and more about closing a feature gap while strengthening an existing search integration.

What to watch next is whether users actually flip on vertical tabs as a default habit and how far **Lens** is available across everyday page types without friction. Builders evaluating browser choice for dense multi-tab work should try the optional side layout on real session size; teams that rely on visual QA or design review should test whether the expanded **Lens** path is faster than their current screenshot-and-search workflow. The concrete signal will be adoption of the layout switch and how consistently **Lens** shows up where people already work, not the announcement alone.