---
title: "How saving works"
description: "What Chat to Markdown saves and when: the first sync of your history, the pace each site allows, continued chats, the Free limit, offline and restarts."
url: https://chattomarkdown.com/docs/how-saving-works/
version: "1.0.5"
updated: 2026-11-15
---

# How saving works

> After you press Start saving, the extension checks your chat services on a schedule (every 3 hours by default), when you leave a chat and when you press Save. The first sync saves your newest chats first, one request at a time, and slows down when a site asks. A continued chat updates the same file; it never makes a second copy.

Chat to Markdown saves your chats on its own, in the background, as Markdown files in the folder you chose. This page explains what starts a save, how the first sync of a long history works, and what happens when something gets in the way.

## Before anything is saved

Nothing is downloaded until three things are true:

1. You chose a folder. See [Choose your folder](https://chattomarkdown.com/docs/folder/).
2. At least one chat service is on, and Chrome allowed its site. See [Chat services](https://chattomarkdown.com/docs/services/).
3. You pressed **Start saving**, on the welcome page or in the popup's **Get set up** list.

Until then the popup shows **Get set up** with the steps left, and **Settings → Chat services** says "Nothing is saved until you start." **Sync now** in the popup or in Settings also counts as starting. After **Delete all saved chats** in **Settings → Start over**, nothing is saved on its own until you press **Start saving** again. See [Start over or delete saved chats](https://chattomarkdown.com/docs/start-over/).

The **Save** button on a chat page works before you press Start saving: saving one chat by hand is always your own choice. Before you press Start saving, leaving a chat updates it only if you saved it yourself. No other chat is saved until you start.

## What starts a save

| What | What it saves |
|---|---|
| The schedule | New and changed chats from every service that is on. Every 3 hours by default; see [Auto-save and schedule](https://chattomarkdown.com/docs/schedule/). |
| **Sync now** | The same, right away. In the popup, in **Settings → Chat services** and on the [Sync log](https://chattomarkdown.com/docs/sync-log/). A service card's menu has its own **Sync now** for that service only. |
| Turning a service on | That service, right away. |
| Leaving a chat | The chat you left, a few seconds after you switch away, if it changed. Before you press **Start saving**, only chats you saved yourself. |
| **Save** on the chat page, or <kbd>Alt</kbd>+<kbd>Shift</kbd>+<kbd>S</kbd> | The chat open in that tab. See [The Save button and shortcut](https://chattomarkdown.com/docs/save-button/). |
| **Save chat** or **Update** in the popup | The chat open in the current tab. |
| An import | The chats in a data export. See [Import a data export](https://chattomarkdown.com/docs/import/). |

The extension also starts a sync by itself in a few cases: after it updates to a new version (if the update changes how a service's chats are saved, those chats are saved again once, a few at a time), after you upgrade to Pro, when you open a service's site after it said you were signed out, and to retry after no connection or after a site asked it to slow down.

"Leaving a chat" means the tab closes, the tab shows another chat or another page, you select another tab, or Chrome loses focus for about five seconds. The chat is saved once it has been quiet for a few seconds, so a reply that is still being written isn't cut off.

## The first sync

The first sync goes through each service's chat list from the newest chat to the oldest.

- **On Free**, it saves your latest chats, up to 10 in all, from all services together. The 10 most recently updated chats win, wherever they are.
- **On Pro**, it saves every chat, newest first, then older and older ones until your whole history is saved.

A long history is saved in batches of up to 40 chats per service. Each service has its own lane, up to four services at a time, so one slow site never holds up the others. Between batches there is a short pause, and the next batch carries on by itself. You can close every extension page while this runs; the popup and the [Sync log](https://chattomarkdown.com/docs/sync-log/) show how far it got.

The popup shows the history being saved, for example "Saving your chat history" with how many older chats are left and when the next batch starts. While a batch runs, it shows the chat it is reading and the files it is downloading.

## How fast it goes

Chat sites limit how many chats one account can open in a short time. The extension stays under that limit:

- It sends one request at a time to each site, spaced out: about one a second for most services, one every 2.5 seconds for ChatGPT.
- If a site answers "too many requests", that service waits for as long as the site says. If the site doesn't say, it waits 5 minutes, then 15, 30 and 60 for limits in a row, never more than 6 hours. Nothing is lost; it tries again by itself.
- After a limit, it asks that site more slowly for a while, and speeds up again only slowly.
- It learns how many chats a site lets one account open per minute. When that is low, the popup says so, for example "ChatGPT allows only about 1 chat a minute", and saves a few chats at a time until all are saved.

> [!TIP]
> If a service is slow because of its limit, the popup offers **Import instead**: request that service's data export and import every chat at once. See [Import a data export](https://chattomarkdown.com/docs/import/).

While a service waits, its card in the popup says "Waiting" or "Asked to slow down" with the time it goes on. Pressing **Sync now** then checks your other services and leaves that one until its time comes, because starting early would only get saving blocked for longer.

## When a chat changes

Every check asks each service for its list of chats and compares each chat's last update with the version you have. Only chats that are new or changed are downloaded again.

A continued chat updates the file it already has:

- The file keeps its name and place. If the chat moved into or out of a project, the file moves to the new project folder.
- Only the part between `<!-- chattomarkdown:start ... -->` and `<!-- chattomarkdown:end -->` is rewritten. Anything you wrote above or below it stays.
- The `title`, `source`, `url`, `id`, `model`, `created`, `updated` and `project` properties are refreshed. Properties you added yourself stay, and so do edits to `tags`.
- The version before the change is kept, so you can see what changed. See [Version history](https://chattomarkdown.com/docs/version-history/).

> [!WARNING]
> If you delete either marker, the extension leaves that file as it is from then on and the Sync log says "Left as is". Put the markers back to have it updated again.

If the extension finds a file that already holds the same chat (its `id` property matches), for example after you reinstalled the extension, it updates that file instead of making a new one.

Chats deleted on the site stay on your disk, marked `deleted: true`. See [Choose what to save](https://chattomarkdown.com/docs/what-to-save/).

## What counts against the Free limit

Free saves 10 chats in all, from all services together. A chat counts the first time it is saved, however it was saved: by a sync, the **Save** button or shortcut, saving when you leave it, **Re-sync** in the reader, or an import. Copying a chat or saving it as a file (PDF, Word and the rest) from the chat page saves it first, so a chat that isn't one of your 10 uses one.

Once a chat is one of your 10, it stays up to date for good, and saving it again never counts twice. When all 10 are used, Free saves no new chats; the files you already have stay as they are. See [Free and Pro](https://chattomarkdown.com/docs/free-and-pro/).

## When something gets in the way

| What happens | What you see | What to do |
|---|---|---|
| You are signed out of a chat site | "Not signed in" on its card, with **Sign in** | Open the site and sign in. Its sync starts by itself once the page loads. |
| A site wants a check that you are human | "Open Perplexity once" (or the service's name) on its card, with **Open** | Open the site in a tab once. Saving goes on from there. |
| GitHub Copilot isn't open | "Needs its page open" | Keep github.com/copilot open in a tab while it syncs. |
| No internet | "No internet" on the cards | Nothing. The sync waits and starts within a minute of the connection coming back. |
| A site doesn't answer | "Couldn't connect", with **Retry** | Nothing, or **Retry**. It tries again after 1, 2 and 5 minutes, then every 10 minutes. |
| Chrome needs your OK for the folder again | "Chrome needs your OK to save", with **Allow access** | Click **Allow access**. See [Choose your folder](https://chattomarkdown.com/docs/folder/). |
| A site changed and saving stopped working | A red **!** on the toolbar icon and "Saving from ChatGPT stopped working" in the popup | Click **Check for an update**. Your saved files are safe. |

Chrome can stop an extension in the background at any time, also in the middle of a sync. When that happens, the extension notices within a minute and carries on where it left off; the Sync log says "Carrying on after a cut-off". If Chrome stops it three times in a row, it gives up until the next scheduled check and says "Chrome kept stopping the sync. The next sync tries again."

## Stop and pause

- **Stop** (shown while a sync runs) ends that sync after the chat being saved. Auto-save stays on, and the next check carries on where it stopped. A check that was due within 15 minutes moves to the next slot, so it doesn't start again right away.
- **Pause** (the arrow next to **Sync now**) stops auto-save for 1 hour, until tomorrow at 9:00, or until you resume. While paused, nothing is saved on its own, including saving when you leave a chat. **Sync now** and the **Save** button still work.

See [Auto-save and schedule](https://chattomarkdown.com/docs/schedule/).

## Chrome closed, sleep and offline

Checks run only while Chrome is open. If a check was due while Chrome was closed or your computer was asleep, it runs soon after Chrome is open again. The extension doesn't start a sync while Chrome reports it is offline; it looks again every minute and starts once you are back online.

## Several Chrome profiles or computers

Each Chrome profile has its own copy of the extension, with its own folder, settings, schedule and list of saved chats. Pro belongs to your account, so you can sign in on another profile or computer and use it there. See [Upgrade, sign in and manage your plan](https://chattomarkdown.com/docs/upgrade/).

If two profiles or computers save to the same folder (for example a vault synced between computers), each saves on its own. When one finds a file that already holds the same chat under the name it would use, it updates that file. To keep things simple, let one profile save each chat account.

## Questions

### Do I need to keep the chat site open while it saves?

No. The extension reads your chats with the session you already have in Chrome, in the background. Only GitHub Copilot needs github.com/copilot open in a tab while it syncs.

### Will saving a long history get my account blocked?

The extension asks each site one request at a time, spaced out (about one a second, and one every 2.5 seconds for ChatGPT), and slows down as soon as a site says it got too many requests. When a site allows only a few chats a minute, it saves a few at a time until all are saved.

### Does it save a chat twice if I continue it?

No. A continued chat updates the file it already has. Only the block between the two chattomarkdown markers is rewritten, so your own notes above or below it stay.

### Does anything save while Chrome is closed?

No. Checks run only while Chrome is open. A check that was due while Chrome was closed runs soon after you open it again.
