How to Export AI Chats to Obsidian With the Images and Files Still Attached (2026)

Two tools, two scales:

• One conversation. In the free XWX AI Chat Exporter extension, export a chat as Markdown and choose Download when it asks what to do with images and files. You get a single ZIP — a clean .md plus an images/ folder and a downloads/ folder. Unpack it into your Obsidian vault and the pictures show up where they were in the chat, and the generated files are links you can click to open.
• Your whole history. The optional XWX Backup desktop app (Windows) batch-exports every conversation into a local vault and mirrors it into an XWX Backup subfolder inside your Obsidian vault, carrying each note’s images and files along with it. Re-runs only add what changed.

Copy-paste and the official data exports both lose the images and files — that’s the gap this guide closes.

Saving the words of an AI chat is easy. Everything that isn’t text is where exports fall apart — the generated images, and the downloadable files the model produced (spreadsheets, decks, PDFs, code).

• ChatGPT → Export data gives you conversations.json, and images are stored as links that expire — weeks later they’re broken. Code Interpreter files aren’t in the archive at all.
• Claude → Export data is JSON too, and the download link expires in 24 hours. Files Claude created live in a sandbox that gets torn down.
• Gemini → Takeout is a flat activity log, not notes.
• Copy-paste loses images and files entirely, and usually mangles code and tables.

The platforms keep shifting the format underneath you — ChatGPT changed how it stores attachments as recently as 2026, breaking import tools overnight. If your backup depends on the official format, it isn’t really a backup. The net effect: a chat that looks complete in the browser becomes, once exported the official way, a text transcript with dead image links and no attachments.

Obsidian is just a folder of Markdown files, so a note with images and files only works if those files sit next to the note and are linked by relative path — the same format GitHub, Typora, and VS Code understand:

![Quarterly revenue chart](images/image-001.jpg)

→ [quarterly_budget.xlsx](downloads/quarterly_budget.xlsx)

Put the note and its folders in a vault and: the image renders inline, and the file link is clickable — Obsidian opens it in your default app. The two usual failure modes are leaving images as expiring web links (broken icons) or base64-embedding them (renders, but a huge file you can’t click). XWX lets you pick per export.

Step 1 — Install. Search XWX AI Chat Exporter in the Chrome Web Store and click Add to Chrome. It works on 13 AI platforms, needs no account, and Markdown is generated entirely in your browser.

Step 2 — Open the chat and choose Markdown. Click the floating save button on a ChatGPT, Claude, or Gemini conversation and select Markdown.

Step 3 — Pick “Download” when asked. If the chat contains images or generated files, XWX shows a small dialog with the real counts and asks how to handle each. Choose Download for both: images become files in an images/ folder, generated files become files in a downloads/ folder, and the note links to both. (You can tick Remember so it stops asking.)

The export downloads a single ZIP that unpacks to exactly the layout Obsidian wants — the note, an images/ folder, and a downloads/ folder. Extract it into any folder inside your vault and open the note: images render in place, files open on click. No plugin, no configuration, no converter.

If you always want the same behavior, set it once in Settings instead of answering the dialog. On the Text & Markdown tab, set Images to Download; on the General tab, set File cards to Download. Turn Ask on export off and XWX stops prompting. The other modes stay available: Embed keeps every image inside one self-contained .md, and Placeholder writes text only.

For more than one chat at a time, the optional XWX Backup desktop app (Windows 10/11) automates the same result across your account:

1. Connect the extension once — the app drives your logged-in browser over localhost; nothing is uploaded.
2. Batch-export the conversations you want, across the 11 platforms that have a conversation list. Each becomes one Markdown file in a local vault.
3. Turn on Obsidian sync in Settings → Vault → Export to Obsidian, pointing at your vault. Notes mirror into an XWX Backup subfolder.

The part that matters for images and files: when asset sync is on, each note’s images and generated files are copied into a single `assets/` folder beside the Markdown, and the sync carries that folder too — so the links keep working inside Obsidian. (One difference from the browser: a single export uses separate images/ and downloads/ folders in its ZIP, while the desktop vault keeps everything together in one flat assets/ folder.) Re-runs skip unchanged chats, so nothing duplicates, and a schedule (every 30 minutes to daily) keeps the archive current on its own.

This is the part worth seeing. A saved conversation opens as a normal note: the AI’s chart renders inline where it appeared in the thread, and the files the assistant built sit below as links — click one and Obsidian hands it to your default app. Because the export writes standard Markdown with YAML frontmatter, everything else works too: backlinks, the graph, and Dataview queries over platform, model, and date.

• Downloaded images are optimized (smaller, JPEG) so a long chat stays a sane size. That means PNG transparency is flattened and animated GIFs keep one frame — use Embed if you need exact pixels inside the note.
• Expired files can’t be recovered. Generated files come from a temporary sandbox; once it’s recycled the bytes are gone and no tool can get them back. If a chat produced a file you care about, export it soon.
• Desktop automation is Pro. The extension and single-chat Markdown are free. Batch export, scheduled backups, and automatic Obsidian sync are the paid layer, and the desktop app is Windows-only today (macOS and Linux planned).
• A few images may stay as links if a host blocks the download — the note still renders; that one asset may need a manual save.

• PKM and second-brain users who want the analysis and the chart, not a text stub of it.
• Analysts, finance, and ops — the AI built a .xlsx with the real numbers; you need the file, not a description of it.
• Developers keeping generated scripts, notebooks, and diagrams with the reasoning behind them.
• Researchers and students preserving figures and data tables alongside the discussion that produced them.
• Anyone who has opened an old chat only to find the image or download is already a dead link.