How visualOS stores your data

Your device and your folder

visualOS keeps a working copy and local changes in browser/app storage. A connected folder contains the shared workspace and media. Local storage can contain work not yet delivered to that folder; it is not always a disposable cache.

All devices share the workspace file canvas-data.json in that folder. When a newer version arrives from another device, visualOS combines it with local changes that have not reached the folder yet, rather than simply replacing one with the other.

Saving is not the same as cloud delivery

The app confirms local saving and folder saving separately. Your provider then transfers files. A device that is closed or offline receives them later. See sync across devices.

Preserve independent copies

Do not clear browser site data or uninstall an app while it may hold the only copy of recent changes. Browser profiles and different website origins have separate storage. Use backup exports and back up the complete downloaded folder, including hidden files.

Cloud sync propagates changes and can propagate deletions; it is not a substitute for an independent backup. History, conflict copies and guarded writes reduce risk, but do not promise protection from every storage failure or external deletion.

Without a folder

Your data stays in that browser/app’s storage. Clearing it, private-mode behaviour or storage pressure can remove it. Export backups regularly and check for local save errors.