Project files
Keep the work you make, and return to it later.
An in-memory example using the project-file format. It does not write browser storage or replace a workspace.
No copy yet
Save to create a project copyEdit the note, save a copy, then change it and reopen the saved copy.
Calendar, CSV reconciliation, Microscopy, Music, Wallpaper and the modernization brief share project controls. A project contains the workspace’s actual records and settings. Music projects reopen stopped; wallpaper projects retain the generated geometry.
Save and reopen
Choose Save project file for a portable JSON copy, or Save in browser to enable saves as you work. Opening a project asks for confirmation, then saves the outgoing work in Recent projects as a before-opening copy. If that recovery copy cannot be saved, the current work stays on screen. You can also download it before opening another project.
Browser storage keeps up to 20 projects per workspace and 20 revisions per project. Clearing site data removes those copies. Project files are limited to 8 MiB; the workspace reports an export or storage failure without claiming the work was saved.
Conflicts and recovery
When another tab has saved the same project, a later save stops instead of replacing it. Open the latest revision or save your work as a separate copy. History opens an earlier revision as a copy, keeping the current saved project.
Download recovery data from Recent projects before clearing damaged storage. Open that JSON file with Open project to inspect recoverable entries. Unsupported entries remain in the original recovery file. A browser backup is useful; a downloaded file is the copy you control outside the browser.
Projects and exports
Project files retain editable work. PNG and WAV exports are finished artifacts. Calendar’s iCalendar export and reconciliation’s CSV export serve other tools; their supported fields and formatting choices are separate from a full project backup. Microscopy exports describe a plan and never imply an acquisition occurred.