Convert 3GPP to ALAC — Free Online Tool

Convert 3GPP mobile video files to ALAC (Apple Lossless Audio Codec), extracting the audio track and re-encoding it into a lossless M4A file compatible with iTunes, Apple Music, and all Apple devices. Since 3GPP files use lossy AAC audio, this conversion produces the highest-quality lossless representation of whatever audio was preserved in the original mobile recording.

FFmpeg Command

Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg

Free — no uploads, no signups. Your files never leave your browser.

Estimated output:

Conversion Complete!

Download

How It Works

3GPP files typically carry AAC-encoded audio, which is already a lossy compressed format designed for the bandwidth constraints of 3G mobile networks. During this conversion, FFmpeg extracts the AAC audio stream from the 3GPP container and re-encodes it using the ALAC (Apple Lossless Audio Codec), discarding the video stream entirely. The output is stored in an MPEG-4 (.m4a) container. Because the source audio is lossy AAC, ALAC will encode it losslessly — meaning every bit of what survived the original AAC compression is preserved with zero further degradation. File sizes will be notably larger than the source 3GPP file, as ALAC prioritizes perfect reconstruction over compression efficiency.

What Each Flag Does

Flag What it does
ffmpeg Invokes the FFmpeg tool, the open-source multimedia processing engine that powers this conversion both in the browser via WebAssembly and on the desktop command line.
-i input.3gp Specifies the input file — a 3GPP container (.3gp) typically containing a video stream (H.264 or MJPEG) and a lossy AAC or AMR audio stream recorded on a mobile device.
-c:a alac Sets the audio codec to ALAC (Apple Lossless Audio Codec), which losslessly re-encodes the extracted AAC audio from the 3GPP file into a perfect, bit-for-bit reproducible audio representation stored in the M4A output.
-c:a alac This flag appears twice in the resolved command, which is redundant but harmless — FFmpeg applies the last valid instance. Both instances instruct FFmpeg to use the ALAC encoder for the audio stream, and no video stream is mapped to the output since M4A in this configuration is audio-only.
output.m4a Specifies the output filename with the .m4a extension, which signals to FFmpeg that the output container is MPEG-4 Audio — the correct and standard container format for ALAC files compatible with iTunes, Apple Music, and Apple devices.

Common Use Cases

  • Archiving voice memos or field recordings made on older 3G-era mobile phones into a lossless format for long-term preservation without introducing additional quality loss
  • Importing audio from 3GPP video clips captured on Nokia, Sony Ericsson, or other legacy handsets into an iTunes or Apple Music library in a native Apple-compatible format
  • Extracting interview audio recorded on a mobile device in a 3GPP format to preserve as ALAC before editing in GarageBand or Logic Pro, which handle ALAC natively
  • Converting 3GPP ringtone or audio sample files into ALAC for use as a lossless reference baseline when comparing audio quality across different codec pipelines
  • Stripping the video from a 3GPP concert or event clip recorded on a mobile phone to keep only the audio track in a format compatible with Apple's ecosystem of devices and software

Frequently Asked Questions

No — ALAC is lossless, but it cannot recover audio information that was already discarded when the 3GPP file was originally encoded with AAC. The audio in a 3GPP file has already passed through lossy compression optimized for narrow mobile network bandwidth, so artifacts from that encoding are permanent. What ALAC guarantees is that no additional quality loss occurs during or after this conversion — the output is a perfect, lossless copy of whatever audio the 3GPP file contained.
3GPP files are engineered for minimal file size — they use aggressive AAC compression and low bitrates (often 32–64 kbps) specifically for 3G network transmission and limited mobile storage. ALAC, by contrast, uses lossless compression that must preserve every audio sample exactly, typically resulting in bitrates 5–10 times higher. Additionally, the video stream present in the 3GPP file is discarded, but the audio portion alone stored losslessly will still be significantly larger than the compressed AAC audio in the original.
FFmpeg will attempt to copy compatible metadata tags from the 3GPP container into the ALAC M4A output. However, 3GPP files from older mobile devices often contain minimal or no metadata beyond basic file properties. The M4A/ALAC format supports rich iTunes-style metadata tags (title, artist, album, artwork), but any tags not present in the source file will not be created automatically. You may want to use a tag editor like MusicBrainz Picard or iTunes after conversion to add metadata manually.
ALAC has been open-sourced by Apple since 2011 and is supported beyond just the Apple ecosystem. VLC, foobar2000, Android (with appropriate apps), and many modern media players support ALAC playback. However, if your goal is broad cross-platform compatibility, FLAC is often better supported on non-Apple platforms. ALAC's strongest native support remains in iTunes, Apple Music, iPhone, iPad, Mac, and Apple TV.
The displayed command processes a single file, but you can wrap it in a shell loop for batch processing. On Linux or macOS, use: `for f in *.3gp; do ffmpeg -i "$f" -c:a alac "${f%.3gp}.m4a"; done`. On Windows Command Prompt: `for %f in (*.3gp) do ffmpeg -i "%f" -c:a alac "%~nf.m4a"`. This iterates over all 3GPP files in the current directory and produces a corresponding ALAC M4A file for each. This approach is especially useful for archiving a folder of old mobile recordings.
The video track is completely dropped. FFmpeg extracts only the audio stream and encodes it to ALAC — no video data is written to the output M4A file. ALAC is a purely audio format and the M4A container in this context holds only audio. If you need to retain the video alongside lossless audio, you would need a different output format such as MKV with FLAC audio, as ALAC in M4A does not support embedded video.

Technical Notes

3GPP audio is encoded with AAC at bitrates typically ranging from 32k to 64k — the low end of what AAC can handle — reflecting the format's origins in 3G mobile infrastructure where bandwidth was scarce. When ALAC re-encodes this audio, it losslessly captures every sample of that already-compressed audio signal, meaning the ALAC file is an exact digital replica of the 3GPP's audio content, not an improvement of it. The output container is MPEG-4 Audio (.m4a), which is the standard container for standalone ALAC files and the format expected by iTunes and Apple Music for lossless imports. ALAC does not support adjustable quality settings — it is always lossless, so there are no bitrate or quality parameters to tune. The M4A container supports chapter markers, though chapters present in the source 3GPP file are unlikely given the format's mobile origins and limited metadata support. One known limitation: very old 3GPP files using AMR-NB or AMR-WB audio codecs (common on early 3G phones) rather than AAC will still be converted, but the narrowband AMR audio characteristics (optimized for voice, 8kHz or 16kHz sample rates) will be faithfully preserved in the ALAC output — fidelity will be limited by the original AMR codec's voice-centric design, not by the conversion process.

Related Tools