Add to Chrome — free

How to back up your Chrome tabs

A Chrome update, a profile reset, or a crash can wipe a live session of 200 tabs in seconds, and Chrome keeps no backup of its own — once the window closes, the tabs are gone. To back up Chrome tabs you need two things working together: an automatic safety net that captures the session on a schedule without you remembering to, and a manual copy you can move off the machine. Tabwell covers both. It reads your open windows through the chrome.tabs and chrome.tabGroups MV3 APIs and writes each session as a snapshot to local IndexedDB, so a recent state is always on disk. An auto-snapshot runs every 60 minutes on Free and every 5 minutes on Pro, and Free keeps the latest 5 of those snapshots — enough to recover from a crash or a bad close, though it is a rolling window, not an archive. On top of that automatic layer you can save a snapshot by hand at any point and export your snapshots to a single JSON file, the off-machine copy that survives a wiped profile or a new laptop. This guide covers both layers — what the automatic snapshots protect, where the 5-snapshot Free cap stops, and when to take a manual export — so you know which one to reach for.

Two layers of a Chrome tab backup

A backup is only useful if it exists when you need it, so Tabwell runs two layers at once. The automatic layer captures your session on a schedule and keeps it on the same device, ready for a quick recovery after a crash or a bad close. The manual layer is a copy you create deliberately and can move off the machine — the one that survives a wiped profile or a dead laptop. The automatic layer reads your open windows through chrome.tabs and chrome.tabGroups and stores each session as a snapshot in local IndexedDB via dexie; nothing is uploaded, and the only network call Tabwell makes is to Polar for license checks.

The automatic layer: auto-snapshots

Tabwell takes an auto-snapshot on a fixed interval so a recent state of your tabs is always on disk without you doing anything. On Free that interval is 60 minutes; on Pro it drops to 5 minutes, so the most you can lose is the work since the last capture. Each snapshot records every window, each tab's title and URL, and each tab's group assignment with the group name, color, and collapsed state — a full session, not a flat URL list. Be clear about the limit: Free keeps the latest 5 auto-snapshots and rolls the oldest off as new ones arrive, so it is a short recovery window, not a long archive. Pro lifts that cap to unlimited snapshots. Tabwell also takes a snapshot on browser exit, so the next launch can offer to restore whatever was open when Chrome closed.

The manual layer: save and export to a file

The automatic layer lives on one device. For a copy that leaves the machine you save a snapshot by hand and export it:

  1. Install Tabwell from the Chrome Web Store and pin it to the toolbar.
  2. Open the side panel and click Save snapshot to capture the current windows, tabs, and groups.
  3. Export your snapshots as a single JSON file and store it wherever you keep backups.

That JSON file is the copy that outlasts a reinstall or a new machine. The mechanics of writing it out and importing it on another computer are covered in the dedicated export guide linked below — this page stays on the broader backup strategy rather than repeating the export steps.

What each tier backs up

Every install starts with a 14-day Pro trial. After it, the Free tier keeps the latest 5 snapshots with manual save, restore, JSON export, and a 60-minute auto-snapshot — a working safety net for most single-machine recovery. Pro removes the 5-snapshot cap for unlimited history, auto-snapshots every 5 minutes, indexes every saved tab for full-text search, and adds importers for OneTab, Session Buddy, and Tab Session Manager. Pro is $3.99/month, $29/year, or $19 one-time for the first 1,000 Founders buyers, with a 30-day refund.

FAQ

How often does Tabwell back up my tabs automatically?

Tabwell takes an auto-snapshot every 60 minutes on Free and every 5 minutes on Pro, so a recent copy of your session is always on disk. It also takes a snapshot on browser exit, which is what lets the next launch offer to restore whatever was open when Chrome closed. You do not have to trigger any of these manually.

Is the 5-snapshot Free limit a problem for backups?

Free keeps only the latest 5 snapshots and rolls the oldest off as new ones arrive, so the automatic layer is a short recovery window rather than a long archive. For most single-machine crash recovery that is enough. If you need permanent history, export a snapshot to a JSON file by hand, or move to Pro for unlimited snapshots.

Do I need Pro to back up my Chrome tabs?

No. The Free tier keeps the latest 5 snapshots with manual save, restore, JSON export, and a 60-minute auto-snapshot, which covers most single-device recovery. Pro adds unlimited snapshots, 5-minute auto-snapshots, full-text search, and importers, for $3.99/month, $29/year, or $19 one-time as a Founders purchase. Every install begins with a 14-day Pro trial.

Where are my backed-up tabs stored?

Snapshots are stored locally in IndexedDB on your own device via the dexie library. Tab titles and URLs never leave the machine unless you export the JSON file and move it yourself. The only network call Tabwell makes is to Polar for license verification, which carries no tab data.

Does the backup keep my Chrome tab groups?

Yes. Every snapshot records each tab's group assignment along with the group name, color, and collapsed state, read through the chrome.tabGroups API. When you restore a snapshot, Tabwell rebuilds the groups exactly rather than handing you a flat list of URLs. This holds for both the automatic snapshots and a manual export.

Does automatic backup work on Chrome 114?

Yes. Chrome 114 is the minimum version Tabwell supports, because it relies on the chrome.sidePanel API introduced in that release. The auto-snapshot and manual save both work from that version on. Edge and other Chromium browsers may run it but are not officially supported, and Firefox and Safari are not supported.