Convert OGG to MP3 — Free Online Tool
Convert OGG (Vorbis/Opus) audio files to MP3 using FFmpeg in your browser — no upload required. OGG's Xiph.Org container is decoded and re-encoded via the LAME encoder to produce a universally compatible MP3 file, ideal for devices and platforms that don't support OGG playback.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your OGG 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
OGG files most commonly contain audio encoded with Vorbis or Opus codecs, neither of which can be stored in an MP3 container. This means a full transcode is required: FFmpeg decodes the OGG audio stream back to raw PCM audio, then re-encodes it using the libmp3lame encoder at 128k bitrate by default. Because both OGG/Vorbis and MP3 are lossy formats, this is a lossy-to-lossy conversion — each encoding step introduces some generation loss. The resulting MP3 file will play on virtually any device, media player, or platform. Note that OGG's chapter support is not carried over, as the MP3 container does not support chapters, and metadata tags are mapped from Vorbis comments to ID3 tags where fields align.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary — the open-source multimedia processing engine that handles all decoding, encoding, and container muxing in this conversion pipeline. |
-i input.ogg
|
Specifies the input file, which is an OGG container. FFmpeg will detect whether the stream inside is Vorbis, Opus, FLAC, or another supported OGG codec and select the appropriate decoder automatically. |
-c:a libmp3lame
|
Selects the LAME MP3 encoder for the audio stream. This is required because MP3 output mandates re-encoding — the Vorbis or Opus audio inside the OGG container cannot be directly remuxed into MP3 format. |
-b:a 128k
|
Sets the MP3 output bitrate to 128 kilobits per second using constant bitrate (CBR) encoding. 128k is the most universally compatible MP3 bitrate and provides acceptable quality for most listening scenarios; increase to 192k or 320k for higher fidelity at the cost of larger file size. |
output.mp3
|
Defines the output filename and format. The .mp3 extension tells FFmpeg to wrap the libmp3lame-encoded audio in an MP3 file, complete with ID3 tags mapped from the original OGG Vorbis comments. |
Common Use Cases
- Uploading game audio exports or sound effects (commonly distributed as OGG) to platforms like Spotify, SoundCloud, or podcast hosts that require MP3
- Playing OGG audiobooks or music downloads on older iPods, car stereos, or Bluetooth speakers that only support MP3 playback
- Converting OGG voice recordings from open-source communication tools like Mumble or older Discord exports into MP3 for archiving or sharing
- Preparing OGG music tracks from open-source games or creative commons libraries for use in video editing software that lacks OGG codec support
- Sending audio files to clients or colleagues who are on Windows systems where OGG playback is not natively supported without extra codecs
- Stripping an OGG file's container and re-encoding it as MP3 to meet submission requirements for radio stations or music licensing platforms
Frequently Asked Questions
Yes — this is a lossy-to-lossy transcode, which means audio quality degrades at each encoding stage. Your OGG file was already compressed with Vorbis or Opus, and converting it to MP3 means decoding that compressed audio and re-encoding it again with a different lossy algorithm. At 128k MP3 the result is generally acceptable for casual listening, but audiophiles will notice artifacts. If you have access to the original lossless source (WAV, FLAC), it's always better to encode MP3 directly from that instead.
Not exactly — Vorbis uses a variable quality scale (0–10) while MP3 uses a fixed bitrate (like 128k). Vorbis quality 4 produces roughly 128k average bitrate, which is why 128k is a reasonable MP3 target for this conversion. However, Vorbis at quality 4 is generally considered to sound better than MP3 at 128k due to its more modern psychoacoustic model, so the resulting MP3 may sound slightly inferior even at the same nominal bitrate.
Replace the '-b:a 128k' flag with a higher bitrate such as '-b:a 192k', '-b:a 256k', or '-b:a 320k'. For example: 'ffmpeg -i input.ogg -c:a libmp3lame -b:a 320k output.mp3'. 320k is the maximum standard MP3 bitrate and will produce the best possible output, though it still cannot exceed the quality of the original OGG source. Alternatively, you can use VBR encoding with '-q:a 0' (highest quality) instead of '-b:a' for a variable bitrate approach.
FFmpeg will automatically attempt to map Vorbis comment tags (the metadata format used in OGG files) to ID3 tags (the metadata format used in MP3 files). Common fields like TITLE, ARTIST, ALBUM, DATE, and TRACKNUMBER are mapped correctly in most cases. However, some OGG-specific or non-standard Vorbis tags may be dropped since the ID3 specification has a different set of defined fields. You can verify the output tags using a tool like Mp3tag after conversion.
No, the conversion process and command are identical regardless of whether your OGG file contains Vorbis or Opus audio. FFmpeg automatically detects the codec inside the OGG container and decodes it accordingly before re-encoding to MP3 with libmp3lame. Opus is actually a higher-quality codec than Vorbis at low bitrates, so converting an Opus OGG to 128k MP3 may result in a more noticeable quality drop than converting from Vorbis at a similar bitrate.
The command shown converts a single file, but you can adapt it for batch processing in a terminal. On Linux or macOS, run: 'for f in *.ogg; do ffmpeg -i "$f" -c:a libmp3lame -b:a 128k "${f%.ogg}.mp3"; done'. On Windows PowerShell, use: 'Get-ChildItem *.ogg | ForEach-Object { ffmpeg -i $_.FullName -c:a libmp3lame -b:a 128k ($_.BaseName + ".mp3") }'. The browser tool processes one file at a time, so local FFmpeg is the better option for large batch jobs.
Technical Notes
OGG is a container format, not a codec — it can carry Vorbis, Opus, FLAC, or even Speex streams, though Vorbis is most common. MP3 is both a codec and effectively its own container, encoded exclusively via the LAME encoder in FFmpeg (libmp3lame). Because neither Vorbis nor Opus audio is natively embeddable in an MP3 file, a full decode-and-reencode pipeline is mandatory — stream copying ('-c:a copy') is not possible here. The default 128k CBR output is compatible with essentially all MP3-capable hardware and software, but users with high-quality OGG sources should consider 192k or higher to minimize perceptible generation loss. OGG supports multiple audio tracks and chapters; MP3 supports neither, so any secondary audio tracks and chapter markers in the source OGG file will be silently dropped during conversion. ID3v2 tags will be written to the output MP3, preserving most common Vorbis comment fields, but cover art embedded in OGG (via the METADATA_BLOCK_PICTURE tag) may or may not transfer depending on the FFmpeg version — if album art preservation is critical, verify the output with an ID3 tag editor.