breadboard
08 · Your work

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 circuit and Code editor buffers are saved as a local draft. Reloading restores your work and starts a new simulation from power-on; it does not resume the processor or restore the previous Serial output.
  • Save to My Projects (Ctrl+S): keep a named project in your library. File → My Projects… (Ctrl+O) opens the library. Local projects belong to this browser; signed-in cloud sync makes cloud-saved projects available on other devices.
  • File → Export… → Project: download a .breadboard.json file with parts, wiring and attached code. Reopen it with File → Import project (.json)….
Browser storage is local to this browser profile and site. Clearing site data removes local drafts and saves. Keep an export or a cloud-saved copy of work you want to keep. A JSON export stores references to uploaded firmware and microSD files, so keep the original files too; another browser may need you to upload them again.

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 source back. MicroPython scripts can run on boot once the board has MicroPython firmware; Arduino source needs Compile & upload when you change it. Untick the checkbox to omit the Code panel source from the saved document.

Share a copy

Sign in, then use File → Share project… → Create link. The link is a snapshot of the bench when you create it; later edits do not update that snapshot. Anyone with the link can open a local copy without an account. You can revoke the link in the same dialog.

Shared and gallery projects open with their Code scripts waiting for the visitor to press Run on board. Real-internet access also needs the visitor's own consent. See running code and networking for the next steps.

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 .cir card 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.