Turn a ChatGPT chat into an Excel workbook.
A CSV opened in Excel is not a file, it is an import dialogue: pick an encoding, pick a delimiter, hope the quoting survived. Extry writes a real .xlsx instead — the file opens, and that is the end of it.
- retry-backoff-design.xlsx28.4 KBexcel
Why not just CSV
Because every answer has a line break in it
A message that runs to several lines is exactly what breaks a CSV in Excel. It arrives either as one unreadable line or as several rows pretending to be separate messages, and the byte-order mark we write helps with the alphabet and with nothing else.
The workbook has no such problem: a cell holds the whole answer, the text wraps, and the row keeps its height.
What is in it
Two sheets, and the second one is the point
The first sheet is the conversation: one row per message, with the same six columns the CSV has — index, role, author, model, created at, text — only here the headings are in your language and the header row stays put while you scroll.
The second sheet holds what usually gets crammed into a comment nobody opens: when the conversation was created and exported, which models wrote it, and the link back to it. Field and value, nothing else.
What makes it usable
The parts a converter usually skips
A file that is merely valid is not the same as one you can work in.
A frozen header
The heading row stays where it is through a hundred messages, so column four is still the model on screen nine.
Wrapped text, real widths
Columns are sized for what is in them and long answers wrap inside the cell instead of running under the next one.
Honest limits
Excel holds 32 767 characters in a cell. An answer longer than that is cut with a note saying so — a spreadsheet that lies about the text is worse than one that admits where it stopped.
How it works
Three steps, one workbook
- Open the conversation in ChatGPT and click the Extry button on the page.
- Pick Excel in the panel.
- Press Download and open the .xlsx from the archive.
No account, no upload step. The workbook is built in the page, so the conversation is not sent to a converter.
Processing
Where each part runs
| What | Where it happens |
|---|---|
| Export to every format | In your browser |
| Attachments and images | In your browser |
| Conversation content | Not sent anywhere |
| Usage statistics | Not collected |
| Typeset PDF (later, opt-in) | On a server, file deleted right after |
Questions
About the Excel export
Is it a real .xlsx or a renamed CSV?
A real one. It is the same kind of package as a .docx — a ZIP of XML — written by the same code, and another implementation of the format reads it back with the sheets, the freeze, the widths and the wrapping intact.
Which columns are there?
Six: index, role, author, model, created at, and text. The same set the CSV export writes, with the headings translated.
What happens to a very long answer?
It is cut at Excel’s own limit of 32 767 characters, with a note in the cell saying where it stopped. Nothing is truncated silently.
Do I still need the CSV?
Only if something downstream wants CSV specifically. For opening in a spreadsheet, the workbook is the one that opens without a dialogue.
More
Other shapes for the same chat
The same conversation, written differently: CSV, Word, JSON, the main page.