Understand your local file library
The editor stores copies in IndexedDB on your device. The library belongs to the browser profile and website origin that created it. A different browser, device or subdomain has a separate library.
What stays local, and what still uses the network
The browser downloads editor code and font resources from our Cloudflare-hosted website. Selected document content is processed on your device; this service has no document upload endpoint. Hosting still receives ordinary connection information. Local processing does not make the browser library a cloud backup or a cross-device sync service.
A useful copy, not your only backup
Copies are updated on opening and export, not after every keystroke. Clearing site data, private browsing and storage eviction can remove them. The website cannot recover copies that the browser has already removed. Download your work and keep a separate backup.
- Download after a meaningful change and keep the file in a folder you control.
- Do not use private browsing as a place to keep the only saved copy.
- Before clearing site data or changing browser profiles, download every copy you need.
Moving from the original website
The editor now lives at app.editdocfree.com. In the browser you used before, visit the recovery page on editdocfree.com, download the stored copies individually, then open those downloads in the new workspace. Only stored snapshots can be recovered, not edits that were never saved or exported.
If a file is missing from the recent list
Check that you are using the same browser profile and the correct subdomain. Look in your device’s Downloads folder for an exported copy. If the browser removed its site data, this website cannot restore it from a server. The recovery page only reads snapshots still present on the original website origin; it cannot retrieve unsaved edits.