Start taming your tabs today
Add SideBoo to Chrome for free, then use these articles to get every tab, bookmark and history entry under control.
Chrome sets no tab limit. What runs out is memory — and that depends far more on what is inside your tabs than on how many you have. Here is the honest answer, and how to measure your own ceiling.
7 min read · Published · Updated
Chrome does not publish a maximum tab count, and for everyday use you will never reach a hard ceiling. What you run into first is memory — and how quickly you get there depends far more on what is inside the tabs than on how many of them there are.
Ten tabs running Google Docs, Figma and a video call can cost more than a hundred tabs holding plain articles you already finished reading. That is why every article promising you a number — “16 GB means 60 tabs” — is guessing. The number is not a property of your RAM. It is a property of your tabs.
There is an honest number, and it takes about a minute to get: open Chrome's task manager, read the median memory footprint of your open tabs, and divide the RAM you can spare by it. That division is the entire answer. No article can run it for you, because the median is the half that belongs to you.
The intuition behind the question is that each tab costs a fixed amount of memory, so you can divide your RAM by that number. Chrome does not work that way.
Chrome's default process model groups pages by site rather than by tab. Several tabs opened from the same site — the six GitHub issues you middle-clicked out of one page — can end up sharing a single renderer process, while six tabs on six different sites cannot. So the same tab count produces very different memory footprints depending on how those tabs came to exist.
On top of that, a tab Chrome has discarded costs almost nothing. Your tab strip can show a hundred tabs while only a handful are actually resident in memory. Counting the strip tells you very little about what the browser is holding.
Memory Saver is the reason a large tab strip is survivable at all, and it is widely misdescribed as “suspending” tabs. Chrome's own developer documentation is blunter than that: when a tab is discarded, the tab keeps its title and favicon in the strip, but the page itself is gone, exactly as if the tab had been closed normally. Returning to the tab reloads it from scratch.
That distinction matters in practice. Anything the page was holding and had not written to storage — a half-typed comment, an unsubmitted form, scroll position in an infinite feed — is not preserved by Chrome. Sites that survive this do so because they chose to save state themselves.
| Setting | What it does |
|---|---|
| Memory Saver | Discards tabs you have not used for a while, on a Moderate / Balanced / Maximum schedule. Google's launch announcement claimed up to 40% less memory and up to 10 GB saved; the help documentation itself gives no figure. |
| Energy Saver | A different feature. Lowers the image capture rate and pauses eligible CPU-heavy background tabs when you are unplugged or low on battery. Video calls and audio playback are exempt. |
Since the answer depends on your tabs, the only number worth having is your own. Chrome ships a task manager that shows memory per process, and it takes about ten seconds to open.
With the median in hand, the arithmetic is one division. The middle column is a rule of thumb, not a measurement: leave the operating system, your editor and everything else their share before counting what is left for Chrome.
| RAM installed | Roughly free for Chrome | Your tab limit |
|---|---|---|
| 8 GB | about 5 GB | 5,000 MB ÷ your median |
| 16 GB | about 12 GB | 12,000 MB ÷ your median |
| 32 GB | about 26 GB | 26,000 MB ÷ your median |
Worked through: if your task manager puts the median tab at 120 MB, 16 GB holds roughly a hundred tabs. If you live in Google Docs and Figma and the median is 400 MB, the same machine is full at about thirty. Both figures come off the same 16 GB. That is why “16 GB means 60 tabs” is not a fact about 16 GB, and why the number you want is the one on your own screen.
There is a second ceiling, and most people hit it long before the machine complains: the point where the tab strip stops working as navigation. Titles vanish, favicons blur together, and finding the page you had five minutes ago becomes slower than searching for it again from scratch.
Researchers at Carnegie Mellon studied exactly this: in a 2021 CHI paper, Joseph Chee Chang and Aniket Kittur found that about 25% of participants in one part of the study had had a browser or computer crash from too many open tabs.
That is why “just close them” is advice nobody follows. The cost of closing a tab is not the click; it is the decision about whether you will ever need it again. That decision, and the two very different fears behind it, is the psychology of tab hoarding.
SideBoo takes the last one seriously: one keystroke searches open tabs, history, bookmarks and recently closed pages together, so a tab you cannot see is still one keyword away. Nothing leaves your machine.
Chrome does not publish a maximum number of tabs, and there is no setting that caps it. The practical limit is your machine's memory, which you will reach at wildly different tab counts depending on what those tabs contain.
There is no single honest number, and articles that give you one are estimating. Ten heavy web apps can use more memory than a hundred finished articles. Open Chrome's task manager (Shift + Esc on Windows and Linux, Window → Task Manager on macOS) and sort by memory footprint to see your own answer.
They can, but usually a few specific pages are responsible rather than the count. Chrome discards tabs you have not used recently, so a long tab strip is not the same as a lot of live pages. Check the task manager before closing anything.
It can. Chrome's documentation describes a discarded tab as gone exactly as if it had been closed normally; returning to it reloads the page. Anything the site did not save itself — a half-written comment, an unsubmitted form — is not preserved. Pin the tab, or mark the site as always active, if that matters.
Chrome's built-in task manager lists memory per process: press Shift + Esc on Windows or Linux, or use the Window menu on macOS. Note that one row is not always one tab — tabs on the same site can share a process.
Research
Closing a tab takes one click. Deciding whether to close it does not, and that decision is what tab hoarding is made of. There are two different reasons people will not close a tab, they look identical from the outside, and they need opposite fixes.
Comparison
Chrome's Tab organizer suggests AI tab groups from a right-click. It is useful — and it is gated, desktop-only, and clusters by topic, not by project.