AI UX PlaygroundNewsletterJoin 2K+ AI designers and PMs on Substack. New teardowns, patterns, and prompts as they drop.

Chatbot

Export Conversation

Download or share a chat as Markdown, PDF, JSON, or another portable format. Keep prompts, answers, and metadata usable outside the product.

Interactive demo

Acme renewal pricing
8 messages · Updated Jan 15

Overview

How might we design export conversation so people can trust and act on AI output?

When to use

  • Essential for documentation workflows, knowledge management, and users who need to preserve or share conversations outside the platform.

When to skip

  • Throwaway sessions where nothing needs to leave the product.
  • Chats that contain secrets the product cannot safely redact on export.
  • Real-time collaborative canvases where the source of truth is already a shared doc.

Rules

  • Exports that drop citations, tool calls, or attachments.

  • PDF-only dumps that are useless for reuse in code or docs.

  • Silent exports that include private system prompts the user never saw.

  • No preview of what will be included before download.

Evidence

ProductImplementation
ChatGPTExport and share options for conversations and shared links.
ClaudeCopy and export flows for conversation content.
NotionExport pages and AI sessions to Markdown or PDF.
ObsidianPlain-text portability of AI-assisted notes.

FAQ

What formats should conversation export support?

Markdown for editing, PDF for sharing, and JSON for tooling are the common trio. Let power users pick what they need.

Should exports include tool traces?

Include them when the user saw them in-product. Offer a toggle to omit raw traces for cleaner reading exports.

How is export different from share link?

Export creates a file the user owns offline. A share link keeps content hosted in your product with permissions.

What about PII in exports?

Warn when sensitive fields are detected, and offer redaction when you can. Never surprise-export hidden system data.