Convert M4A to MP3 — Free Online Tool
Convert M4A files (AAC-encoded audio in Apple's MPEG-4 container) to MP3 using the LAME encoder — producing universally compatible audio files that play on virtually every device, platform, and media player without needing iTunes or Apple software.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your M4A file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
M4A files typically contain AAC-encoded audio wrapped in an MPEG-4 container. Since MP3 uses a completely different codec (MPEG Audio Layer III via the LAME encoder), this conversion cannot be a simple remux — the audio must be fully decoded from AAC and then re-encoded into MP3. This means two lossy compression stages occur: the original AAC encoding and then the new MP3 encoding. The tool uses FFmpeg's libmp3lame encoder at 128k bitrate by default, which balances file size and audio quality well for most listening scenarios. One important consequence of this format change is that M4A's chapter markers and iTunes-specific metadata tags will not carry over, as the MP3 format (which uses ID3 tags) does not support the same metadata structures as MPEG-4.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg command-line tool, which handles the decoding, audio transcoding pipeline, and output file writing for this M4A-to-MP3 conversion. |
-i input.m4a
|
Specifies the input file — an M4A file containing an AAC-encoded audio stream inside an MPEG-4 container. FFmpeg reads and demuxes this file to extract the raw AAC audio for decoding. |
-c:a libmp3lame
|
Selects the LAME MP3 encoder for the audio stream, which re-encodes the decoded AAC audio into the MP3 format. LAME is the gold-standard open-source MP3 encoder and is required since M4A's AAC codec is not directly compatible with the MP3 container. |
-b:a 128k
|
Sets the MP3 output audio bitrate to 128 kilobits per second, a common default that balances file size and perceptual audio quality for general listening. This can be increased to 192k or 320k to reduce quality loss from the AAC-to-MP3 transcode. |
output.mp3
|
Defines the output filename and container. The .mp3 extension signals FFmpeg to mux the LAME-encoded audio into a standard MP3 file with ID3 tag support, ready for use on any MP3-compatible device or platform. |
Common Use Cases
- Uploading podcast episodes to distribution platforms or RSS feeds that require MP3 and do not accept M4A files recorded on iPhone or GarageBand
- Sharing music purchased from the iTunes Store (as DRM-free M4A) with friends who use MP3 players, older car stereos, or Android devices that lack AAC support
- Preparing audiobook chapters exported from Apple Books or Audible (M4A format) for playback on a dedicated MP3 audiobook player or older Kindle
- Submitting audio tracks to royalty-free music libraries, stock audio sites, or video editing platforms that mandate MP3 submissions
- Converting voice memos recorded on an iPhone (saved as M4A) into MP3 for embedding in presentations, websites, or email attachments requiring broad compatibility
- Archiving a collection of M4A albums into MP3 for use with legacy DJ software or hardware that only reads MP3 files
Frequently Asked Questions
There will be some quality loss because both AAC (used in M4A) and MP3 are lossy formats, meaning converting between them involves decoding one lossy format and re-encoding into another — sometimes called 'generation loss.' In practice, at 128k or higher bitrates, most listeners will not notice a meaningful difference for music and speech. However, if audio fidelity is critical, consider using the highest available bitrate (320k) to minimize the degradation introduced by the second encoding pass.
No. MP3 does not natively support chapter markers the way the MPEG-4 container does. Any chapter data embedded in your M4A file — common in audiobooks and podcasts — will be lost during conversion. If chapter navigation is important, consider formats like M4B (for audiobooks) or OGG, which have better chapter support, rather than converting to MP3.
FFmpeg will attempt to map common iTunes metadata fields (such as title, artist, album, and track number) to their ID3 tag equivalents in the output MP3 file. However, some iTunes-specific fields and embedded album art may not transfer perfectly depending on the tag structure of your source file. It is worth inspecting the output MP3 in a tag editor like Mp3tag to verify that key metadata carried over correctly.
Replace the '128k' value in '-b:a 128k' with your preferred bitrate. For example, use '-b:a 320k' for the highest MP3 quality (closest to the original AAC audio), or '-b:a 96k' for smaller files where storage is limited. MP3 supports bitrates from 64k up to 320k — higher values produce better audio quality and larger files. For music, 192k or 320k is generally recommended to minimize the audible impact of the second lossy encoding pass.
Yes. On the command line, you can use a shell loop to process multiple files. On Linux or macOS, run: for f in *.m4a; do ffmpeg -i "$f" -c:a libmp3lame -b:a 128k "${f%.m4a}.mp3"; done. On Windows Command Prompt, use: for %f in (*.m4a) do ffmpeg -i "%f" -c:a libmp3lame -b:a 128k "%~nf.mp3". This processes every M4A file in the current directory and outputs a corresponding MP3 file with the same base filename.
AAC is a more efficient codec than MP3, meaning an AAC file at 128k generally sounds better than an MP3 at the same bitrate. When you convert from M4A to MP3 at 128k, you are re-encoding audio that was already compressed with a more efficient algorithm into a less efficient one at the same bitrate — so the output MP3 may sound slightly worse than the source M4A at that setting. To compensate, bumping the output bitrate to 192k or 256k can help offset some of this difference.
Technical Notes
The core challenge of M4A-to-MP3 conversion is that it is a transcode between two lossy codecs (AAC and MP3), not a lossless remux. AAC, as used in M4A, is a more modern and efficient codec than MP3 — it achieves better perceptual quality at equivalent bitrates, particularly below 192k. Because FFmpeg must fully decode the AAC stream before re-encoding it with libmp3lame, some quality degradation is inherent and unavoidable. The LAME encoder used here is widely regarded as the best available MP3 encoder and produces excellent results at 128k and above. One notable feature lost in this conversion is gapless playback: M4A supports gapless playback metadata used by iTunes and Apple Music, while MP3's gapless support is limited and relies on unofficial LAME-specific header extensions that are not universally recognized by players. Additionally, M4A's support for multiple audio encodings (AAC, ALAC, Opus, FLAC within the container) is reduced to a single MP3 stream, and the MPEG-4 chapter atom structure is discarded entirely. For DRM-protected M4A files (purchased from older iTunes versions), conversion will not be possible as the encrypted stream cannot be decoded.