Saving, history & exporting
Autosave has your back; the library, edit history, JSON import/export, and build artifacts cover the rest. Your code travels inside the project.
Saving
- Autosave: the working bench persists locally on every change; reload the page and you're where you left off, serial session and all.
- My Projects (Ctrl+S): a named local library with thumbnails, in File → My Projects.
- Export / Import JSON: the full project document as a file. Back it up, move machines, or hand it to someone to import.
Your code travels with the project
The Code panel's Save code with project checkbox (on by default) embeds the program in the project document itself, so saving, exporting, or sharing carries the code along: reopening the project brings the program back and runs it on boot. Untick it to keep a save wiring-only.
Edit history
File → Edit history opens two timelines. On this device is free and always on: checkpoints are recorded automatically to browser storage while you edit (about every two minutes, and whenever the bench is replaced), and they work for unsaved drafts and offline. The cloud timeline is a Pro feature on cloud-saved projects: the last 50 saves plus automatic between-save checkpoints, restorable from any device.
Build artifacts
- Image (PNG): a clean render of the circuit, grid and UI chrome stripped.
- Bill of materials (CSV): parts grouped by type and value, ready for a shopping list.
- SPICE netlist: a
.circard deck of the analog parts for cross-checking in ngspice. - Embed snippet: an iframe that shows a read-only live bench in a blog post.