What Is a Browser Tab, and What It Cannot Separate

A tab in a web browser is a slot inside one window that holds one web page, with its own address and its own back and forward history. Click a different tab and the window shows a different page, while the others keep their place in the background. That is the part everyone knows. The part that matters for daily work is what tabs share: every tab in a window belongs to the same browser profile, so they all use the same cookies and the same logins. A tab can separate pages, but it cannot separate accounts. This guide explains how tabbed browsing works, the keyboard shortcuts on a Mac, what a pile of open tabs actually costs, and where the tab stops being the right tool.

Where browser tabs came from

Tabs feel like a permanent part of the web, but they arrived late. Before them, every page opened in a separate window, and a desktop filled with overlapping windows the way a browser now fills with tabs.

According to the Wikipedia entry on tabs as an interface element, BookLink Technologies shipped tabbed windows in its InternetWorks browser in 1994. NetCaptor, a shell around Internet Explorer, followed in 1997, Opera added tabs with version 4 in 2000, Phoenix (the browser that became Firefox) had them in October 2002, and Safari arrived with tabs in 2003. With Internet Explorer 7 in 2006, every major browser had a tabbed interface.

The same entry cites a June 2009 study of tab behavior that found users switched tabs in 57% of tab sessions, and that 36% of users opened search results in new tabs at least once. Tabs went from novelty to default within a few years, because they solved a real problem: one window, many pages, no hunting across the desktop.

What they did not change is the model underneath. A tab is still a page in a browser that was designed for reading documents. It was never designed as a home for a dozen applications that stay signed in all day, and most of the friction people feel with tabs comes from that mismatch.

What a tab is under the hood

From the outside, a tab is a strip at the top of the window with a title and a site icon. Inside the browser it is more than a label.

Each tab keeps its own navigation history. Pressing back in one tab does not affect another. Each tab also has its own scroll position, form state and media playback, which is why a video keeps playing in a background tab.

In Chrome, tabs are also separated at the level of the operating system. The Chromium project's page on Site Isolation explains that pages from different sites are put into different processes, each running in a sandbox that limits what it can do. That is a security boundary: a page that misbehaves cannot read the memory of a page from another site. It is also the reason every tab costs memory, because each process carries its own overhead.

What a tab does not have is its own storage for cookies and logins. Those belong to the profile, and every tab in every window of that profile reads from the same place. Sign in to Gmail in one tab and every other tab on Gmail is signed in as the same person. Sign out in one, and the others are signed out too.

Working with tabs in Chrome on a Mac

The shortcuts below are taken from Chrome's keyboard shortcuts help page, Mac section, as checked on October 18, 2026.

Action	Mac shortcut
Open a new tab and jump to it	Cmd T
Reopen closed tabs in the order they were closed	Cmd Shift T
Jump to the next tab	Cmd Option Right arrow
Jump to the previous tab	Cmd Option Left arrow
Jump to tab 1 to 8	Cmd 1 to Cmd 8
Jump to the last tab	Cmd 9
Close the current tab	Cmd W
Close the current window	Cmd Shift W
Open a link in a new tab	Cmd and click the link

Chrome's help page on managing tabs covers the rest of the basics. Drag a tab along the top of the window to reorder it, or drag it outside the window to give it a window of its own. Right-click a tab and choose Pin to shrink it to its icon and keep it at the left. Right-click and choose Add tab to group, then New group, to put several tabs under one colored label that you can name and collapse.

One detail on that help page is easy to miss and says a lot about how tabs work. To move a tab into a different window, Google notes that both windows must be signed in to the same profile. A tab cannot cross from one profile to another, because the cookies that make its page work live in the profile it came from.

Finding a tab once there are too many to read

Past a certain number, tab titles shrink to icons and the strip stops being something you can scan. Chrome has two built-in ways to search instead of scan, both described on the same tab help page.

The first is Tab Search. It is on by default and pinned in the tab strip as a small icon. Select it, type a few letters from the site or page title, and pick the tab from the list. On a Mac, Cmd Shift A opens it from the keyboard. The second is the address bar: type @tabs, press space or tab, then type keywords, and the suggestions narrow to open tabs only. Either way, the result is a list of open pages you can pick from, instead of a strip of icons you have to hover over one at a time.

Tab groups also do more than add color. Collapse a group by selecting its name or colored circle and only the label stays in the strip. In Settings, under Appearance, Chrome can show tab groups in the bookmarks bar and pin new groups there automatically, which turns a group into something you reopen rather than something you keep open. One caution from the help page: when tab groups are synced to a Google Account, deleting or ungrouping a group removes it on every device that uses that account, not only the one in front of you.

A simple pattern holds up well on a Mac. Keep one window for pages you are reading and expect to close. Pin the few tools you keep all day at the left of that window. Put each project's reference pages into a named group and collapse it when you are not working on it. Search rather than scroll when you need something that is not in view.

What too many tabs cost

Wikipedia has a name for the habit of leaving dozens of tabs open: tab hoarding. The entry describes people keeping tabs as reminders of tasks to finish, and notes that the clutter can add to stress and information overload. Browser makers have responded with memory features rather than fewer tabs.

Chrome's answer is Memory Saver. According to Chrome's help page on performance settings, Memory Saver deactivates tabs you are not using to free memory, and a deactivated tab reloads automatically when you go back to it. It sits under Settings, then Performance, and offers three levels: Moderate, Balanced (the recommended one) and Maximum, which deactivate tabs after a longer, an optimal or a shorter period.

The same page lists what stops a tab from being deactivated: active audio or video including calls, screen sharing, page notifications, active downloads, partially filled forms, pinned tabs, and connected USB or Bluetooth devices. You can also add sites under "Always keep these sites active", for example mail.google.com, so an inbox you rely on for alerts does not go quiet.

That list is useful beyond memory. A tab that reloads when you return to it has lost its live connection in the meantime. For a news article that does not matter. For a chat app or a mail client that you expect to notify you, it does, and the fix is either the exception list or a pinned tab.

What a tab cannot separate

Because tabs share the profile's cookies, a single window of tabs can hold only one signed-in account per site. That is the limit behind most of the workarounds people build.

• Two Gmail accounts. Google lets you sign in to several accounts in one browser and switch with the account picker. Both accounts still share one cookie jar, and Google may apply settings from the default account when it cannot tell which one you mean.
• A private window. An Incognito window gives you a second, temporary session, but it forgets the login when it closes.
• A second profile. A new Chrome profile gives you a fully separate set of cookies, at the cost of a separate window with its own tab strip.
• Containers in Firefox. Mozilla's Multi-Account Containers extension is the one mainstream case where the separation happens per tab. Cookies are separated by container, so a work tab and a personal tab can sit side by side in one window.

The comparison below puts tabs next to the other units a browser offers.

Unit	Separate pages	Separate logins	Stays signed in after closing
Tab	Yes	No	Yes, through the profile
Tab group	Yes	No	Yes, through the profile
Incognito window	Yes	Yes, temporarily	No
Chrome profile window	Yes	Yes	Yes
Firefox container tab	Yes	Yes	Yes

When the tab is the wrong unit

Tabs work well for reading: open a few pages, compare them, close them. They work less well for applications you keep open the whole day, such as mail, chat, calendars and project tools. Those pages are not read and closed. They sit in tabs for weeks, get mixed in with the articles opened around them, and need separate logins when the same service is used for two clients.

The usual escalation is more profiles, which turns the problem from too many tabs into too many windows. Another route is an app aggregation browser, which gives each web app its own place in a sidebar and its own cookie container instead of a tab. Mail stays in one spot, every signed-in account is a separate entry, and the reading tabs stay out of the way. One such tool for macOS lists the services it can add by name on its supported apps page and adds anything else by URL, and its features page describes link routing that sends a link to the app it belongs to.

What to do next

Count the tabs you never close. If they are mostly mail, chat and dashboards, give them pinned tabs and add them to Memory Saver's keep-active list today. If several of them are the same service under different accounts, that is a sign the tab has stopped being the right unit, and a per-app setup such as SpaceDeck is worth a look.