Web2MD 2.0

Export Your Entire AI Chat History to Markdown

A Chrome chat-history exporter for researchers, developers, and anyone switching AI assistants. Export one open conversation free; signed-in bulk history export requires Web2MD Pro. Download one searchable .md file or one file per chat.

Quick answer

To export an AI chat history, open the AI platform while signed in, click Web2MD, choose Export all conversations, select the chats, and download them as Markdown. One open chat can be exported free; listing and bulk export require Pro or the $15 30-Day Pro Pass. Web2MD supports five platforms and keeps titles, dates, source links, turn structure, code blocks, and citations where available.

Supported AI platforms

When bulk AI chat export is useful

Full-history export is most useful when the conversation itself is work product—not just a disposable answer.

Move from one AI assistant to another

Keep the useful conversations you already paid for and import selected Markdown files into a new ChatGPT Project, Claude Project, Gemini Gem, or notes vault.

Build a searchable personal knowledge base

Store one file per conversation in Obsidian, Logseq, or Git. Titles, original dates, platforms, and source URLs make the archive sortable and searchable.

Preserve research before an account or plan changes

Create a portable copy of project decisions, cited sources, code explanations, and long research sessions before deleting an account or changing providers.

Hand off AI-assisted work with context

Export the relevant chats as one file with a table of contents so a teammate or another agent can see the questions, constraints, decisions, and cited evidence.

How to export every conversation

  1. 1Install Web2MD and sign in to Web2MD Pro.
  2. 2Open ChatGPT, Claude, Gemini, DeepSeek, or Perplexity while signed in to that platform.
  3. 3Open Web2MD and choose “Export all conversations”.
  4. 4Select every conversation or only the chats you want to keep.
  5. 5Download one Markdown file with a table of contents, or one .md file per conversation.

Choose the archive format

One merged Markdown file

Best for search, handoff, and AI context. The file starts with a table of contents linking to every exported conversation.

One file per conversation

Best for Obsidian or Logseq. Each file includes YAML frontmatter with its title, original conversation date, platform, and source URL.

First-party validation report · 2026-11-05

What “complete export” does—and does not—mean

Download a synthetic Markdown sample

The table below describes the current implementation and automated regression coverage. It is a product-team report, not an independent audit. Provider interfaces change, so Web2MD reports per-conversation failures instead of claiming a lossless account backup.

PlatformHistory discoveryContent validationKnown boundary
ChatGPTAccount conversation API with rendered-sidebar fallbackTitles, dates, turns, code and links; merged/per-file formatting testsNot a replacement for the official OpenAI account export; deleted and inaccessible chats are excluded
ClaudeSigned-in account list plus page-by-page exportRegression coverage for virtualized long chats and detached early turnsProjects, attachments and provider-specific artifacts require spot checking
GeminiRendered sidebar discovery; per-chat browser RPC fast pathTurn parsing, ordering, malformed payload and Markdown formatting testsSidebar does not expose reliable original timestamps for every chat
DeepSeekSigned-in conversation APIStructured user/assistant extraction and shared export-format testsProvider DOM/API changes can require an extension update
PerplexitySigned-in thread listMulti-turn and uneven question/answer regression tests; rendered citations kept as linksOnly content returned or rendered by the provider can be exported

Included when the provider exposes it

  • Conversation title, source URL and available date
  • User/assistant turn order
  • Code blocks, tables, links, supported math and citations
  • Per-chat YAML frontmatter or merged table of contents
  • A visible failure instead of silently marking a failed chat as complete

Not guaranteed

  • Deleted, inaccessible or never-listed conversations
  • Binary attachments and generated files
  • Hidden branches, internal reasoning, or provider-only metadata
  • Every archived/project chat when the platform does not expose it
  • A legally complete account backup—keep the provider’s official export too

Frequently asked questions

Can I export my entire ChatGPT or Claude history at once?

Yes. Web2MD lists the conversations available in your signed-in account, selects them by default, and exports the set you choose. The same bulk workflow supports ChatGPT, Claude, Gemini, DeepSeek, and Perplexity.

What is included in each exported Markdown file?

Each chat keeps its title, conversation date, source link, user and assistant turns, code blocks, links, and supported math or citations. Per-chat files include YAML frontmatter so they sort cleanly in Obsidian, Logseq, and other Markdown note apps.

Can I export one file per chat instead of one large file?

Yes. Choose one merged .md file with a table of contents, or one .md file for every selected conversation. The second option is designed for importing a chat archive into a notes vault.

Does bulk chat-history export require Pro?

Yes. Exporting one open conversation remains free. Listing and bulk-exporting a full history requires Pro. A $15 30-Day Pro Pass includes the feature without a subscription or automatic renewal.

Does Web2MD publish my chats or require public share links?

No. The extension reads conversations through the AI platform session already open in your browser and assembles the export for download. It does not require you to publish a ChatGPT, Claude, Gemini, DeepSeek, or Perplexity share link.

Keep the conversations you own

Single-chat export is free. Full-history export is included with Pro, including the $15 one-time 30-Day Pass with no automatic renewal.

Install the Chrome Extension