Cookies for analytics and advertising
We use cookies for analytics and advertising, both sent to Google. Refusing changes nothing you can see.Read the privacy page
Converting M4A to OPUS is the shortest route from a long spoken recording to a file small enough to send. An hour of iPhone Voice Memo lands near 17 MB at the smallest band and stays completely intelligible, because Opus was designed for voice. Nothing is uploaded to do it.
Up to 100 files at once. Mixed formats are fine.
They convert one after another and download together as a ZIP.
M4A to OPUS
M4A is Apple's audio container from 2004 and it turns up in two very different roles. One is a music file from a store or a library. The other, far more common on a phone, is a recording: a Voice Memo, a lecture captured on a desk, a meeting exported from Teams or Zoom, an interview, a call. Those are long, spoken and frequently mono.
That distinction decides everything on this page. Music at 38 kbps is a compromise; speech at 38 kbps is what messaging apps have sent for a decade and nobody complains. If your M4A is an album track, the Opus band should be High quality and the page you probably want is the one about fitting a library on a phone. If it is forty minutes of somebody talking, read on — the numbers are dramatic.
An iPhone Voice Memo recorded in its default quality is around 64 kbps of mono AAC, which is roughly 28 MB an hour. A lecture captured at a higher setting, or in stereo, can be two or three times that. Email attachment limits are commonly 25 MB, and a good many upload forms stop at 20.
Opus at the Small file band writes 38 kbps, putting an hour near 17 MB; Balanced writes 64 kbps for about 29 MB; High quality writes 128 kbps for about 58. So the low band alone is usually the difference between an attachment that sends and one that bounces, and a three-hour recording that was 84 MB becomes about 51 MB without becoming harder to follow.
Opus was standardised as RFC 6716 in 2012 out of two codecs designed for different jobs — one for speech, one for music — and it switches between their techniques according to what it hears, without being told. That is why it holds together at bitrates where MP3 produces a warbling mess and AAC starts to smear.
The practical comparison for this pair: Opus at 38 kbps is roughly what MP3 needs 96 kbps to match on spoken material, and messaging apps run voice notes at 16 to 32 kbps on the same codec. Nothing else offered on this site is close for speech. The trade is compatibility, which the section below deals with honestly rather than in a footnote.
A recording of one person talking into a phone carries almost identical information in both channels, and storing it twice is a straight waste of the bitrate budget. Converting to mono roughly halves the file again on top of everything above, with no perceptible effect on a lecture, an interview or a meeting.
There is no channel control on this page, so a stereo M4A produces a stereo Opus. Where a recording is genuinely single-source, the sequence that pays is to sum it to mono in a free editor first and convert afterwards. Where a recording has two people at opposite ends of a table on separate microphones, leave it alone — the separation is the thing that makes a transcript attributable.
Every current browser decodes Opus, Android has for years, VLC and the desktop players all read it, and most transcription tooling accepts it because it passes the file to a decoder rather than to a list of extensions. That covers the majority of destinations for a converted recording.
What does not: older upload forms with a fixed allow-list, some legal and medical intake systems, car head units, and the built-in preview on iOS in certain situations. When a file is refused for looking wrong rather than being wrong, renaming it to .ogg occasionally helps, since the same stream is legal under either extension. When the receiving system genuinely has no Opus decoder, this was the wrong conversion and MP3 is the file it wants.
The M4A holds AAC and the AAC already threw away what its model of hearing said would not be missed. Opus now discards a second helping using different rules, and spends part of its budget describing the first encoder's artefacts rather than the recording. That is the unavoidable cost of any lossy-to-lossy conversion and there is no setting that removes it.
On speech it is close to unmeasurable in practice. Consonants and sibilance are what degrade first, and at 38 kbps Opus they survive well enough that automatic transcription accuracy is not meaningfully affected. On music, applause, or a recording with music underneath narration, the low band starts to sound like a phone call — take High quality there, or keep the M4A.
Opus runs on a fixed 48,000 Hz clock and a decoder reports that rate regardless of what the encoder was handed. Phone recordings are usually 44,100 or 48,000 Hz already, so in most cases nothing visible happens; a 16,000 Hz voice recording will nonetheless present as 48 kHz afterwards.
For listening this changes nothing. It matters in one place: a speech pipeline that expects a specific input rate, or a tool that reads the technical rate out of the file and logs it, will see 48 kHz rather than the original figure. Anything that resamples internally — which is nearly all current transcription tooling — is unaffected, but a pipeline built around a fixed rate should be told.
The registry lists two codecs for M4A: AAC and Apple Lossless. Recordings and purchases are AAC; a CD ripped in iTunes with the lossless setting is ALAC, and ALAC cannot be decoded on this path at all. Such a file stops with a message saying nothing in it could be converted, rather than producing something broken.
Size tells you which you have before you start. Four minutes of AAC is three to five megabytes; four minutes of Apple Lossless is twenty to thirty. If it is ALAC and the goal is a small file, the sensible route is to re-export from the source rather than through a converter that cannot open it — and if the goal was archival, ALAC was already doing that job.
A large share of the recordings this page exists for contain other people: a lecturer, an interviewee, colleagues in a meeting, a patient, a source. Those people agreed to be recorded by you, not to have a copy pass through a conversion service that keeps files for an hour and says so in a footer.
Nothing here goes anywhere. The AAC is decoded by your own device, and Opus is the one audio target that needs no encoder download, so the entire operation happens in the tab with the network idle. Files are capped at 100 MB each — comfortably over three hours of a typical Voice Memo — and a hundred can be dropped at once and taken back as a ZIP.
| M4A | OPUS | |
|---|---|---|
| Full name | MPEG-4 Audio | Opus Audio |
| File extension | .m4a | .opus |
| Media type | audio/mp4 | audio/opus |
| Compression | Lossy — file size is bought with quality | Lossy — file size is bought with quality |
| First published | 2004 | 2012 |
| Published by | Apple | Xiph.Org |
| Specification | — | RFC 6716 |
| Licensing | Published, not standardised | Open standard |
| Standing today | Current | Current |
| Audio channels | up to 48 | up to 255 |
| Opens in a browser | Every browser | Current browsers |
| Considered instead | MP3, FLAC | AAC, MP3 |
Current browsers read OPUS; older ones do not. It is the less portable of the two, so it is worth being sure the program at the other end accepts it before sending one.
VLC and FFmpeg read both M4A and OPUS, so there is a way to check the result against the original without a second tool.
The two are aimed at different work: M4A at handing a finished file over and phones, OPUS at streaming and the web. That is worth weighing before converting, because the reason one exists is usually the reason the other is awkward.
OPUS comes from Xiph.Org and dates from 2012, specified as RFC 6716. VLC, FFmpeg and Audacity all read it.
A one-hour M4A recorded by an iPhone at around 64 kbps mono is roughly 28 MB. At the Small file band, which writes 38 kbps Opus, the same hour lands near 17 MB; converted to mono in an editor first it goes further still. The saving is largest on long recordings, which is exactly where an upload limit tends to bite.
Yes. Opus was designed for real-time voice and is the codec messaging apps use for voice notes at 16 to 32 kbps. At 38 kbps a lecture, an interview or a meeting recording is completely intelligible, and the second encode is not what limits it — room noise and microphone placement in the original recording almost always matter more.
Yes. The M4A holds AAC, which already discarded detail permanently, and Opus discards a further helping using different rules. On speech that is close to undetectable at any of the three bands. On music it is audible at the low band, so pick High quality — 128 kbps — if the recording contains anything you would call a performance.
Most modern ones do, because they hand the file to a decoder that reads it. Some older pipelines and some upload forms accept a fixed list of extensions and reject .opus without looking inside. If yours does, the honest answer is that Opus was the wrong intermediate step and a WAV or an MP3 is what that tool wants — check before converting a semester of lectures.
The tag fields do. Ogg stores metadata as Vorbis-style comments, so title, artist, album, date and comment map across from the MP4 atoms. What does not survive is anything Apple-specific with no equivalent — purchase records, custom atoms, and the location data some recorders attach. A Voice Memo named in the app keeps its name; a file whose only identity was its filename keeps that too.
No, and for this material that is the point. Interviews, meetings and lectures are frequently other people speaking without having agreed to a third party holding a copy. The AAC is decoded by your own device and Opus needs no encoder download at all, so nothing carrying the audio crosses the network — which you can confirm in the network tab while a conversion runs.