Export a Google AI Studio chat to Obsidian

If you use Obsidian, plain Markdown from a chat export is only half useful. A note in a vault wants properties you can query, attachments that link by name, and long blocks of model thinking folded out of the way. AI Studio Exporter has an Obsidian format that does all three, so a conversation lands in your vault looking like a note you wrote.

The Obsidian format is part of the one-time Pro licence. The plain Markdown export is free and works in a vault too, without the extras below.

#How to do it

1. Install AI Studio Exporter and activate Pro in its settings.
2. Open the conversation on aistudio.google.com.
3. Click the extension's icon, choose Obsidian from the format list, and click Export this conversation.
4. Move the result into your vault. With attachments it is a ZIP: extract it, and put the note and the files anywhere inside the vault.

#What makes it an Obsidian note

#Frontmatter you can query

Every note starts with YAML properties, so Dataview and Bases can list and filter your conversations:

---
title: "How does the RPC auth work?"
exported: 2026-07-31T06:40:38.000Z
modified: 2025-06-15T15:06:40.000Z
source: https://aistudio.google.com/prompts/1AbCdEfGhIjKlMnOp
model: "gemini-3-pro"
temperature: 1
top_p: 0.95
top_k: 64
total_tokens: 882
messages: 5
tags: [ai-studio, conversation]
---

The keys use snake_case, which is the convention Dataview users expect. You can show every conversation made with one model, sort by length, or list everything modified this month.

#Attachments as wikilinks

Images and files are linked the Obsidian way, ![[screenshot.png]], which resolves by filename rather than by path. That means they keep working once the files are anywhere in your vault, and you do not have to rewrite paths when you move things around.

#Collapsed callouts for the thinking

The model's reasoning, and the system instruction, are written as collapsible callouts that start closed:

> [!note]- Reasoning
> ...

A note opens showing the conversation, not pages of thinking, and you expand the callout when you want it.

#A workable routine

• Export straight into a folder inside the vault, such as AI Studio/. Obsidian picks the files up on its next scan.
• Use a tag such as the default ai-studio to find them, or filter by the source property.
• To keep a whole library in sync, turn on scheduled backups (Pro), choose Obsidian as the format, and the exports arrive on their own. How backups work.

#Settings that change the note

The model settings, system instruction, timestamps, token counts and source link each have a switch. Turn one off and its property or section is removed from the note. The settings reference lists them all.

#Questions

#Does it need an Obsidian plugin?

No. The export is a normal Markdown file with standard features: YAML properties, wikilinks and callouts. Nothing in the vault is changed except the files you drop into it.

#Are the properties compatible with Bases?

They are plain YAML properties, so any Obsidian feature that reads properties can use them. Dataview is the one most people use for this.

#Can I export every conversation to the vault at once?

Yes, with the whole-library export (Pro), which writes one folder per conversation with an index.

#What if a property I need is missing?

Open an issue on the GitHub repository and say which one. The property list is meant to follow what people actually query.