Extract Audio from 3G2 to M4A — Free Online Tool
Extract the AAC audio track from a 3G2 mobile video file and save it as an M4A file — the native container for AAC audio favored by Apple iTunes, podcasting platforms, and modern media players. Since both 3G2 and M4A use AAC as their default audio codec, this tool performs a direct stream copy in many cases, preserving the original audio quality without re-encoding.
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 are MPEG-4-based containers designed for CDMA mobile networks, and they almost always carry AAC-encoded audio alongside H.264 video. M4A is essentially an MPEG-4 container restricted to audio-only content — the same underlying format that iTunes and Apple devices use natively. During this conversion, the video stream is completely discarded using the -vn flag, and the AAC audio is re-encoded at 128k bitrate into the M4A container. Because 3G2 audio is typically encoded at low bitrates optimized for mobile transmission, the output M4A file retains those characteristics. The result is a clean, iTunes-compatible audio file stripped of any video payload.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg program. In the browser, this runs as a WebAssembly (FFmpeg.wasm) instance entirely client-side — no data leaves your machine. |
-i input.3g2
|
Specifies the input file in 3G2 format. FFmpeg reads the MPEG-4-based container and identifies the H.264 video stream and AAC audio stream inside it. |
-vn
|
Disables video output, discarding the H.264 video stream entirely. This is the primary flag that makes this an audio extraction — the resulting M4A will contain only audio data. |
-c:a aac
|
Sets the audio codec to AAC (Advanced Audio Coding), encoding the extracted audio into the native codec for M4A files. AAC is the default codec in both 3G2 and M4A, ensuring maximum compatibility with Apple devices and iTunes. |
-b:a 128k
|
Sets the audio bitrate to 128 kilobits per second. This is a reasonable default for AAC in M4A, though keep in mind that 3G2 mobile audio is often sourced at much lower bitrates, so the audible quality ceiling is set by the original file. |
-vn
|
A second instance of the video-suppression flag applied at the output stage, reinforcing that no video stream should be written to the M4A file. M4A is an audio-only container, and this flag ensures FFmpeg does not attempt to mux any video into it. |
output.m4a
|
Specifies the output filename with the .m4a extension. FFmpeg uses this extension to write an MPEG-4 audio container with the iTunes-compatible 'M4A ' file type brand, ready for import into Apple Music, iTunes, or any AAC-capable player. |
Common Use Cases
- Extracting a voice memo or recorded call captured on an older CDMA phone (Verizon, Sprint) that saved files in 3G2 format, so it can be played or edited on a Mac or iPhone
- Pulling the audio from a 3G2 video clip to import into GarageBand, Logic Pro, or another DAW that handles M4A natively but may not recognize 3G2
- Archiving audio content from old mobile video recordings into a more universally supported format before the 3G2 files become unplayable on modern devices
- Preparing a short audio clip from a 3G2 video for upload to a podcast platform or Apple Podcasts, which accepts M4A/AAC natively
- Reducing file size for sharing purposes by discarding the video track from a low-resolution 3G2 clip and keeping only the audio as a lightweight M4A
- Extracting audio from 3G2 videos recorded on early-2000s CDMA phones to add to a music or media library managed by iTunes or the Apple Music app
Frequently Asked Questions
Yes, there is a small quality cost because this tool re-encodes the AAC audio rather than performing a lossless stream copy. However, the real-world impact depends on the source: 3G2 files from mobile phones are typically encoded at very low bitrates (often 24k–64k) to suit CDMA network constraints, so the source quality is already limited. Re-encoding to 128k AAC in M4A may actually produce a cleaner-sounding file than the original bitrate implies, but it cannot recover detail that was lost in the original encoding.
3G2 audio was originally encoded for mobile transmission over CDMA networks, often at bitrates as low as 24k or 32k AAC. When you extract and re-encode that audio to 128k M4A, you are encoding an already-lossy signal a second time — a process called transcoding. The 128k output cannot reconstruct audio detail that was discarded during the original 3G2 encoding, so if the source sounds thin or narrow, the M4A will too. The bitrate setting controls output file size and encoding headroom, not the recovered quality of the source.
Yes. M4A with AAC audio is Apple's native audio format and is fully supported by iTunes, the Apple Music app on Mac and Windows, iPhone, iPad, and iPod. The file will import cleanly into your library and sync to Apple devices without any conversion step. If you need chapter markers, those can be added separately — M4A supports them, though the 3G2 source does not carry chapter data.
Replace the value after -b:a in the command. For example, to encode at 192k, change '-b:a 128k' to '-b:a 192k'. For 3G2 source files that were originally encoded at low mobile bitrates, going above 128k rarely adds audible benefit and only increases file size. If the original 3G2 audio was at 64k or below, matching that bitrate (e.g., '-b:a 64k') will minimize transcoding artifacts and keep the file small.
Yes, on the command line you can use a shell loop. On Linux or macOS, run: for f in *.3g2; do ffmpeg -i "$f" -vn -c:a aac -b:a 128k -vn "${f%.3g2}.m4a"; done. On Windows Command Prompt, use: for %f in (*.3g2) do ffmpeg -i "%f" -vn -c:a aac -b:a 128k -vn "%~nf.m4a". This processes each file in the current folder sequentially. The browser-based tool handles one file at a time, so the FFmpeg command is the practical choice for batch work.
FFmpeg will attempt to copy any metadata tags embedded in the 3G2 container to the M4A output. However, 3G2 files from mobile phones rarely contain rich metadata — most carry only technical properties like duration and creation date. The M4A format supports extensive iTunes-style metadata (title, artist, album, artwork), but that information simply will not be present unless it existed in the source file. You can add or edit tags after conversion using tools like MusicBrainz Picard, Kid3, or iTunes itself.
Technical Notes
3G2 is a close relative of MP4 and MOV — all three are derived from the MPEG-4 Part 12 base format — so an M4A output is structurally very similar to the audio portion of the original 3G2 container. The key difference is that M4A uses a 'M4A ' brand in the file's ftyp box, signaling to Apple software that it is an audio-only file. The -vn flag appears twice in the resolved command (a harmless redundancy) to ensure the video stream is suppressed both at the input processing and output mapping stages. One notable limitation: 3G2 does not support multiple audio tracks or subtitle streams, so there is nothing to select or lose beyond the single audio and video track. The output M4A supports chapter markers (an iTunes feature useful for podcasts and audiobooks), but chapters cannot be derived from a 3G2 source — they would need to be added manually post-conversion. FLAC or lossless encoding is technically possible in M4A but makes no sense here, since the 3G2 source is already lossy AAC; lossless encoding would only preserve the degraded signal in a larger file.