What's in a saved file

A saved chat file explained line by line: properties, the synced block and your notes, message headings, thinking, tool calls, sources, artifacts and pictures.

View as Markdown

In short

Each saved chat is a plain Markdown file: YAML properties at the top, then a block between two chattomarkdown comments that holds the title and the messages under ## You and ## <service> headings. The extension only ever rewrites that block and its own properties, so anything you write above or below it is kept.

On this page
  1. A complete example
  2. Properties
  3. Dates in an Obsidian vault
  4. The synced block
  5. Your own notes
  6. Title and messages
  7. Thinking
  8. Tool calls
  9. Sources
  10. Artifacts and canvases
  11. Pictures and uploads
  12. Earlier versions
  13. Math and diagrams
  14. Deleted chats
  15. Problems
  16. Questions

Every saved chat is one plain .md file. You can open it in Obsidian, any Markdown editor, or a text editor. This page walks through a real file from top to bottom and explains each part, so you know what you can change and what the extension will keep up to date.

A complete example

This is a ChatGPT chat in a project called Travel, saved with Model thinking and Tool calls turned on. It was produced by the extension’s own code.

Markdown
---
title: "Lisbon food trip"
source: "ChatGPT"
url: "https://chatgpt.com/c/68f1c2a0-5b7e-8003-9a41-2c6d0e7f1a93"
id: "68f1c2a0-5b7e-8003-9a41-2c6d0e7f1a93"
model: "gpt-5"
created: 2026-10-17T10:41:00
updated: 2026-10-17T11:05:12
tags: [ai-chat, chatgpt]
project: "Travel"
---

<!-- chattomarkdown:start · updated automatically on sync; write your own notes above or below this block -->
# Lisbon food trip

## You

![[market 3f9a1c2e.jpg]]

Plan 3 days of eating in Lisbon. Here is the market I liked.

## ChatGPT

> [!abstract]- Thinking
> **Planning the days**
> Group by neighbourhood so walking stays short.

Day 1 starts at Time Out Market.[^1] Budget about $\frac{60}{3} = 20$ euros a meal.

**Tool call → web**

```
search("pastel de nata best bakery")
```

[^1]: [Time Out Market Lisboa](https://www.timeoutmarket.com/lisboa/)

## You

Draw the plan as a diagram.

## ChatGPT

```mermaid
graph LR
  A[Day 1: Baixa] --> B[Day 2: Belém] --> C[Day 3: Alfama]
```
<!-- chattomarkdown:end -->

The sections below go through it part by part.

Properties

The lines between the two --- at the top are YAML frontmatter. Obsidian shows them as properties.

PropertyWhat it holds
titleThe chat’s title on its site. Chats without one get their first words, or “Untitled chat”, until the site names them.
sourceThe service: ChatGPT, Claude, Gemini, Copilot (Microsoft Copilot), Perplexity, Grok, DeepSeek or GitHub Copilot.
urlThe chat’s address on its site.
idThe chat’s id on its site. Always written: it is how the file is matched to its chat.
modelThe model that answered, when the site says.
createdWhen the chat started, in your computer’s local time.
updatedWhen the chat last changed on its site.
tagsai-chat, the service’s id (chatgpt, claude, gemini, copilot, perplexity, grok, deepseek, ghcopilot) and any extra tags you set.
projectThe ChatGPT or Claude project, or Perplexity Space, when the chat is in one.
messagesNumber of messages. Off by default.
wordsNumber of words in the messages. Off by default.
privatetrue for a temporary or incognito chat, which isn’t in the site’s history.
deleted, deleted_atAdded when the chat is deleted on its site. See Deleted chats.

Choose which properties are written, and add extra tags, in Settings → File names. See File names and properties.

What happens to properties on each save:

  • title, source, url, id, model, created, updated, project, messages and words are rewritten from the chat every time it is saved.
  • tags is written only when the file is created. Tags you add or remove later stay as you left them.
  • Properties you add yourself (for example rating: 5 or status: read) are never touched.

Dates in an Obsidian vault

Obsidian treats a property as text unless the vault says what type it is. If the folder you chose is the top folder of a vault (the one that holds the .obsidian folder), the extension sets created and updated to the Date & time type in .obsidian/types.json. Once a chat is deleted on its site, deleted_at is added too:

JSON
{
  "types": {
    "created": "datetime",
    "updated": "datetime"
  }
}

Obsidian then shows a date picker for them, and you can sort and filter your chats by them. The extension only adds what is missing. If you or a plugin already set a type, it stays as it is, and nothing else in the file is changed. A property you turned off in Settings → File names isn’t added.

The synced block

The block starts with this comment:

Markdown
<!-- chattomarkdown:start · updated automatically on sync; write your own notes above or below this block -->

and ends with:

Markdown
<!-- chattomarkdown:end -->

Everything between them is generated from the chat, and rewritten each time the chat is saved again (for example after you continue it on the site). The comments don’t show in Obsidian’s reading view.

If you remove either marker, the extension treats the file as yours and never changes it again. The sync log notes it as Left “…” as it is: its start and end markers were removed. Put the markers back to resume updates.

Your own notes

Write anything above the start comment or below the end comment. It is kept when the chat is updated. Here is the same kind of file after a few edits of your own and a sync:

Markdown
---
title: "Sourdough starter schedule"
source: "Claude"
url: "https://claude.ai/chat/4b1d6a0e-2f3c-4e5d-9a8b-7c6d5e4f3a2b"
id: "4b1d6a0e-2f3c-4e5d-9a8b-7c6d5e4f3a2b"
model: "claude-sonnet-4-5"
created: 2026-10-20T09:00:00
updated: 2026-10-20T09:20:00
tags: [ai-chat, claude, baking]
messages: 2
words: 14
rating: 5
---

My notes: try rye next week.

<!-- chattomarkdown:start · updated automatically on sync; write your own notes above or below this block -->
# Sourdough starter schedule

## You

Make me a feeding schedule as a table.

## Claude

Here is a week of feedings:
<!-- chattomarkdown:end -->

Follow-up: it doubled in 6 hours.

rating: 5, the line above the block and the line below it were written by hand. The extension keeps all three.

Warning

Edits inside the block last only until the chat is saved again. Then the block is rewritten from the chat. The version history keeps your edit as its own version, so you can copy it back out. See Version history.

Title and messages

The block starts with the title as a # heading. Each message follows under a ## heading: ## You for your messages, and the service’s name for its answers (## ChatGPT, ## Claude, ## Gemini, ## Copilot, ## Perplexity, ## Grok, ## DeepSeek, ## GitHub Copilot).

Answers keep their own formatting: headings, lists, tables, code blocks with their language, links and quotes. A few things are adjusted so the note reads well in Obsidian:

  • Headings sit under their speaker. Headings inside a message are moved down a level or two, so that they start at ###. Only ## You and ## Claude (or the service’s name) are level-2 headings, so Obsidian’s outline shows the chat turn by turn, and you can fold a whole turn. A heading written as text underlined with === or --- is rewritten with # signs.
  • A “#word” stays text. Obsidian would turn #fyp in a drafted post or #0B1017 in a stylesheet into a tag. So the extension saves them with a backslash, \#fyp, which Obsidian shows as plain text. Code, web addresses, [[links]] and HTML are left as they are, and so is C#.
  • Prices stay prices. Two prices in one of your messages, like “$20 or $30”, would be shown as a formula, so their dollar signs are saved as \$. A real formula you wrote is left as it is.

Obsidian and other Markdown apps show \# and \$ as plain # and $. The reader, search, exports, Notion and Google Docs do too, and they show notes saved by older versions the same way as new ones.

Thinking

With Model thinking on (off by default), the reasoning a model shows before its answer is saved above the answer. How thinking looks decides the style.

Callout (default) is an Obsidian callout, folded until you click it:

Markdown
> [!abstract]- Thinking
> **Planning the days**
> Group by neighbourhood so walking stays short.

Plain is a bold label and a quote, which any Markdown app shows:

Markdown
**Thinking**

> **Planning the days**
> Group by neighbourhood so walking stays short.

Tool calls

With Tool calls on (off by default), the web searches and code runs behind an answer are saved as a bold label and a code block:

Markdown
**Tool call → web**

```
search("pastel de nata best bakery")
```

Sources

Web sources an answer cites become footnotes. The marker sits where the site showed the citation, and the list of sources follows the message:

Markdown
Day 1 starts at Time Out Market.[^1] ...

[^1]: [Time Out Market Lisboa](https://www.timeoutmarket.com/lisboa/)

Numbers run through the whole chat, so a source cited again later keeps its number. Sources an answer listed without citing them in the text go into a folded callout under it:

Markdown
> [!info]- More sources (1)
> - [Visit Lisboa \[official\]](https://visitlisboa.example/)

Artifacts and canvases

Code, documents and diagrams Claude makes are saved with Claude artifacts on (the default). With Artifacts as separate files on (also the default), each one is its own file in the attachments folder, shown inside the note:

Markdown
**Artifact: Feeding schedule**

![[Feeding schedule 794b3f96.md]]

With Artifacts as separate files off, the content is written into the note itself:

Markdown
**Artifact: Feeding schedule**

```markdown
| Day | Flour | Water |
|---|---|---|
| Mon | 50 g | 50 g |
```

A dashboard Claude made (charts built from data) gets a card where Claude made it, its page from attachments shown under it, and its data files linked below:

Markdown
**Dashboard: Bakery sales** · [Open in Claude](https://claude.ai/artifact/…)

![[Bakery sales 58cb2743.html]]

[[monthly_sales 244d3b68.csv]]

ChatGPT canvases are saved where they were made, as a > [!note] Canvas: <name> callout for documents and a code block for code. Charts and interactive answers are saved as a page in attachments, which the reader runs. See The reader.

Pictures and uploads

With Images and files on (the default), pictures and uploaded files are saved in an attachments folder next to the note and embedded where they appeared:

Markdown
![[market 3f9a1c2e.jpg]]

Pictures, audio, video and PDFs use ![[...]] so Obsidian shows them. Other files get a plain [[...]] link.

When a picture isn’t saved (the option is off, or the download failed), its place shows *[image]*. Uploaded files that aren’t saved are listed by name, with Names of uploaded files on:

Markdown
*Attachments: brief.pdf, logo.png*

Earlier versions

With Earlier versions on (off by default), the other versions of a message you edited, or of an answer you asked for again, are kept in a folded callout under it:

Markdown
## ChatGPT

Blue.

> [!note]- Other versions (1)
> **Version 1 of 2 · earlier**
>
> Red.

Math and diagrams

Formulas are saved as LaTeX, with dollar signs: $...$ inline and $$...$$ on their own lines. Obsidian, GitHub and the reader draw them.

ChatGPT, Copilot, DeepSeek, Grok and Perplexity write formulas between \( and \) or \[ and \]. In their answers, these are saved with dollar signs instead. Text that only looks like a formula stays as it is: code such as find . \( -name … \), a\[0\], a task like - \[x\] done, words in escaped brackets, and links.

Mermaid diagrams are saved as ```mermaid code blocks. Obsidian draws them natively, and so does the reader.

Deleted chats

With Keep chats you delete on (the default), a chat you delete on its site stays in your folder, and two properties are added:

YAML
deleted: true
deleted_at: 2026-11-02T14:03:00

The rest of the file stays as it was. If the chat comes back on the site (you restored it), the properties are removed at the next save. See Choose what to save.

Problems

Obsidian shows [!abstract]- as text. Your app has no callouts. Set How thinking looks to Plain, then use Apply to saved files in Settings → File names to switch existing files.

A picture shows as *[image]*. It wasn’t saved. Check that Images and files is on and that the popup doesn’t ask you to allow the service’s picture server. Then use Re-sync in the reader on that chat.

My notes inside the block disappeared. The chat was saved again and the block rewritten. Find your text in the chat’s Changes in the reader, and move it above or below the block.

A file stopped updating. One of its markers was removed or changed. Compare it with the example above and put both back.

Questions

Can I write my own notes in a saved chat file?

Yes. Write above the start comment or below the end comment. The extension never changes text outside its block, and properties you add are kept.

What happens if I edit the messages inside the block?

Your edit stays until the chat is saved again, for example when you continue it on the site. Then the block is rewritten from the chat. The version history keeps your edit as its own version.

Will the files work outside Obsidian?

Yes. They are plain Markdown. Obsidian-only parts are callouts and ![[...]] embeds; set How thinking looks to Plain if your app has no callouts.

↑↓ to move ↵ to open Esc to close