Cookies and browser storage

Last updated: 31 October 2026.

Interface preferences

The website may store preferences and cache content in your browser to support navigation and improve your experience. This storage does not replace saving your work.

Development account sessions

The development API uses host-only, HttpOnly session cookies to recognise a signed-in browser. HTTPS cookies are Secure and use SameSite=Lax. Authentication may also use short-lived cookies while completing sign-in. The project dashboard and editor send session cookies to the configured API; session tokens are not stored in localStorage.

Local cloud-project recovery

The editor automatically stores working .vlfg drafts after edits, and stores a separate before-open recovery checkpoint in the IndexedDB database volumeforge-cloud-recovery. The package may include model geometry, imported sources, textures, view settings and undo history. A random vf-recovery-tab value in sessionStorage associates the checkpoint with the tab.

Each checkpoint or draft is limited to 32 MiB. Writes keep the five newest tab entries of each kind; successfully restoring a checkpoint removes that entry. Working drafts resume in the same tab after refresh. Browser recovery never overwrites the original file on disk and browser storage may be cleared or evicted. Use Restore previous model in the editor’s Projects panel, or clear the site’s browser data to remove local checkpoints.

Managing stored data

Use your browser’s site-data settings to inspect or clear stored preferences and cached files. Clearing preferences resets the theme and documentation navigation state. Downloaded design files are managed separately on your device.

Save your work before clearing site data or reloading. See the privacy notice for hosting and external material providers.