Updated on 2026-06-12
Export AI conversations to JSON
JSON export is for local and developer workflows. It should describe conversation structure without implying that RecallBase provides a server upload API for chat content.
Before you start
Use JSON when you need structured local data rather than a readable document.
Export JSON
Shared Free/Pro capability table: Markdown is unlimited on Free and Pro. PDF is 3/day with a footer or watermark on Free and unlimited with no footer or watermark on Pro. Word/DOCX is 3/day on Free and unlimited on Pro. Image/PNG is watermarked on Free and has no watermark on Pro. JSON is unlimited. Notion is 3/day on Free and unlimited on Pro. Obsidian handoff and local RecallBase import are unlimited, but browser handoff cannot prove a final Obsidian note was created. JSON is useful for local scripts, migration, and debugging your own archive.
- 1 Open Export Studio.
- 2 Choose JSON.
- 3 Generate the structured export.
- 4 Store it locally or process it with your own tooling.
Privacy boundary
Do not paste raw JSON exports containing sensitive conversations into support channels.
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 |
| JSON | Unlimited | Unlimited | Use for local/developer workflows |
| Notion | 3/day | Unlimited | Export/handoff behavior depends on the current browser workflow |
| Obsidian | Unlimited | Unlimited | Browser cannot prove final note creation |
| Local RecallBase import | Unlimited | Unlimited | Requires CLI/native host |