Transcript export vs full backup: what is the difference?

The confusion is understandable, because both actions end the same way: you tap something in the app and a file lands somewhere you can save it. It is easy to assume that exporting a transcript here and there adds up to a backup over time, or that a full backup is just a bundle of the same exports you would have gotten one at a time. Neither is true, and the gap between them matters most at the exact moment you need one of them and only have the other.

What a transcript export actually contains

Exporting from a single recording gives you that recording's transcript, as either TXT or JSON, plus its title, date, time and location above the words. Choosing JSON adds duration, mood and tags as separate fields alongside the transcript text. Either way, it is one recording's worth of information, deliberately scoped to the recording you were looking at when you tapped export. Nothing about it references any other recording in the library.

The audio itself is not part of either export format — sharing the recording as sound is a separate option that hands over the original .m4a file, distinct from both text formats.

What a full backup actually contains

The full backup, found in Settings, is a single JSON file covering every recording in the library at once — its details and its transcript, for all of them, not just the one you had open. It is built for one purpose: restoring the app to the state it was in, whether that is on a new phone or after something on the current one went wrong. It is not meant to be opened and read the way a transcript export is; it is meant to be handed back to the app.

Why one does not stand in for the other

• Exporting transcripts one at a time, even for every recording in the library, still leaves out anything a transcript export leaves out — nothing beyond what that format already carries — and doing it recording by recording is a slow, manual way to approximate what the backup does in one file.
• A full backup is not a transcript reader. Opening the backup file directly gets you the same dense, bracket-heavy JSON structure a per-recording JSON export gets you, just for every recording stacked together, which makes it a poor substitute for exporting the one transcript you actually want to read or share right now.
• The backup does not include the audio files themselves — restoring from it brings back recording details and transcripts, not the original .m4a files, so it is not a way to keep copies of the recordings as sound either.

Picking the right one for what you are trying to protect

If the goal is sharing or reading one recording's words — sending a transcript to someone, pasting it into a document, keeping a readable copy of one interview — that is a transcript export, TXT or JSON depending on whether a person or a program is reading it next.

If the goal is not losing anything before getting a new phone, reinstalling the app, or just wanting a safety copy of the whole library at once, that is the full backup. It is the one action that covers every recording's details and transcript in a single file, which is exactly what restoring later needs.

The two are not mutually exclusive, and using one regularly does not make the other unnecessary. A transcript export you send to a colleague today does not help you three months from now when the question is whether last year's recordings are still safe; a backup sitting untouched in a folder does not help you right now when you just need to paste one transcript into an email.

How Voice Studio handles this

Exporting a transcript from any recording gives you TXT or JSON for that recording alone, plus a separate option to share the .m4a itself. The full backup in Settings is always one JSON file covering every recording's details and transcript at once, meant for restoring the whole library rather than for reading any single transcript — choosing TXT for your everyday exports does not change what the backup produces, since a backup is data to be restored, not prose to be read. Neither the recordings nor the backup file leave the phone on their own; there is no account and no CloudKit sync moving either one anywhere without you choosing to share or save it yourself.

Common questions

Does exporting every transcript in my library add up to the same thing as a full backup?

No. Even done for every recording, transcript exports still only carry what that format carries — no more just because there are more of them — and doing it one recording at a time is a slower, incomplete way to approximate what the single backup file does at once.

Does the full backup include the audio recordings themselves?

No. The backup covers every recording's details and transcript as JSON, not the original .m4a audio files. Keeping copies of the audio itself means sharing each recording separately.

Which one should I use before getting a new iPhone?

The full backup. It is the single file built to restore the whole library, details and transcripts included, rather than a per-recording export meant for reading or sharing one transcript at a time.

Is the full backup easy to read on its own, the way a transcript export is?

Not really. It is JSON covering every recording at once, which makes it dense and hard to read directly — it is built to be restored by the app, not read by a person the way a TXT transcript export is.