How to Sync Claude Conversations to Obsidian (2026)

Two routes, by volume. For individual conversations, the free XWX Exporter extension exports the open Claude chat as a Markdown file with YAML frontmatter — move it into your vault folder and Obsidian indexes it instantly. For a whole history, the XWX Backup desktop app mirrors your Claude (and ChatGPT, Gemini, and more) archive into an XWX Backup subfolder inside your vault as standard Markdown, auto-syncing new and changed conversations. Both preserve code blocks, tables, and math; both write real frontmatter, so Dataview can query the notes.

Obsidian is built on plain .md files, and that’s the whole point: a conversation saved as Markdown is

• Editable — annotate, trim, and link it like any other note;
• Searchable — Obsidian’s search and backlinks index it immediately;
• Portable — the file works in Logseq, VS Code, or any future tool, and syncs via Obsidian Sync, Git, iCloud, or Dropbox;
• Queryable — with YAML frontmatter, the Dataview plugin can list, table, and filter your AI conversations like structured data.

PDF or Word copies have their place for sharing and records, but the vault wants Markdown.

A pasted blob of chat text is a dead note. A useful one carries structured metadata in its YAML frontmatter:

---
id: "a1b2c3d4"
platform: "claude"
title: "Debugging the WebSocket reconnect loop"
model: "claude-sonnet-4-5"
created_at: 2026-08-12T09:14:00Z
updated_at: 2026-08-12T11:02:00Z
messages: 24
tags:
  - "xwx-backup/claude"
---

# Debugging the WebSocket reconnect loop

…full conversation as Markdown…

Every XWX Markdown export includes this frontmatter automatically: platform, model, timestamps, message count, and source URL. platform: and model: enable filtering, created_at/updated_at drive sorting and timelines, and tags: plugs into your existing taxonomy.

Step 1 — Install the extension. Search for XWX AI Chat Exporter in the Chrome Web Store — free, no account.

Step 2 — Open the Claude conversation on claude.ai. The extension detects Claude automatically, including Projects.

Step 3 — Click the floating button and choose Markdown. The file downloads with frontmatter and the full conversation — code blocks, tables, LaTeX, images, and thinking blocks included.

Step 4 — Move the file into your vault. Drop it in a folder like Sources/Claude/ and Obsidian indexes it on arrival. That’s the loop for day-to-day use: it takes under a minute per conversation.

Use this for the conversations you actively want in your graph — and expect to do it by hand each time.

Manual exports stop being fun around conversation thirty. The XWX Backup desktop app (Windows 10/11) turns the vault into a destination instead:

1. Install XWX Backup and connect it to the extension once — pairing stays on your machine, nothing leaves it.
2. Batch-import your history — pick Claude (each organization listed separately) and a count; the app pulls conversations into a local vault at ~/.xwx-backup/ as one Markdown file each. Already-saved chats are skipped on re-runs.
3. Point Obsidian Sync at your vault — in Settings → Vault, select your Obsidian vault root. The app validates it (it must contain an .obsidian folder) and mirrors conversations into an XWX Backup subfolder.
4. Leave it on. Auto-sync mirrors new and changed conversations within seconds. Notes you’ve edited inside Obsidian are left untouched unless the conversation itself changed; deleting in XWX Backup never deletes from Obsidian — the folder only grows.

The mirror reflects whatever the local vault holds, and the vault stays current on its own: enable Scheduled export and new Claude conversations flow in on your interval — 30 minutes to daily — incrementally, with hash-based dedupe so nothing duplicates. The combined effect: you keep working in Claude, and the Obsidian subfolder keeps up in the background.

One honest limitation: fetching still needs your logged-in browser session, so a run only happens while the desktop app is running. If the machine was off, the schedule re-arms and the next run catches up.

With frontmatter in place, the Dataview plugin turns the folder into a structured archive. Two queries to start with:

TABLE model, updated_at, messages FROM "XWX Backup" WHERE platform = "claude" SORT updated_at DESC

A live table of every Claude conversation, newest first. Add a tag filter to narrow to a project:

LIST FROM "XWX Backup" WHERE contains(tags, "architecture") SORT created_at DESC

Because tags and stars are written back into the frontmatter (edit them in XWX Backup’s vault view or in Obsidian — both directions persist), the same notes answer to Obsidian’s graph view, backlinks, and search without any extra setup.

• One-way, platform → vault. Sync writes conversation changes into your notes; it never overwrites your own annotations. If you edit a note and the conversation changes on claude.ai, the conversation’s new content updates the file while your edits in Obsidian are preserved on the XWX Backup side — treat the note as the living copy, the platform as the source.
• Browser session required for fetching. The desktop app reads through your real logged-in sessions; it can’t pull conversations when you’re logged out.
• Claude’s rendering quirks apply. Artifacts and canvas-style outputs export as well as the platform exposes them; very old chats shared with you (not authored by you) may not be enumerable.
• Windows only for now. The desktop app ships for Windows 10/11 64-bit; macOS is planned. The extension route works on any Chromium browser.

• Writers and researchers — Claude drafting sessions become queryable source material next to their own notes.
• Developers — debugging threads and design discussions land in the vault, grep-able and linkable; the next step is making them machine-readable too (see Claude conversations as an MCP knowledge base).
• PKM builders — the AI half of the second brain stops being a separate silo and joins the graph.