---
title: "File names and properties"
description: "Set how saved chat files are named with tokens like {date} and {title}, pick a date format, choose the properties and tags, and rename files you already have."
url: https://chattomarkdown.com/docs/1.0.4/file-names/
version: "1.0.4"
updated: 2026-11-04
---

# File names and properties

> In Settings → File names, build the file name from parts such as {date}, {time}, {title}, {service}, {project} and {id}, pick how the date is written, choose which properties go at the top of each file and add your own tags. New chats use it at once; Apply to saved files renames and updates the files you already have.

Each saved chat's file name, and the details at its top, follow the settings in **Settings → File names**. This page explains every option, shows what each part of a name turns into, and how to bring your existing files in line after a change.

![The File names section of Settings, with the pattern, its parts and a preview](https://chattomarkdown.com/docs/shots/1.0.4/settings-format-light.webp "Settings → File names")

## The file name

The **File name** field holds a pattern, `{date} {title}` by default. Parts in braces are replaced for each chat; everything else is kept as you typed it.

1. **Open Settings → File names.**
2. **Edit the pattern.** Type in the field, or click a part under it (**Date**, **Time**, **Title**, **Service**, **Project**, **ID**) to add it where the cursor is.
3. **Check the preview** under the parts. It shows how a name will look, for a sample chat called "Trip planning" in a project called "Travel".
4. **Press Enter or click elsewhere.** The pattern is saved. New chats use it from now on.

### The parts

| Part | Turns into | Example |
|---|---|---|
| `{date}` | The day the chat started, in your local time, written as chosen under **Date in the name** | `2026-10-17` |
| `{time}` | The time the chat started, as hours and minutes | `09.41` |
| `{title}` | The chat's title, at most 80 characters | `Lisbon food trip 3 days` |
| `{service}` | The service | `ChatGPT` |
| `{project}` | The project or Perplexity Space, or nothing | `Travel` |
| `{id}` | The chat's id on its site | `68f1c2a0-5b7e-8003-9a41-2c6d0e7f1a93` |

Real results for a ChatGPT chat titled "Lisbon food trip: 3 days?", started on 17 October 2026 at 9:41 in the Travel project:

| Pattern | File name |
|---|---|
| `{date} {title}` | `2026-10-17 Lisbon food trip 3 days.md` |
| `{date} {time} {title}` | `2026-10-17 09.41 Lisbon food trip 3 days.md` |
| `{service} - {title}` | `ChatGPT - Lisbon food trip 3 days.md` |
| `{project} - {title}` | `Travel - Lisbon food trip 3 days.md` |
| `{title} ({id})` | `Lisbon food trip 3 days (68f1c2a0-5b7e-8003-9a41-2c6d0e7f1a93).md` |

Rules that apply to every name:

- **Characters that can't be in a file name** or that break Obsidian links (`\ / : * ? " < > | # ^ [ ] ~`) become spaces, and repeated spaces become one. That is why "Lisbon food trip: 3 days?" became "Lisbon food trip 3 days".
- **An empty part takes its separator with it.** With `{project} - {title}`, a chat outside any project is named just `Quarterly OKR draft.md`, not ` - Quarterly OKR draft.md`.
- **Every name names the chat.** A pattern without `{title}` or `{id}` gets `{title}` added at the end, so `{date}` alone becomes `{date} {title}`. A pattern without any part, or an empty one, goes back to `{date} {title}`.
- **Names are at most 120 characters** (less for scripts such as Chinese or Japanese, which take more room on disk).
- **Clashes get a number.** A second chat with the same name in the same folder gets ` (2)`, and so on.
- `{time}` uses a dot, `09.41`, because a colon can't be in a file name.

### Date in the name

**Date in the name** sets how `{date}` is written. The four buttons show today's date in each format:

| Format | Example |
|---|---|
| Year-month-day (default) | `2026-10-17` |
| Day.month.year | `17.10.2026` |
| Month-day-year | `10-17-2026` |
| Year month day, no separators | `20261017` |

Year first sorts your files by date in any file list.

> [!NOTE]
> A chat renamed on its site keeps its file name. The `title` property and the heading inside change at the next save. To rename files to match their new titles, use [Apply to saved files](#apply-to-saved-files).

## Properties

**Properties** lists the details written at the top of each file. Click a property to turn it on or off. `id` has a lock: it is always written, because it links the file to its chat.

| Property | Default |
|---|---|
| `title`, `source`, `url`, `model`, `created`, `updated`, `tags`, `project` | On |
| `messages` (number of messages), `words` (number of words) | Off |

`messages` and `words` are numbers, so Obsidian's Dataview plugin can sort and add them up. What each property holds is described in [What's in a saved file](https://chattomarkdown.com/docs/1.0.4/file-format/#properties).

Turning a property off affects new files. In files you already have, it stays until you use **Apply to saved files**, which removes it.

## Extra tags

Every file gets the tags `ai-chat` and the service's id (`chatgpt`, `claude` and so on). **Extra tags** adds your own after them, for example `inbox` or `ai/chats`.

Type a tag and press <kbd>Enter</kbd> or a comma. Tags are cleaned the way Obsidian expects: a leading `#` is dropped, spaces become `-`, and only letters, digits, `_`, `-` and `/` are kept. A tag made only of digits is dropped, because Obsidian doesn't accept it.

Tags are written when a file is created. Tags you change in a file yourself stay as you left them.

## Apply to saved files

Changes on this page apply to chats saved from now on. **Apply to saved files** brings the files you already have in line.

1. **Click Apply…** under **Files you already have**.
2. **Read the question.** It says how many files there are, for example **Rename 1,204 files and update their properties? Links to them from your own notes won’t change.** When the names already match, it asks **Update the properties of 1,204 files? Their names already match.**
3. **Click Rename 1,204 files** (or **Update 1,204 files**). Click **Cancel** to stop here. If Chrome needs your permission for the folder, it asks now.
4. **Wait for it to finish.** A bar shows **Updating files… 300 of 1,204**. Keep the Settings tab open; Chrome warns you if you try to close it.
5. **Read the result.** For example **Done. 1,180 files renamed, 24 files already matched.**

### What it changes

- **File names**, from the current pattern. Each file stays in its folder, so its `attachments` keep working.
- **Properties**, rebuilt for the ones that are on. Values already in a file stay as they are; missing ones are filled in; properties you turned off are removed. `id` is always kept, and a `project` you set yourself is never removed.
- **Tags**: your extra tags are added; extra tags you removed from the list since the last Apply are taken out. Tags you added by hand stay.
- **Thinking**, switched to the current **How thinking looks** style.
- **Secrets**, hidden in the chat when **Hide secrets** is on.

It also updates the extension's records (so the reader and search find the renamed files), the table of contents note, and daily note links.

### What it doesn't change

- Text you wrote above or below the chat, and properties you added.
- Files whose start and end markers you removed. The result says how many were left as they are.
- Which folder a file is in. Folder settings apply to new chats only.
- What the chat contains: options in **What to save** such as **Model thinking** or **Tool calls** need the chat read from its site again. Use **Re-sync** on a chat in the reader for that.
- Links to the files from your own notes.

### Is it safe?

It works on your computer only, without contacting any chat site, in small batches so a sync never sees a half-renamed folder. It never writes over another chat's file: when a name is taken, the file gets ` (2)`. With **Keep a history of changes** on, each changed file keeps its previous version as **File format applied** in its [version history](https://chattomarkdown.com/docs/1.0.4/version-history/).

If something goes wrong (Chrome takes back folder access, for example), it stops and says **Stopped early**, with what was done so far. Run it again: files that already match are counted as such.

## Problems

**The preview shows a different name than I typed.** The pattern was missing `{title}` or `{id}`, or had characters that can't be in a file name. The preview shows what will really be used.

**“1 file wasn’t found”.** Its file was moved, renamed or deleted outside the extension. It comes back at the next sync if its chat changes. See [Moving and renaming files yourself](https://chattomarkdown.com/docs/1.0.4/folder-structure/#moving-and-renaming-files-yourself).

**“Chrome needs your permission to change files in …”.** Click **Apply…** again and allow access when Chrome asks. See [Choose your folder](https://chattomarkdown.com/docs/1.0.4/folder/#allow-access-again-after-a-restart).

**Links in my own notes broke after renaming.** Apply doesn't rewrite links in your own notes, and Obsidian only updates links for renames made inside Obsidian. Update those links by hand, or settle on a pattern before you start linking to chats.

## Questions

### Why does my pattern get {title} added to it?

Every file name has to name the chat, or all chats from one day would clash. A pattern with neither {title} nor {id} gets {title} added at the end.

### Does Apply to saved files change the chat text?

No. It renames files and rebuilds the properties. Inside the chat, it only switches the thinking style and hides secrets when that option is on.

### Will renaming break links in my own notes?

Links from your own notes to a renamed file are not updated. The table of contents and daily note links made by the extension are.
