Convert 3G2 to AIFF — Free Online Tool
Convert 3G2 mobile video files to AIFF, extracting the compressed AAC audio track and decoding it to uncompressed PCM audio stored in Apple's lossless AIFF container. Ideal for recovering audio from legacy CDMA mobile recordings in a format suitable for professional audio editing on macOS.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your 3G2 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
3G2 files typically carry AAC-encoded audio alongside H.264 video, both compressed with lossy codecs designed for low-bandwidth CDMA mobile networks. During this conversion, FFmpeg discards the video stream entirely and decodes the AAC audio from the 3G2 container into raw PCM samples, then re-encodes them as 16-bit big-endian PCM (pcm_s16be) wrapped in an AIFF container. Because AAC is lossy, the conversion does not recover any quality lost during the original mobile encoding — instead it 'freezes' the audio at its current fidelity in an uncompressed form. The result is a much larger file than the source, but one that can be loaded directly into any macOS audio application without further decoding overhead.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg program, the open-source multimedia processing engine that handles the decoding of the 3G2 container and re-encoding to AIFF in this conversion. |
-i input.3g2
|
Specifies the input file — a 3G2 container typically holding H.264 video and AAC audio encoded for CDMA mobile transmission. FFmpeg will demux both streams but only the audio will be passed to the output stage. |
-c:a pcm_s16be
|
Sets the audio codec to signed 16-bit big-endian PCM, the native and default encoding for AIFF files. This decodes the lossy AAC audio from the 3G2 source into uncompressed PCM samples stored in the big-endian byte order Apple's AIFF specification requires. |
output.aiff
|
Defines the output file name and triggers FFmpeg to wrap the uncompressed PCM audio in an AIFF container — Apple's lossless audio format widely supported on macOS and in professional DAWs. The .aiff extension is what tells FFmpeg which container format to use for the output. |
Common Use Cases
- Recovering voice memos or field recordings captured on older CDMA phones (e.g., Verizon or Sprint devices) for editing in Logic Pro or GarageBand on macOS, which work natively with AIFF.
- Archiving audio from 3G2 video clips shot on early-2000s mobile devices into an uncompressed format that will remain readable without proprietary codecs decades from now.
- Extracting interview or meeting audio recorded on a 3G2-compatible device and importing it into a professional digital audio workstation (DAW) that requires uncompressed PCM input.
- Preparing audio from 3G2 clips for forensic analysis or transcription services that require uncompressed audio files to avoid artifacts introduced by lossy codec re-compression.
- Converting a collection of 3G2 ringtones or short audio clips originally downloaded for 3GPP2 phones into AIFF so they can be managed and played back in iTunes or the macOS Music app.
- Stripping and preserving the audio layer from 3G2 home videos before the source device or software becomes too obsolete to read the format, creating a stable archival master.
Frequently Asked Questions
No. The audio in a 3G2 file is encoded with AAC, a lossy codec optimized for the narrow bandwidth of CDMA mobile networks — quality information discarded during that original compression cannot be recovered. Converting to AIFF decodes the AAC stream and stores the result as uncompressed PCM, which means no further quality is lost in subsequent edits or exports, but the audio ceiling is still set by the original mobile recording. Think of it as locking in current quality rather than upgrading it.
3G2 uses AAC audio compression, which typically achieves 10:1 to 20:1 size reduction compared to raw audio. AIFF stores audio as uncompressed 16-bit big-endian PCM samples, so every second of stereo audio at 44.1 kHz requires roughly 176 KB. A 10 MB 3G2 clip with a few minutes of audio could easily expand to 50–100 MB as AIFF. The video stream is also discarded, but that rarely offsets the dramatic size increase from removing audio compression.
The video stream — typically H.264 or MJPEG in a 3G2 file — is completely dropped. AIFF is a pure audio format with no support for video streams, so FFmpeg extracts only the audio and ignores the video data entirely. If you need to keep the video, you should choose a different output format such as MP4 or MOV.
pcm_s16be stands for signed 16-bit big-endian PCM, which is the native and default audio encoding for the AIFF format as defined by Apple's original specification. AIFF was designed around big-endian byte ordering (consistent with Motorola 68k and PowerPC architectures), and 16-bit depth matches CD-quality audio, which is more than sufficient to represent the fidelity available from a compressed AAC source. Other AIFF-compatible variants like pcm_s24be or pcm_f32be exist for higher-precision workflows, but pcm_s16be is the universally compatible baseline.
Replace pcm_s16be with pcm_s24be in the command: ffmpeg -i input.3g2 -c:a pcm_s24be output.aiff. This produces a 24-bit big-endian AIFF file, which is common in professional audio workflows. Other valid options include pcm_s32be (32-bit integer) and pcm_f32be or pcm_f64be (32/64-bit floating point). Keep in mind that since the source audio is AAC from a mobile recording, increasing bit depth will make the file larger without recovering lost audio information.
Yes. On macOS or Linux you can use a shell loop: for f in *.3g2; do ffmpeg -i "$f" -c:a pcm_s16be "${f%.3g2}.aiff"; done. On Windows Command Prompt, use: for %f in (*.3g2) do ffmpeg -i "%f" -c:a pcm_s16be "%~nf.aiff". Each file is processed sequentially, and the output AIFF will have the same base name as the source 3G2 file. This is especially useful when migrating a folder of old mobile recordings.
Technical Notes
AIFF is a big-endian format rooted in Apple's legacy architecture, and FFmpeg correctly writes the pcm_s16be codec to honor that byte order — some tools that write AIFF with little-endian PCM produce files that are technically malformed per the spec. The source 3G2 container does not carry rich metadata fields (no chapter markers, no subtitle streams, and typically only a single audio track), so there is little metadata to lose in this conversion beyond basic tags like title or creation date, which FFmpeg may or may not transfer depending on how they were written by the originating 3G2 device. Because the original AAC encoding in 3G2 was typically performed at low bitrates (64–128 kbps) targeting CDMA network constraints, the effective audio bandwidth is usually limited to 16 kHz or less, meaning the uncompressed AIFF output may exhibit a noticeable high-frequency rolloff compared to a native studio recording at the same bit depth. No special flags are required for AIFF output because, unlike formats such as MP4, AIFF does not use a moov atom or require seek optimization directives.