Convert OGG to M4A

This is not a bug or a missing codec pack you can install. Ogg was released by Xiph.Org in 2000 with Vorbis alongside it, explicitly as a patent-free alternative at a time when MP3 licensing cost money, and the container was documented as RFC 3533 in May 2003. The open-source world adopted both immediately. Apple did not: Safari 18.4 added playback of Ogg carrying Vorbis or Opus, and that is where the support stops.

So an `.ogg` file on an iPhone is inert outside the browser. It will sit in the Files app, it will not import into Music, it cannot be dropped into iMovie or Keynote, and AirDropping it achieves nothing. The registry records Ogg's browser support as patchy and that is the polite version. Converting is not a workaround; it is the only path that does not involve installing a third-party player on every device that needs to hear the file.

M4A is Apple's name for an MP4 file holding a single audio track, in use since 2004, and it is what every Apple audio path expects. The MP4 header states the exact duration, indexes where every sample begins so seeking is instant, records the channel layout and sample rate, and provides a metadata block for the title, artist, album and cover image.

That is why an M4A behaves so much better on an Apple device than any other option. It imports into Music, syncs to a phone, plays in the Files app, drops into iMovie, Keynote and GarageBand, and shows its artwork everywhere. None of it is magic — it is the same container structure MP4 video uses, and Apple built its whole media stack around it.

This conversion decodes lossy audio and compresses it again, which always costs something: the second encoder does not know which parts of the signal are original and which are artefacts of the first pass, so it spends bits on both. That is unavoidable and it is worth pricing rather than hiding.

What you can control is which codec pays for it. AAC was standardised in 1997 as MP3's designed successor and does meaningfully more with the same bitrate — a 128 kbps AAC is broadly comparable to a 192 kbps MP3. Converting Vorbis into AAC therefore loses less than converting it into MP3 at the same file size. If the destination is Apple, you get the better codec and the native container in one step, which is the whole argument for this pair over the MP3 one.

Ogg carries three codecs according to the registry — Vorbis, Opus and FLAC — and the extension does not tell you which. Vorbis is what game asset folders and older Linux exports hold. Opus turns up in newer material and browser recordings. FLAC inside Ogg is uncommon and appears in archival and reference material.

The difference matters for one decision. From Vorbis or Opus, this is a second lossy pass and Balanced at 128 kbps is defensible. From FLAC, it is the first compression the recording has ever had, and High quality at 192 kbps is the only sensible choice — you would be economising on a master. Size gives it away before you open anything: four minutes of FLAC-in-Ogg is twenty to thirty megabytes against three to five for Vorbis.

AAC is offered a fixed set of bitrates here: Small file writes 96 kbps, Balanced writes 128 and High quality writes 192. A four-minute track lands near 2.9 MB, 3.8 MB and 5.8 MB respectively, which is comfortably smaller than the equivalent MP3 at similar perceived quality.

For narration, game voice lines, lecture audio or a Wikimedia pronunciation clip, Small file is genuinely sufficient. For music, Balanced. For anything that started as FLAC-in-Ogg, or that will be edited after conversion, High quality — 192 kbps recovers nothing but leaves the encoder enough room that it contributes almost nothing of its own to the damage.

Ogg stores tags as Vorbis-style comments: an open list of uppercase key-value pairs — TITLE, ARTIST, ALBUM, ALBUMARTIST, TRACKNUMBER, TRACKTOTAL, DISCNUMBER, GENRE, DATE, COMMENT, LYRICS. All of the recognised fields map onto the MP4 metadata block and arrive intact in Apple Music.

Cover art moves as well: an image stored in the Ogg as a METADATA_BLOCK_PICTURE comment is rewritten as MP4 artwork, which is what the Music app, the Files app and a car display all read. What does not survive is the long tail of custom keys that a particular game engine or tool invented for its own purposes — those have no MP4 equivalent and are dropped rather than written where nothing will read them.

Much of what arrives as `.ogg` is game audio, and looping assets deserve a warning. Vorbis loops cleanly and engines commonly read loop points from the Ogg's comment fields; AAC encoders add priming samples at the start and padding at the end because the encoder works in blocks and a recording rarely ends on one.

An M4A does record how many samples to skip, so a player trims them and gapless playback works in Apple Music — that part is genuinely preserved, and it is one place M4A beats MP3 outright. What is not preserved is the loop metadata itself, since the field names are engine-specific and have no MP4 equivalent. If the audio is a game loop, keep the Ogg for the engine and use the M4A only for listening.

The decoding uses the codecs on the machine you are sitting at, which means whether a given Ogg opens depends on your browser rather than on this page. Opus is universal because every browser needed it for calls. Vorbis is widely but not uniformly available, and FLAC inside Ogg is narrower still.

Where the codec is absent, the conversion stops and says that nothing in the file could be converted and that it may use a codec this browser cannot read, rather than producing an empty M4A and reporting success. There is a second, separate limitation on the encoding side: Firefox has no AAC encoder, so a WebAssembly build is loaded on demand there. If a conversion refuses to start, trying it in a different browser is a five-second test worth running before blaming the file.

Drop a whole folder: each Ogg converts independently and the M4A files return as one ZIP, with a 100 MB per-file ceiling and a hundred files to a batch, since everything runs on your own processor. Practical batches are fifty to a hundred at a time, because AAC encoding is real work and a browser tab grinding through a full hundred at once is unpleasant.

Once converted, the files import into Music the way any purchased track does and sync to a phone from there. Nothing was uploaded to get them there — the decode uses your device's own codec and the muxing happens in the tab — and if you want to verify rather than trust that, open the network tab of your developer tools while a conversion runs and look for a request carrying the file. There is not one.