Promotional offer50% off every paid plan, billed monthly.See pricing
Billing and plans

Exports

PDF and Word for people, CSV and JSON for tools, pushing for systems. Exports work on every plan, because evidence you cannot take with you is not yours.

Updated
8 October 2026
Read
4 min
For
Everyone; all plans
Formats

Four formats, two audiences.

PDF
The deliverable format: a formatted document built from what you choose, such as the timeline, transcript, and findings, ready to send to a client or attach to a sign-off.
Word (.docx)
The same document, editable, for teams that annotate findings or fold the export into their own report template.
CSV
Rows for spreadsheets: findings with their type, severity, review state, evidence quote, and timestamp.
JSON
Structured data for scripts and pipelines.
Where

Three ways out.

  • From a recording

    Export on the recording page asks where it should go: Download, Google Sheets, Google Docs, or Google Drive. Choose the content (timeline, transcript, findings) or, for Sheets and Docs, the sections and their order, then the format. Export settings set the name, timestamps, speaker names, screen images, and an optional time range.

  • From Artifacts

    Export on the Artifacts page, or on one recording's findings page, downloads the list as CSV: every bug across a release, every decision for the quarter.

  • Into your tools, not a file

    If the goal is findings landing in another system, that is pushing, not exporting: connect Jira, Linear, Notion, Slack, or a webhook and send them there directly.

Exporting a recording: where it goes, what it contains, and the format.
Choosing

Which output for which job.

  • Client deliverable

    PDF with the timeline and findings. Citations print with their timestamps, so the document stays checkable against the source.

  • Engineering handoff

    Push to the tracker instead of exporting: a Jira issue with a timestamped evidence link beats a PDF row.

  • Analysis

    CSV from Artifacts, filtered to what you are analysing.

  • Archive

    PDF or Word per recording. Remember plan retention: export before a recording ages out of your plan's window if you need the derived record longer.

For continuous delivery into trackers and channels, see the Jira, Notion, and Slack guides.

Common questions

Exports, answered.

  • All of them, free included. Downloads are part of the product, not an upsell: your evidence is yours to take.

  • Yes. In the export dialog, choose Google Sheets, Google Docs, or Google Drive and connect your Google account the first time. The export lands under your own Google account, and Open in Google takes you to it. Downloads work whether or not Google is connected.

  • Answers are sent rather than exported: push a cited answer to Slack, Notion, or your webhook and it arrives with quotes and timestamped links intact. For a file, the report export includes the recording's substance.

  • Not yet. Exports are clean and unbranded, and white-label presentation is on the roadmap. Nothing in an export identifies your client's stack or your internal setup.

  • One row per finding: title, type, severity, review state, the verbatim evidence quote, its timestamp, and when it was created. PDF and Word exports include screen images only for recordings with visual evidence, and only when Include screen images is on.

Related

Where exports matter most.