How to save claude conversation as a file you keep

Claude.ai already keeps every signed-in chat in History. There is no Save button that writes a file. To save claude conversation as Markdown, JSON, text, XML, or PNG, use Download Claude conversations in Chrome, print the page, or request Settings → Privacy → Export data. Closing the tab does not delete the thread.

Does Claude already save claude conversation in History?

Yes. Claude.ai already stores the signed-in thread in History on the Anthropic account. Closing the tab does not wipe the conversation. There is still no Save control that writes a disk file. A save claude conversation action as Markdown or JSON is a separate job from History.

History is the left-hand list of chats on claude.ai. Each row is a conversation Anthropic stored for that login. Open a row later and the same turns come back. That is account storage, not a download folder on your laptop.

People who type how to save conversation in claude often mean “will this vanish when I leave?” The answer for a normal signed-in session is no. Claude.ai does not require a Save click to keep the thread in the account. The missing control is a file exporter, not a keep-alive switch.

History is not a Markdown file, not a JSON tree you can grep, and not a PNG you can drop into a slide. History lives behind the Anthropic login. If you cannot sign in, you cannot open those chats. A local file still opens after the password is gone.

Two different “saves.” History = Anthropic keeps the chat in the account. File = you write Markdown, JSON, text, XML, or PNG to disk. Claude.ai has the first. Claude.ai has no button for the second.

Projects and Recents on claude.ai are still History. Grouping a chat into a Project does not create a file. Renaming the conversation does not create a file. Starring or pinning, if the UI offers those, still does not write Markdown.

Team and Enterprise workspaces follow the same split. If you can open the conversation on claude.ai, Anthropic already stored that conversation for the workspace. Company retention rules may still delete or hide chats on a schedule you do not control. A file you exported is then the copy you keep.

Incognito and a second Chrome profile do not share History. The thread is tied to the Anthropic account used in that session. Signing into a different Anthropic login shows a different History list. Cross-account “save” is a file, not a History merge.

How to save claude conversation as a file?

To save claude conversation as a file, pick a method that writes to disk: Download Claude conversations in Chrome, Print → Save as PDF, or Settings → Privacy → Export data. History on claude.ai is account storage, not a Markdown, JSON, text, XML, or PNG file.

The Chrome extension is the per-chat path. Open the conversation URL, click the orange button next to the message box, choose a format, click Export. Chrome’s download API writes the file locally. Quota uses Google sign-in. Chat bodies stay on the machine.

Print is the visual path. Ctrl+P or Cmd+P, destination Save as PDF. The result looks like the claude.ai page, including chrome that print styles did not hide. Code blocks often split across sheets. Use print when a reviewer wants a snapshot, not a notes file.

Official Export data is the account path. Settings → Privacy → Export data on claude.ai. Anthropic emails a link that expires. The ZIP is JSON for the whole account, not one named file for the chat on screen. Wait time is the cost of a full backup.

What “save” means on claude.ai versus a file on disk
You want Method You get You still lack
The chat not to vanish Stay signed in; use History The thread in the Anthropic account A file you can email or git
One chat, readable file, now Chrome extension (this product) Markdown, JSON, text, XML, or PNG A native PDF from the extension
Visual PDF of this screen Print → Save as PDF A paged snapshot of claude.ai Clean code, tables, collapsed artifacts
Full account backup Settings → Privacy → Export data JSON ZIP by email Per-chat formatting; wait for the link

Pick the row that matches the job. Most searches for how to save claude chat want row two: a file they can open in Obsidian, VS Code, or a wiki. History already handled row one. Print and Export data remain real; those methods solve different jobs.

A file is the right move before offboarding, before a laptop wipe, before a research archive, or before you paste a coding review into git. History is enough when you only need to reopen the same thread tomorrow on the same Anthropic login.

Copy-paste is a fifth method and a weak file. Select text on claude.ai, paste into Docs. Fences collapse. Tables become run-on lines. Message boundaries disappear. Fine for one paragraph. Poor as the only save claude conversation record for a 40-turn design review.

How to save claude chat with the Chrome extension?

How to save claude chat with Download Claude conversations: install the Chrome extension, open the thread on claude.ai, click the orange button next to the message box, pick Markdown, JSON, text, XML, or PNG, then Export. Google sign-in counts the 3 free exports.

  1. Install Download Claude conversations from the Chrome Web Store (Chromium browsers that load Chrome extensions also work).
  2. Reload claude.ai if the page was already open during install. Chrome does not always inject a content script into old tabs.
  3. Open a real conversation URL from History — the orange button appears on a thread, not on the empty composer home.
  4. Click the orange download button to the right of the message box.
  5. Choose Markdown, JSON, plain text, XML, or PNG. Click Export. Chrome downloads the file immediately.

The extension is a Chrome content script on claude.ai only. The parser reads the conversation already loaded in the logged-in session. Download Claude conversations does not call a separate Anthropic API with its own credentials, and does not upload the thread to our servers to generate the file.

Before the first export, Google sign-in is required. That sign-in exists so we can count the 3 free exports per account and restore Pro later. Google sign-in is not a login for reading chats. We store a Google-verified email for quota and subscription status. Conversation bodies stay on your machine.

Each completed file counts as one export, whether the format was Markdown or PNG. Free accounts get 3 exports total. Pro is $3.99 per month or $26.99 per year and removes that cap for both single chats and bulk Export All. Paddle processes Pro payment. We do not see card numbers.

Local files. Markdown, JSON, text, XML, and PNG are built in the browser and handed to Chrome’s download API. Quota checks go to our worker. Chat text does not. Version 1.13.0 is rated 5.0 on the Chrome Web Store.

Optional toggles on the same widget: include or skip extended thinking, include metadata (title, timestamps, model), filter by sender (all / human only / assistant only), and pick an artifact layout — Original, Inline, Nested, or Flat. Those toggles apply to this one chat the same way they apply on the bulk browse page.

If the thread is very long, scroll until claude.ai has loaded the earlier messages. The extension can only export what the page has rendered. A half-loaded thread produces a half-loaded file. That looks like a bug and is usually an un-scrolled DOM.

Wait for the assistant to finish streaming before Export. A mid-stream save claude conversation file cuts the last answer. On the free tier, a second attempt uses another quota slot — one reason to confirm the thread is complete first.

The last-used format is remembered. If you wanted Markdown and received JSON, the dropdown was still on JSON from the previous export. Check the dropdown every time you switch jobs. Step-by-step screenshots of the same orange button live on how to download a Claude chat.

We hear the same mix-up every week: people hunt for a Save button because they think History is a draft that will vanish. Claude.ai already stored the thread. Our orange button only writes a local Markdown, JSON, text, XML, or PNG file from the page you already opened — we never invent a PDF format.
The Download Claude conversations team — builders of the Claude Chat Downloader Chrome extension

How to save conversation in claude without an extension?

How to save conversation in claude without an extension: print the claude.ai page, or request Anthropic’s Export data ZIP. Print is a visual PDF of the webpage. Export data is a delayed JSON archive of the whole account. Neither writes a per-chat Markdown file.

Print path: open the conversation on claude.ai, hide the sidebar if the UI allows it, press Ctrl+P (Windows/Linux) or Cmd+P (Mac), set the destination to Save as PDF, then save. Composer chrome can repeat on every sheet. Full print notes live on download Claude chat as PDF.

Official path: Settings → Privacy → Export data on claude.ai. Anthropic emails a link that expires. Unpack the ZIP yourself if you need one conversation out of thousands. That archive is the legal-style backup, not a notes file for tomorrow’s standup.

Copy-paste remains available with zero install. Highlight turns on claude.ai, paste into a notes app. Indentation in code usually collapses. A multi-turn thread becomes an unstructured wall. Use copy-paste for a single snippet, not as the only how to save conversation in claude plan.

No-extension ways to get a Claude chat off the screen
Method Speed Scope Best for
Print → Save as PDF Immediate The open page A visual attachment
Settings → Privacy → Export data Delayed email Whole account Offboarding or a legal hold
Copy-paste Immediate Whatever you selected One short answer
History only (no file) Already done Signed-in chats Reopening the same thread

None of those rows replace Download Claude conversations when you need structured Markdown from one History item now. The no-extension methods still matter when IT blocks Chrome extensions, when you need the official ZIP, or when a PDF-looking printout is the deliverable.

Mobile Safari and Chrome on a phone can print. Those browsers cannot install this Chrome Web Store item. For a reusable Markdown file, open the same History item in desktop Chrome after you add the extension.

Will History still save claude conversation after close?

Yes. History will still save claude conversation after you close the tab, refresh claude.ai, or shut the laptop — as long as the chat was created while signed in. Closing a tab is not delete. Delete from History is the action that removes the thread from the account UI.

Log out of claude.ai and the page goes blank. Log back into the same Anthropic account and History returns those chats. Logout hides the list; logout does not, by itself, erase the account store. A different Anthropic login shows a different History.

Delete from History is the vanishing case people actually hit. Remove a conversation in the claude.ai UI and that thread is gone from the sidebar. A Markdown file you already exported with the orange button stays on disk. Export first if the chat is about to be cleaned up.

Delete is not close. Closing a claude.ai tab leaves History intact. Deleting the conversation from History removes the chat from the account UI. Official Export data will not help after a delete if Anthropic no longer includes that thread. Write the file before you prune.

Incognito ends when the window closes. If you used claude.ai in a private window without a lasting login, do not assume History kept the work. Sign in on a normal Chrome profile, or export a file before the incognito session dies.

Workspace admins can retain or restrict chats on Team and Enterprise. A policy you did not set can hide a thread later. Treat company History as borrowed storage. Treat an exported Markdown or JSON file as the copy on your side of the policy.

Switching from a phone to a laptop does not require a special save claude conversation click when both devices use the same Anthropic account. Open History on the laptop. If the chat is missing, you are on a different login, a different workspace, or the thread was deleted — not “unsaved.”

Claude Desktop may show the same account’s chats when that app is logged into the same Anthropic user. Sync is Anthropic’s job. The Chrome extension never injects into Desktop. If the thread exists on claude.ai, open claude.ai in Chrome to write a file.

How to save claude conversation in Markdown or JSON?

How to save claude conversation in Markdown or JSON: open the orange button on claude.ai, choose the format, then Export. Markdown is the notes file. JSON is the message tree for scripts. Plain text has no markup. PNG is a picture, not a PDF.

Markdown keeps headings, fenced code with language tags, and tables. Markdown is the usual pick for Obsidian, GitHub, or a wiki. Layout notes for that format: Markdown export. JSON preserves the tree the parser already built, including artifacts and thinking when those toggles are on.

JSON from Download Claude conversations is not the same shape as Anthropic’s account ZIP. The extension JSON is one conversation as the page rendered it. Export data JSON is an account dump Anthropic emails later. Do not mix the two schemas in one script without checking keys.

Plain text is the right choice when the destination strips markup — a ticketing field, an email body, a search index that wants raw strings. XML is the niche interchange pick. PNG is for a slide or a bug-report figure of the thread, not for a 40-turn review you will grep.

Formats Download Claude conversations writes from claude.ai
Format Best for Not for
Markdown Notes, git, later conversion Pixel-perfect layout
JSON Scripts, message tree Reading in a word processor
Plain text Zero-markup archives Keeping tables as tables
XML XML-only pipelines Casual reading
PNG A figure of the thread Search, diff, or print-as-document

There is no native PDF in version 1.13.0. If a client requires PDF, export Markdown and print that file from Word, Google Docs, VS Code, or Obsidian. Or print claude.ai itself. Do not wait for a .pdf option that this extension does not ship.

Thinking, metadata, sender filter, and artifact layout change what lands in Markdown and JSON. Turn thinking on when you need the extended reasoning in the archive. Turn thinking off when the file is for a reader who should see only the final answer. Metadata adds title, timestamps, and model when you want a header on the notes file.

Sender filter “human only” writes your prompts. “Assistant only” writes Claude’s replies. “All” is the default full thread. Artifact layout Original / Inline / Nested / Flat changes how artifacts sit in Markdown. Pick a layout once and reuse it so a folder of saved chats stays consistent.

How to save claude chat History in bulk?

To save claude chat History as many files, do not repeat the orange button once per tab. Open View and Download All Conversations from the extension popup, filter the table, then click Export All. Each finished file still counts against the same 3 free exports unless you are on Pro.

The browse page lists conversations from the claude.ai account you are logged into — the same History you already have, turned into a table you can filter. Search by name. Filter by All, New (not yet exported), Exported, and by Project if you group chats that way on claude.ai.

Bulk uses the same five formats and the same toggles as a single-chat export: thinking, metadata, sender filter, artifact layout. Export All is not a lesser pipeline. Export All is the same parser applied to many conversation IDs in one pass. Details: bulk Export All.

Anthropic’s Export data is still the account backup. One ZIP, one email, JSON for everything, including chats you forgot. Bulk Export All is the opposite job: you pick which History rows, you pick Markdown or JSON, files land immediately. Use both if you want a legal-style archive and a folder of readable notes.

Quota is shared. Three free exports cover single chats and bulk files together. Selecting 40 conversations on a free account will stop after the third file. Plan the selection, or upgrade to Pro at $3.99/mo or $26.99/yr via Paddle.

The browse table remembers what you already exported, so a later visit can filter to New only. That is how a weekly how to save claude chat habit stays incremental instead of duplicating last month’s Markdown. Reinstalling the extension does not reset the 3-export count; the Google-signed account does.

Select a subset when History is full of one-line drafts. Export All does not mean you must take every row. A tight filter plus Markdown is a cleaner research folder than 200 empty “hello” threads.

Export Claude chat as a product verb is the same orange button and the same Export All table. The adjacent page export Claude chat maps those controls if you arrived from an “export” query instead of “save.”

Can I save claude conversation on Desktop or Code?

No. Download Claude conversations cannot save claude conversation from Claude Desktop or Claude Code. The Chrome extension runs on claude.ai in desktop Chrome only. Claude Desktop is a separate app. Claude Code is the terminal agent with /export and JSONL on disk.

If the Desktop chat also exists on claude.ai, open that URL in Chrome and use the orange button. If the thread only lives in Desktop, copy-paste or wait for Settings → Privacy → Export data. The extension never injects into the Desktop window.

Inside an active Claude Code session, type /export. Anthropic’s CLI opens a menu to copy the transcript or save a plain-text file. Pass a filename to skip the menu. That transcript is rendered text for a person to read, not this extension’s Markdown/JSON/PNG. Full paths: Claude Code export.

JSONL on disk is the internal log under ~/.claude/projects (Windows: %USERPROFILE%\.claude\projects). The schema can change between Claude Code versions. Anthropic’s own docs tell you to prefer /export over parsing JSONL. We do not wrap that CLI. We do not read ~/.claude.

Where each Claude surface stores a conversation you can keep
Surface Already “saved”? How to write a file This Chrome extension
claude.ai in Chrome Yes — History on the account Orange button or Export All Yes — that is the product
Claude Code terminal JSONL on disk for the session /export or copy JSONL No
Claude Desktop app If the same Anthropic account syncs Open the chat on claude.ai, or copy-paste No — not injected into Desktop
Account-wide backup Anthropic’s store, plus emailed ZIP Settings → Privacy → Export data Different job — delayed JSON ZIP

Team and Enterprise workspaces work with the extension if you can open the conversation on claude.ai in Chrome. The parser reads the rendered page, not a consumer-only API. If a company policy blocks extensions, that is an IT decision, not a plan-tier switch in our settings.

Independent Chrome extension, not affiliated with Anthropic, PBC. Claude is a trademark of Anthropic. Follow Anthropic’s Terms of Service. We cannot give legal advice about whether a given export is allowed in your workplace. The extension uses your existing session the same way the website does and does not automate account actions.

Paddle bills Pro. Google sign-in does not grant us the conversation. The Cloudflare worker that checks Pro status receives license state, not message text. Billing on the server, chat on the disk — that boundary is the privacy story for every save claude conversation file this product writes.

FAQ: how to save claude conversation

How do I save claude conversation as a file?

Install Download Claude conversations, open the thread on claude.ai, click the orange button next to the message box, pick Markdown, JSON, text, XML, or PNG, then click Export. The file downloads locally. History already stored the chat in the Anthropic account; the orange button writes a disk copy.

How to save claude chat on claude.ai?

You do not need a Save button to keep the thread in the account. Claude.ai History already lists signed-in chats. To save claude chat as a file, use the Chrome extension, Print → Save as PDF, or Settings → Privacy → Export data for a delayed account JSON ZIP.

How to save conversation in claude without an extension?

Print the claude.ai page (Ctrl/Cmd+P → Save as PDF) for a visual copy, or use Settings → Privacy → Export data for an emailed JSON ZIP of the whole account. Copy-paste works for a short answer. None of those methods write a structured per-chat Markdown file the way the Chrome extension does.

Does Claude already save claude conversation in History?

Yes. Signed-in chats on claude.ai stay in History on the Anthropic account. Closing the tab, refreshing, or opening another device with the same login does not wipe the thread. History is not a Markdown, JSON, text, XML, or PNG file on your disk.

Will a Claude conversation vanish if I close the tab?

No. Closing a claude.ai tab does not delete the conversation from History. Deleting the chat from History does remove it from the account UI. A file you already exported with Download Claude conversations stays on disk even after that delete.

Can I save claude conversation as PDF?

Not with Download Claude conversations 1.13.0. Formats are Markdown, JSON, plain text, XML, and PNG. For a PDF-like snapshot, print the claude.ai page. PNG is an image of the thread, not a PDF.

How many free files to save claude conversation?

Every Google-signed account gets 3 free exports in any of the five formats. After that, Pro is $3.99 per month or $26.99 per year. Paddle processes payment. Bulk Export All files count against the same 3.

Does save claude conversation work on mobile?

The Chrome extension does not. It runs in desktop Chrome (or another Chromium browser that can install Chrome Web Store items). There is no iOS or Android app. Mobile browsers can still open History and print a Claude chat; they cannot show the orange button.

Can I save claude chat from History in bulk?

Yes. Open View and Download All Conversations from the extension popup, filter the table, then click Export All. That bulk path is not Anthropic’s Export data ZIP. Official Export data is one archive of the whole account, emailed later. See bulk download.

Does this save claude conversation from Claude Code?

No. Claude Code lives in the terminal. Use /export or copy JSONL from ~/.claude/projects (Windows: %USERPROFILE%\.claude\projects). This Chrome extension only runs on claude.ai. Guide: Claude Code export.

Is Google sign-in required to save claude chat?

Yes, starting with the first export. Google verifies which account you picked so we can enforce the 3-export quota and restore Pro after a reinstall. Conversation content is not sent with that sign-in. We store the verified email for quota and Pro status only.

Where is official Export data to save Claude chats?

On claude.ai: Settings → Privacy → Export data. Anthropic emails a link that expires. The ZIP is an account-level JSON archive, not a named Markdown file for the chat you were reading. Use Export data as a backup; use the orange button for one readable file now.

Download Claude conversations

Install the extension and save claude conversation as a file

History already keeps the chat. Turn the open claude.ai thread into Markdown, JSON, text, XML, or PNG — locally, from Chrome.

Add to Chrome