Extract Audio from 3GPP to AIF — Free Online Tool
Extract audio from 3GPP mobile video files and convert it to AIF format — a lossless, uncompressed PCM audio file ideal for high-quality archiving on Mac systems. Because 3GPP files typically carry AAC-encoded audio, this tool decodes that compressed audio stream and re-encodes it as 16-bit big-endian PCM, giving you an uncompressed AIF file ready for professional audio workflows.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your 3GPP 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
3GPP files store audio using lossy AAC compression, optimized for mobile networks with low bitrates (often 64k or below). During this conversion, FFmpeg discards the video stream entirely and decodes the AAC audio track from the 3GPP container back to raw PCM samples. Those samples are then written to an AIF file using the pcm_s16be codec — 16-bit signed, big-endian PCM — which is the native uncompressed format Apple's AIF container expects. Importantly, this is a lossy-to-lossless pipeline: the output AIF is technically lossless and uncompressed, but the quality ceiling is set by the original AAC encoding in the 3GPP file. No further quality is lost in this conversion, but any quality already lost to AAC compression cannot be recovered.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg tool — in the browser, this runs as a WebAssembly binary (FFmpeg.wasm) with no server upload required. On your desktop, this calls your locally installed FFmpeg executable. |
-i input.3gp
|
Specifies the input 3GPP file. FFmpeg reads the container, identifies the AAC audio stream and any video streams, and makes them available for processing. |
-vn
|
Disables video output entirely, discarding the H.264 or MJPEG video stream from the 3GPP file. Since AIF is an audio-only format and you only need the audio track, this prevents FFmpeg from attempting to process the video stream at all. |
-c:a pcm_s16be
|
Sets the audio codec to pcm_s16be — 16-bit signed big-endian PCM — which decodes the compressed AAC audio from the 3GPP file into raw, uncompressed samples stored in the byte order AIF expects. This is the standard codec for AIF files and is natively compatible with all Apple software. |
output.aif
|
Specifies the output filename with the .aif extension. FFmpeg uses this extension to determine the container format, writing the uncompressed PCM audio into a valid AIFF container structure that Mac applications can open directly. |
Common Use Cases
- Recovering audio from old mobile phone video clips (3GP files recorded on early Nokia, Sony Ericsson, or similar devices) for archiving in a Mac-compatible lossless format
- Extracting voice memos or field recordings captured as 3GPP video on a mobile device and importing them into Logic Pro or GarageBand as uncompressed AIF tracks
- Preparing audio from 3GPP video interviews or lectures for editing in professional Mac-based audio editors like Adobe Audition or Pro Tools, which prefer uncompressed AIF over compressed mobile formats
- Converting 3GP ringtone audio or MMS message audio into AIF for use as high-quality sample material in a DAW or sound design project
- Archiving audio from 3GPP video files in an uncompressed format before the original mobile files degrade or become inaccessible due to aging hardware
- Stripping audio from 3GPP video files received via MMS or messaging apps to use as clean voice-over stems in a video production workflow
Frequently Asked Questions
No — and this is an important distinction. 3GPP files store audio as AAC, which is a lossy codec that permanently discards audio data during encoding on your phone or device. Converting to AIF produces an uncompressed file, meaning no additional quality is lost in this conversion, but the quality ceiling is fixed by the original AAC encoding. The AIF output is a perfect, bit-accurate representation of what the AAC decoder produces — just stored without further compression.
This is expected and is a direct consequence of the format difference. A 3GPP file stores audio as compressed AAC — often at 64kbps or lower for mobile compatibility. AIF stores audio as raw, uncompressed PCM samples at 16-bit depth, which requires roughly 1.4 MB per minute per channel at standard sample rates. A one-minute 3GP clip might have 500KB of audio; the equivalent AIF could be 10–15MB. The file is larger, but it contains no more information than the decoded AAC stream.
The output uses pcm_s16be — 16-bit signed big-endian PCM — which is the standard and most compatible codec for AIF files, matching the format Apple originally designed. AIF also supports higher bit-depth codecs like pcm_s24be or pcm_s32be, but since your source is AAC-compressed mobile audio from a 3GPP file, using 16-bit is appropriate and avoids artificially inflating the file size without any real quality benefit. If you need a higher bit depth for a specific professional workflow, you can change the codec in the FFmpeg command by replacing pcm_s16be with pcm_s24be.
Metadata preservation between 3GPP and AIF is limited. 3GPP files can contain MP4-style metadata atoms (title, artist, creation date, GPS location from a phone), but AIF has a different metadata structure based on AIFF MARK and NAME chunks, and not all fields map cleanly. FFmpeg will attempt to copy compatible metadata fields, but container-specific tags like GPS coordinates or mobile device information are likely to be dropped. If preserving exact metadata matters, check the output file in a tag editor like Kid3 or iTunes after conversion.
Since AIF with PCM is uncompressed, there is no bitrate setting to adjust — quality is determined by bit depth and sample rate. To change the output sample rate, add -ar 44100 or -ar 48000 before the output filename (e.g., ffmpeg -i input.3gp -vn -c:a pcm_s16be -ar 44100 output.aif). To use a higher bit depth, replace pcm_s16be with pcm_s24be or pcm_s32be. Note that the source AAC audio from the 3GPP file was likely encoded at 8kHz or 16kHz for mobile use, so upsampling beyond the original rate will not add real quality.
Yes — on the command line you can use a shell loop to process multiple files. On macOS or Linux, run: for f in *.3gp; do ffmpeg -i "$f" -vn -c:a pcm_s16be "${f%.3gp}.aif"; done. On Windows Command Prompt: for %f in (*.3gp) do ffmpeg -i "%f" -vn -c:a pcm_s16be "%~nf.aif". This is especially useful for processing large collections of old mobile video recordings in one pass. The in-browser tool handles single files, so for bulk conversions the command-line approach is more efficient.
Technical Notes
3GPP audio streams are almost always AAC-LC (Low Complexity AAC), encoded at low bitrates such as 32k–64kbps and often at reduced sample rates like 8kHz, 16kHz, or at most 44.1kHz, depending on the mobile device and network conditions. When FFmpeg decodes this stream for conversion to AIF, it uses its built-in AAC decoder to produce raw floating-point PCM internally, which is then quantized to 16-bit signed big-endian samples for the pcm_s16be codec. The big-endian byte order is a deliberate choice for AIF: the format was designed by Apple on Motorola 68k hardware where big-endian is native, and AIF players on modern systems handle this correctly. One known limitation is that 3GPP files with multiple audio tracks (rare, but possible) will only have the first audio stream extracted by default — add -map 0:a:1 to target a specific track. Also note that 3GPP does not support subtitles or chapters, so nothing beyond the audio stream is relevant for this conversion. The resulting AIF file is fully compatible with macOS Finder, iTunes/Music, Logic Pro, GarageBand, and most professional Mac audio software.