Convert 3GPP to OGA — Free Online Tool

Convert 3GPP mobile video files to OGA audio by extracting and re-encoding the audio stream as Vorbis inside an Ogg container. This is ideal for salvaging audio from old mobile recordings while moving to a fully open, patent-free audio format.

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 or AMR audio paired with H.264 video, designed for 3G mobile networks with low-bitrate constraints. During this conversion, FFmpeg discards the video stream entirely and transcodes the audio — most commonly AAC — into Vorbis, a lossy open-source codec, wrapped in the OGA (Ogg Audio) container. Because AAC and Vorbis use different psychoacoustic compression models, this is a full decode-and-re-encode operation, not a simple remux. The Vorbis encoder uses a variable bitrate quality scale, so the output bitrate adapts to the complexity of the audio rather than being fixed. The result is an audio-only file with no video overhead, making it significantly smaller than the original 3GPP file.

What Each Flag Does

Flag What it does
ffmpeg Invokes the FFmpeg tool, which handles all decoding, audio stream extraction, Vorbis encoding, and Ogg container writing entirely within your browser via WebAssembly in this tool.
-i input.3gp Specifies the input 3GPP file. FFmpeg reads the container, identifies the video and audio streams inside (typically H.264 video and AAC or AMR audio), and prepares them for processing.
-c:a libvorbis Selects the libvorbis encoder for the audio output stream. This decodes the 3GPP's AAC (or AMR) audio to raw PCM and then re-encodes it as Ogg Vorbis, a patent-free, open-source lossy audio codec used as the default in the OGA format.
-q:a 4 Sets the Vorbis variable bitrate quality level to 4 on a 0–10 scale, targeting approximately 128–160 kbps. This is a sensible default for 3GPP source material, which rarely contains high-fidelity audio due to the low-bitrate constraints of 3G mobile encoding.
output.oga Defines the output filename and signals to FFmpeg that the result should be written as an OGA file — an audio-only Ogg container. The video stream from the 3GPP input is automatically dropped because OGA cannot carry video.

Common Use Cases

  • Extracting the audio from old mobile phone video clips recorded on 3G-era devices to archive them as standalone audio files
  • Converting 3GPP voice memos or call recordings into OGA format for use in open-source media players like VLC or Audacious that natively support Ogg Vorbis
  • Stripping the audio track from 3GPP video messages received via MMS to use in open-source or Linux-based multimedia projects
  • Preparing mobile field recordings captured on 3GPP-compatible devices for use in open-format audio archives or digital libraries that require patent-unencumbered formats
  • Reducing file size when sharing audio content originally recorded as 3GPP video, by removing the video stream and outputting a compact Vorbis-encoded OGA file
  • Migrating a collection of 3GPP mobile recordings to OGA as part of a workflow that avoids proprietary codecs like AAC in favor of fully free and open formats

Frequently Asked Questions

Yes, some quality loss is inevitable because this conversion transcodes from one lossy codec (AAC) to another (Vorbis). The original 3GPP file's AAC audio is fully decoded to raw PCM first, then re-encoded as Vorbis. That said, the default quality setting of -q:a 4 produces Vorbis output in the 128–160 kbps range, which is generally clean-sounding — and often higher quality than the low-bitrate AAC found in 3GPP files from 3G-era mobile devices. For typical voice recordings or mobile video audio, the perceptible difference is minimal.
OGA is strictly an audio-only container — it cannot store video streams. The conversion intentionally discards the video track and extracts only the audio. If you need to keep the video, you should convert to a format like OGV (Ogg Video) or MP4 instead. The OGA format is specifically designed for distributing audio content in the open Ogg ecosystem.
Adjust the -q:a value, which controls Vorbis variable bitrate quality on a scale from 0 (lowest) to 10 (highest). The default is 4, roughly equivalent to 128 kbps. For better quality, try -q:a 6 or -q:a 7 (around 192–224 kbps). For smaller files from low-quality 3GPP source audio, -q:a 2 or -q:a 3 is usually sufficient since the original mobile audio rarely benefits from high target quality settings.
Yes. On Linux or macOS, you can loop over files in a directory with a shell command like: for f in *.3gp; do ffmpeg -i "$f" -c:a libvorbis -q:a 4 "${f%.3gp}.oga"; done. On Windows, a similar loop works in PowerShell. This applies the same Vorbis encoding settings to every 3GPP file in the folder, which is useful when processing a large archive of old mobile recordings.
FFmpeg will attempt to copy metadata tags from the 3GPP container to the OGA output, and the Ogg Vorbis comment format supports common tags like TITLE, ARTIST, and DATE. However, 3GPP files from mobile devices often carry minimal or no metadata beyond technical stream information, so the OGA output may also have sparse tags. You can add or edit Vorbis comment tags after conversion using tools like EasyTag or the vorbiscomment command-line utility.
Yes. Opus is also valid inside an OGA container and generally outperforms Vorbis at lower bitrates, making it a strong choice given the typically low-bitrate audio found in 3GPP files. Replace -c:a libvorbis -q:a 4 with -c:a libopus -b:a 96k in the FFmpeg command. Note that Opus uses constant or average bitrate targeting (-b:a) rather than the Vorbis quality scale, so you specify a bitrate like 64k or 96k instead of a quality number.

Technical Notes

3GPP audio streams are most commonly encoded as AAC-LC or, in older recordings, AMR-NB (Adaptive Multi-Rate Narrowband), which is a codec optimized for voice at very low bitrates (as low as 4.75 kbps). When converting AMR audio to Vorbis, the quality ceiling is limited by the source — Vorbis at -q:a 4 will cleanly encode whatever PCM the AMR decoder outputs, but cannot reconstruct frequencies that AMR discarded during the original recording. The OGA container supports chapters (via Ogg skeleton metadata), though FFmpeg does not populate chapters from 3GPP sources automatically. Vorbis does not support more than two channels in most implementations, but 3GPP mobile audio is virtually always mono or stereo, so this is rarely a concern. The output OGA file will have no video stream, no subtitle data, and no secondary audio tracks — OGA is inherently single-stream audio. If the source 3GPP file used AAC at a very low bitrate (common at 32k or 48k for 3G video), setting Vorbis -q:a above 5 offers diminishing returns since the source fidelity is already limited.

Related Tools