SnipAudioCut audio

How do you convert an iPhone voice memo to MP3, and which bitrate should you pick?

Published 2026-10-22 · by patrick-eu

Short answer: export the memo from Voice Memos as a .m4a file (Rendered, not Editable), open it in the M4A to MP3 converter, pick MP3 at 192 kbps, or 256 kbps if you want nothing measurable lost, and press Download. A one-minute memo took about 3 s on our test machine.

We did not have a real Voice Memos recording to test with; everything below was done on mono AAC and ALAC files we made ourselves. Where we don't know what an iPhone writes, we say so.

What a voice memo file is

Apple's iPhone User Guide for iOS 27 says that recordings are exported from Voice Memos in .m4a format by default, "so layered recordings are flattened and Spatial Audio becomes stereo" (Export a Voice Memos recording to Files on iPhone, read 2026-10-22). The same page says you can instead tap Options and choose Editable to export "a file where the effects and layers can be adjusted later (QuickTime Audio format)". The sharing page describes the same two choices: Rendered, "a single .m4a file with all audio effects and layers mixed in", and Editable (Share a recording in Voice Memos on iPhone, read 2026-10-22). For conversion you want the Rendered .m4a; we had no Editable file and don't know whether a browser can decode one.

An .m4a is an MP4 container, and the sound inside is usually AAC. Apple's Voice Memos app also has an Audio Quality setting with two choices: "Compressed (for lower-quality, smaller files) or Lossless (for high-quality, larger files)" (Change Voice Memos settings on Mac, Voice Memos User Guide, read 2026-10-22). The iPhone guide pages we read do not describe this setting, and none of Apple's pages we found name the codec, bitrate or sample rate of either choice. So we don't know what bitrate a Compressed memo is recorded at, and we tested a range of them instead. Lossless on an Apple device means ALAC (Apple Lossless), which is the case the converter cannot open.

How we tested

Which bitrate to pick

Same 64 kbps mono stand-in, every setting the converter offers. The stand-in itself scored 30.4 dB against the original speech, so no MP3 can beat that.

SettingScore vs original speechScore vs the memo it came fromSize for 1:00Times the 64 kbps memoTime
MP3 128 kbps24.2 dB25.8 dB0.92 MB1.653.3 s
MP3 160 kbps24.3 dB25.9 dB1.14 MB2.063.1 s
MP3 192 kbps27.0 dB30.4 dB1.37 MB2.473.3 s
MP3 256 kbps30.4 dB61.4 dB1.83 MB3.303.7 s
MP3 320 kbps30.4 dB66.2 dB2.29 MB4.123.3 s
WAV 16-bit30.4 dB72.5 dB5.05 MB9.090.5 s
Measured by snipaudio.com, 2026-10-22, Chromium 153. Input: 60 s mono AAC, 582,178 bytes. 1 MB = 1,048,576 bytes. Time = from pressing Convert to the row saying done, one run each.

At 128 and 160 kbps the converter's encoder changed the waveform about as much as the AAC recording had (25.8 dB against the decoded memo). At 256 kbps that drops to 61.4 dB, far below anything the memo itself had lost, and the score against the original speech is back to the memo's own 30.4 dB. 192 kbps is the middle: 3.4 dB under the memo at 1.37 MB a minute. The encoding time did not depend on the bitrate; a WAV needs no encoder and took half a second.

The MP3 came out 60.029 s long instead of 60.000 s, and the speech starts 1,105 samples (25.1 ms) later than in the memo, because the MP3 encoder pads the start and end to whole frames. A WAV keeps the exact length and timing. The converter's encoder is mono-aware: a mono memo gives a mono MP3, but a mono MP3 at 128 kbps is the same 960,470 bytes as the stereo one, so mono does not make the file smaller.

Low-bitrate memos: the MP3 can't be better than the recording

Every stand-in converted at the smallest MP3 setting, 128 kbps. The second column is the recording before conversion.

Stand-in memo (mono AAC)Actual bitrateMemo size for 1:00Memo scoreMP3 128 kbps scoreMP3 size for 1:00
32 kbps38.7 kbps0.29 MB16.9 dB16.3 dB0.92 MB (3.19 times)
48 kbps57.5 kbps0.42 MB24.6 dB21.8 dB0.92 MB (2.17 times)
64 kbps76.1 kbps0.56 MB30.4 dB24.2 dB0.92 MB (1.65 times)
96 kbps107.4 kbps0.78 MB38.7 dB25.4 dB0.92 MB (1.18 times)
128 kbps135.4 kbps0.98 MB45.5 dB25.6 dB0.92 MB (0.94 times)
Measured by snipaudio.com, 2026-10-22. Scores are signal-to-error against the original speech. All five MP3s were 960,470 bytes: the encoder runs at a constant bitrate, so the input bitrate changes nothing about the output size.

A 32 kbps recording converted at 128 kbps is three times the size and no better than it was: 16.3 dB against 16.9 dB. The MP3 setting puts a ceiling of about 25 dB on this speech at 128 kbps, whatever went in; a recording below that ceiling keeps its own score, one above it is pulled down to the ceiling. If you need the file small, keep the .m4a; if a player insists on MP3, the extra bytes buy nothing you can measure.

Lossless memos, 48 kHz, quiet recordings and trimming

Long memos: an hour-long lecture

Mono files take half the memory of stereo, so a memo can be longer than a song before the browser gives up. We looped the speech into 30, 60, 90 and 120 minute mono AAC files at 64 kbps.

MemoSettingResultTimePeak Chromium memoryOutput
30:00 (16.4 MB)MP3 128 kbpsdone85.3 s (2.84 s per minute)1,403 MB27.47 MB, 30:00.046
60:00 (33.0 MB)MP3 128 kbpsdone166.3 s (2.77 s per minute)2,400 MB54.93 MB, 60:00.039
60:00 (33.0 MB)WAV 16-bitdone14.1 s2,398 MB302.81 MB, 60:00.000
90:00 (49.4 MB)MP3 128 kbpsdone248.8 s (2.76 s per minute)3,304 MB82.40 MB, 90:00.033
120:00 (65.9 MB)MP3 128 kbps"Your browser couldn't decode this file." after 15.7 s15.7 s3,098 MBnone
Measured by snipaudio.com, 2026-10-22, Chromium 153 on a 4-core server with 3,541 to 3,726 MB free before each job. Mono AAC at 44.1 kHz, 64 kbps nominal. One run each; a phone will be slower and has less memory.

Up to 90 minutes converted, and the time grew in step with the length: about 2.8 s per minute of speech on this machine, so an hour of lecture is a three-minute wait, and the tab needs about 2.4 GB of memory for it. The 120-minute file was refused with the same message as the ALAC files, after 15.7 s and without the tab crashing; the kernel log shows no process killed, so this was not the machine running out of memory. It matches what we found for the cutter, which rejects mono 44.1 kHz files between 101 and 102 minutes long: see how long a file an online MP3 cutter can open. For a memo longer than that, split it first on a computer (ffmpeg -i memo.m4a -c copy -f segment -segment_time 3600 part%d.m4a) and convert the parts. The page shows "long file: converting can take several minutes, and very long files can run out of memory" next to any file over 30 minutes.

Step by step

  1. In Voice Memos, tap the recording, tap the More button, then Share. Under Options keep Rendered. Choose Save to Files and pick a folder (Apple's export page, linked above).
  2. Open the M4A to MP3 converter in a browser, choose the .m4a from Files (or from wherever you copied it on a computer).
  3. Set MP3, 192 or 256 kbps, 44.1 kHz. Leave Volume at 100% unless the recording is quiet. Type start and end times if you only need part of it.
  4. Press Convert, wait for the row to say done, press Download. The memo itself is not changed; the MP3 is a new file.

If you have several memos, pick them all at once; they convert one after another. To join them into one file first, see how to merge voice memos and MP3 files.

Questions

Does converting a voice memo to MP3 lose quality?

Some, always, because the AAC is decoded and encoded again. How much depends on the bitrate you pick: in our test 128 kbps lost 6.2 dB from a 64 kbps memo, 192 kbps lost 3.4 dB, and 256 kbps lost nothing measurable (0.0 dB). It cannot gain anything: no MP3 scored above the memo it came from.

Why is my MP3 bigger than the voice memo?

Because the smallest MP3 setting is 128 kbps and MP3 has no mono discount, while a Compressed memo is a low-bitrate mono AAC. Our 64 kbps stand-in grew 1.65 times at 128 kbps and 3.30 times at 256 kbps.

Can I convert on the iPhone itself?

The converter is a web page, so it should run in Safari once the .m4a is in Files, but we tested in Chromium on a server, not on an iPhone or in Safari, so we can't say how long a memo an iPhone's memory will take.

Continue with the next audio task