5 articles, every claim sourced
Every article about browser memory contains a benchmark table. Almost none of them contain a methodology, and the numbers get copied between sites until they look like consensus. Ours were invented too, and we removed them rather than replacing them with different invented numbers.
START HEREChrome Memory Saver: What It Does, and What It Doesn't Fix- it covers what Memory Saver actually does, and admits where an earlier version of it was wrong.
We have not published a test method, so we do not put our own number on it. The articles show you how to measure your own browser instead.
Firefox shipped vertical tabs, tab groups, split view, local AI grouping and built-in Containers in eighteen months, and leaves nearly all of it switched off. Including the tab unloading that only runs on Windows, and the one thing Firefox still has no answer for.
READ ARTICLE →
Chrome frees memory in process-sized units, not tab-sized ones. Chromium's source says which of your tabs share a process, the six things that keep one running after you close its tab, and why your Task Manager will not show the drop either way.
READ ARTICLE →
Google describes the three Memory Saver levels as "a longer period of time" and never says how long. Chromium's source does: 6 hours, 4 hours, 2 hours, plus three more gates most tabs never pass.
READ ARTICLE →
What Chrome, Firefox, Edge, Vivaldi, Brave, Opera, Safari and Zen each give you for handling tabs, sourced and dated. Including Chrome's vertical tabs landing in April 2026, the Collections feature Edge deleted in June, and why Arc is now a warning rather than a pick.
READ ARTICLE →
What Chrome's Memory Saver actually frees, the three modes and where to find them, the tabs it will never touch, and why Chrome can still feel slow with it switched on.
READ ARTICLE →