Skip to content

Saving & Opening

A diagram can live in two places: in the cloud, tied to your account, or as a file on your own device. You can use either, or both.

Cloud Device
Stored Encrypted, in your Schema account A .json file wherever you put it
Autosave Yes No
Version history Yes No
Share links Yes No — send the file
Works without Schema’s servers No Yes

Click Save in the ribbon, or press Ctrl+S (⌘S on a Mac).

  • The first time, Schema asks where: this device (downloads a .json file) or Cloud (asks for a name).
  • After that, a cloud diagram just saves — no questions. The status under the diagram’s name in the ribbon shows Saving… then Saved to cloud.

A save captures everything — both Engineer and Manager views, every device and its details, every connection, container, and compliance rule.

The File menu has the less common variations:

  • Save a Copy to Cloud… — creates a new cloud diagram from what’s on the canvas and switches to it. The original is left as it was.
  • Save a Copy to Device — downloads a .json copy without changing where the diagram lives. Useful as a personal backup.

Once a diagram is in the cloud, changes save themselves a few seconds after you stop making them. You can turn this off under File → Autosave to cloud if you’d rather save deliberately; the status line then reads Unsaved changes until you do.

Autosave is safe to leave on: every cloud diagram keeps a version history, and the state a diagram was in when you opened it is always kept, however long you then work on it.

If you try to close the tab or open another diagram with unsaved changes, Schema saves first (for a cloud diagram) or asks before discarding them.

Use the File menu:

  • Open from Cloud… lists every diagram in your account, most recently changed first, with search once you have more than a few. Hover a row to rename or delete it. Deleting asks first, and also removes that diagram’s version history and share links.
  • Open from Device… loads a .json file saved from Schema.

Opening replaces what’s on the canvas, and clears undo history — undo covers edits to a diagram, not having opened it.

Files are checked as they’re opened. A file that isn’t a Schema diagram produces a message rather than a broken canvas; a diagram with damaged parts (for example from hand-editing) is repaired where possible, with anything unrecognizable left out.

If a cloud diagram is changed somewhere else — another tab, another device — after you opened it, your next save is stopped rather than silently replacing those changes. Schema asks what you want to do:

  • Save mine as a copy — keeps both; yours becomes a new diagram.
  • Load their version — replaces your canvas, discarding your unsaved changes.
  • Overwrite with mine — their version stays available in version history.

A saved .json file is plain, readable JSON — open it in a text editor if you’re curious, keep it in version control next to your configs, or generate one from a script. It records node positions, types, labels and details (IP, hostname, owner, and so on), connection endpoints and styling, container bounds and subnets, and the full rule set for each view.

A view can hold up to 5,000 nodes and 10,000 connections. A cloud diagram can be up to about 700 KB of JSON (several thousand devices); beyond that, split it into more than one diagram or save it to your device. An account can hold up to 200 cloud diagrams.

If you need to bring content from a second file into the one you’re working on rather than replacing it outright, see Merging Diagrams.