Portable export guide
Export ChatGPT to Markdown.
Export the current chat as plain text with its useful structure intact. Keep it in your downloads folder, write it to a selected notes folder, or add metadata for Obsidian and publishing workflows.
Export one conversation
- Open the ChatGPT conversation you want to keep.
- Wait for the final response to finish loading.
- Open AI Chat Backup.
- Select Export Chat.
- Open the downloaded file or the local export folder configured in settings.
Why Markdown works well for AI chats
Markdown is plain text, easy to search, version, move, and edit. It works with Obsidian, many static-site generators, GitHub, code editors, and document conversion tools. You retain control of the exported file even if the original platform changes.
Formatting and limitations
AI Chat Backup preserves headings, paragraphs, lists, links, fenced code, and tables when ChatGPT exposes them. Deep Research reports may request one-time access to the ChatGPT report frame. Canvases, interactive embeds, session-bound media, and complex interface elements may need separate handling.
Optional YAML front matter
Enable Add YAML Front Matter in the Export settings to include generated title, date, and source fields. You can disable those fields or add custom key and default-value pairs for Obsidian, static sites, and automated content pipelines.
Choose where files are written
By default, Export Chat uses the browser downloads folder. In extension settings, choose a Markdown Export Folder to write future files directly to a notes directory or Obsidian vault. If folder permission expires, the extension falls back to a normal browser download.
Download generated images separately
For ChatGPT conversations with generated images, use Download generated images to save the files locally. Images are downloaded separately from the Markdown conversation and are not included in Notion sync because their source URLs block external access.
Keep local exports private
Markdown downloads are created locally in your browser. Treat the files like any other document: choose an appropriate folder, avoid committing private conversations to public repositories, and remove sensitive data before sharing.