How to export your AI chat history before you lose it

Short answer: ChatGPT, Claude and Gemini each let you request a data export, but it arrives as one raw archive you have to request again every time. For a copy you can actually use, save conversations as you go, as Markdown or JSON on your own disk.

Chat history feels permanent until it is not. Accounts get closed, retention policies change, a shared login deletes a thread, a provider sunsets a feature. Your conversations are on someone else's computer under someone else's terms.

The official route, and its limits

Every major assistant offers an account data export. The flow is broadly the same: settings, data controls, request export, wait for an email, download a zip.

Where each one is:

• ChatGPT: Settings → Data controls → Export data. A download link arrives by email.
• Claude: Settings → Privacy → Export data. A download link arrives by email.
• Gemini: Google Takeout, where your Gemini conversations are part of your activity data.

It works, and you should do it. But know what it is:

• It is slow. Hours, sometimes longer. Useless when you need something now.
• It is a snapshot. Valid the moment it was made. Everything after it needs another request.
• It is a data dump, not a document. Usually JSON built for the provider's own storage, with internal ids and epoch timestamps. Readable by a program, unpleasant for a person.
• It is per platform. Three assistants means three separate exports in three different shapes.
• The link expires. Download it promptly or repeat the whole thing.

What a good export actually looks like

Most people want one of three things, and they are genuinely different:

• Something to read. One page, every conversation, searchable with Ctrl+F, printable. Not a folder of JSON.
• Something to analyse. A spreadsheet row per conversation — when, which platform, how many messages. One row per message sounds better and is not: an answer is four thousand characters of prose and a cell is one line.
• Something to keep. A complete, documented file with every field spelled out and real ISO timestamps, so it is still readable in five years by whatever you have then.

Backup is not the same as export

An export is for reading. A backup is for restoring — it needs to come back complete after a reinstall, which means it should be encrypted, because it contains everything you have ever asked.

If you only ever make exports, a lost laptop costs you the archive. If you only ever make backups, you cannot read your own history without the tool that wrote it. Both is correct.

How Tvara handles it

Because Tvara already keeps a local copy of your conversations, export is instant and offline — no request, no waiting email, no expiring link. Three formats, one ordering, so they cannot disagree with each other:

• A page (.html) — one self-contained file, every conversation in full, with a contents list. Ctrl/Cmd+P paginates it per conversation if you want paper.
• A list (.csv) — one row per conversation, with a byte-order mark so spreadsheets read the text correctly instead of as mojibake.
• Everything (.json) — every field named, ISO 8601 times, and a block inside the file explaining the file.

Export is free. Encrypted backup and restore are Pro. Either way the file lands in your Downloads folder and nothing is transmitted.

See also what happens when a conversation is deleted on the site.