How to Bring an Exported Claude Chat into Obsidian

Direct answer: Download one Claude conversation as Markdown, keep that original file, and place it in your Obsidian vault folder. Open it in Obsidian, check the passage you care about, then make a separate working note that links back to the original. You have a readable local copy without setting up a plugin or a live connection.

If your best idea is still buried in a chat, an export gives you something you can actually inspect and use in your notes. This guide follows one small, public Claude example from an existing Multiplist Markdown export into an isolated Obsidian vault. It shows a local file workflow. It does not claim automatic chat capture, live sync or AI access to the vault.

# See the useful result first

In our example, the original export is Original Claude export.md. A second note, My chat-to-note routine.md, contains the five checklist items and next step taken exactly from the answer's Markdown block. It links back to the unchanged export. A small Review index.md links to both notes. We opened all three files in Obsidian 1.15.0 and followed the source and return links in the app.

The result is deliberately modest: you can read a useful checklist and inspect where its words came from. Open the offline example guide or download the three Markdown files. The included conversation is a public tutorial sample, not a founder or customer archive.

# 1. Export the conversation you want to keep

For one active Claude chat in desktop Chrome, use the Multiplist Chrome extension and choose its Markdown Quick Export. Our one-conversation export guide shows the exact extension route and how to reopen the download. That is different from downloading your whole account history.

Before moving the file, open it in a text editor. Check its title, speakers, the beginning and end of the conversation, and the answer, code or list you want to preserve. A chat can include private prompts or tool output, so inspect it before sharing or placing it in a shared vault. A link to the original Claude session can help you return to it if your account has access, but the link does not replace the local Markdown copy.

You can use another Markdown export if you already have one. The exact headings and attachment references will depend on the exporter. This article's tested example is one Claude conversation from the released Multiplist extension; it does not establish identical output for every provider or export format.

# 2. Put the Markdown file in your vault

An Obsidian vault is a local folder of Markdown files. Use Finder on macOS or your system's file browser to place the .md export in the vault folder. You can also drag a Markdown file into Obsidian's File Explorer. The basic file route does not need the optional Importer plugin. Obsidian: create or open a vault · Import Markdown files

For a first try, use a separate demo vault or a small folder in your existing vault. Keep the original export's name and content so you can compare later working notes to it. In our isolated test, we put the original export, checklist and index in the same vault folder and reopened them in Obsidian.

If your export refers to an image or other attachment, check whether that file exists and whether its path still works. Moving a Markdown file does not create missing attachments. Obsidian's Importer offers extra options for larger or more complex imports; this single-file route does not demonstrate them. Obsidian Markdown import guidance

# 3. Open it and check what survived

Open the export in Obsidian. Check the actual heading, message order, useful answer and any fenced code block. Our sample export contains a Markdown fence around the assistant's checklist. In reading view, Obsidian displays that fence as code, so the original answer remains visually distinct from the new working note.

The sample's working note keeps the answer text and adds two new links afterward:

Source: [Original Claude export](Original%20Claude%20export.md)

[Back to review index](Review%20index.md)

These links are additions to the working note; they are not words the assistant wrote in the original chat. Obsidian supports Markdown internal links, and spaces in Markdown link destinations should be URL encoded as %20. Click your links in the app and verify the target file, rather than assuming a filename alone proves navigation works. Obsidian internal links

# 4. Make one reusable note while preserving the source

You may only need one paragraph, list or code block from a long conversation. Copy the part you need into a separate note, give it a useful title, and keep a local source link. Compare the copied text to the original before treating it as an exact excerpt. Add your own summary or next action separately so it cannot be mistaken for the source.

Our tested checklist has five unchecked tasks and one “Next step” sentence. The original export is byte-for-byte unchanged in the sample kit; the checklist's answer block matches it exactly. We followed the checklist's source link to the export and used the index to return to the checklist in Obsidian. The offline guide lets you inspect the files without signing in.

You do not need Multiplist's hosted vault to read these local files. If you later want selected material available to connected assistants, saving a source in your Multiplist vault is a separate step with separate data handling and authorization. See using selected Obsidian notes in Claude for the reverse direction.

# What this route does and does not do

If you only want to revisit the conversation inside Claude, its native history may be enough. For a quick personal note, manual copy and paste may also be enough. Export when you want a portable file you can keep, inspect and use in your own notes. When the chat changes, export again or update your working note deliberately.

Multiplist sample export and isolated Obsidian 1.15.0 vault checked November 5, 2026. Obsidian's vault, Markdown import and internal-link documentation checked November 6, 2026. The example is a local-copy workflow; no attachment migration, live synchronization or AI retrieval was tested.

Related: Export one AI conversation with the Multiplist Chrome extension · Make ChatGPT and Claude data exports readable.