Extract Audio from 3GPP to AIFC — Free Online Tool
Extract audio from a 3GPP mobile video file and save it as an AIFC file with uncompressed PCM audio using the pcm_s16be codec. This conversion is ideal when you need to move audio from a mobile-recorded 3GP file into a professional Apple audio format suitable for high-fidelity editing or archiving.
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 (.3gp) typically contain AAC-encoded audio paired with a video stream optimized for mobile bandwidth constraints. During this conversion, FFmpeg discards the video stream entirely and decodes the AAC audio from the 3GP container, then re-encodes it as 16-bit big-endian PCM (pcm_s16be) wrapped in an AIFC container. Unlike a simple remux, this requires full audio transcoding — the compressed AAC data is decoded to raw PCM samples, which means the output is uncompressed and significantly larger than the source. The AIFC format, as an extension of Apple's AIFF, uses big-endian byte ordering for its PCM data, making the result compatible with professional Apple audio tools and classic Mac-based workflows.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg media processing tool. In the browser-based version of this tool, FFmpeg runs locally via WebAssembly (FFmpeg.wasm) — no data leaves your device. |
-i input.3gp
|
Specifies the input 3GPP file. FFmpeg reads the 3GP container, which typically holds a video stream (H.264) and an AAC audio stream optimized for mobile delivery. |
-vn
|
Disables video output entirely, stripping the H.264 (or other) video stream from the 3GP file so only the audio track is processed and written to the AIFC output. |
-c:a pcm_s16be
|
Transcodes the AAC audio from the 3GP file into 16-bit big-endian signed PCM, the default and most widely compatible uncompressed codec for the AIFC/AIFF container format used by Apple audio tools. |
-b:a 128k
|
Sets a target audio bitrate of 128k, though for uncompressed pcm_s16be this parameter has no practical effect — the actual bitrate is determined by the source audio's sample rate and the fixed 16-bit depth, not a compression target. |
output.aifc
|
Specifies the output filename with the .aifc extension, which tells FFmpeg to wrap the decoded PCM audio in an AIFC container — Apple's extended AIFF format that supports both compressed and uncompressed audio data. |
Common Use Cases
- Extracting a voice memo or phone-recorded 3GP clip and converting it to AIFC for import into Logic Pro or Final Cut Pro on a Mac
- Archiving mobile-captured audio from 3GPP video files in an uncompressed PCM format to prevent any further generational quality loss during editing
- Preparing audio from 3G-compatible video recordings for use in professional broadcast or post-production workflows that require AIFF-family formats
- Recovering the audio track from a 3GPP video sent via MMS or recorded on an older mobile device and bringing it into a Mac-based DAW for cleanup or mastering
- Converting field recordings made on a mobile phone (saved as 3GP) into AIFC for compatibility with audio analysis tools that require uncompressed big-endian PCM
Frequently Asked Questions
No — the audio quality ceiling is set by the original AAC encoding in the 3GP file. Since 3GPP files are designed for low-bitrate mobile use (often encoded at 64k or lower), any artifacts introduced during the original AAC encoding are permanent. The AIFC output will be a lossless, uncompressed representation of that already-compressed audio, meaning it is a perfect capture of the decoded AAC data but cannot recover information discarded during the original 3GP encoding.
3GPP files use AAC audio compression, which achieves small file sizes by discarding perceptually redundant audio data. AIFC with pcm_s16be is completely uncompressed — every audio sample is stored as a raw 16-bit integer. A one-minute audio track that might be 500KB as AAC in a 3GP file could easily be 10MB or more as uncompressed PCM in AIFC. This is expected behavior and is the trade-off for having a fully editable, artifact-free PCM file.
AIFC is a superset of AIFF — it shares the same basic structure but adds support for compressed audio codecs alongside uncompressed PCM. When using pcm_s16be (as this tool does), the AIFC output is functionally equivalent to a standard AIFF file and will open in any software that supports AIFF, including Logic Pro, GarageBand, Audacity, and Adobe Audition. The big-endian byte order of pcm_s16be aligns with the AIFF/AIFC specification's native format.
Generally, no. 3GPP containers use MP4-style metadata atoms for tags like title or recording date, while AIFC uses a different chunk-based metadata structure. FFmpeg does not reliably map 3GP metadata to AIFC chunks during this conversion, so most tags will be dropped. If metadata preservation is important, you should re-add tags using a dedicated audio tagging tool like Mp3tag or FFmpeg's metadata flags after the conversion.
You can replace pcm_s16be with other PCM variants supported by AIFC, such as pcm_s24be for 24-bit audio or pcm_f32be for 32-bit floating-point audio, by changing the -c:a flag: for example, ffmpeg -i input.3gp -vn -c:a pcm_s24be output.aifc. Note that the -b:a bitrate flag is largely irrelevant for uncompressed PCM (the bitrate is determined by sample rate and bit depth), but FFmpeg accepts it without error. For the highest fidelity extraction from a 3GP source, pcm_s16be or pcm_s24be are the most practical choices.
Yes. On Linux or macOS, you can use a shell loop: for f in *.3gp; do ffmpeg -i "$f" -vn -c:a pcm_s16be -b:a 128k "${f%.3gp}.aifc"; done. On Windows Command Prompt, use: for %f in (*.3gp) do ffmpeg -i "%f" -vn -c:a pcm_s16be -b:a 128k "%~nf.aifc". This processes each 3GP file in the current folder and saves a corresponding AIFC file with the same base name. This is particularly useful when dealing with large batches of mobile-recorded files over 1GB total, since the browser-based tool processes one file at a time.
Technical Notes
The 3GPP format encodes audio as AAC at low bitrates (the default in this tool's input spec is 64k), which is appropriate for mobile streaming and 3G network delivery but represents a lossy starting point for any downstream workflow. When FFmpeg decodes this AAC stream and re-encodes it as pcm_s16be in an AIFC container, it performs a full decode-encode cycle — there is no stream copy possible here because the source codec (AAC) and destination codec (PCM) are entirely different. The pcm_s16be codec stores samples as 16-bit signed integers in big-endian byte order, which is the native byte order of the AIFC/AIFF specification and matches the format expected by classic Mac audio tools. AIFC technically supports compressed audio codecs like pcm_alaw and pcm_mulaw (used in telephony), but for professional use the uncompressed PCM codecs are strongly preferred. The -b:a flag has no meaningful effect on uncompressed PCM output since the bitrate is fixed by the sample rate and bit depth of the source audio, but it is included in the command for consistency. One known limitation: 3GP files recorded on older mobile devices may have non-standard sample rates (e.g., 8000 Hz for voice calls), and the AIFC output will preserve that sample rate — if you need 44.1 kHz or 48 kHz output, add -ar 44100 or -ar 48000 to the command to resample.