How to move voice memos from Android to iPhone

Switching phones usually feels close to automatic for the things Apple and Google both agreed to move: contacts, photos, messages on some paths. A folder of recordings made by whatever voice recorder app you were using on Android is a different case entirely, because that app chose its own way of storing them, and nothing on either platform promises to carry a third-party app’s private files across a change of phone, let alone a change of operating system.

Why nothing moves on its own

Every app on a phone, Android or iPhone, keeps its files in storage that belongs to that app and is not generally reachable by anything else. A phone-to-phone migration tool works by moving the categories of data both platforms agreed to standardise — contacts, calendar entries, photos in the camera roll — not by reaching into every app’s private folder and guessing what matters. A voice recorder’s library was never on that list, on either side. The recordings are still sitting exactly where the old app put them; the new phone simply has no route to them unless you make one yourself.

This is not specific to moving between operating systems, either. Switching recorder apps on the same iPhone runs into the identical wall, because iOS keeps every app’s storage sealed off from every other app’s as a matter of course. Android-to-iPhone is the same problem with an extra step, not a different one.

The two things that decide whether this goes smoothly

Getting the files off the Android phone at all

The recordings have to leave the old app’s storage before anything else can happen. The reliable routes are the ones that do not depend on the two platforms talking to each other directly: connect the Android phone to a computer over a cable and copy the files out the way you would copy any other files, or upload them from the Android phone to a cloud drive — the same one already handling your photos or documents is fine — and download them again on the iPhone once they are there. Either way, the point of the step is the same: turn "files inside an app" into "files sitting somewhere you can reach from the other phone", which is the part no migration tool does for you here.

Whether the format will actually open once they arrive

This is the part worth checking before you assume everything will just work. Some Android recorder apps save in .m4a with AAC inside, the same combination an iPhone itself records — that opens everywhere without a second thought. Others use formats that were more common on older or budget Android hardware: .amr, .3gp, or audio wrapped in a container that is not as widely supported outside Android’s own media stack, such as Opus inside .ogg. Widely used formats like .m4a, .mp3 and .wav play on essentially anything, iPhone included. The narrower, older ones sometimes do not open cleanly without converting them first, on the Android side or with a general-purpose desktop tool, before you move them across. Checking what your old app actually saved — often visible from the file extension once you can see the files on a computer — takes a moment and saves a wasted transfer.

What actually survives the move, and what does not

The audio itself survives cleanly if the format is a common one: moving a file copies the exact bytes that were recorded, nothing is re-encoded, and what plays back on the new phone is identical to what was captured on the old one.

A transcript, if your old app generated one, is a different story. Text a recorder produced is data that app kept in its own library, tied to that recording inside that app — it is not baked into the audio file itself, so copying the .m4a, .mp3 or whatever the file turns out to be does not bring the words with it. If a transcript from the old app matters to you, export or copy that text separately, as its own file or even pasted into a note, before you move on from the old phone. Otherwise, the audio arrives on the iPhone with no transcript attached, and whatever transcribes it next starts from the recording, not from anyone else’s old text.

Anything the old app layered on top for its own organizing — folders, labels, favourites, whatever it called them — belongs to that app’s way of keeping a library and has nowhere to go either. None of that is specific to Android; it is the same limit any app-to-app move runs into, just crossing a bigger gap this time.

Getting the files into a recorder on the new iPhone

Once the audio files are somewhere the iPhone can reach — downloaded from a cloud drive into the Files app, or copied over by cable through a computer — an app that supports importing an existing audio file can pick them up from there the same way it would treat something recorded natively. Voice Studio does this: point it at a file already in the Files app, and it comes into the library ready to play, mark and transcribe, without needing to have been recorded in the app itself.

From there, transcribing an imported recording works the same as transcribing a fresh one. iOS attempts the on-device speech model first; if that pass comes back empty or errors, it retries with on-device recognition turned off, which sends the audio to Apple’s server for that one attempt when you are online. That is true of anything transcribed on the phone, imported or not, and it is worth knowing plainly rather than assuming an imported file is somehow more private than one recorded natively — the same rule applies either way.

How Voice Studio fits into this

Voice Studio can import an existing audio file straight from the Files app, so a recording that made the trip from an Android phone — by cable or by cloud drive — lands in its library and can be played, marked and transcribed exactly like anything recorded on the iPhone itself. There is no account to set up first, and nothing about the import depends on where the file originally came from. Requires iOS 16.4 or later, the same as everything else in the app. Once it is in, the usual export options apply going forward: the transcript as TXT or JSON per recording, the audio as its original .m4a, or every recording and transcript together in one full backup file, so the next move — whenever it happens — is a manual export rather than a repeat of this one.

Common questions

Will my old Android voice recordings just show up on my new iPhone?

No. There is no automatic transfer for a third-party recorder app’s files, on either platform. You need to move the audio files off the Android phone yourself — by cable or a cloud drive — and then import them into a recorder app on the iPhone.

Do I need to convert the files before moving them?

Depends on the format. Common ones like .m4a, .mp3 and .wav play and import without conversion. Older or less common formats some Android recorder apps use, such as .amr or .3gp, sometimes need converting first — worth checking the file extension before you move a large batch across.

Will the transcripts from my old Android app come across too?

No, not automatically. A transcript is text the old app generated and stored in its own library, separate from the audio file. Export or copy that text yourself before switching if you want to keep it; otherwise the new app transcribes the imported audio fresh.

Does Voice Studio need an account to import recordings from another phone?

No. Voice Studio has no account and no server of its own. Importing an audio file from the Files app works the same whether that file was recorded on the iPhone or arrived from somewhere else, including an old Android phone.