Markdown
Export a ChatGPT conversation into Obsidian
Markdown shaped for a vault: front matter your queries can read, a filename that sorts, and links that don't fight the editor.
No account, nothing stored. Files are built in your browser — revoke sensitive share links afterwards.
The converter is preset to Markdown. You can change the format at any time.
Why this format
Front matter Dataview can query
Title, source, export date, and tags are written as YAML at the top of the note.
Tags applied on export
Obsidian mode adds transcript tags so conversations collect in one place instead of scattering across folders.
Filenames that behave
The filename is slugified — no colons, slashes, or emoji to upset sync clients on other platforms.
Heading depth that nests
Choose where the transcript starts so it slots under an existing note structure rather than fighting it.
Example output
---
title: "Designing a typed conversion service"
source: https://chatgpt.com/share/5f2a9c41…
exported: 2026-03-14T14:07:00.000Z
tags: [chatgpt, transcript]
---
## Assistant · 14:02
Define the contract first, then write a mock…Step by step
- 01Paste the public share link and load the conversation.
- 02Turn on YAML front matter and Obsidian-compatible mode.
- 03Set the filename — it becomes the note title in your vault.
- 04Download the .md file and drop it into your vault folder.
Tradeoffs and limits
- Wiki-style [[links]] are not generated automatically; add them after import.
- Images are referenced by name and are not copied into your attachments folder.
- Existing notes with the same filename are not merged — Obsidian will create a duplicate.
Files are generated in your browser. Nothing is stored.
Questions about this export
Related tools
- ChatGPT to MarkdownThe most faithful text format: fenced code, real tables, and links that survive a copy-paste into any editor.
- ChatGPT to JSONA stable, versioned structure meant to be read by code rather than by people.
- Export ChatGPT code blocksKeep indentation, language identifiers, and block boundaries — the three things that break when you copy code by hand.
