Account
BillingExport AI conversations to text
Text export creates a simple readable .txt file from a supported conversation. Use it when you want less structure than Markdown and do not need JSON.
Browse docsMenu
Browse docs
Before you start
Open a supported AI conversation, or choose a saved capture that still has full text in browser storage. Use Text when you want a plain readable file without Markdown syntax.
Where to export text
Text export is available from the popup, right-click menu, and Export Studio. The floating button does not show Text directly; use its Studio button first.
- 1
Popup: choose Text for the current chat.
- 2
Right-click menu: choose Export to Text on a supported chat page.
- 3
Export Studio: choose Text after previewing the chat or selected messages.
- 4
Floating button: choose Studio, then choose Text.
Export to text
Text export turns the captured conversation into a plain .txt file. It is useful for quick review, simple note apps, and local scripts that do not need Markdown or JSON. See the Free and Pro limits in the capability table below.
- 1
Open the popup, right-click menu, or Export Studio.
- 2
Choose Text or Export to Text.
- 3
Download the .txt file.
- 4
Open it locally or paste the text into your own tool.
Limits
Text export does not require Pro and should not count toward PDF, Word, or Notion daily limits.
When plain text is useful
Plain text is the lowest-friction format for quick review, grep-style searching, or pasting into tools that do not preserve Markdown. It has less structure than Markdown on purpose. Use Markdown when headings, code fences, links, or metadata matter.
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 / local day + watermark | Unlimited + no watermark | The browser controls the final PDF save dialog | |
| Word | 3 / local day | Unlimited | Rich export runs locally |
| Text | Unlimited | Unlimited | Plain local text export |
| Image | Watermarked | No watermark | Size preflight may block very large captures |
| JSON | Unlimited | Unlimited | Use for local developer workflows |
| Notion | 3 / local day | Unlimited | Requires the current authorized Notion workflow |
| Google Docs | 3 / local day | Unlimited | Requires the current authorized Google Docs workflow |
| Obsidian | Unlimited | Unlimited | The browser cannot prove final note creation |
