Both exports live in the Data group of the action rail.
Export as JSON
Section titled “Export as JSON”Export the map as JSON — nodes, routes and journeys.
The JSON export contains the whole map: the map header, every node with its type, position, links and origin, every route, and every journey with its steps annotated.
Use it for:
- Keeping a copy of a map you have invested real curation in
- Feeding the structure into another tool
- Diffing a map against an earlier export to see how the product changed
- Backing up before a large restructure
Download as a Picture
Section titled “Download as a Picture”Download the map as a picture on the canvas, or Download the tree as a picture in the tree view.
The action names whichever view is on screen, because it exports the one you are looking at — the other view is not rendered, so there is nothing to capture.
The image includes a caption and a colour key, so a map pasted into a release document still explains its own health colours to someone who has never opened Atlas.
Use it for release review decks, sign-off documents, onboarding material, and anywhere a picture of the product’s shape is worth more than a link.
What Is Not Exported
Section titled “What Is Not Exported”Coverage numbers and health states are computed from live execution data. They are shown on the image export because it is a snapshot, but the JSON export carries the map’s structure rather than a frozen coverage report.
For a coverage or readiness artifact, use Reports or the release sign-off report.