Convert AIF to MP3 — Free Online Tool
Convert AIF (Apple's uncompressed PCM audio format) to MP3 using the LAME encoder, reducing file sizes by up to 10x while preserving perceptually acceptable audio quality. Ideal for making studio-quality AIF recordings portable and compatible with virtually any device or streaming platform.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your AIF 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
AIF files store audio as uncompressed PCM data — typically 16-bit, 24-bit, or 32-bit big-endian samples — which means every single audio sample is stored verbatim with no compression. During conversion, FFmpeg reads those raw PCM samples from the AIF container and feeds them through the LAME MP3 encoder (libmp3lame), which applies psychoacoustic compression: it analyzes the audio in frequency-domain frames and discards sounds that human hearing is least likely to notice, such as frequencies masked by louder nearby sounds. The result is an MP3 file encoded at a target bitrate (128k by default), which is a fundamentally lossy process — the original PCM data cannot be recovered from the MP3. The AIF's big-endian sample format is handled automatically by FFmpeg during decoding, so no manual byte-order conversion is needed.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary — the open-source multimedia processing engine running here via WebAssembly in your browser. This is the same command you would type in a terminal on macOS, Windows, or Linux to run the conversion locally. |
-i input.aif
|
Specifies the input file as an AIF audio file. FFmpeg reads the AIF container, identifies the PCM audio stream (big-endian 16-bit by default), and decodes it into raw samples for processing. |
-c:a libmp3lame
|
Selects the LAME MP3 encoder for the audio stream. libmp3lame is the industry-standard open-source MP3 encoder and produces the most compatible MP3 files, recognized by every device, browser, and media player that supports MP3 playback. |
-b:a 128k
|
Sets the MP3 output bitrate to 128 kilobits per second. This is the most common bitrate for general-purpose MP3 distribution, balancing file size (roughly 1 MB per minute of stereo audio) against audio quality for typical listening conditions. |
output.mp3
|
Defines the output filename and tells FFmpeg to write an MP3 container. The .mp3 extension causes FFmpeg to automatically use the MP3 muxer, which packages the LAME-encoded audio along with any mapped ID3 metadata from the original AIF file. |
Common Use Cases
- Exporting a Logic Pro or GarageBand session mix (which saves as AIF by default on Mac) for distribution on Spotify, Apple Music, or SoundCloud, which require compressed audio uploads.
- Sharing field recordings or podcast interviews captured on a Mac audio interface as AIF files with editors or clients who need smaller, universally playable files.
- Converting a library of uncompressed AIF sample packs or sound effects into MP3 for use in video editors or mobile apps where AIF is not natively supported.
- Reducing the storage footprint of an AIF music archive on a portable device like an iPhone or iPod that has limited capacity but full MP3 playback support.
- Preparing AIF voiceover recordings from a professional studio session for upload to a podcast hosting platform or e-learning system that only accepts MP3.
- Converting AIF masters from a CD ripping workflow into MP3 for embedding in presentations, websites, or email attachments where file size matters.
Frequently Asked Questions
Yes — this is an irreversible lossy conversion. AIF stores audio as uncompressed PCM, preserving every detail of the original recording, while MP3 permanently discards audio information to achieve compression. At the default 128k bitrate most listeners find the result acceptable for casual listening, but trained ears or critical listening environments will detect differences, especially in high-frequency detail and stereo imaging. If you need to preserve the original quality, keep the AIF file as your master and only distribute the MP3.
For music with a wide dynamic range or complex high-frequency content (cymbals, acoustic instruments, orchestral recordings), 320k produces the closest result to the original AIF and is indistinguishable to most listeners. For voice-only content like podcasts or audiobooks, 96k or 128k is entirely sufficient and keeps file sizes small. 192k is a popular middle ground for general music distribution. The default 128k used by this tool is a widely accepted standard for streaming and web playback.
AIF files can store metadata in either an embedded ID3 chunk or Apple's native AIFF metadata chunk, and FFmpeg will attempt to map recognized fields (title, artist, album, track number, etc.) to MP3 ID3v2 tags during conversion. However, some proprietary or non-standard AIF metadata fields may not survive the conversion. It is good practice to verify tags in a tool like MP3Tag or iTunes after conversion, especially if the AIF originated from Logic Pro or a professional DAW with custom metadata.
AIF stores audio as uncompressed PCM, meaning a stereo 16-bit AIF file at 44.1 kHz consumes approximately 10 MB per minute. A 128k MP3 of the same audio uses roughly 1 MB per minute — about a 10:1 size reduction. At 24-bit or 32-bit AIF, the size difference is even more dramatic since the MP3 bitrate stays fixed regardless of the source bit depth. This size reduction is the primary reason for converting AIF to MP3 for distribution or web use.
Replace the '128k' value in the '-b:a 128k' flag with your desired bitrate. For example, to encode at 320k (the highest standard MP3 bitrate), run: ffmpeg -i input.aif -c:a libmp3lame -b:a 320k output.mp3. Valid options with the LAME encoder include 64k, 96k, 128k, 160k, 192k, 224k, 256k, and 320k. You can also use LAME's Variable Bitrate mode by replacing '-b:a' with '-q:a' and a quality value from 0 (best) to 9 (worst), for example '-q:a 2' for near-transparent VBR quality.
Yes — on the command line you can use a shell loop to process an entire folder. On macOS or Linux, run: for f in *.aif; do ffmpeg -i "$f" -c:a libmp3lame -b:a 128k "${f%.aif}.mp3"; done. On Windows Command Prompt, use: for %f in (*.aif) do ffmpeg -i "%f" -c:a libmp3lame -b:a 128k "%~nf.mp3". This applies the same LAME encoding settings to every AIF file in the current directory, producing a matching MP3 for each one. The browser-based tool on this page processes one file at a time.
Technical Notes
AIF uses big-endian PCM encoding (pcm_s16be, pcm_s24be, pcm_s32be, or floating-point variants), which FFmpeg decodes correctly on all platforms regardless of the host system's native byte order. When the source is 24-bit or 32-bit AIF, FFmpeg internally converts the samples to a suitable intermediate format before passing them to the LAME encoder, which works with 16-bit PCM input. This means any dynamic range advantage of 24-bit AIF is not preserved in the MP3 output — MP3 has an effective dynamic range of roughly 96 dB, equivalent to 16-bit audio. The LAME encoder's default joint stereo mode is used, which can reduce stereo width at lower bitrates; for critical stereo content at 128k, consider adding '-joint_stereo 0' to force true stereo encoding. AIF files with multiple audio tracks are not supported by this conversion — only the first audio stream will be encoded. Chapter markers and embedded album art stored in AIF are not reliably transferred to the MP3 container via this command, and dedicated metadata tools should be used if those elements must be preserved.