Export AI conversations to JSON
JSON export is for local and developer workflows. In the browser extension, JSON and Copy JSON are available from the right-click menu on supported chat pages.
Before you start
Use JSON when you need structured local data rather than a readable document. JSON is a right-click workflow in the browser extension.
Where to export JSON
JSON is currently a right-click menu export. It is not shown in the popup, floating menu, or Export Studio.
- 1
Right-click on a supported AI conversation page.
- 2
Choose Export JSON to download a file.
- 3
Choose Copy JSON to copy the structured data.
- 4
Use Markdown or Text if you want a readable export instead.
Export JSON
JSON is useful for local scripts, migration, and debugging your own archive. See the Free and Pro limits in the capability table below.
- 1
Right-click on a supported AI conversation page.
- 2
Choose Export JSON or Copy JSON.
- 3
Save the file, or paste the copied JSON into your local tool.
- 4
Do not paste sensitive JSON exports into support channels.
Privacy boundary
Do not paste raw JSON exports containing sensitive conversations into support channels.
When JSON is the right export
Use JSON when another local tool, script, or agent needs structured conversation data. JSON is not meant to be the easiest human reading format. For review, use Markdown or PDF. For automation, keep the JSON local, inspect the fields, and avoid sending sensitive prompt or answer content to third-party processors unless you explicitly choose that workflow.
Export entry point table
Use this table to see where each browser extension export action appears.
| Action | Popup | Floating button | Right-click menu | Export Studio |
|---|---|---|---|---|
| Open Export Studio | Yes | Yes | Yes | Already there |
| Markdown download | Yes | Yes | Yes | Yes |
| Copy Markdown | Yes | Open Studio first | Yes | Yes |
| Yes | Yes | Yes | Yes | |
| Word / DOCX | Yes | Yes | Yes | Yes |
| Image / PNG | Yes | Open Studio first | Yes | Yes |
| Copy Image | Yes | Open Studio first | Yes | Yes |
| Text | Yes | Open Studio first | Yes | Yes |
| JSON | No | No | Yes | No |
| Copy JSON | No | No | Yes | No |
| Obsidian | Yes | Yes | Yes | Yes |
| Notion | Yes | Yes | Yes | Yes |
| Settings | Yes | No | Yes | No |
Free and Pro export capability table
The same limits apply across export docs, pricing, and the browser extension.
| Export target | Free | Pro | Notes |
|---|---|---|---|
| Markdown | Unlimited | Unlimited | No Pro required |
| 3/day + footer/watermark | Unlimited + no footer/watermark | Browser PDF dialog limitation applies | |
| Word / DOCX | 3/day | Unlimited | Rich export runs locally |
| Image / PNG | Watermarked | No watermark | Size preflight may block very large captures |
| Text | Unlimited | Unlimited | Plain local text export |
| JSON | Unlimited | Unlimited | Use for local/developer workflows |
| Notion | 3/day | Unlimited | Sending to Notion depends on the current browser workflow |
| Obsidian | Unlimited | Unlimited | Browser cannot prove final note creation |