Claude Exporter: How to Export Claude Conversations to PDF, Markdown, and More

In December 2025, Koi Security researchers discovered that four Chrome extensions with over 8 million combined installs were silently harvesting AI conversations from Claude, ChatGPT, and eight other platforms. The extensions, which included Urban VPN Proxy and three related tools, overrode the browser's fetch and XMLHttpRequest APIs to intercept every AI conversation before routing it to external analytics servers. Users had no toggle to disable the collection. The only fix was uninstalling entirely.

That finding frames the central tension in exporting Claude conversations. Anthropic's built-in data export produces a full JSON dump of your conversation history, but it's not human-readable and offers no per-conversation control. So people turn to browser extensions for cleaner formats like PDF and Markdown, and choosing the wrong one puts every prompt and response you've shared with Claude in someone else's hands.

The good news: several open-source, privacy-first Claude exporter extensions now support six distinct output formats across Chrome and Firefox. This guide compares the four leading options, covers Anthropic's native export, and walks through how to evaluate any extension before installing it.

Before reaching for a browser extension, check what Anthropic already provides. Claude.ai includes a data export feature accessible through Settings > Privacy on the web app or Claude Desktop. Click "Export data," and Anthropic sends a download link to your registered email address.

The export arrives as a ZIP archive containing JSON files with your full conversation history and account data. It's comprehensive but inconvenient for most use cases. The JSON format preserves every message, but you'll need a script or parser to turn it into something readable. There's no way to export a single conversation, filter by date range, or choose a different output format.

Limitations worth knowing before you rely on this method:

• The download link expires 24 hours after delivery
• Exports are not available on iOS or Android
• Exported data cannot be imported into another Claude account
• Model information (whether a message used Opus, Sonnet, or Haiku) is not included per message
• Claude Projects cannot be exported through this feature
• Memory data (your stored preferences and context) is not part of the export

The built-in export works for compliance requests, full account backups, or as raw material for custom processing scripts. For sharing a single conversation with a colleague in PDF, or archiving research threads as Markdown, you'll need a browser extension.

Six formats are available across the leading extensions: JSON, Markdown, plain text, PDF, HTML, and CSV. No single tool supports all of them, so the right choice depends on which formats you actually need and whether you value open-source code over polish.

Claude Exporter by agoramachina (Chrome + Firefox)

The most feature-complete open-source option. This extension supports JSON, Markdown, and plain text exports with full branch awareness, meaning it correctly preserves all conversation paths rather than flattening them into a single thread.

• Bulk export of filtered or all conversations as a ZIP file
• Artifact extraction: code, documents, and other generated content saved as separate files
• Searchable conversation browser with sorting by name, date, project, and model
• Automatic model inference for conversations that used default model settings
• Light and dark mode support

The trade-off is format coverage. There's no PDF or HTML export, so if you need print-ready output, pair this with another tool. Rate limiting can slow large batch exports, and VPN usage occasionally triggers 403 errors from Claude's API. Version 1.10.17 (May 2026), open source under MIT license, 1,578 Firefox users with a 3.5/5 rating.

Claude Exporter by squired (Chrome)

A minimal extension built for single-conversation exports with the smallest footprint of any option at 25 KiB. It produces clean Markdown files, self-contained HTML documents with inlined styles, and print-quality PDFs through your browser's native print dialog.

• Handles text, code blocks, artifacts, thinking blocks, attachments, and branched conversations
• Clipboard copy in Markdown or HTML for quick pasting into other apps
• No backend, no analytics, no telemetry, no third-party services

The limitation is straightforward: no bulk export. If you need to download your entire conversation history at once, this isn't the right tool. But for grabbing a single conversation in a readable format, the simplicity is a feature. Version 0.1.0 (April 2026), open source under MIT license, 1,000 users.

AI Chat Exporter by Mark Zhao (Chrome)

The most popular Claude exporter by user count, with over 70,000 installs and a 4.9/5 rating from 724 reviews. It supports the widest range of formats: PDF, Markdown, text, CSV, and JSON. It also works with ChatGPT and Gemini, making it useful if you use more than one AI assistant.

• PDF customization: light/dark themes, page formats, margins, font sizes, table of contents, and page numbers
• Selective export of specific portions of a conversation
• Available in 31 languages

The catch: PDF exports are limited to 3 per day on the free tier, with a paid PRO plan for additional usage. All other formats remain unlimited. The source code is not publicly available, so the "conversations stay on-device" claim relies on trust rather than verification. Version 3.1.0, 582 KiB installed size.

Claude-Conversation-Exporter by socketteer (GitHub)

A developer-oriented tool that requires manual Chrome installation through Developer Mode. Supports JSON, Markdown, and plain text with full branch-aware bulk exports.

• Metadata control with optional timestamps and model information
• Bulk export as ZIP files with a searchable conversation browser
• Requires your Claude Organization ID from account settings during setup

This extension has no Chrome Web Store listing, which means no automatic updates. You'll need to pull new versions from the GitHub repository manually. That's a feature for users who want to audit every update before installing it, and a friction point for everyone else. Open source, fully auditable, free.

Store and search your exported Claude conversations

A shared workspace where exported conversations are versioned, indexed for semantic search, and ready to share with granular permissions. Start with a 14-day free trial.

Start 14-Day Trial

The Koi Security incident proved that Chrome Web Store listings alone don't guarantee safety. Four extensions passed Google's review process while actively harvesting AI conversations from millions of users. Before installing any Claude exporter, work through this checklist.

Check the source code. Open-source extensions let you read every line before installing. Three of the four tools reviewed above publish their code under MIT licenses. If the code is closed, you're trusting the developer's privacy claims without verification.

Review the permissions. A Claude exporter needs access to claude.ai and possibly browser tabs. It should not need access to all URLs, your browsing history, or broad network request interception. The malicious Urban VPN extensions overrode the browser's fetch and XMLHttpRequest APIs globally, intercepting traffic from every site, not just AI platforms.

Monitor network requests. Open your browser's developer tools (Network tab) while using the extension. A legitimate exporter should make requests only to claude.ai to read your conversation data. Any calls to unfamiliar analytics or data collection endpoints are a red flag.

Verify the developer's identity. Extensions maintained by identifiable developers with linked GitHub repositories, real contact emails, and consistent update history are lower risk than anonymous or abandoned projects. Check the extension's update cadence: a tool last updated two years ago may have unpatched vulnerabilities.

Watch the install size. A simple exporter that parses page content and formats it shouldn't need hundreds of kilobytes of code. Unusually large extensions may bundle functionality you didn't ask for. For reference, the squired Claude Exporter does its job in 25 KiB.

Exporting solves one problem and creates another. A folder of 200 Markdown files is technically portable but practically useless if you can't search through them or share specific conversations with your team.

Local folders work for personal archiving if you maintain a naming convention. Tools like grep or ripgrep can search file contents, but there's no semantic search. You'll need to remember the exact words Claude used, which defeats the purpose of archiving conversations you might revisit months later.

Note-taking apps like Obsidian handle Markdown natively and offer full-text search, tags, and bidirectional links between conversation files. The Claude to Obsidian Chrome extension even exports directly into Obsidian's vault format. For individual research and reference, this combination works well.

Cloud storage (Google Drive, Dropbox, OneDrive) adds sharing and basic filename search but treats exported conversations like any other document. You can find a file by name, but searching across the content of every conversation requires opening them individually.

Team workspaces become relevant when exported conversations contain project decisions, research findings, or code reviews that other people need. Fast.io's Intelligence Mode auto-indexes uploaded files for semantic search, so you can ask questions across an entire archive of exported conversations rather than opening files one by one. Version history tracks changes if conversations are updated or annotated, and granular permissions control who can access specific files. For teams collaborating with AI-generated content, the workflow is export from Claude, upload to a shared workspace, and let the search layer handle discovery.

The right destination depends on your use case. Solo archiving? Obsidian. Team reference? A workspace with semantic search. Compliance or legal holds? Start with Anthropic's built-in export for the complete JSON record, then supplement with formatted exports for readability.