Skip to content

Export conversations

Export conversations as separate files to keep a record, share them, or use them with other tools. Files are saved to a folder you choose.

To export the open conversation, click Export in the conversation toolbar, then confirm the format and destination.

To export several conversations at once, click Select in the conversation list, check the conversations you want, and click Export selected. You can also open Export in the sidebar and choose a range:

  • All: every conversation Context has found.
  • Filter: a group of conversations selected by Agent, working directory, and modification date.
  • Favorites: conversations in your favorites.
  • Selected: conversations you checked manually, or the single conversation brought in from the conversation toolbar.

The page shows an estimated export count. Filter uses the conditions on the export page. To export conversations found by keyword search, select them manually in the search results, then click Export selected.

You can export up to 10,000 conversations at once. If your range exceeds this limit, filter by Agent, working directory, or modification date and export in batches.

Exporting a single conversation is free. Exporting several at once requires activation. See Activation and device management for instructions and the website pricing page for plans and included features.

Format When to use it
Markdown (.md) To edit the content, organize notes, or use it with AI and text tools.
HTML (.html) To read offline in a browser, share, or print.
JSON (.json) To process conversation data with code or other tools. Data uses the ATIF v1.8 format.

Markdown or HTML is usually enough for reading or keeping a record. Both export user and AI messages by default. You can choose from the following content types, keeping at least one selected:

  • User messages
  • AI messages
  • System messages
  • Reasoning
  • Tool calls
  • Tool results

For example, select only user messages to collect your own questions. To preserve tool activity, select both tool calls and tool results.

JSON exports all conversation data Context has read.

Under Output settings, choose the destination folder and how files are organized. The examples below use Markdown, with paths relative to your chosen folder:

Organization How files are saved Example path
By working directory (short path) Uses the directory’s short name, adding parent directory names to distinguish duplicates. project/Travel plans.md or work-project/Travel plans.md
By working directory (full path) Combines the full path into one folder name, shortened if too long. Users-name-work-project/Travel plans.md
By Agent Groups conversations from the same Agent. Codex/Travel plans.md
By month Groups by the month the conversation started, with a separate group for conversations without a date. 2026-10/Travel plans.md
All in one folder Saves directly to your chosen folder. Travel plans.md

Files are named after conversation titles. Characters that cannot be used in file names are adjusted automatically. The example path on the page updates when you change the organization or file format.

If a file with the same name already exists, choose Keep both, Skip existing file, or Overwrite existing file. Use Keep both to preserve the old version. Overwriting replaces the existing file.

Once you have confirmed the range, content, and destination, start the export. The progress area shows how many conversations were exported, skipped, or not exported. If any were not exported, expand the details to see why, then retry as needed.

Export requires the Agent’s original records. If Context reports that a conversation changed during export, wait for the Agent to finish saving, then try again. See Export failed or only partly completed for other issues.

Cancelling does not delete files already exported. Before sharing, check for private information such as reasoning, tool results, and file paths. For long-term storage, also check that attachments have been saved separately. See Data and privacy for how exports relate to backups.