Convert 3G2 to MP3 — Free Online Tool
Extract and convert the audio track from a 3G2 mobile video file into a universally compatible MP3 using the LAME encoder. This tool strips away the CDMA-era video container and AAC audio, re-encoding only the audio stream to MP3 — ideal for rescuing sound from old mobile recordings.
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 store audio most commonly as AAC within a MPEG-4 derived container built for CDMA mobile networks. Since MP3 is an audio-only format, the video stream is completely discarded during this conversion — it is not remuxed or retained in any form. The AAC audio track is decoded from the 3G2 container and then re-encoded from scratch using the LAME MP3 encoder (libmp3lame) at 128kbps. This is a full transcode of the audio, meaning audio data passes through two lossy compression stages: first decompression from AAC, then recompression into MP3. The result is a standalone .mp3 file with no video, no container overhead, and broad compatibility across virtually every audio player and platform.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg command-line tool. In this browser-based tool, the same FFmpeg engine runs locally via WebAssembly — the command shown is identical to what you would run on your desktop terminal. |
-i input.3g2
|
Specifies the input file — a 3G2 container originating from a CDMA mobile device, which typically holds an H.264 or MJPEG video stream alongside an AAC audio track. |
-c:a libmp3lame
|
Selects the LAME MP3 encoder to re-encode the AAC audio from the 3G2 source into MP3. This is the only codec option for MP3 output in FFmpeg and produces the most widely compatible MP3 files. |
-b:a 128k
|
Sets the MP3 output audio bitrate to 128 kilobits per second, the standard default for general-purpose MP3 encoding. This is a reasonable quality level for mobile-originated audio, which was itself typically recorded at low bitrates in the 3G2 source. |
output.mp3
|
Defines the output file as a standalone MP3 file. FFmpeg infers the MP3 container format from the .mp3 extension, and all video data from the 3G2 source is automatically discarded since MP3 cannot carry video streams. |
Common Use Cases
- Recovering audio from old mobile phone videos shot on CDMA devices (Verizon, Sprint era) to play on modern audio players that don't support 3G2
- Extracting voice memos or field recordings captured on early 2000s 3G mobile phones for archiving as MP3
- Converting 3G2 video clips from legacy mobile devices into audio files for playback in car stereos or MP3 players that don't support video containers
- Pulling background music or ambient audio recorded on a CDMA phone out of a 3G2 file for use in a podcast or audio project
- Stripping the audio from a 3G2 mobile video to reduce file size dramatically when only the sound content is needed for sharing
- Batch-processing a collection of old 3G2 phone recordings into a standardized MP3 archive for long-term digital preservation
Frequently Asked Questions
Yes, there is a generation of quality loss because this conversion involves two lossy compression stages. The original AAC audio in the 3G2 file was already lossy, and re-encoding it to MP3 introduces a second round of compression artifacts. However, at 128kbps MP3 the result is generally acceptable for voice recordings and casual listening. If the source 3G2 was recorded at a very low mobile bitrate (common on early CDMA devices), the output quality ceiling is already set by the source — increasing the MP3 bitrate beyond 128k will not recover detail that was discarded when the 3G2 was originally recorded.
MP3 is a pure audio format — it has no container structure capable of holding video streams, subtitles, or any non-audio data. When converting to MP3, FFmpeg automatically discards all video tracks from the 3G2 source. If you need to preserve the video, you should convert to a format like MP4 instead. This audio-only output is intentional and is what makes the resulting file so small and universally compatible.
Basic text metadata tags may carry over if they are present in the 3G2 file and have equivalent ID3 tag fields in MP3, since FFmpeg attempts to map common metadata. However, 3G2 files from older mobile phones often contain minimal or no embedded metadata beyond technical stream information. The MP3 format supports ID3 tags for title, artist, and date, but any mobile-specific metadata unique to the 3G2/3GPP2 spec will be lost. You can add or edit ID3 tags in the output MP3 using tools like Mp3tag after conversion.
Replace the value after '-b:a' with your desired bitrate. For example, use '-b:a 320k' for the highest standard MP3 quality, or '-b:a 192k' for a good balance between file size and fidelity. The full command would become: ffmpeg -i input.3g2 -c:a libmp3lame -b:a 320k output.mp3. Keep in mind that if the original 3G2's AAC audio was encoded at a low mobile bitrate, setting a high MP3 bitrate will increase file size without recovering lost audio detail.
Yes. On Linux or macOS, you can use a shell loop: 'for f in *.3g2; do ffmpeg -i "$f" -c:a libmp3lame -b:a 128k "${f%.3g2}.mp3"; done'. On Windows Command Prompt, use: 'for %f in (*.3g2) do ffmpeg -i "%f" -c:a libmp3lame -b:a 128k "%~nf.mp3"'. This is especially useful for processing a large archive of old mobile recordings. The browser-based tool on this page processes one file at a time, so the FFmpeg command is recommended for batch jobs.
When the output format is MP3, FFmpeg automatically ignores any video streams from the input because MP3 simply has no mechanism to store video data. The '-vn' flag (which explicitly disables video output) is redundant here — FFmpeg will not attempt to encode video into an MP3 container regardless. The command is intentionally kept minimal: only the necessary audio codec and bitrate flags are needed to produce a valid MP3 from the 3G2 source.
Technical Notes
3G2 (3GPP2) is structurally derived from the MPEG-4 Part 12 container, making it a close relative of MP4 and MOV. Its audio track is almost universally AAC in mobile-originated files, though some devices used AMR-NB for voice. This tool's FFmpeg command assumes the default AAC audio path. The libmp3lame encoder used here is the standard open-source LAME library, which produces the most compatible MP3 output across all devices and platforms. MP3's fixed bitrate mode (CBR) is used at 128k by default, which is the long-standing 'CD quality' benchmark for MP3, though modern listeners may prefer 192k or 320k for critical audio. One key limitation: 3G2 does not support multiple audio tracks or subtitles, so there is no concern about selecting the wrong track — the single audio stream will always be used. Chapter markers and advanced container metadata from 3G2 are not preserved in MP3. If the source 3G2 file uses MJPEG video or an unusual audio codec variant from a niche CDMA handset, FFmpeg should still handle decoding correctly, but the audio re-encode stage may reflect any artifacts already present in the source.