Tabwell vs Session Buddy: a current feature checklist

For Tabwell vs Session Buddy, separate two questions that comparison pages often blur: how an archived export migrates, and how a future browser crash is recovered. Tabwell's current Session Buddy importer expects a JSON object containing sessions, windows, and tabs. It converts each source window with tabs into one imported snapshot, carries URL, title, order, and pinned state where present, and places the tabs in a single grey Imported group. After migration, newly created Tabwell snapshots can record native Chrome group title, color, and collapsed state. Future crash recovery uses the latest periodic auto-snapshot, not a new capture at shutdown: Free runs every 60 minutes and retains one automatic recovery slot, while Pro offers 5, 15, 30, or 60-minute intervals. Verify Session Buddy's current export and recovery behavior in its own documentation, then compare both flows with a sample you can safely discard.

Test migration separately from recovery

First export three representative Session Buddy items: a single-window set, a multi-window set, and one containing pinned tabs. Keep the source file unchanged. Import it into Tabwell and verify the number of non-empty windows, tab counts, titles, URLs, and pinned state. Tabwell's importer creates one imported snapshot per source window; it does not invent Chrome group metadata that is absent from the accepted JSON shape.

Then run a recovery drill

Create a fresh Tabwell snapshot, wait for a periodic auto-snapshot, and check its timestamp before simulating an unexpected shutdown in a disposable profile. Tabwell records a graceful marker when the last window closes normally. When the previous browser session appears interrupted, it can offer the latest auto-snapshot that already exists. Any changes after that capture can be missing, so a manual snapshot is still the right choice before a planned update.

Questions for the current Session Buddy release

What exact fields are included in its current export?
Does a restore rebuild native Chrome group title, color, and collapsed state?
How are backups retained and moved off-device?
What does its current privacy disclosure say about external requests?

Answer these from the current product and documentation rather than historical store commentary.

Tabwell data handling and plans

Snapshots, tab titles, and URLs stay in local IndexedDB. Billing and license requests use Tabwell's billing service and Polar without sending tab data. Optional redacted crash diagnostics can be enabled; they are off by default. See the privacy policy. The importer is a Pro feature available during the local 14-day Pro trial. Free remains available afterward with manual save, restore, JSON export, and its stated limits. Current prices, purchase options, and terms are listed on the pricing page.

FAQ

How does Tabwell read a Session Buddy export?

The current importer expects Session Buddy-style JSON with sessions, windows, and tabs. Each non-empty source window becomes one imported snapshot with URL, title, order, and pinned state where supplied.

Does the importer invent missing Chrome group metadata?

No. Imported windows begin in one grey Imported group. You can arrange them into native Chrome groups and save a new Tabwell snapshot afterward.

Does Tabwell capture a new snapshot when Chrome closes?

No. It records a graceful-shutdown marker. After an unexpected shutdown, recovery can offer the latest periodic auto-snapshot that already exists.

How should I validate a large migration?

Import a small representative sample first. Compare source and destination window counts, tab counts, pinned state, titles, and a selection of URLs before importing the full archive.

What leaves the device when using Tabwell?