Cloud version and local cache
Which copy is authoritative, the order of saving and uploading, how images go up, and what is left when you are signed out.
Which copy is authoritative
Projects on ordinary free accounts stay on this device; signing in does not upload them. All three active subscription tiers allow unlimited cloud projects. With an active subscription or recorded legacy Global access, the current project automatically starts syncing when you create, import or open it, including the full draft, images and supporting project records. A local copy stays on your device. Other unopened projects are not scanned or uploaded. The web app uses IndexedDB in the current browser; Desktop uses a local project folder and SQLite. Unlimited project count does not mean unlimited storage capacity: individual file and upload size limits still apply.
Opening a linked project runs this check:
- Compare against the summary in the project list first: unchanged cloud and nothing pending locally means no full pull—start writing.
- If the cloud is newer and your local copy is clean, pull it and overwrite the cache; desktop then rewrites the design file and derived memory.
- If you have pending local edits (including the 350 ms debounce) and the cloud moved on too, that is a conflict, and both copies are kept.
Automatic sync and the version check before project AI apply to the current web app. Desktop requires a client that supports these features; older versions may behave differently.
The order of saving and uploading
Every edit saves locally first, without waiting for the network. With valid cloud access, saved changes are batched for upload in the background; each keystroke is not uploaded immediately. Network failure never undoes a local save. Reconnecting retries the latest draft while access is valid. Expiry or a failed access check pauses uploads while local writing continues.
- Save notices distinguish Saved locally from Synced to cloud. A successful local save does not mean an upload has finished. Routine saves and background sync do not repeatedly show notices; errors and recovery are reported separately.
- An open linked project reconciles on window refocus and on a 60-second summary heartbeat; background tabs run no timer, and switching away or closing the project stops it. Heartbeats never swap your draft while you are typing.
- Each project chat turn, one-shot skill, rewrite, image task, import analysis and maintenance task checks cloud access and confirms that the latest local content has synced first. Offline, conflicting or failed sync blocks that AI task. Credit packs do not grant cloud access. The start flow before a project exists and cost-only estimates are handled separately.
How images go up
On the way up, long data-URL images in the draft and in records are split into content-addressed blobs: the same image shares a stored asset within each project, and the project JSON keeps only a light reference. Opening and reconciling restore images from those references before handing the draft to the local cache. First upload takes the same path—if the images have not finished, the cloud project just created goes to the trash and no local link is made, so no half-finished project is left behind.
- A reference whose image cannot be fetched stays in the draft as it is, with a sync error attached; it is not quietly deleted.
- A single image over 20 MB of raw bytes, or a draft still over 32 MB after dehydrating images, is marked as an error and the same content is not re-uploaded in a loop. Split or shrink such images.
Signed out, or offline
Offline writing saves locally and uploads on reconnect while cloud access remains valid. Expiry does not delete existing work: local editing, saving and export continue, and existing cloud projects remain available to read, export or delete. Renewal checks both versions before resuming sync. If the cloud project is deleted, its local link is removed while the work itself stays on the device.
Limits and troubleshooting
- Sync reconciles whole content versions, not field-level three-way merges—which is exactly why a conflict keeps both sides instead of auto-merging.
- On a sync error keep the page and the local project; never clear site data. A repeated failure stays visible as “Sync failed” with a reason.
- Before changing devices, confirm that the current project has synced, then open its cloud version with the same account. Export a .quill.json pack first for local-only projects or edits that have not uploaded; do not migrate by copying browser storage.
Recovering after a conflict: Conflict copies; backup and migration: Exporting and importing a project pack.