AIFF to M4A Converter

AIF vs M4A — Which One Should You Keep?

.aif is Apple's AIFF under its three-letter, Windows-safe spelling: uncompressed PCM, bit-for-bit accurate, and about 10 MB per minute. .m4a is the MPEG-4 audio container, normally holding an AAC track, and it is what an iPhone, a Mac, a car stereo, and a browser all expect when you hand them music. The decision is rarely "one or the other" — it is keep the AIF as the master you edit, and ship an M4A as the copy people actually listen to.

AIF and M4A Side by Side

When M4A Is the Right Target

• The audio is going onto a phone or into a music library. M4A is the container Apple's Music app, iTunes purchases, and Voice Memos all use, so it imports, tags, and syncs without a conversion step at the other end.
• You need artwork and tags to survive. Unlike a bare .aac stream, M4A has proper fields for title, artist, album, artwork, and chapters — which is the main reason to prefer it over AIF to AAC for anything you will browse in a library.
• You want the best quality per megabyte from a mainstream codec. AAC was designed as MP3's successor and generally sounds better at the same bitrate, most obviously below 128 kbps.
• You are sending the file to someone. A three-minute AIF is an unwieldy 30 MB attachment; the same track at 256 kbps M4A is closer to 5 MB.

When to Keep the AIF — or Choose Something Else

• You are still editing. Re-encoding a lossy file after every edit stacks generations of loss. Work on the AIF, export a fresh M4A when you are done.
• You need a smaller file with nothing thrown away. That is lossless compression, not AAC — AIF to FLAC typically halves the size while staying bit-exact.
• The destination is a decoder or pipeline that wants a bare stream. Some broadcast and embedded tooling expects raw AAC rather than a container; AIF to AAC covers that case.
• Compatibility with genuinely old hardware matters most. Ancient car decks and MP3 players may not read M4A at all — AIF to MP3 is the lowest common denominator.

Choosing Between the Common Targets

How to Convert AIF to M4A

1. Upload Your AIF File: Drag and drop your .aif or .aiff onto the page, or click "+ Add Files" to browse. GarageBand and Logic bounces, Pro Tools renders, and Mac CD rips all work, and several files can be queued at once.
2. Choose a Variable Bitrate Band: Open Advanced Options. File Compression opens on Quality Preset — the hands-off mode, with nothing pre-selected in its dropdown and the least predictable result on the page. Switch to Variable Bitrate and pick one of the five AAC bands (20k-32k up to 96k-112k) to let the encoder allocate the bits by content, or to Constant Bitrate when you want to name the rate outright — that dropdown runs from 8 kbps to 384 kbps and opens on 128 kbps, with 192-256 kbps the usual choice for music off an AIF master.
3. Or Set an Exact Bitrate or Size: Switch File Compression to Constant Bitrate (the list opens on 128 kbps and runs to 384 kbps; 256 kbps is the usual music choice), Custom Bitrate to type a rate, or Specific file size to cap the result. Audio Channel, Audio Sample Rate, and Trim stay on their original values unless you change them.
4. Convert and Download: Click Convert and save your .m4a, or take the batch as a ZIP. No sign-up, no watermark.

Frequently Asked Questions

Will converting AIF to M4A lose audio quality?

Yes, but cleanly and usually inaudibly. AIFF is uncompressed and M4A carries AAC, a lossy codec, so the encoder discards detail the way a high-quality JPEG discards image data — at a sensible bitrate the difference is very hard to hear. Because the source is a lossless master, this is a single-generation encode, which is the normal way to make a big file usable. The loss is one-way, so keep the .aif; converting the M4A back later restores the format, not the detail.

What bitrate should I pick for M4A?

For music, 256 kbps is the sweet spot — it is the rate Apple's own standard AAC streaming tier uses, and it is effectively transparent for most listeners from a lossless source. 192 kbps is a good balance if size matters, and 320 kbps buys a little headroom at noticeably larger files. For speech, podcasts, or audiobooks, 96–128 kbps is plenty, and a mono source halves the bytes again. AAC's efficiency means you can usually step down a notch from whatever you would have chosen for MP3.

Is M4A the same thing as AAC?

Not quite — M4A is the container, AAC is the codec inside it. An .m4a from this page holds an AAC track, so the audio is identical to what AIF to AAC produces; what M4A adds is the MPEG-4 wrapper, with real fields for title, artist, album, artwork, and chapters, plus the framing that music apps expect. That is why a raw .aac file often refuses to import into a music library while the same audio as .m4a imports instantly.

Is .aif the same file as .aiff?

Yes — identical bytes, two spellings. Apple specified AIFF in 1988, and .aif survives from the era when file extensions were capped at three characters. This page accepts either, and the M4A is the same in both cases. If your source uses the longer spelling, AIFF to M4A runs the same conversion. One caveat: a file that is really AIFF-C with a compressed payload was already lossy before upload, so encoding it to AAC adds a second generation of loss.

Will an M4A play on Windows and Android, or is it Apple-only?

It is not Apple-only. AAC in an MPEG-4 container is standard on Android, plays in Chrome, Edge, and Safari, and opens in the built-in media players on current Windows releases as well as in VLC, foobar2000, and Winamp. Browser-support tracking puts AAC near 97% globally, with Firefox listed as partial because it relies on the operating system's decoders. The rare failures are old car head units and legacy MP3 players, where AIF to MP3 is the safe choice.

Will the artwork and track tags carry over from the AIF?

Check them rather than assume. M4A has proper metadata fields, but AIFF stores its own metadata in optional chunks that many recorders and editors either skip or write in their own way, so there may be nothing to carry across in the first place. The dependable approach for a batch destined for a music library is to convert first and tag the .m4a afterwards in your player or a tag editor — M4A tagging is well supported everywhere.

How much smaller will the M4A actually be?

We size this from the bitrates rather than by guessing. Uncompressed 16-bit / 44.1 kHz stereo PCM is a fixed 1,411 kbps — about 10 MB per minute — so a three-minute track is roughly 30 MB as AIF. At 256 kbps that becomes about 1.8 MB per minute, near 5.5 MB for the same track; at 128 kbps it is closer to 2.7 MB. AAC is variable in practice, so the finished file lands around those figures rather than exactly on them, and Specific file size works backwards from an exact target if you need one.

Are my uploaded files kept private?

Files are uploaded over an encrypted connection, converted on our servers, and deleted automatically a few hours after conversion — never shared, never made public, with no sign-up and no watermark. Because AIF is uncompressed, the upload is normally the slowest part of the job, so trimming a long session down to the part you need before converting saves real time.