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 OPUS to M4A puts audio into the container Apple software actually files: a title, an artist, a cover and a track that syncs to a phone. The M4A holds AAC, which is the better codec for a second encode, and the whole conversion runs in your browser.
Up to 100 files at once. Mixed formats are fine.
They convert one after another and download together as a ZIP.
OPUS to M4A
Opus is a Xiph codec published in 2012 and Apple never adopted it for its media apps. Third-party players that bundle their own decoder handle it perfectly well, and a `.opus` file will play in several apps on an iPhone. What it will not do is behave like a library item: appear in the Music app with a cover, sync across devices, or show up where a song is expected.
M4A is the container Apple designed for exactly that role. It is MPEG-4 audio from 2004 holding AAC, decoded in hardware on every Apple device made in twenty years, with metadata atoms the whole ecosystem reads. Converting is not about playback in the narrow sense — it is about the file being recognised as a record rather than as a document that happens to make sound.
Any conversion out of Opus into a lossy format costs a second round of compression. What you can choose is which encoder pays for it, and AAC is the strongest option on the Apple side. It was standardised in 1997 as MP3's designed successor and does measurably more with the same bitrate — 128 kbps AAC is broadly comparable to 192 kbps MP3.
So converting Opus into M4A loses less than converting it into MP3 at the same file size, and it lands in the native container in one step rather than two. The exception is a destination that genuinely cannot read AAC, which on Apple hardware does not exist. Where a file has to play on a fifteen-year-old car stereo as well, MP3 is the pragmatic choice and this is not the page for it.
Opus is carried in an Ogg container that stores metadata as Vorbis comments — an open list of uppercase keys with text values. MPEG-4 stores it as atoms with fixed names. The mapping between them is well established, so title, artist, album, album artist, track and disc numbers, genre, date, comment and lyrics all cross over intact.
Artwork is the field people most expect to lose and it survives: a cover stored in the Ogg as a METADATA_BLOCK_PICTURE comment becomes a cover atom, which is what the Music app displays in a list and on a lock screen. Custom keys with no MPEG-4 equivalent are dropped rather than written as junk atoms, which is the right behaviour — an unreadable field is worse than an absent one.
Three sources account for most of them. Audio extracted from web video is very often Opus, because that is what the web's video containers carry. Voice notes and exported chat audio are Opus, because messaging apps standardised on it. And download tools frequently produce it by default, since it is the highest-quality stream available without re-encoding.
The origin matters for one decision. A file extracted from a stream at 128 kbps or better will convert to a 192 kbps M4A that nobody will fault. A voice note encoded at 24 kbps for a phone call is already at the bottom of what the codec does, and no band on this page improves it — High quality only avoids adding to the damage. Set expectations from the source, not from the setting.
The Quality control resolves to a real bitrate inside the encoder and AAC is offered a fixed set: Small file writes 96 kbps, Balanced 128, High quality 192. A four-minute track lands near 2.9 MB, 3.8 MB and 5.8 MB. There is no 256 or 320 option on this path.
For this pair the choice is nearly always High quality. You are re-encoding audio that has already been compressed once, and the only defence against the second pass being audible is to give the encoder enough room that it contributes almost nothing of its own. The size difference between 128 and 192 kbps is fifty percent on a file that is already small, and a library is not the place to economise on two megabytes.
Opus runs on a fixed 48,000 Hz clock and a decoder reports that rate regardless of what was encoded, so the AAC inherits 48 kHz whatever the audio originally was. A track that began life as a 44,100 Hz CD rip, went through a video, and came out as Opus does not return to 44.1 through this route.
Nothing on the Apple side minds. The Music app, iPhones, HomePods and CarPlay all handle 48 kHz normally, and no listener has ever identified a well-executed resample by ear. It is worth knowing only if something downstream compares technical rates — a library that reports a mixture of 44.1 and 48 kHz files is not broken, it is telling you which ones passed through a video or a voice codec.
Once the M4A exists, the remaining risk is something re-encoding it on the way in. Import settings in music software have historically been able to convert files during import, and a library set to "convert to 256 kbps AAC" will happily take your 192 kbps M4A and make a third-generation copy of it.
Check that setting before adding a batch. The file you converted is already in the library format and needs no further processing at all — adding it should be a copy, not an encode. The same warning applies to syncing with a "convert higher bitrate songs" option enabled, which is designed for lossless masters and does nothing useful to a file that is already at 192.
Files are capped at 100 MB each — for Opus that is several hours of speech and a long stretch of music — and a hundred can be dropped at once, coming back as a ZIP. That fits the shape of this job, since the reason anyone is here is usually a directory of accumulated files rather than a single one.
The batch is real processor time on your own machine rather than bandwidth, so it is worth starting and leaving. Nothing is queued behind anyone else and nothing is metered, because there is no server involved in the work at any point.
Opus decodes natively in every browser, because WebRTC made it mandatory, so nothing is fetched to read your files. Chrome, Edge and Safari also have an AAC encoder built in and use it directly; Firefox does not, so a WebAssembly AAC encoder comes down once on that browser and never on any other page.
The audio itself never crosses the network in either direction. For voice notes — which are frequently other people speaking, sent privately — that is worth more than the convenience, and it is checkable rather than promised: open the network tab, convert a file, and watch the encoder arrive while nothing goes back.
| OPUS | M4A | |
|---|---|---|
| Full name | Opus Audio | MPEG-4 Audio |
| File extension | .opus | .m4a |
| Media type | audio/opus | audio/mp4 |
| Compression | Lossy — file size is bought with quality | Lossy — file size is bought with quality |
| First published | 2012 | 2004 |
| Published by | Xiph.Org | Apple |
| Specification | RFC 6716 | — |
| Licensing | Open standard | Published, not standardised |
| Standing today | Current | Current |
| Audio channels | up to 255 | up to 48 |
| Opens in a browser | Current browsers | Every browser |
| Considered instead | AAC, MP3 | MP3, FLAC |
OPUS defines up to 255 audio channels and M4A up to 48. A surround mix is folded down rather than carried across.
M4A opens in every current browser. OPUS has narrower browser support than that. If the file is going onto a web page or into a form, that is usually the whole reason for the conversion.
M4A is a container rather than a single format. What actually plays is the codec inside it — usually AAC and ALAC — which is why two files with the same extension can behave differently on the same device.
VLC and FFmpeg read both OPUS and M4A, so there is a way to check the result against the original without a second tool.
The two are aimed at different work: OPUS at streaming and the web, M4A at handing a finished file over and phones. That is worth weighing before converting, because the reason one exists is usually the reason the other is awkward.
OPUS is Xiph.Org's format, published in 2012. The specification is RFC 6716, and it is worth reading if the file has to outlive the tool that wrote it.
M4A comes from Apple and dates from 2004. iTunes, VLC and FFmpeg all read it.
Apple never adopted Opus for its media apps. Some third-party apps bundle their own decoder and play it fine, but the Music app, the built-in previews and the sync path do not treat it as a library format. Converting to M4A gives you the container Apple designed, holding AAC, which every Apple device has decoded in hardware for twenty years.
For a second-generation encode, yes. M4A holds AAC, which was standardised in 1997 as MP3's designed successor and does meaningfully more with the same bitrate — 128 kbps AAC is broadly comparable to 192 kbps MP3. You also get the container Apple software files properly, with fields for artwork, album artist and track numbers that a bare MP3 tag handles less consistently.
Yes. Opus is carried in an Ogg container holding Vorbis comments, and those map into MPEG-4 metadata atoms: title, artist, album, album artist, track and disc numbers, genre, date and comment all cross over. Embedded artwork stored as a METADATA_BLOCK_PICTURE comment becomes a cover atom, which is what the Music app displays.
Some, unavoidably — Opus discarded detail and AAC discards more using different rules. At High quality, which writes 192 kbps, it is very hard to hear on anything this conversion is normally used for. Voice notes and podcasts are unaffected in practice. If the Opus was a low-bitrate download to begin with, no setting here improves it and 192 kbps only avoids making it worse.
48,000 Hz. Opus works on a fixed 48 kHz clock and reports that rate whatever it was encoded from, so the AAC inherits it. Nothing on Apple's side objects — the Music app, iPhones and CarPlay all handle 48 kHz normally — but a file that started as a 44,100 Hz recording will not come back to 44.1 through this route.
No. Opus decodes natively in every browser and Chrome, Edge and Safari have an AAC encoder built in; Firefox does not, so a WebAssembly encoder is fetched once there. Nothing carrying the audio crosses the network. Files are capped at 100 MB each and a hundred can be dropped at once, which suits a folder of downloads or voice notes.