How to turn a JSON transcript export into a spreadsheet on iPhone

This comes up once someone has more than a couple of transcripts and starts wanting to do something a document cannot: sort by date, filter to a tag, see which recording ran longest, scan a column of titles instead of scrolling a page of paragraphs. A spreadsheet is the right tool for that. A transcript export, on its own, is not one yet.

Why a spreadsheet app can’t just open the file

Open a .json file in Numbers, Excel or Google Sheets and, at best, it lands as a single cell of raw text — braces, quotes and all — because none of them read JSON as their native format. Spreadsheets are built around a flat grid: a fixed set of columns, one row per item. JSON is built around labeled fields nested inside an object, which is a different shape even when the underlying information is simple. The two formats can hold the same facts and still not be interchangeable, the same way a paragraph and a table can both describe the same three numbers without one being usable as the other without some work in between.

Why this particular JSON happens to be an easy case

Not every JSON file converts cleanly to a spreadsheet — deeply nested data, with lists inside lists, does not flatten without decisions about what to do with it. A transcript export is a friendlier shape than that. A full backup, for instance, is a list of recordings, and each recording has the same handful of fields sitting at the same level: a title, a date, a duration, a transcript, and whatever tags or mood you attached. That is already close to a table in spirit — each recording is a row waiting to happen, and each field is a column waiting to happen. What is missing is not structure, it is the mechanical step of laying it out that way, which nothing in a text viewer does for you.

The three routes that actually work

A handful of recordings: just type them in

For five or ten recordings, opening the JSON as text, reading off the title, date and duration for each one, and typing them into a spreadsheet by hand is genuinely the fastest option. It feels unsophisticated next to converting a file automatically, but building a conversion process costs more time than a few minutes of typing does, and that trade only flips once the number of recordings gets large enough to matter.

A larger batch, on a computer

Once typing stops being reasonable, a JSON-to-CSV conversion is the standard move, and CSV is a format every spreadsheet app opens natively as a table, no import wizard required. A code or scripting environment does this in a few lines because the file is already structured; a general-purpose "convert JSON to CSV" tool does the same thing without writing anything, for anyone who would rather not. The file goes in already organised as a list of similar objects, which is exactly the input those tools expect — this is not a case of forcing an awkward format into a table, it is closer to relabelling one.

Staying on the phone, with Shortcuts

iOS ships a general-purpose automation app, Shortcuts, that can open a file, parse it as a dictionary, step through a list of entries one at a time, and build a line of text per entry — enough to turn a list of recordings into a CSV-style file without leaving the phone or installing anything else. It takes some setup the first time and is worth it only if this is something you expect to do more than once; for a one-off job, the computer route above is faster to reach for.

The one thing worth being careful with

Plenty of free JSON-to-CSV and JSON-viewer tools run entirely in a browser tab you paste a file into, and a good number of them upload what you paste to a server to do the conversion. A transcript can contain anything you said, so treat those the way you would treat pasting the transcript itself into a stranger’s website — fine for something you would not mind existing on someone else’s server, not fine for anything you would not. A conversion that runs locally, in a code editor or in Shortcuts on your own phone, never has that question to answer.

What gets flattened out along the way

A spreadsheet row wants one value per cell, and a transcript is a paragraph, sometimes a long one. Converting to rows and columns usually means the whole transcript lands in a single cell rather than being split into anything more granular — there is no timestamp data in a transcript export to split it by in the first place, so a spreadsheet built this way is good for sorting and filtering by the short fields — date, duration, tags — and for scanning titles, but reading the transcript itself is still more comfortable back in a document. Use the spreadsheet to find the recording you want, then go to the transcript to actually read it.

When TXT was the format you actually wanted

If the goal was ever "read one transcript comfortably," none of the above was necessary — plain text does that natively with nothing to convert. The spreadsheet route only earns its keep once the point is comparing or filtering across several recordings at once, which a paragraph of prose is genuinely bad at and a table is genuinely good at. Picking between TXT and JSON when you export is picking between those two jobs, not between a better option and a worse one.

How Voice Studio handles it

Voice Studio’s JSON export — per recording or as a full backup covering everything at once — keeps title, date, duration, tags, mood and transcript as separate fields rather than folding them into a paragraph, which is exactly the shape a spreadsheet conversion needs and exactly why JSON, not TXT, is the export to reach for when a spreadsheet is the eventual goal. Turning that file into rows and columns still happens outside the app, the same way it would with any recorder’s export, because building and maintaining a spreadsheet importer is a different job from recording and transcribing, and the free app already covers that without limits or a Pro gate on the export itself.

Common questions

Can I open a JSON transcript export directly in Numbers or Excel?

Not as a table. It opens, if anything, as one cell of raw text, because spreadsheet apps read rows and columns, not nested JSON fields. Converting to CSV first is what makes it open as an actual table.

Do I need to convert every recording separately?

No — a full backup export already lists every recording in one file, each with the same fields, so a single conversion turns the whole set into one spreadsheet rather than needing one file per recording.

Will the transcript text be searchable in the spreadsheet, or does it stay as one block?

It stays as one block per recording, in a single cell, since there is no timestamp or sentence-level structure in the export to split it by. The spreadsheet is best used for sorting and filtering the shorter fields — date, duration, tags — and then opening the transcript separately to read it.

Is it safe to paste an exported transcript into an online JSON-to-CSV converter?

Only if you would not mind that content sitting on someone else’s server — many of those tools convert by uploading what you paste. A conversion that runs locally, such as through the Shortcuts app on the phone itself, avoids that question entirely.