Keep Claude chats as notes in Obsidian

To move a chat from Claude to Obsidian, export Markdown and put the .md file inside your vault. Obsidian opens it as a note without conversion. Add a date and project reference, keep the source link, and save essential images locally for offline reading.

Export the chat into your vault

DocMyChat saves the conversation you have open on claude.ai as Markdown. You’ll need Google Chrome on a desktop computer, and Markdown downloads are always free.

1. Open the chat in Chrome with DocMyChat installed.
2. Click Export next to Share.
3. Choose Markdown.
4. Find the downloaded .md file in your file manager.
5. Move it into a folder inside your Obsidian vault.
6. Open the file in Obsidian.
7. Compare the beginning, end, and any complex sections with the chat.

Move the file with Finder or File Explorer, or drag it into Obsidian’s File explorer, as Obsidian’s import guide describes. There’s no importer to run.

Use a folder such as Sources/Claude for saved chats. It keeps them apart from your own notes and loose downloads. See the Markdown export guide for the format’s limits.

Keep just one reply without an extension

For a short answer, use Claude’s Copy button under the reply and paste the text into a new note. Check headings, tables, and code blocks. Select text by hand if you only need a few lines.

Put the relevant prompt above the answer and label both parts. A parser-bug explanation needs the input that caused the failure. Add the chat URL too, so you can return while the conversation is available.

DocMyChat’s export icon under a reply saves just that answer in your chosen format. Use it for a finished checklist that doesn’t need the whole discussion.

Check the note’s structure and formatting

Open the note in reading view. If something looks wrong, check its Markdown source. Dollar signs and backticks are formatting instructions, so seeing them in the source is normal.

A full-chat export gives each message a ## You or ## Claude heading. Obsidian’s core Outline plugin lists those headings, so you can jump between turns. A single-reply file has the title, a “Claude reply” meta line, and the answer, without a turn heading.

For a long debugging thread, add descriptive headings such as ## Initial failure, ## Proposed fix, and ## Final decision. Keep speaker names so you can find the decision and tell your words from Claude’s.

Check the content inside each section:

• Formulas: the export keeps LaTeX between dollar signs. Obsidian’s math support uses MathJax for inline and block expressions. Check unfamiliar commands if a formula won’t render.
• Code: exported code fences include language identifiers for highlighting. If a block looks wrong, check its opening and closing fences and indentation.
• Tables: Obsidian supports pipe tables and GitHub Flavored Markdown. Look for escaped vertical bars inside cells and the separator beneath the header.
• Lists: check nested items and completed tasks. An extra indent can put a line under the wrong item.

See Obsidian’s basic syntax reference for code fences, headings, lists, and internal links. Keep repairs small so you can compare the note with the chat.

Save images and artifact files separately

Markdown image references point to claude.ai and need your signed-in session. They won’t give you an offline image, even if the picture opens in your browser now.

Save essential charts and screenshots in your vault’s attachment folder, then replace or supplement remote references with local links. Choose a descriptive filename and embed the image with syntax such as ![[parser-flow.png]].

Keep working files too. DocMyChat’s artifacts ZIP holds the most recent version of each artifact or file. The ZIP has no folders, so arrange the extracted files as your project needs. A code appendix is useful for reading. Use parser.py itself to run or edit the program.

The ZIP contains no earlier drafts, so save those separately. For newer Docs, Slides, Design, Dashboards, and Motion, open the artifact itself and use its own export or sharing controls.

A Claude Doc or published deck appears in the exported note as a titled link where it was made, without the artifact’s content. Slide HTML and JSON files used only to build a published deck are left out of the appendix and ZIP.

Add a naming and property convention

Try 2026-11-02-parser-empty-fields.md. The date sorts related saves, and the remaining words name the problem. “Claude chat final” becomes ambiguous after the next revision.

Add these properties by hand at the very beginning of the note:

---
source: Claude
date: 2026-11-02
project: "[[CSV importer]]"
---

Keep the exported conversation link below the properties. These fields are your own additions. The exporter doesn’t create this filing system for you.

Obsidian’s properties guide explains YAML, dates, and quoted internal links. Set date to Date, and source and project to Text. Types apply to a property name throughout the vault, so use names consistently.

Link the conversation to the work it informed

Suppose the chat found why a CSV importer drops empty fields. Save it in Sources/Claude and link to it from [[CSV importer]]. Above the link, write your decision: “Preserve empty fields. Add a trailing-delimiter test before release.”

You can read the decision first and open the conversation when you need the reasoning. If a later chat changes your approach, add a dated note explaining what changed.

For a complete account backup, use Claude’s official data export. DocMyChat exports individual open chats and doesn’t process the official data archive.

Connect Claude to local notes

For Claude to read vault files, see Anthropic’s desktop and web connector guide. It covers desktop extensions for local files and folders. Before choosing a connection or community plugin, check that it supports your vault and review its folder permissions.

To read the finished note on another device, follow Obsidian’s sync guidance. Connecting Claude to local files and syncing your notes between devices are separate tasks.

Questions