What a capture package is
DRAFT· By SnipSteps
This post is a draft awaiting the founder's signature. It describes the product as the site shows it, not as the product ships.
The zip a session becomes: plain files, a published schema, and a viewer that reads it in the browser.
Every session SnipSteps captures is also written as one zip, the capture package. It is the thing you send when someone asks "how did you do that", and the thing anything you build on SnipSteps reads.
Plain files
Inside are a manifest.json that says what the package is, a session.json with the steps in order, an events.csv with the same steps as a table, one screenshot per step, and the flow diagram as an SVG. No database, no proprietary container. Unzip it and read it.
A published schema
The fields are documented on the format page, and the schema is the one the site itself validates packages against. When the format changes in a way an older reader would misread, the version number changes with it.
A viewer in the browser
Drop a package on the open page and it renders as the Quick Guide, the test evidence, the flow and the JSON, with the package's own screenshots. The reading happens in your browser and the file stays there. Send the page and the zip; no account is needed.