Help with your sessions.

Getting started

1. Create a box with a name and website address.
2. Open the box and sign in on the website if needed.
3. Use Save before leaving when you need a manual save. Automatic saving runs while using the browser.
4. To move supported data, export a file, transfer it securely and import it on the other device.

Why did a website ask me to sign in again?

Websites can expire or revoke sessions, bind access to a device, or use data the app cannot transfer. A successful import does not guarantee an active login. Sign in again inside that box when requested.

What can be restored?

The app supports compatible cookies, localStorage, sessionStorage and IndexedDB data, within the session file limit of 20 MiB. Some data may be unavailable, unsupported or stale; review the import preview before continuing.

Cookie attributes and partition contexts may not be fully verifiable. Review the import summary and compatibility options; website-specific rules can still prevent restoring a sign-in. CacheStorage contents, OPFS files, service workers, partitioned iframe data and some IndexedDB values are not transferred. Popup and external-browser login flows may not work.

Why is my Android WebView unsupported?

Separate boxes require the WebView multi-profile feature. Update Android System WebView or Chrome through your device’s supported update mechanism, then use the app’s WebView check. Operating-system version alone does not guarantee support.

Importing, replacing and canceling

Choose a new box or review the replacement target. Importing into an existing box replaces its supported session data after confirmation. Cancellation is available before the commit phase. Keep an export of important data before replacement.

Is there a Session Spaces cloud backup?

No app account or app cloud-sync service is provided. Keep your own exported copies securely. Device backup behavior depends on the operating system and device settings.

How to delete data →