What Chrome Split View is
Split View is Chrome's native side-by-side tabs layout. Instead of creating a second window, you pair two tabs inside one window. Both tabs stay active, both keep their own URLs, and they share the same tab bar and navigation.
The feature has existed in Edge for years and in Arc as "Split". Chrome shipped its native version in Chrome 145 (stable rollout, February 2026). It is a proper keyboard-accessible layout, not just a flag experiment.
How to use it
- Open the two tabs you want to compare.
- Right-click an inactive tab and choose Add tab to new split view. Chrome pairs that tab with the currently active tab.
- Alternatively, right-click any link and choose Open link in split view to open the target URL in the second pane.
- Drag the divider in the middle to resize. Drag a tab out of split view to go back to single-tab mode.
Keyboard shortcuts (documented on Google's support page): Shift+Alt+N on Windows and Linux, Cmd+Option+N on macOS, Ctrl+Alt+N on ChromeOS. Once split view is active, the normal tab shortcuts still work inside each pane.
If you do not see the option
Update to Chrome 145 or later. On older builds, toggle chrome://flags/#side-by-side (some channels also expose #side-by-side-browsing) and relaunch. Rollout is staged by region and channel.
The use cases that actually matter
Split view is sold in marketing videos as a general "productivity" feature. In practice, it pays off most when you have a tight compare-or-reference loop between two tabs. Here are the patterns I actually see people use.
Docs vs implementation
Developer reading the Next.js docs while writing a component. Instead of Alt+Tabbing between the browser window with docs and the editor window with code, you split the two Chrome tabs (docs + web-based editor or GitHub view) inside one window. Your eyes barely move. The code context sits next to the API reference.
Source vs draft
Writer with a transcript tab on one side and their Google Doc on the other. Researcher with a source paper on one side and their notes on the other. The entire "read a thing, write about the thing" loop collapses into one window.
Staging vs production
QA or design review with staging on the left and production on the right. You scroll both, you compare both, you do not have to remember which tab you are on because both are visible at once. Chrome for developers covers more of these workflows.
Email vs calendar
Inbox on one side, calendar on the other. You triage invitations without bouncing between tabs. Slack on one side, incident dashboard on the other during an on-call shift. Ticket tracker on one side, deploy log on the other during a release.
Shopping or research
Two products side by side. Two flight search results. Two apartment listings. A review article on the left and the product page on the right.
Split view and tab groups
Split view's tab pair shows up in the tab strip as its own paired representation. It can sit next to a tab group without conflict, and you can keep your grouped tabs on one side and a split pair on the other. Google's own support docs do not currently promise that a split pairing is preserved inside a collapsed group, so treat that combination as a "works in the moment" layout rather than a guaranteed saved structure.
In practice: use tab groups to organize the project, and use split view to pair the two tabs you are actively comparing. When you need both to survive Chrome closing, rely on saved tab groups plus a snapshot tool rather than assuming split pairings persist automatically.
For the full tab-groups primer, see the complete guide to Chrome tab groups.
Split view vs multiple windows
Two windows is the traditional answer to "I need to see two tabs at once". Split view is not strictly better; it trades some flexibility for some integration.
| Dimension | Split view (one window, two panes) | Two separate windows |
|---|---|---|
| Vertical space per tab | Full window height | Full window height |
| Horizontal space per tab | Half the window width | Whatever size you make each window |
| Separate tab bars | No, shared tab bar | Yes, independent tab bars per window |
| Cross-monitor | No, both panes on one screen | Yes, windows can span monitors |
| Save/restore structure | Part of the tab group, easy | Must rebuild window layout each time |
| Keyboard focus management | One window to target | OS-level window switching required |
| Fullscreen apps on secondary monitor | Awkward | Natural |
Rule of thumb: use split view when the two tabs belong to the same task. Use multiple windows when the two contexts are genuinely independent (for example, deep-focus writing on one monitor and reference material on the other).
For research and dev workflows
Two setups that hold up over a full work week:
Research workflow
- One tab group per topic, named and colored.
- Inside each group, pair the "reading" tab with the "notes" tab in split view.
- Keep a sidebar (native vertical tabs) visible so you can swap the left pane (the article you are reading) without touching the right pane (your notes doc).
- Snapshot the workspace so you can return to it tomorrow morning without rebuilding the whole thing.
Dev workflow
- One tab group per feature or ticket.
- Inside the group, pair docs + PR, or staging + production, in split view.
- Pin the dashboard, inbox, and messaging apps outside any group, so they survive group collapse.
- Save the tab group so closing the window does not destroy the layout.
Where TabGroup Vault fits
Once you have a split-view layout that works, you want it to survive Chrome closing. Save the group inside Chrome (right-click the pill, toggle Save group) to keep it across launches, and take a TabGroup Vault snapshot for durability beyond Chrome's own storage. Free tier covers 5 snapshots; Pro is $29 lifetime.
Things to know before relying on it
Below about 1280 px wide, split panes get cramped — on a 13-inch laptop it is usable but not great. Some dashboards and web apps with rigid layouts break at half window width; test before using it for a client demo. Extensions that modify page layout (reader mode, sidebar tools, fullscreen video) sometimes misbehave in split view. For video tutorials, picture-in-picture is smoother because it floats above everything. And keyboard shortcut support varies between Chrome builds — the documented ones (Shift+Alt+N, Cmd+Option+N) are the most stable, but some older-build shortcuts may have changed.
The short version
Split view has a specific shape: compare or reference two tabs that belong to the same task. When the shape fits, it cuts a lot of Alt+Tabbing. It is less useful when you need two fully independent contexts or different window sizes. Pair it with saved tab groups and you have something that survives Chrome closing and is worth setting up.