Machinery TwinProjects: saving, loading, storage
Where projects live, what gets stored, and how to not lose work.
Local-first storage
Projects are stored on your machine, in the browser's IndexedDB, not on a server. Nothing about your machine designs leaves your computer unless you explicitly export a file.
A project contains:
- Project metadata (name, description, timestamps)
- All objects, variables, motion cams, connections and state machines
- Scene settings and a thumbnail
- References to imported 3D models, the model files themselves are stored alongside, keyed by ID, so several objects (or several projects) can reuse one model without duplicating it
Save, load, new
- Save writes the current state to local storage. Saving is explicit, the app tracks unsaved changes and warns you if you close the tab with work pending, but it does not autosave.
- Load lists your stored projects with thumbnails.
- New starts a blank project.
The last opened project is restored automatically when you return to the app.
Browser storage is per browser, per profile
IndexedDB lives inside the specific browser profile you used. A different browser, a different machine, a private window, or clearing site data means your projects are not there. For anything you care about, keep an exported archive as a backup, see below.
Export & import
Export packs the project JSON and all its model files into a single archive you can store, version, or send to a colleague. Import restores it, on any machine, any browser. Details in Export & import.
Limits
The number of projects, objects, variables, cams, state machines and models per project depends on your plan (guest/free: 3 projects, 10 objects, 20 variables, among others). See Plans & limits.