chattrove archives your Claude.ai conversations — text, images, attachments, and structured metadata — into a single portable ZIP. Not an export. An archive built for reuse.
Get it on Web Store →Most "export" buttons give you a flat text file: useful for compliance, useless for anything else. chattrove was built around a different idea — that the conversation itself is the raw material.
Built because the official export drops the images, flattens the structure, and isn't shaped for what comes next: the article you'll write, the video you'll cut, the notebook you'll keep.
Three pieces designed to work together. Read on its own, or feed straight into whatever you build next.
Inline images, screenshots, and file attachments are downloaded alongside the text — named, numbered, and linked back to the message that referenced them.
/attachmentsMarkdown for reading, JSON for processing, CSV for editing. Speaker, timestamp, message ID, attachment references — all queryable, all yours.
conversation.jsonThe whole archive is a single download. Drop it into Obsidian, hand it to your editor, feed it into a video pipeline — no online service required to read it back.
chattrove_*.zipAdd chattrove to Chrome. No account, no signup, no server connection.
Click the chattrove icon. It scans the conversation in place — including images and attachments you've uploaded.
One ZIP. Markdown, JSON, CSV, and every asset, ready to read or repurpose.
Plain files. No proprietary format. Drop the archive into the tools you already use.
Drop the ZIP into a Notion page — attachments unpack into a media database, conversation.md becomes a readable note.
drag .zip → dropMarkdown reads natively. Wikilinks survive. Dataview your archives across conversations.
extract → vaultFeed conversation.md and attachments as a research source. Ask Gemini across your past Claude work.
upload .md + assetstimeline.csv opens as a sortable table. Filter by speaker, search the conversation log.
open timeline.csv
conversation.md, conversation.json, timeline.csv, metadata.json, an EXPORT_RESULT.md summary, and an attachments/ directory with every image and file referenced in the chat. Everything is plain text or standard binary formats — no proprietary container.v1.0 lands on the Chrome Web Store soon. Get notified via X or the developer blog.