Why is my voice memo not transcribing?

The most common causes, in order, are an iOS version below 18, a mismatch between the spoken language and the device language, audio that is too quiet for the recogniser to detect speech in, and an on-device language model that has not finished downloading.

Does Voice Memos transcribe on every iPhone?

No. Built-in transcripts arrived with iOS 18, so an iPhone on an earlier version will not show them regardless of model. It also depends on the language being one Apple supports for transcription on that device.

Why does my transcript come back empty or almost empty?

Usually the audio is far quieter than it sounds on playback — a phone in a pocket or bag, or a microphone covered by a case. Recognisers need detectable speech, and a recording that is audible to you can still be below the threshold.

Why is my transcript complete nonsense?

Because the spoken language does not match the device language. Transcription follows the language your iPhone is set to rather than detecting each recording, so speaking Turkish into an English-language phone produces English-looking words that mean nothing.

Can I force a voice memo to transcribe again?

Not directly, but closing and reopening the recording usually re-triggers it, and so does toggling airplane mode off if the transcript needs a network step. If nothing works, re-recording a short test clip tells you whether the problem is the device or that one file.

Voice Memo Not Transcribing? 8 Reasons, in Order

The short answer: Work down this list in order — iOS version, language mismatch, audio too quiet, model still downloading, recording too long, storage full, unsupported language, corrupted file. The first four account for the overwhelming majority of cases, and the quiet-audio one is the most commonly missed.

A recording that will not turn into text gives you almost nothing to work with: no error, no explanation, just a transcript that never appears or arrives blank. Here are the actual causes, ordered by how often each turns out to be it.

1. Your iOS version is below 18

Apple’s built-in Voice Memos transcription arrived with iOS 18. On anything earlier there is no transcript feature at all, regardless of how new the iPhone is.

Check Settings → General → About → Software Version. If it starts with 17 or lower, that is your answer, and the fix is either updating or using an app that does its own transcription.

2. The spoken language does not match the device language

This is the one that produces the strangest symptom: a transcript that is full of real words arranged into nonsense.

Transcription follows your device and Siri language. It does not detect the language of each recording. Speak Turkish into an English-language iPhone and the recogniser will do its honest best to hear English, producing a stream of plausible English words that mean nothing.

There is no per-recording language setting in Voice Memos. If you regularly record in a language other than your device language, this is a structural limitation rather than a bug to fix.

3. The audio is quieter than you think

The most-missed cause by a distance, because the recording sounds fine when you play it back with the phone at your ear.

Speech recognition needs a detectable speech signal, and several ordinary situations produce audio well below that threshold:

The phone was in a pocket or bag. Fabric attenuates far more than people expect.
A case or a finger covered the microphone. The mics are at the bottom edge and the top; both are easy to block.
The speaker was more than a metre or two away in a room with any reverberation.
The recording is mostly room tone with brief speech — the recogniser may return nothing rather than guess.

The tell: play the recording at normal volume without holding the phone to your ear. If you have to strain, so did the transcriber. Improving speech-to-text accuracy covers what to change before the next recording; nothing recovers a take that never captured usable speech.

4. The on-device model has not finished downloading

Transcription on recent iOS runs against a language model that downloads separately from the OS update. Until it lands, the feature is present but does nothing — and there is no progress indicator anywhere obvious.

It downloads over Wi-Fi, usually when the phone is charging and idle. If you have just updated iOS or just changed the device language, give it a night on the charger connected to Wi-Fi before concluding anything is broken.

5. The recording is very long

Long recordings are more likely to fail, time out, or come back partial. A three-hour lecture is a fundamentally harder job than a two-minute memo, and both the OS and third-party services have limits — sometimes stated, sometimes not.

If a long file will not transcribe, splitting it is the practical move. It also makes the result more usable: nobody reads a three-hour transcript in one piece. Related: how long an iPhone can record audio covers the recording-side limits, which are a different constraint from the transcription-side ones.

6. Storage is full or nearly full

Transcription writes a file. A device with almost no free space fails at that step, and the failure surfaces as a transcript that simply never appears.

Settings → General → iPhone Storage. Anything under a gigabyte free is worth clearing before you debug anything else.

7. The language is not supported at all

Distinct from cause 2. Apple supports a specific list of languages for transcription, and it is shorter than the list of languages iOS itself supports. If yours is not on it, the device language is set correctly and transcription still will not run.

A third-party app using a different speech engine may well cover a language Apple does not. This is one of the few cases where switching apps genuinely solves the problem rather than moving it.

8. The file itself is damaged

Rare, and worth checking last. A recording interrupted by a crash, a force-quit, or a battery death mid-write can be playable for the portion that reached disk and still unreadable to a transcriber.

The test: does it play all the way through? Does the duration shown match how long you actually recorded? A file that reports 47 minutes and stops at four is damaged, and no transcription will fix it. That failure mode — and how a recorder should be built so it cannot happen — is why iPhone recordings get lost.

Quick diagnostic

Record a thirty-second clip, speaking normally, phone on the desk in front of you, in your device language. Then:

Result	What it means
Transcribes fine	The device is healthy — the problem is specific to the original file (cause 3, 5 or 8)
Also fails	Device-level: iOS version, model download, storage, or unsupported language (1, 4, 6, 7)
Transcribes as nonsense	Language mismatch, confirmed (cause 2)

That one test splits the eight causes into two much smaller lists.

When you would rather it just worked

Most of these are limitations of the free built-in route rather than faults. Record and Transcribe (our app, for iPhone and Apple Watch) runs transcription as part of recording rather than as something you request afterwards, so there is no separate step to fail silently — a badge tells you when the transcript is ready, and every line carries a speaker label.

It does not repeal physics: audio that never captured clear speech will not transcribe well in any app, ours included. What it removes is the category of failure where you cannot tell whether anything is happening at all.

Three transcriptions free, no card needed. If you are weighing it against the built-in option, Voice Memos compared with our app is the honest side-by-side, and Just Press Record compared with ours covers the closest paid alternative if you have already ruled Apple’s out.