Local Browser Saves & Recent Projects
What Gets Saved Locally
While you edit, Vtila saves your open documents to IndexedDB in your browser — database name vtila-projects. Each project stores layer pixels (as PNG data), positions, opacity, blend modes, text settings, masks, and PDF page structure. Images, PSDs, and PDFs you open are saved in this internal format, not as copies of the original files.
Auto-Save and Status Bar
Changes are saved automatically about two seconds after you stop editing. The status bar shows Saving locally…, Unsaved changes, or Saved locally in browser. Use File → Save or ⌘S to save right away without waiting. Auto-save pauses while AI tools are running or while you are editing text inline.
Recent Projects
On the welcome screen, Recent projects lists everything stored in your browser. Click a row to reopen that document with layers intact. Hover and click ✕ to remove a project from browser storage. If you had several tabs open, each document appears as its own entry after it has been saved.
What Is Not Saved
Undo and redo history is not stored — after you reopen a project, the history panel starts fresh. Your original file on disk is not kept in the browser; only the editable state inside Vtila. Selections and in-progress transforms are not restored.
Export vs Browser Save
Browser save keeps you editing inside Vtila on the same device and browser. To keep a file on your computer or share it, export: ⇧⌘S or File → Export for PNG, JPEG, or WebP; File → Save as PSD for layered interchange; Export as PDF for multi-page work.
| ⌘S | Save to browser storage now |
| ⇧⌘S | Export as PNG |
Limits and Privacy
Storage is per browser on this device only — not synced to the cloud and not shared with other browsers or profiles. Clearing site data, uninstalling the browser, or using a private window that discards data can delete saved projects. If storage is full, delete old entries from Recent projects or export important work as PSD or PNG. Nothing is uploaded; AI and saves run locally.