Why We Built It
Because Closing Tabs
Is Not a Solution
Every piece of advice about tab overload comes down to the same instruction: close some tabs. It ignores why the tabs are open. They are open because each one is a thread you have not finished pulling, and closing it means paying the cost of finding it again — which is exactly the cost you were avoiding when you left it open.
The real problem is not the count. It is that Chrome gives every tab its own process memory, so pages nobody is reading keep holding RAM, and that a browser tab strip gives you no way to organise, preserve, or extract the set you have assembled. Forty tabs is a working document that the browser refuses to treat as one.
So TabFold treats it as one. Fold tabs into groups by the site they came from. Suspend the ones you are not reading, without losing what is in them. Snapshot the whole set so a project can be put down and picked up. And when the research is finished, export the list as a document — because the value of those forty tabs was always the list, and it should not take forty copy-pastes to get it out.
Zero Setup
Install, open the popup, and it is already useful — no account, no onboarding.
Memory Back
Idle tabs stop holding RAM while staying exactly where you left them.
Native, Not Novel
Grouping uses Chrome's own Tab Groups, so nothing new to learn.
Your List, Portable
Four export formats mean the session leaves the browser as a document.
Nothing Phones Home
No cloud, no tracking, no collection — everything runs on your device.
Free for Everyone
One tier, every feature, no upgrade prompt sitting on the button you need.