Chrome 155 Split View API Lets Extensions Open Side-by-Side Tabs

Share
Key Takeaways: Split View API
Chrome 155: a new Split View API lets extensions detect, create and manage Chrome’s built-in side-by-side tabs.
No extra permissions: it is part of the tabs namespace and needs no manifest permissions.
Built with Mozilla: Google developed it with Mozilla and other browser vendors in the WebExtensions Community Group.
No more hacks: extensions no longer need to resize windows or embed pages in frames to show two pages side by side.

Chrome got native Split View in Chrome 145 back in February 2026, but until now only you could put tabs side by side, using the browser controls. Extensions had no way to do it. That changes in Chrome 155 with a new Split View API, announced on the Chrome for Developers blog.

What the Split View API does

Full control: the API lets extensions detect, create and manage built-in split views. Google built it in close collaboration with Mozilla and other browser vendors in the WebExtensions Community Group.

No permission prompts: the API lives inside the browser.tabs namespace and does not need any manifest permissions. As PiunikaWeb points out, that means fewer scary permission warnings for users.

Goodbye workarounds: before this, extensions that wanted side-by-side layouts had to resize several native windows, embed pages in frames, or use side panels. Google calls those workarounds brittle.

How it works for developers

FeatureWhat it does
splitViewIdEvery tab has it. Paired tabs share an ID, and it is -1 if the tab is not in a split view.
splitWithTabIdNew option in tabs.create that opens a new tab split with an existing one (on the right by default).
tabs.createSplitPairs two existing tabs into a split view.
tabs.unsplitSeparates a split view back into two normal tabs.

Rules for pairing: the two tabs must sit next to each other, must not already be in a split view, and must share the same pinned, window and tab group state. When you unsplit them, they keep those states and their positions.

Our take: this is a small change you will not see right away, but it should lead to better tab and productivity extensions. Because Mozilla helped build it, extension makers have a better shot at tools that work the same way across browsers.


Discover more from Chrome Geek

Subscribe to get the latest posts sent to your email.

Sophie is a Chicago-based editor for Chrome Geek covering Chromebooks, Gemini, and the Google ecosystem. When she is offline, you can usually find her watching Blackhawks hockey or grabbing iced coffee in the city.