Where Does Session Buddy Store Collections and Backups?
Session Buddy keeps collections in a Chrome IndexedDB folder plus in-app backups. Exact folder names, backup routine and restore.
Last updated
Session Buddy stores collections, history and settings inside Chrome's IndexedDB, in a folder named after its extension ID. A companion blob folder usually sits beside it. Both live under your Chrome profile, which is why reinstalling the browser without a backup vaporizes years of saved sessions.
The vendor's own docs beg you to do two things: run the gear-menu Backup regularly, and include these exact folders in system backups like Time Machine. Automated in-app backups exist since v4.1 but can lag a day behind. Restoring means replacing both folders whole while Chrome is closed.
Where Session Buddy stores this, by platform
%LOCALAPPDATA%\Google\Chrome\User Data\Default\IndexedDB\chrome-extension_edacconmaakjimmfgnblocblbcdcpbko_0.indexeddb.leveldb
Main data folder; grab the sibling .indexeddb.blob folder too when present. Adjust Default to your profile name. Use the gear-menu Backup for portable restores.
~/Library/Application Support/Google/Chrome/Default/IndexedDB/chrome-extension_edacconmaakjimmfgnblocblbcdcpbko_0.indexeddb.leveldb
Same extension-ID folder as Windows. Include both folders in Time Machine. Exports (gear menu) suit sharing; Backup/Restore suits disaster recovery with history intact.
Frequently asked questions
How do I back up Session Buddy properly?
Open the gear menu and run Backup to a file you keep, plus include the two IndexedDB folders above in system backups. The file covers collections and history together; exports alone skip history.
Session Buddy lost everything after a browser reset, now what?
Close Chrome, restore both data folders from backup into the profile's IndexedDB directory, and reopen. Then immediately run an in-app Backup. If no backup exists, check whether the blob folder survived: history sometimes outlives the main store.
Notice an outdated path? Let us know.