How to save Claude chats in an Obsidian vault

Start with a vault location you can manage

In Obsidian, you can create a vault or open an existing folder as one. A vault contains notes, attachments, and Obsidian’s configuration folder, so decide where the conversation archive belongs before connecting a saver. If this is an existing vault, make a separate folder such as AI Conversations/Claude/. Keep provider transcripts away from your curated project notes so you can change the filing approach without breaking those notes.

Obsidian’s help describes a vault as a file-system folder and explains how to open an existing folder as a vault (Manage vaults). This also means a vault’s local files deserve ordinary file care: choose a location you can back up, and avoid placing sensitive material in a shared folder unless that is intended.

Capture new Claude activity

With Chatlog, select the vault’s chat folder, connect Claude, allow access to claude.ai, and refresh the open tab. With automatic capture enabled, Chatlog records new and continued Claude activity while Chrome is open and you are signed in. For one open conversation, use Save conversation in the extension popup. A closed tab or permission that was never granted is not a background account scan: Chatlog does not fetch all older Claude conversations from your account.

Each conversation is stored as an individual Markdown file. This keeps messages searchable and avoids one huge document that is awkward to link. A longer thread updates its file as new activity arrives. If you have edited the note and an incoming update conflicts, your version is kept and the incoming text is saved in a separate conflict copy. Check both when you intentionally edit a transcript, and do not assume a queued save has reached an optional Notion destination.

File project threads and artifacts with care

Here is one suggested vault organization. These are example folder names for you to create; they do not promise that Chatlog will place files at these exact paths:

AI Conversations/
  Claude/
    Projects/
    General/
    Artifacts/

Keep project conversations under a project folder only when the project name is useful and stable. Otherwise, use a general conversation folder and link the transcript from a project index. This prevents a renamed project or a changing work area from becoming a maze of duplicated files.

Claude can show outputs that are more than plain text, such as files or interactive artifacts. A transcript and a separately saved source file are different things. Chatlog can save supported files and artifact source when accessible and enabled; it does not preserve a complete interactive preview in every case. Binary attachments are not uploaded to Notion. Open any source file you rely on, confirm it contains the intended content, and keep its relationship to the conversation clear with a link or short note.

Turn transcripts into a readable workflow

Use the transcript as a source, then write a short project note with the conclusion, assumptions, and next action. As an illustrative example, if you create the folders above, a link could look like [[AI Conversations/Claude/Projects/Research brief]]. Obsidian supports links to notes by name or folder path and can update internal links when files are renamed (Internal links).

For a thread that generated code, store the reviewed source as its own file and add a link in the project note. Do not treat an assistant’s draft as approved code simply because it is preserved. For a research conversation, note which claims still need checking and keep the relevant source links with the summary rather than expecting a transcript alone to preserve context.

Import older conversations and check the result

To bring in older Claude history, open Claude’s web app and go to Settings → Privacy → Export data. Anthropic says exports are available for individual Free, Pro, and Max users; Team or Enterprise access depends on an organization owner enabling member exports. The export link arrives by email, requires sign-in to download, and expires after 24 hours. Request the export, download it promptly, then import the appropriate ZIP or JSON file in Chatlog settings. (Claude export instructions.)

After capture or import, open a few notes in Obsidian and check titles, message order, links, and any file or artifact you intend to use. Search for a distinctive sentence from a recent thread. If a chat is missing, verify Chrome was open, site permission and automatic capture were enabled, and the Claude tab was refreshed. For export issues, check the email account used by Claude and request a fresh link if the earlier one expired. Do not read a partial or marked-unavailable item as a complete record.

Frequently asked questions

Will saving one Claude chat also import my old chats?

No. A single-chat save captures the conversation you open. Older history requires Claude’s export file and a separate import step.

Can an Obsidian vault preserve every Claude artifact?

No blanket guarantee applies. Accessible, supported source may be saved when enabled, but a full interactive preview or every attachment may not be available. Verify the specific files you need.

Should transcripts and project notes be mixed together?

Keep raw conversations in a dedicated folder and link selected threads from concise project notes. This keeps the source searchable without making every transcript part of your working outline.

Can I also send Claude chats to Notion?

Yes, if you choose and configure Notion as a destination. It is separate from the local vault; check delivery status in each place you use.

For related workflows, see Claude to Obsidian setup and how to export Claude chat history.