MP3 to M4A re-encodes an MP3 file's audio into AAC and wraps it in the M4A container — the file extension Apple's software and hardware expect by default. M4A is not a separate codec; it's an MPEG-4 audio container holding an AAC stream, the same container family used for M4R ringtones and a lot of Apple Podcasts and Voice Memos exports. The distinction matters because a raw .aac file and an .m4a file can contain functionally identical audio data, but some Apple apps and older iOS versions are pickier about recognizing the .aac extension as a valid import than they are about .m4a, which is the format iTunes and the Music app have always treated as native.
The practical reason to make this conversion is almost always about where the file is going next, not the audio quality itself. If you're importing a track into iTunes or the Music app, setting it as a custom ringtone source, dropping it into GarageBand, or syncing audio onto an iPhone through Apple's own sync tools, handing those apps an .m4a file sidesteps any ambiguity about format recognition that an .mp3 — or worse, a raw .aac — can sometimes run into in specific Apple workflows. AAC is also genuinely a more modern, more efficient codec than MP3 at a comparable bitrate, so there's a small technical upside beyond pure compatibility, even though in practice the difference is rarely audible at the bitrates involved here.
It's worth being clear-eyed about what this conversion is: MP3 is already a lossy format, so taking MP3 audio and re-encoding it to AAC is a lossy-to-lossy transcode. No information lost during the original MP3 encode is recovered, and the AAC encode introduces its own (generally smaller) additional compression artifacts on top. At the 192kbps target used here, that second generation of lossy encoding is not something most listeners will notice, but the file is not a bit-for-bit match to an M4A encoded directly from a lossless source. If the original uncompressed or lossless file is still available, encoding to M4A from that source instead will always produce a cleaner result than going through an intermediate MP3.
FFmpeg handles the whole transcode locally in your browser tab via WebAssembly — the MP3 is decoded, the AAC encoder (FFmpeg's native aac encoder) re-encodes at a constant 192kbps, and the result is packaged into an .m4a container, all without the file ever reaching a server.
Already have the lossless source instead of an MP3? Converting from WAV or FLAC directly to AAC avoids the extra lossy generation this MP3-based conversion involves.
