JSON is the format you pick when the reader is a program: feeding chats into a pipeline or RAG index, analyzing your history, or archiving conversations with every timestamp and metadata field intact. Here's how to export a ChatGPT conversation to JSON — one chat instantly, or all of them at once — and what the structure inside actually means.

Method 1: Export ChatGPT to JSON with a Browser Extension (Fastest)

ChatGPT Pro Tools is a free extension that adds export options directly to ChatGPT.

The export is a lossless, pretty-printed copy of the conversation exactly as ChatGPT's own interface loads it — nothing trimmed, nothing reformatted. That makes it the one format that keeps everything: timestamps, model info, message metadata, and every branch of the conversation.

What's Inside the JSON File

The file has three parts that matter: the conversation's metadata (title, timestamps), a mapping object holding every message as a node, and current_node — the id of the last message on screen. Trimmed to the essentials, it looks like this:

{
  "title": "My conversation",
  "create_time": 1754900000.0,
  "update_time": 1754910000.0,
  "mapping": {
    "<node-id>": {
      "id": "<node-id>",
      "message": {
        "author": { "role": "user" },
        "content": { "parts": ["The message text"] },
        "create_time": 1754900100.0
      },
      "parent": "<parent-node-id>",
      "children": ["<child-node-id>"]
    }
  },
  "current_node": "<last-node-id>"
}

Roles are user, assistant, system, and tool — the last two are internal messages ChatGPT never renders, which is why a raw dump has more nodes than your chat has bubbles. On the free tier the file also carries one trailing _generatedBy attribution key; the conversation data above it is untouched.

Why It's a Tree, Not a List

ChatGPT conversations branch: every prompt edit and every "regenerate" starts a new path, and the mapping keeps all of them as parent/child nodes. The thread you see on screen is one route through that tree. To reconstruct it, start at current_node and follow parent links to the root — that chain, reversed, is the visible conversation. Everything off that path is the history of edits and regenerations most exports silently throw away.

Method 2: ChatGPT's Built-in Export (conversations.json)

For your entire history in one file, use ChatGPT's native export:

It's the right tool for a full backup or a bulk analysis job. It's the wrong tool for "I need this one chat as a file right now" — the export is all-or-nothing and arrives by email, not instantly.

Comparison

Method	Scope	Speed	Output
Browser extension (.json)	Single chat	2 seconds	One pretty-printed file
Built-in export	All chats	Minutes (email)	ZIP with conversations.json

JSON vs Other Export Formats

JSON is for machines. If a person is going to read the file, export it in a readable format from the same right-click menu instead:

• Markdown — notes apps, repos, anything text-based with formatting
• Word (.docx) — the conversation still needs editing
• PDF — sharing and archiving as-is
• Text (.txt) — maximum compatibility, zero structure

For the full overview of every method, see the complete export guide. And if you're archiving many chats, the Chat Workspace can multi-select conversations and batch-export them — .json included.

Frequently Asked Questions