Projects and documents
Auto-save, versions, cloud sync and conflicts: where your work is at any moment, and how to get an old state back.
aukimi saves two kinds of thing, and the difference decides what you can do with them later.
| Project | Document | |
|---|---|---|
| Holds | the state of every studio | one studio's file |
| Created from | New project, on the dashboard | Start straight in a module |
| Cross-studio transfers | yes | no |
| Cloud save, sharing, collaboration | yes | no, Upload to Cloud first |
| Convertible | , | Convert to Project |
A project is the normal unit of work. A document is the fast lane for "I just want to draw something", and it can be promoted later without losing anything. The reverse, turning a project back into a document, is deliberately not offered.
Auto-save#
On by default, interval configurable in Settings → General. Your work is written to IndexedDB, with localStorage as a fallback, scoped per project: a studio's state in one project can never bleed into another.
Ctrl+S forces a save now. It is rarely necessary; it is there for the reflex.
Local storage is finite, and the browser owns it. aukimi warns you when the quota is nearly full instead of failing a save silently. Clearing site data for aukimi.com erases every project that was never uploaded, with no undo.
Versions#
Each project keeps a version history, reachable from its card on the dashboard.
- Autosaved versions are taken as you work.
- Saved versions are the ones you asked for, Save a version. If nothing changed since the last one, aukimi says so rather than storing a duplicate.
- Before a restore versions are written automatically the moment you restore something, so a restore is itself undoable.
Versions live in the browser, and the newest N per project are kept. Pin one to keep it past that limit, and, when cloud save is on, to copy it to the cloud. Preview a version, or pick a second one and compare the two side by side, before restoring.
Cloud save#
Off unless you turn it on (Settings → Cloud Save), and it needs a subscription. Once on, aukimi uploads the project roughly every 60 seconds when something has changed.
What travels is one file per studio that has state: .engine, .ink,
.sculpt3d, .p3d, .daw and so on, listed in
Import and export: plus the project's binary assets and,
where the studio supports it, its undo history.
The dashboard labels each project with where it lives: On this machine, In the cloud, Shared with me.
Conflicts#
Changed elsewhere, needs a decision.
That state means the cloud copy moved since your last sync: another machine, or another tab. aukimi does not guess. It offers exactly two answers:
- Keep local (overwrite cloud): your current work wins; the cloud version is replaced.
- Keep cloud (discard local): the cloud version wins; your local changes are lost.
There is no automatic merge, and that is on purpose: a half-merged sculpt or a half-merged timeline is worse than either version whole. If both sides matter, export the local one first (File → Export, or the per-studio export in Import and export) and only then take the cloud copy.
Modification history#
Separate from versions, and readable: each project keeps a log of what changed and when, grouped by day, on the dashboard under History. It answers "what did I do on Tuesday", not "give me Tuesday's file back", that is what versions are for.
Offline#
The app keeps working with no connection. Auto-save is local, so nothing is lost; the sync pill says Offline and the cloud copy stays at your last sync. New projects created offline are labelled as such and upload when you come back.