Local storage and recovery
Where files remain and how optional temporary recovery works.
Last updated: 2026-10-10
Browser memory by default
Selected files and results remain in browser memory during use. They do not sync with your account or go to the site server. Closing or losing a tab may require selecting files again.
The homepage processes files directly. Single Export usually completes in the Stripe dialog, keeping the original file in page memory; bank verification or other payment channels may redirect. Purchase credentials and recovery codes retain rights, not documents. After clearing files or changing devices, select the same original input again.
Before sign-in or payment
You can explicitly opt to store input files in the current browser’s IndexedDB. This is optional: proceed without storage and select files again on returning.
Only inputs and a local manifest are saved, not duplicate previews or ZIPs. Recovery availability is shown only after the complete write commits. Quotas and private browsing can prevent storage.
A 15-minute recovery window
After 15 minutes, files are no longer eligible for recovery. Startup, returning to the foreground and recovery attempts clear expired or incomplete records. While active, the app also attempts cleanup at expiry.
A closed or suspended browser cannot guarantee a timer runs. Expiry limits recovery, not deletion at an exact time. Record deletion does not guarantee physical disk or swap-memory erasure.
Clearing and retrying
You can clear local files. Signing out or changing accounts clears temporary recovery in this browser. Triggering a download clears corresponding temporary inputs, while the in-memory result may remain available for retry.
Starting a download does not prove operating-system saving. Check your destination and retry when needed.
When recovery fails
Choose the input files again. Confirmed Pro access stays valid even if local storage has been removed. This does not require another payment.