How to export Grok chats (every real way, and what each misses)
On August 6 a paying SuperGrok subscriber was forced to sign back in on desktop and found their entire conversation history and projects gone — the subscription showed as invalid too, and repeated messages to support never got a human response. There was no export button they could have pressed the day before, because Grok doesn’t have one: no per-conversation export exists on grok.com or in the apps, and nothing in xAI’s July and August releases changes that. What does exist: an account-wide data download that arrives as raw JSON, a PDF trick for single responses on Premium+, copy-paste one reply at a time, a crop of page-scraping browser extensions — and Carry, which saves your Grok conversations as Markdown files in a folder you own. Here’s each option and what it misses.
The ways out, at a glance
| Method | What you get | Effort | Habit or one-off | Best for |
|---|---|---|---|---|
| Account data download | Raw JSON; needs a converter to read | Request, wait, unzip | One-off snapshot | A full archive, occasionally |
| Copy-paste | One reply at a time; formatting suffers | High per conversation | One-off | A single short exchange |
| “Export as PDF” prompt | Single responses only; Premium+ | Low, per response | One-off | A fixed record of one answer |
| Extensions & scripts | Scraped from the page; breaks when Grok’s UI changes | One click, until it doesn’t | Ongoing | Convenience, if you vet it |
| Carry | Clean Markdown from Grok’s own data | One click per sync — manual on Grok, recent window only | Ongoing | Your own copy, going forward |
Method 1: xAI’s account data download (raw JSON)
The official route is not in the chat window. Go to accounts.x.ai/data and click Download under “Download account data” — the same request also lives at Settings → Data Controls in the Grok app and under Account settings on grok.com. xAI prepares a zip; the conversations inside are one big structured file, prod-grok-backend.json, holding your conversation history (with branches), your projects, and tasks; file assets sit alongside in id-named folders. It’s machine-shaped, not readable. Two tools convert it: Grok to Markdown, a free converter that turns the zip into one Markdown file per conversation (it says the parsing stays in your browser), and a small Python script that can also pull out Grok’s thinking traces. For other data rights — deletion included — there’s a formal privacy request, which wants your full legal name, email, and where you live.
The same limits as every takeout apply. It’s a snapshot — everything up to the moment you asked, nothing after, so staying current means requesting again. And it can only contain what’s still in your account — requested after a wipe like the one up top, it’s already too late. Private Chat conversations — the ghost-icon mode that skips your history — may already be missing from it, since xAI clears those within 30 days. And if you use Grok inside the X app, those chats live in X’s separate data archive, not the xAI one. Fine as occasional insurance; not a daily working copy.
Method 2: copy-paste and the PDF trick
Grok’s interface copies one reply at a time — there’s no copy-this-conversation control. Selecting the whole page by hand sort of works, except Grok lazy-loads older messages, so anything you haven’t scrolled up to isn’t on the page to select. Tolerable for one short exchange; across a real working history you’ll stop by the third conversation.
The other native trick is PDF: ask Grok to “export as PDF”, or use the menu under a response. Both routes — the prompt and the menu item — cover individual responses only, not full conversations, and require Premium+, which is X’s subscription tier. Good for freezing one answer you want to share; a dead end for a searchable archive.
Method 3: extensions and userscripts
The strongest open-source option is a multi-provider userscript (208 stars, grok.com supported, runs in the Tampermonkey userscript-manager extension) — and even it scrapes the rendered page, which is the field’s structural weakness. One Grok exporter needed a patch just to survive a Grok UI restyle; when the markup changes, every scraper’s formatting breaks at the same spot.
Below that, 2026 has brought a wave of closed-source Grok exporters that are hard to vet: Chrome-store entries with 54 and 59 users and anonymous gmail-address developers, one of which discloses that it handles personally identifiable information, authentication information, and user activity. Another markets itself as private while processing PDF exports on its own servers, and its “open source” GitHub repo contains a README and no code. The trust bar for anything that can read your AI conversations: local-only, minimal permissions, a clear reason for each one. Extensions have turned hostile after silent auto-updates before, including two caught exfiltrating AI chats from 900,000 users to a remote server. The ChatGPT guide has the full vetting checklist; it applies to Grok unchanged.
Why a copy outside grok.com is urgent
The August 6 story up top is the latest in a pattern. In late July a user reported losing most of their saved Imagine media; the week before, within days of each other, users documented chat history rolling back three months after closing a laggy app, Supergrok wiping history and generations outright, and sync quietly breaking between phone and desktop. In the same window, grok.com quietly enabled data sharing, history tracking, and chat linking by default.
The safety net under all this is thin. Chats you delete may be restorable for up to 30 days via Recently Deleted, after which they’re permanently purged — and that folder only restores, never exports, and never catches chats a bug took. Private Chat conversations never enter your history at all, and xAI deletes them from its side within 30 days, per Grok’s own account. So the platform’s floor is: bugs can take history at any time, and deletion becomes irreversible after 30 days. A copy that lives outside grok.com is the only version of your history whose lifespan you control.
Doing it with Carry
Carry is the browser extension we built for this: it saves your Grok conversations as Markdown into a folder you own — local-only, no account, no API key. It reads Grok through the session you’re already signed into rather than the rendered page, so a UI restyle can’t break your formatting and code, tables, and structure survive intact.
Three steps, and the animation below is the whole thing:
Pick your folder
Connect providers
Then it's automatic
Grok has its own wrinkles — background reads are blocked, so it syncs from the popup, and the archive builds going forward rather than all at once — which the questions below cover. If a plain folder of your Grok chats sounds useful, the homepage has the rest.
Common questions
Does Grok have an export button?
Can I recover deleted Grok chats?
Do chats with Grok inside the X app come with the xAI download?
Can I save Grok chats to Obsidian?
Can Carry back up my entire Grok history?
What happens to my saved files when the Carry trial ends?
Carry is local-only — no server, no account, and only the providers you connect. It syncs Grok, ChatGPT, and Claude into your own folder as Markdown — see how it works to get started. If you also use Claude, the Claude + Grok export guide covers that side.
Save every conversation.
Sync your ChatGPT, Claude, and Grok conversations into your own folder — as clean Markdown, local-only.