Does exporting a transcript delete it from the app on iPhone?

The worry makes sense even though the answer is simple. "Export" is a word that, on a computer, has sometimes meant move a file out of one place and into another, so it is a fair guess that exporting a transcript from a phone app might do the same — pull it out, leaving nothing behind. On iOS, for a voice recorder, that is not how it works, and it is worth knowing exactly why rather than just taking that on faith.

Export and share are copy operations, not move operations

When an app sends something through the iOS share sheet, or writes a file for you to save, it is reading its own stored data and handing a copy of it to whatever you pointed it at — Mail, Files, another app, AirDrop. The app’s own copy is not touched in that process, because sharing does not include a step where the app deletes what it just read. Nothing about the mechanism removes the source; the source was never part of the operation in the first place, only the thing being read from.

This holds regardless of which format leaves the phone. A plain-text share, a TXT file, a JSON file, or the audio itself as an .m4a — every one of them is a copy built at the moment you tap export or share, from whatever the app currently has stored. The original stays exactly where it was, unedited and undeleted, available the next time you open the recording.

Where the "does it move it" worry usually comes from

A few genuinely different behaviors get folded into one mental model of "exporting." Some desktop tools do offer an explicit move — take this file out of my library and put it there instead — and people who have used one of those occasionally expect every export button to work the same way. Photo apps sometimes distinguish "Share a copy" from "Move to," which is a real distinction worth having, but it also trains the instinct to double-check, which is a healthy instinct even when a given app only ever does the first of the two.

A voice recorder’s export and share actions are closer to hitting copy on a paragraph of text than to cutting a file from a folder. Nothing is ever moved out of the app’s own storage by tapping export; a copy is created wherever you sent it, and the original stays exactly where it was.

The direction that does matter: edits after export

The one place this can trip someone up is not deletion, it is timing. An exported file is a snapshot of the transcript as it read at the moment you exported it. If you go back into the app afterwards and fix a misheard name or a garbled sentence, that correction happens on the copy still living in the app — it does not reach back out and update a file you already sent somewhere. The two versions quietly drift apart the moment you edit one and not the other, and there is no notification telling you they no longer match. If a transcript is worth correcting, it is worth correcting before the export you actually intend to keep, or re-exporting afterwards so the two agree again.

What genuinely does remove something

The only action that removes a recording or its transcript from the app is an explicit delete on that entry — the kind of action with its own confirmation, not a side effect of some other button. Deleting the app entirely is a separate, larger version of the same thing: it takes everything with it, not just one recording. Neither of those is something export, share or backup do by accident.

The reverse direction is also worth knowing, since it is the other half of the same misunderstanding: once a transcript has been exported and sent somewhere — Files, Mail, a note — that copy is independent of the app from that point on. Deleting the original recording afterwards does not reach into your Files app or your inbox and remove what you already sent. The two copies separate the moment the export happens, in both directions: neither one affects the other from then on.

Why it is worth exporting more than once

Because export never subtracts anything, there is no cost to exporting the same recording more than once, or exporting early and often rather than waiting until you are certain you are finished with it. A transcript exported the day it was made, and again after you have cleaned it up, are simply two files — nothing was consumed making the first one that the second one had to compete for.

How Voice Studio handles this

Copying a transcript, sharing it as text, exporting it as TXT or JSON, sharing the .m4a, or running a full backup export are all read-only as far as the recording is concerned — every one of them reads what is currently stored and writes or sends a copy, and none of them touch or remove the original entry. The only way a recording or its transcript leaves the app is deleting that entry yourself, which is a separate, deliberate action from any of the export options sitting next to it.

Common questions

If I export a transcript as a file, does it disappear from the app?

No. Export reads the transcript that is already stored and writes a copy to wherever you send it. The original stays in the app exactly as it was.

If I delete a recording after exporting its transcript, does the exported file disappear too?

No. Once a file has been exported or shared, it is independent of the app. Deleting the original recording afterwards has no effect on a copy you already sent elsewhere.

Does running a full backup remove anything from the app?

No. A backup export reads every recording’s details and transcript and writes them into one file. Nothing is deleted from the app as part of that process.

If I edit a transcript after exporting it, does the file I already exported update too?

No. An exported file is a snapshot from the moment you exported it. Editing the transcript afterwards only changes the copy in the app — export again if you want a file that matches the corrected version.