Guides ·
Search ChatGPT history locally
Chat Transfer lets you search ChatGPT history locally by saving the open thread into an on-device Library archive, finding it later by title, snippet, or Site, then continuing that archive into Claude, Gemini, Grok, or ChatGPT — without cloud sync and without replacing ChatGPT’s own account history UI.
Version 0.4.0 is live on the Chrome Web Store. Soft Auto-Send stays opt-in and default off. Library bodies stay in chrome.storage.local (large bodies may use IndexedDB). Add to Chrome
What “search ChatGPT history locally” means here
People search “search ChatGPT history,” “find old ChatGPT chat,” or “ChatGPT history search” for two different jobs. Chat Transfer only does the second:
| Job | Where it lives | Chat Transfer |
|---|---|---|
| Find a thread inside your ChatGPT account | OpenAI’s ChatGPT history sidebar / search on chatgpt.com (account-side data) | No — that UI stays on ChatGPT |
| Search archives you saved on this Chrome profile | Chat Transfer Library (CT Memory JSON) in chrome.storage.local / IndexedDB on this device | Yes — title, snippet, or Site |
| Continue a found archive on another AI | Paste (and optional file attach for huge chats) into Claude, Gemini, Grok, or ChatGPT | Yes — Continue from Library |
| Cloud sync / account migration | Upload chats to a Chat Transfer backend, or move memories / custom GPTs between accounts | No. There is no Chat Transfer backend |
If you only need ChatGPT’s built-in history list, use ChatGPT. Use this guide when you want a local archive you can search offline from the extension, then hop or continue into another composer. Siblings: Search Claude history locally, Search Grok history locally. Related: Export ChatGPT chat to another AI (open-thread hop/export) and Local only.
How Library search differs from ChatGPT’s history UI
This comparison is from how Chat Transfer 0.4.0 stores and filters archives — not from OpenAI product docs claiming parity.
| Dimension | ChatGPT history (web) | Chat Transfer Library |
|---|---|---|
| Corpus | Threads already saved to your OpenAI account | Only chats you Export (or long hops that write CT Memory) into the extension |
| Search fields | ChatGPT’s own sidebar / history search | Title, snippet, and Site (ChatGPT / Claude / Gemini / Grok) inside the popup or side panel |
| Where results open | Back into chatgpt.com | Open archive details locally, or Continue into a chosen Target Site composer |
| Device bound | Follows your ChatGPT login across browsers | Bound to this Chrome profile’s local storage (optional folder index if you grant File System Access) |
| Privacy surface | Account-side data under OpenAI’s product | No Chat Transfer upload; see privacy |
Chat Transfer does not scrape your full ChatGPT history in the background. Extract and Export run when you act — popup, side panel, in-page button, hop, Copy, or Export. Empty new chats are not useful archives.
Library loop: archive → search → continue
- Archive. On an open ChatGPT thread at chatgpt.com, Export to Library (popup, side panel, or the optional in-page CT button). That writes a CT Memory JSON archive (
kind: ct-memory) with title, Site, notes, continue prompt, and message text. Large bodies may spill into IndexedDB (ct-memory). Export can also download Markdown, plain text, JSON, CSV, HTML, PDF, State, or ZIP — Library is the durable on-device list. - Search. Open Library in the popup or side panel. Type into the search field (
library-search). Rows filter by title, snippet, or Site. Pin or delete locally. Import brings a saved archive, Markdown, or text file back in. - Continue. Select a row → Continue. Chat Transfer opens the Target Site and pastes the saved archive (optional notes + continue prompt as a preamble). Huge chats may also attach the CT Memory JSON. Soft Auto-Send stays opt-in; Send is never silent.
Optional folder index: if you grant File System Access to a local folder, that handle and a file list stay in IndexedDB (ct-folder-index). Denied or cancelled permission leaves the in-extension Library as-is. Optional Shrink filler (Export checkbox, default off) strips common filler from the archive copy; fenced code and URLs stay intact; Copy is unchanged.
Steps: search a ChatGPT archive on this device
- Add Chat Transfer from the Chrome Web Store (0.4.0).
- Open the ChatGPT chat you care about (a finished thread on chatgpt.com, not an empty new chat). Wait until the last reply has finished streaming.
- Export to Library — popup, side panel, or in-page button (Export to Library). Confirm the row appears under Recent.
- Later: open Library → type a word from the title or snippet (or filter by Site = ChatGPT) → select the row.
- Continue on Claude, Gemini, Grok, or ChatGPT. Preview the paste. You press Send — unless Soft Auto-Send is on and you confirm once.
Longer install walkthrough: How to use. For hopping the currently open ChatGPT thread without using Library first, see Export ChatGPT chat to another AI and the ChatGPT hop guides.
Soft Auto-Send stays opt-in (default off)
Continue-from-Library paste does not silent-send. Soft Auto-Send is opt-in (hopSoftAutoSend in chrome.storage.local, default off). After a successful paste it asks once: “Send this hop now?” Confirm presses destination Send once; Cancel leaves the paste; a failed paste never asks. No upgrade turns the box on for existing installs. Full walkthrough: Soft Auto-Send.
Local only — chrome.storage, no backend
Chat Transfer is a local-only Chrome extension. Settings and Library archives stay on this device. There is no Chat Transfer backend; the marketing site does not receive archive text. Host access is only Claude, ChatGPT, Gemini, and Grok domains. Soft Auto-Send adds no host_permissions and no downloads permission. Same facts as the privacy policy.
Searching the Library does not open a tunnel into OpenAI account data you never exported. Threads you never archived remain only in ChatGPT’s own history.
When not to use Library search
- You need every ChatGPT thread ever — Library only holds what you exported (plus useful long hops that write CT Memory).
- You want the same archive list on another computer without moving files — there is no cloud sync; use Export / Import or a folder you copy yourself.
- You need images, files, or canvases rebuilt inside the destination — Continue pastes text (and may attach CT Memory JSON for huge chats); it does not rebuild binaries.
- You need an ongoing mirror between ChatGPT and another account — see Hop vs migration.
FAQ
Can I search ChatGPT history locally without uploading chats?
Yes. Chat Transfer stores Library archives in on-device chrome.storage.local / IndexedDB. There is no Chat Transfer chat-upload backend.
Is this a replacement for ChatGPT’s history search?
No. ChatGPT’s sidebar still owns account-side history. Library search only covers archives you saved into the extension on this Chrome profile.
Does Continue from Library silent-send?
No. Paste never silent-sends. Soft Auto-Send is opt-in, default off, and asks once after a successful paste.
What can I search by?
Title, snippet, and Site. Pin or delete rows locally. Import restores a saved archive, Markdown, or text file.
Sources
- ChatGPT — source app / account history UI
- Memory FAQ — OpenAI Help Center (account-side Memory is separate from Chat Transfer Library)
- Chat Transfer on the Chrome Web Store
- Chat Transfer privacy policy — Library / CT Memory storage notes
Related
Product · Guides · Export ChatGPT chat to Markdown · Search Claude history locally · Search Grok history locally · Export ChatGPT to another AI · Hop ChatGPT to Claude · Hop ChatGPT to Gemini · Hop ChatGPT to Grok · Soft Auto-Send · How to use · Local only · Hop vs migration · Privacy · Add to Chrome