Convert 3GPP to AIF — Free Online Tool
Convert 3GPP mobile video files to AIF (Audio Interchange File Format), extracting the AAC or MP3 audio track and re-encoding it as uncompressed PCM audio. This is ideal when you need to recover high-integrity audio from a mobile recording and bring it into a Mac-based audio workflow without any further lossy compression.
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
A 3GPP file typically contains a compressed video stream (H.264) alongside a compressed audio stream encoded in AAC or MP3 — both lossy formats optimized for low-bandwidth mobile transmission. During this conversion, FFmpeg discards the video stream entirely and decodes the compressed audio to raw PCM samples, then writes them as big-endian 16-bit PCM into an AIF container (the Apple Audio Interchange File Format). Because the source audio was already lossy, the output AIF is a lossless representation of what was in the 3GPP file — no further generation loss occurs — but it will be substantially larger in file size since it is completely uncompressed. The AIF container itself adds no encoding of its own; it simply wraps the raw audio samples.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary — the open-source multimedia processing engine that handles decoding the 3GPP container and its compressed audio stream, then encoding and writing the AIF output. |
-i input.3gp
|
Specifies the input file — a 3GPP multimedia container that typically holds an H.264 video stream and a compressed AAC or MP3 audio stream recorded on a mobile device. |
-c:a pcm_s16be
|
Sets the audio codec for the output to signed 16-bit big-endian PCM, which is the standard uncompressed audio format used inside AIF files and is natively compatible with Core Audio and Logic Pro on Mac. |
output.aif
|
Defines the output filename and triggers FFmpeg to write an AIF container. FFmpeg infers from the .aif extension that the output should be formatted as an Apple Audio Interchange File, wrapping the raw PCM samples in the correct AIFF chunk structure. |
Common Use Cases
- Extracting spoken-word audio from a 3GPP voice memo or field recording captured on an older mobile phone for editing in Logic Pro or GarageBand on a Mac
- Recovering interview audio recorded on a 3G-era device and importing it into a professional audio editing session that requires uncompressed source files
- Archiving audio from old 3GPP video clips — such as early smartphone footage — into a lossless format for long-term preservation without re-compression
- Bringing mobile-captured audio into a Foley or sound-design workflow where downstream processing and mixing tools expect uncompressed AIF input
- Separating a music or performance audio track from a 3GPP video recorded at a live event to use as a reference or master in a Mac-native audio project
- Preparing a 3GPP audio track for upload to a mastering or audio restoration service that requires uncompressed AIF or WAV source files
Frequently Asked Questions
No — converting from 3GPP to AIF does not recover quality that was lost when the audio was originally encoded as AAC or MP3 inside the 3GPP container. The output AIF will be a lossless, uncompressed representation of whatever lossy audio was already in the source file. The benefit is that no additional quality is lost during or after this conversion, making AIF a better intermediate format for further editing or processing.
3GPP files store audio in compressed lossy formats like AAC, which can be 10–20 times smaller than uncompressed audio. AIF stores raw PCM samples with no compression at all — a 16-bit stereo signal at 44.1 kHz uses roughly 10 MB per minute. A 3GPP file that seemed small on a mobile device can easily expand to tens of megabytes when uncompressed to AIF, even after the video track is discarded.
No. AIF is a pure audio container and cannot store video. FFmpeg automatically discards the video stream during this conversion. Only the audio track is decoded and written to the AIF output. If you need to keep the video, you would need to target a video output format such as MP4 or MOV instead.
The default output codec is pcm_s16be — signed 16-bit big-endian PCM, which is the standard for AIF files and compatible with virtually all Mac audio software including Logic Pro, Pro Tools, and QuickTime. If your workflow requires higher bit depth, you can modify the FFmpeg command to use pcm_s24be (24-bit) or pcm_s32be (32-bit) by changing the -c:a flag value, for example: ffmpeg -i input.3gp -c:a pcm_s24be output.aif.
On macOS or Linux you can use a shell loop: for f in *.3gp; do ffmpeg -i "$f" -c:a pcm_s16be "${f%.3gp}.aif"; done. On Windows Command Prompt you can use: for %f in (*.3gp) do ffmpeg -i "%f" -c:a pcm_s16be "%~nf.aif". This processes each 3GPP file in the current directory and produces a matching AIF file with the same base name.
Metadata preservation depends on what tags are present in the 3GPP source file and whether AIF supports equivalent fields. FFmpeg will attempt to map compatible metadata tags, but 3GPP uses MPEG-4 style atoms for metadata while AIF uses AIFF metadata chunks — some fields may not transfer cleanly or may be dropped entirely. If metadata accuracy is critical, inspect the output file in a tag editor after conversion.
Technical Notes
The 3GPP format is built on the MPEG-4 Part 12 container structure, closely related to MP4/M4A, and its audio streams are almost universally encoded as AAC at low bitrates (typically 32–128 kbps) to suit the constraints of 3G mobile networks. When FFmpeg decodes this to pcm_s16be for AIF output, it performs a full decode of the AAC bitstream — meaning any quantization artifacts introduced at recording time are permanently baked into the output samples. The pcm_s16be codec writes big-endian 16-bit samples, which is the native byte order expected by classic Mac OS and Core Audio, ensuring maximum compatibility with Apple's audio toolchain. One important limitation: if the source 3GPP file was recorded at a sample rate other than 44.1 kHz (some 3G voice recordings use 8 kHz or 16 kHz narrowband audio), the AIF output will reflect that original sample rate — FFmpeg does not upsample by default, so the output will sound narrow or telephone-quality if the source was a voice call recording rather than a music or ambient capture. The video track is silently dropped since AIF has no video container support.