You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Svwergio_mel edited this page Nov 12, 2026
·
1 revision
Export schema: sharegpt — 1
Id:sharegpt/1
ShareGPT-style text for distill / fine-tune pipelines. JSON/YAML center on conversations: [{ from, value }] where from is human or gpt. Markdown uses ### human / ### gpt headings with a <!-- schema: sharegpt/1 --> marker. HTML/PDF still render the message list and note the schema id in the header.
Example (JSON)
{
"schema": "sharegpt/1",
"platform": "chatgpt",
"title": "Bake-off notes",
"conversations": [
{ "from": "human", "value": "What is the capital of France?" },
{ "from": "gpt", "value": "Paris." }
]
}
When to pick
Fine-tune / ShareGPT tooling that expects from/value
Prefer chat-export/1 for archival parse fences
Choose in the UI
Popup → Advanced → Export schemas: set Default to sharegpt — 1, or only override JSON (or any format). Export bar formats unchanged.
MCP: chats_export(..., schema: "sharegpt/1"). Server default: settings.exportSchema in config.json.