OneTab is losing people's tabs. Here's the local-first fix

Let's say the nice thing first: OneTab is brilliant at its one job. Click, and ninety tabs collapse into one list page. Your fan goes quiet. Your laptop stops sounding like it's about to achieve orbit. It's been doing this for over a decade, for free, to two million people.

Now the not-nice thing, which its own community forums will tell you before we do:

The structural problem isn't storage — it's write-only-ness

Even when nothing breaks, OneTab's model has a quieter failure mode: saved lists have no folders, no real search beyond Ctrl+F, no grouping. After a few months you're scrolling a thousand-line graveyard of half-remembered links — the same problem you started with, relocated.

It's what happens to any system that's write-only: putting things in is easy, getting them back out is scroll-and-pray. And systems nobody retrieves from are systems nobody trusts, so the hoard just moves.

What actually earns trust

The local-first checklist

You don't need cloud sync — that just trades Google-account dependency for vendor dependency. You need local storage with exits:

• Export any session as JSON, in one click, without exporting everything. Small exports get used; full backups don't.
• Import must round-trip. An export format you can't load back in is decoration, not backup.
• Organization that survives scale. Folders for sessions, groups inside sessions, restore-a-slice. Retrieval trust is the whole game.
• Optional portability. A share link that carries its payload inside itself means phone access with zero servers involved.

Speed got OneTab its two million users. Trust is what keeps people on what comes next.