Extract Audio from 3GP to M4A — Free Online Tool
Extract audio from 3GP mobile video files and save it as M4A, discarding the video stream and re-encoding the audio to AAC at 128kbps inside an MPEG-4 container. Ideal for rescuing audio from old mobile recordings and making it compatible with iTunes, Apple Music, and modern audio players.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your 3GP 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
3GP files typically carry AAC or MP3 audio alongside a video stream, optimized for 3G mobile network constraints. During this conversion, FFmpeg strips the video stream entirely and re-encodes the audio track to AAC at 128kbps, wrapping it in an M4A (MPEG-4 audio) container. Even though 3GP often already uses AAC audio, a re-encode is performed to ensure the audio conforms to the M4A container's expectations and meets the target bitrate. The result is a clean audio-only file that is significantly smaller than the original 3GP, compatible with Apple's ecosystem including iTunes metadata tagging, and suitable for gapless playback on modern devices. No video processing occurs at any stage.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary — the open-source multimedia processing engine that powers this conversion both in the browser via WebAssembly and locally on your desktop. |
-i input.3gp
|
Specifies the input file — a 3GP container as recorded by a mobile phone, which may contain a video stream alongside an AAC or MP3 audio track, all optimized for low-bandwidth 3G transmission. |
-vn
|
Disables video output, ensuring that the 3GP's video stream is completely discarded and does not get written into the M4A container — this is what makes the output audio-only. |
-c:a aac
|
Sets the audio codec to AAC (Advanced Audio Coding), which is the native and most compatible codec for M4A containers and is required for full compatibility with iTunes, Apple Music, and iOS devices. |
-b:a 128k
|
Sets the audio bitrate to 128kbps, a standard quality level for AAC that is substantially higher than the typical 32–64kbps found in 3GP mobile recordings, providing clean output for archiving or playback on modern devices. |
-vn
|
A second video-disable flag applied explicitly to the M4A output stream, acting as a safeguard to ensure no video track is embedded in the M4A file even if the 3GP source contains multiple video streams. |
output.m4a
|
The output filename with the .m4a extension, which signals to media players and operating systems that this is an audio-only MPEG-4 file suitable for iTunes library import, podcast tools, and Apple ecosystem playback. |
Common Use Cases
- Extracting voice memos or audio notes recorded on an older 3G-era mobile phone to archive them as playable M4A files in iTunes or Apple Music
- Pulling the audio from a 3GP video captured at a live music event or concert to keep as a music recording without the low-quality mobile video
- Converting voicemail attachments received as 3GP files on older Android or Nokia phones into M4A so they can be played on iPhones or imported into podcast editing software
- Recovering the audio commentary track from a 3GP sports clip or short video message sent via MMS to use in a video project or highlight reel
- Batch-extracting audio from a folder of archived 3GP home videos to create a lighter, audio-only archive for long-term storage when the video quality is too poor to keep
- Preparing mobile-recorded audio for upload to podcast platforms that accept M4A, since the format supports iTunes chapter metadata and gapless playback
Frequently Asked Questions
Yes, there is a small quality loss because the audio is being decoded from its original compressed form and re-encoded to AAC at 128kbps. If the original 3GP file's audio was encoded at a lower bitrate — which is common, since 3GP targets low-bandwidth mobile networks and often uses 32k or 64kbps — the output M4A may actually sound better or similar since 128kbps AAC is a more generous target. However, because this is a lossy-to-lossy transcode, some generation loss is unavoidable.
M4A and MP4 share the same underlying MPEG-4 container format, but the .m4a extension was introduced by Apple to signal that the file contains only audio with no video stream. This distinction helps music players like iTunes, Apple Music, and most modern audio apps correctly identify and catalog the file as an audio track rather than a video. FFmpeg writes a valid MPEG-4 file regardless, and the -vn flag ensures no video stream is included.
3GP files support only a limited set of metadata tags, and the metadata model differs from the iTunes-style atom tags used in M4A. FFmpeg will attempt to carry over any compatible metadata it finds in the 3GP container, but fields specific to 3GP's mobile-oriented metadata structure may be dropped or not translated. M4A supports a rich set of iTunes metadata atoms — including title, artist, album, genre, and artwork — so you may want to add or clean up tags using a dedicated tag editor like MusicBrainz Picard or iTunes after the conversion.
Replace the value after -b:a with your desired bitrate. For example, use -b:a 192k for higher quality suitable for music archiving, or -b:a 64k to produce a smaller file closer to the original 3GP's mobile-optimized quality. The M4A format supports AAC bitrates from 64k up to 320k through this tool. Higher bitrates produce larger files but better fidelity, though gains above 192k with AAC are rarely perceptible for typical speech or mobile recordings.
The command shown targets a single file, but you can easily loop over multiple files in a shell. On Linux or macOS, run: for f in *.3gp; do ffmpeg -i "$f" -vn -c:a aac -b:a 128k -vn "${f%.3gp}.m4a"; done. On Windows Command Prompt, use: for %f in (*.3gp) do ffmpeg -i "%f" -vn -c:a aac -b:a 128k -vn "%~nf.m4a". This is especially useful for archiving large collections of old mobile phone recordings in one pass.
The first -vn appears before the output file as part of the M4A output format's required flags to suppress any video stream from being written into the container. The second -vn is technically redundant in most cases but acts as an explicit safeguard ensuring FFmpeg does not attempt to embed video data in the M4A output even if the input 3GP contains multiple video streams. In practice, FFmpeg processes the last relevant flag for the output, so the double -vn causes no harm and makes the intent unambiguous.
Technical Notes
3GP was designed for the constraints of early 3G mobile networks, so its audio tracks are typically encoded at very low bitrates — often 32kbps to 64kbps AAC or 128kbps MP3 — which means the source material itself is already significantly compressed. Converting to M4A at 128kbps AAC is a reasonable target that avoids further degrading the already-limited source audio, though users archiving spoken-word recordings may prefer to drop to 64kbps to minimize file size without audible difference. M4A's support for iTunes metadata atoms (ilst) makes it superior to raw AAC files for library management, and the format's chapter support (enabled by the container's timed metadata tracks) is useful if the audio is later used in podcasting workflows. One known limitation is that 3GP files with multiple audio tracks — while uncommon — will result in only the default audio track being extracted, since neither the 3GP input nor the M4A output in this configuration support multiple audio track selection. Files originating from Nokia or older Samsung devices may use AMR-NB audio rather than AAC; FFmpeg handles the transcode to AAC automatically, but AMR-NB source audio is narrowband (300Hz–3400Hz telephone quality) and the M4A output will reflect that inherent quality ceiling regardless of output bitrate.