ChatGPT Exporter by GerTex

Export any ChatGPT conversation as raw JSON — full tree with branches, edits, and regenerations. By GerTex, LLC.

ChatGPT Exporter by GerTex adds a single "Export JSON" button to the ChatGPT interface. Click it, and the full conversation downloads to your computer as a .json file — not just the messages you can see, but the complete conversation tree that ChatGPT's backend stores: every branch, every edit, every regeneration, every tool call, and all associated metadata. Built by GerTex, LLC — German Engineering In Texas. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ WHAT YOU GET IN THE JSON ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - Conversation title, creation time, update time, and conversation ID - Model slug(s) used throughout the conversation - The full "mapping" tree: every message node with parent/child pointers - All branches — including ones you regenerated away from or edited over - Message authors (user, assistant, system, tool), content parts, and per-message metadata - The current_node pointer marking the leaf of your currently-selected branch - Moderation results, attachments metadata, and any other fields ChatGPT's backend returns This is the same payload ChatGPT's own web app uses internally — no trimming, no lossy reformatting. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ WHY RAW JSON? ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - Archiving — keep a permanent, machine-readable copy of important chats - Analysis — feed conversations into your own tooling, notebooks, or scripts - Migration — move context into other LLM clients or self-hosted chat UIs - Compliance & recordkeeping — preserve the full conversational state, not just the rendered text - Debugging prompt workflows — inspect regenerations and branches that the ChatGPT UI hides ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ HOW IT WORKS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1. Open any conversation on chatgpt.com (or chat.openai.com). 2. An "Export JSON" button appears in the header next to Share. 3. Click it — a .json file with the conversation title downloads instantly. The button only appears when an actual conversation is open. On the new-chat view there's nothing to export, so nothing is shown. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ PRIVACY — THIS IS IMPORTANT ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - No data collection. No telemetry. No analytics. No tracking. - No GerTex server is ever contacted. At all. - The extension only talks to ChatGPT's own domains (chatgpt.com / chat.openai.com) using your existing login session — the exact same API the ChatGPT web app uses. - Your exported JSON is saved directly to your own Downloads folder. Nothing is uploaded anywhere. - Minimum permissions: host access to ChatGPT's domains (to inject the button and fetch the conversation). No API permissions are declared at all. Full privacy policy: https://gertex.us/chatgpt-exporter/privacy ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ JSON STRUCTURE (HIGH LEVEL) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ { "title": "…", "create_time": 1730000000.0, "update_time": 1730000000.0, "mapping": { "<node-uuid>": { "id": "<node-uuid>", "parent": "<parent-uuid>", "children": ["<child-uuid>", …], "message": { "author": { "role": "user" | "assistant" | "system" | "tool", … }, "content": { "content_type": "text", "parts": ["…"] }, "create_time": 1730000000.0, "metadata": { "model_slug": "gpt-…", … } } } }, "current_node": "<node-uuid>", "conversation_id": "…", … } The "mapping" object is the full branch-aware tree. Walk from "current_node" up through "parent" pointers to reconstruct the visible conversation; traverse "children" from the root to see every branch. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SUPPORT ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Questions, bug reports, or feature requests: https://gertex.us GerTex, LLC — German Engineering In Texas Full-stack development · Database management · System integration · Cloud infrastructure · IT consulting