Where Does Tab Session Manager Store Sessions?
Tab Session Manager keeps saved sessions in per-profile browser storage with export files for moves.
Last updated
Tab Session Manager stores sessions in extension storage inside the active profile. Named saves, auto-saves, and settings share that space. There is no external session folder.
Auto-save caps how many snapshots accumulate, which bounds the storage naturally. Named sessions persist until deleted. Export files carry the whole archive between profiles.
Where Tab Session Manager stores this, by platform
%LocalAppData%\Google\Chrome\User Data\Default\Extensions (per profile export file)
Sessions and settings per profile. Export files move named and auto-saved sessions together. Caps bound storage naturally.
~/Library/Application Support/Google/Chrome/Default/Extensions (per profile export file)
Same model on Mac across Chromium and Firefox builds. Restores rebuild windows and tabs exactly. Export before profile wipes.
~/.config/google-chrome/Default/Extensions (per profile export file)
Same storage under profile trees on Linux. No cloud copy exists. Sessions belong to the profile that saved them.
Frequently asked questions
How do I move Tab Session Manager sessions?
Export sessions to files from settings, then import on the new profile. Named sessions and auto-saves travel together. Fresh installs start with empty session lists.
Notice an outdated path? Let us know.