Convert 3GPP to M4A — Free Online Tool
Convert 3GPP mobile video files to M4A audio, extracting the AAC audio track into an iTunes-compatible MPEG-4 audio container. This is ideal for pulling speech, music, or recordings captured on older mobile phones into a high-quality audio format that plays natively on Apple devices and modern media players.
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 typically carry an AAC audio track alongside a video stream encoded with H.264 or MJPEG. During this conversion, FFmpeg strips the video entirely and remuxes the AAC audio stream directly into the M4A container — meaning the audio is not re-encoded in most cases, preserving the original quality without any additional lossy compression. The M4A format is itself an MPEG-4 container restricted to audio, so it is structurally compatible with the AAC codec already present in most 3GPP files. The result is a smaller file containing only the audio, wrapped in a container that supports iTunes metadata, gapless playback, and broad compatibility with Apple and web-based players.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg tool, which handles the demuxing of the 3GPP container, optional audio transcoding, and remuxing into the M4A output container. |
-i input.3gp
|
Specifies the input 3GPP file. FFmpeg reads the container and identifies both the video stream (typically H.264 or MJPEG) and the audio stream (typically AAC or AMR) stored inside. |
-c:a aac
|
Sets the audio codec for the output to AAC. If the source 3GPP file already contains AAC audio, FFmpeg may stream-copy it directly; if the source uses AMR audio (common in older 3G recordings), FFmpeg will transcode it to AAC to produce a compatible M4A file. |
-b:a 128k
|
Sets the audio output bitrate to 128 kilobits per second. This is a standard quality level for AAC that balances file size and audio fidelity, and is the default for M4A output. For voice-only 3GPP recordings, 64k would be sufficient; for music, 192k or higher is preferable. |
-vn
|
Disables video output entirely, which is required because M4A is an audio-only container. This flag tells FFmpeg to ignore the video stream from the 3GPP source and write only the audio track to the output file. |
output.m4a
|
Specifies the output filename with the .m4a extension. FFmpeg uses this extension to determine that the output container should be MPEG-4 audio, producing a file that is natively compatible with iTunes, Apple Music, iPhones, and most modern media players. |
Common Use Cases
- Extracting a voice memo or phone call recording captured on a 3G-era mobile device to archive it as a standalone audio file on your computer or iPhone
- Pulling the audio from a 3GPP video recorded on an older Android or Nokia device to import it into GarageBand, Logic Pro, or another DAW for editing
- Converting mobile video interviews or field recordings stored in 3GP format into M4A so they can be imported into iTunes or Apple Music for syncing to an iPod or iPhone
- Stripping the low-resolution video from a 3GPP clip to produce a lightweight audio podcast episode or audio note without the unnecessary video data
- Archiving spoken-word recordings or lectures captured on a 3G handset into M4A format for long-term storage with proper metadata tagging support
- Preparing audio from 3GPP clips for use in iMovie or Final Cut Pro by converting to an M4A format those applications can natively import
Frequently Asked Questions
In most cases, no — the audio quality is preserved without any additional loss. Because 3GPP files almost universally carry AAC audio, and M4A is simply an MPEG-4 container for AAC audio, FFmpeg can remux the audio stream directly without re-encoding it. The command uses '-c:a aac' and '-b:a 128k', which may trigger a re-encode if the source bitrate differs, but if the original mobile recording was already at or below 128k, the quality impact is negligible.
The size reduction comes almost entirely from discarding the video stream. 3GPP files bundle both video and audio into a single container, and on mobile devices the video track often accounts for the majority of the file size even at low resolution. Once FFmpeg removes the video with the '-vn' flag and writes only the audio, the resulting M4A contains just the audio data, which is typically a fraction of the original file's size.
Yes — replace '128k' in the '-b:a 128k' portion of the command with a higher value such as '192k' or '256k'. However, since 3GPP files recorded on mobile phones were often captured at 32k to 64k AAC, increasing the bitrate in the output command cannot recover audio detail that was never recorded. If your source 3GPP file was recorded at a higher bitrate, increasing '-b:a' will preserve more of that original detail during the conversion.
M4A supports chapter markers and iTunes-style metadata such as title, artist, and album, but 3GPP files recorded on mobile devices rarely contain this kind of structured metadata. The conversion will carry over any basic metadata tags present in the source, but chapter markers from 3GPP are not a standard feature and will not be present in the output. You can add metadata to the output M4A separately using a tag editor or by extending the FFmpeg command with '-metadata' flags.
Yes, M4A with AAC audio is Apple's preferred audio format and plays natively on every iPhone, iPad, Mac, iPod, and in iTunes and Apple Music without any additional software. This is one of the primary advantages of targeting M4A over formats like MP3 or OGG for users in the Apple ecosystem, as the file can be airdropped, synced, or imported without conversion steps.
The single-file command shown on this page can be adapted for batch processing on your desktop using a shell loop. On Linux or macOS, run: 'for f in *.3gp; do ffmpeg -i "$f" -c:a aac -b:a 128k -vn "${f%.3gp}.m4a"; done'. On Windows Command Prompt, use: 'for %f in (*.3gp) do ffmpeg -i "%f" -c:a aac -b:a 128k -vn "%~nf.m4a"'. The in-browser tool processes one file at a time, so the FFmpeg command is particularly useful for large collections of 3GP recordings.
Technical Notes
3GPP is a container format defined by the 3rd Generation Partnership Project for use on 3G mobile networks, and it shares much of its structural DNA with the MPEG-4 container family — meaning the AAC audio codec commonly used inside 3GPP files is directly compatible with M4A without transcoding. The '-vn' flag is essential here because M4A is an audio-only container; attempting to copy a video stream into it would cause an error. One known limitation is that 3GPP files recorded on very old or budget mobile handsets may use AMR-NB (Adaptive Multi-Rate Narrowband) audio instead of AAC, which is optimized for voice telephony at extremely low bitrates (typically 4.75–12.2 kbps). In that case, FFmpeg will transcode the AMR audio to AAC at the specified 128k bitrate, and while the output will be technically correct, the audio quality will reflect the original AMR recording's narrow bandwidth and will not sound like a full-fidelity 128k recording. The M4A container supports chapters and iTunes metadata fields, but these must be added manually post-conversion as 3GPP source files do not carry this information. Files produced by this conversion are fully compatible with Apple's ecosystem including Final Cut Pro, Logic Pro, GarageBand, iPhone, and Apple Music.