Your conversations live in this browser. Which situation you are in, what can still be recovered, and what cannot.
Chats live in the browser that made them. A second machine, a second browser or a second profile is empty because nothing was ever put there - expected behaviour, not a fault.
Chats, personas and rambles stay on this device unless you subscribe to Pro: cloud backup and multi-device sync (1 GB). On Open there is no sync. Disabling sync never deletes local data.
Nothing was ever sent anywhere, so a second device has nothing to fetch. Two in-app messages describe this, not a failure: On the Free plan, chats are saved only in this browser. and Cloud backup is paused. New chats are saved only in this browser.
Chats belong to the account that made them. On the hosted app, signing in moves you between accounts. An empty list means this account did not make those chats - they are still on this machine, under the other account. Sign in as the account you used before and they reappear. Do not clear device data while looking at the empty list.
Two accounts in one browser profile keep separate chat stores, while settings and API keys are shared across the profile. On a shared computer the boundary is the profile, not the account.
Keep on device - the default - leaves everything in this browser: sign back in and the chats are there. Remove from device (Clear & Sign Out) already ran the wipe, and on this device it is permanent. With no cloud backup that option is marked "Will lose all data". The controls themselves: your account and Pro.
Deleting removes it from this device at once. A subscribed account with the cloud trashcan turned on keeps a copy for 90 days and can restore it to every device.
Clearing site data removes the databases the conversations live in. Without a backup file or a cloud copy, there is no way to recover them.
| What | Where the bytes would be |
|---|---|
| conversations | IndexedDB, key app-chats in the keyval-store database · hosted: a database named zync-storage-<id>, or zync-storage-anon |
| images, audio, generated media | a database named Big-AGI, table largeAssets |
| settings, model services, keys | localStorage, keys beginning app- |
Nothing was written to storage, which is what the mode is for. There is no way to recover it.
Big-AGI moves work out of an older local storage format once, on first load, and then marks the job done. Data Actions -> Re-import Local Data, on the account page, clears that marker so the migration runs again.
the confirmation names the conditions under which the button does anything at all:
legacy data still on this device
at most two items per type already here
no earlier migration
Describe what you did immediately before, and on which device: where to send it. Never paste the content you were working on.
BIG-AGI
Resources
© 2026 Token Fabrics·Built with passion in San Diego