Cookies for analytics and advertising
We use cookies for analytics and advertising, both sent to Google. Refusing changes nothing you can see.Read the privacy page
Converting OGG to MP3 gets you a file that an iPhone, a car head unit and every player made in thirty years will accept, which is the entire reason anybody does it. What it costs depends on what is inside the Ogg: Vorbis or Opus means a second round of lossy compression, while FLAC inside Ogg means this MP3 is the first compression the recording has had.
Up to 100 files at once. Mixed formats are fine.
They convert one after another and download together as a ZIP.
OGG to MP3
Ogg is a container specified in RFC 3533 by Xiph.Org, and the registry records three codecs living inside it: Vorbis, Opus and FLAC. That is not a technicality — it is the single most useful thing to know before converting one. Vorbis and Opus are lossy, so an MP3 made from them is a second-generation copy. FLAC is lossless, so an MP3 made from FLAC-in-Ogg is a first-generation copy of untouched audio, and deserves a higher bitrate.
Most `.ogg` files in circulation hold Vorbis, because that pairing is old enough to have become the default meaning of the extension. Newer material — a browser recording, a modern game engine export — is more likely to be Opus, which usually takes the `.opus` extension but not always. Ten seconds in VLC's Codec Information panel settles it, and it is ten seconds well spent.
Ogg exists because Vorbis was designed in 2000 as a patent-free alternative to MP3, at a time when MP3 licensing was a genuine cost for anyone shipping software. That history is why you find it where free licensing mattered: game asset folders — Doom source ports, Minecraft, thousands of indie titles — Linux desktop sound themes, Audacity exports, Wikimedia Commons, Bandcamp's lossless download options and academic corpora.
It stops working the moment the file leaves that world. Apple has never supported it on iOS, macOS or Safari, and the registry marks its browser support as patchy for that reason. Car head units and standalone players mostly ignore it. Windows plays it in some applications and not in Windows Media Player. Nothing is broken; the format was simply never adopted by the companies that decide what hardware plays.
This is the common case and it is a second lossy encode. Vorbis already discarded parts of the recording permanently, and the MP3 encoder discards a second helping using different rules — it does not know which parts of the signal are original and which are artefacts of the first pass, so it spends bits on both.
The damage is smaller than the description makes it sound. On a Vorbis file at a typical quality-5 setting re-encoded at 160 kbps, most listeners hear nothing on ordinary equipment; what shows first is cymbals, applause and reverb tails turning slightly grainy. Convert once, from the Ogg you have, and keep it. Converting an MP3 you made last year into something else is where this genuinely degrades.
FLAC inside Ogg is uncommon and not rare — Bandcamp offers it, some archival projects use it, and a handful of Linux tools default to it. If that is what you have, everything above about a second encode is irrelevant to you. You are compressing untouched audio for the first time.
Two things follow. Pick High quality, which writes 320 kbps, because there is genuine detail to preserve and you have no reason to economise. And keep the original: the Ogg is your master copy, the MP3 is a delivery copy, and once you have deleted the FLAC there is no way back to it. The size difference will tell you which situation you are in before you even open the file.
The Quality control resolves to real numbers: Small file is 96 kbps, Balanced is 160 kbps and High quality is 320 kbps, the MP3 ceiling. A four-minute track lands near 2.9 MB, 4.8 MB and 9.6 MB.
Much of what arrives as Ogg is not music. Game sound effects, voice lines, narration and interface bleeps are short, mono and forgiving, and Small file at 96 kbps is more than they need — for a folder of two thousand effect files that difference is the whole storage budget. Reserve Balanced for music and ambience, and High quality for anything that will be edited after conversion or that came out of a FLAC-in-Ogg.
Ogg has no global metadata block; it stores tags as Vorbis-style comment headers attached to the stream, which is a plain list of uppercase key-value pairs — TITLE, ARTIST, ALBUM, ALBUMARTIST, TRACKNUMBER, TRACKTOTAL, GENRE, DATE, COMMENT, LYRICS. All of those map cleanly onto ID3v2 frames and come across intact.
Cover art is stored in Ogg as a METADATA_BLOCK_PICTURE comment holding an encoded picture block, and it is rewritten as an ID3v2 APIC frame in the MP3, so a phone or car display shows the artwork afterwards. What is dropped is the long tail: custom comment fields a specific tool invented, which have no ID3 equivalent and are removed rather than transliterated into frames nothing reads.
Vorbis is popular in games partly because it loops cleanly — an ambience track or a music bed can be authored to repeat with no seam, and many engines read loop points out of the Ogg's comment fields.
MP3 does not preserve that. The encoder works in fixed blocks, a recording rarely ends on a block boundary, and so a short run of silence is added at each end — a few dozen milliseconds, inaudible in a song and fatal to a seamless loop. There is no setting that removes it. A LAME tag can record how much was added, which is how gapless players trim it back off, and the MP3 muxer used here writes only a Xing frame — a frame count and a seek table, and nothing about the delay. If the audio is a loop, MP3 is the wrong target and the honest advice is to keep the Ogg for the engine and convert only what needs to leave it.
The decode uses your device's own codecs, which means the answer to "will this work" depends on the machine you are on rather than on anything this page controls. Opus is universal because every browser needed it for calls. Vorbis is widely but not uniformly supported, and support for FLAC inside Ogg is narrower still.
When the codec is missing, the conversion stops and says that nothing in the file could be converted and that it may use a codec this browser cannot read. That is a deliberate message rather than a silent half-result: a converter that produced an empty MP3 and called it a success would be worse than one that refuses. If you hit it, try the same file in a different browser before concluding the file is damaged.
Drop the directory in. Each file converts on its own and comes back in a single ZIP, with a 100 MB ceiling per file and a hundred files to a batch — the work runs on your processor, so there is no daily allowance to spend and no queue behind anyone else.
One caution specific to this source. Game folders contain thousands of very short files, and the drop zone takes a hundred at a time — anything past the hundredth is left out of the list rather than queued, so feed the directory through in slices instead of dragging all five thousand at once. And check the licence before republishing anything: an Ogg from a game install is still that game's asset, whatever format you convert it into.
| OGG | MP3 | |
|---|---|---|
| Full name | Ogg Audio | MPEG Audio Layer III |
| File extension | .ogg, .oga | .mp3 |
| Media type | audio/ogg | audio/mpeg |
| Compression | Lossy — file size is bought with quality | Lossy — file size is bought with quality |
| First published | 2000 | 1993 |
| Published by | Xiph.Org | Fraunhofer IIS |
| Specification | RFC 3533 | ISO/IEC 11172-3 |
| Licensing | Open standard | Open standard |
| Standing today | Current | Current |
| Audio channels | — | up to 2 |
| Opens in a browser | Current browsers | Every browser |
| Considered instead | AAC, OPUS | AAC, OPUS, FLAC |
MP3 has nowhere to put the document properties, so that goes no further than the OGG. Worth checking before the original is deleted, and worth knowing if the point was to strip it.
MP3 opens in every current browser. OGG has narrower browser support than that. If the file is going onto a web page or into a form, that is usually the whole reason for the conversion.
Audacity and VLC read both OGG and MP3, so there is a way to check the result against the original without a second tool.
OGG is Xiph.Org's format, published in 2000. The specification is RFC 3533, and it is worth reading if the file has to outlive the tool that wrote it.
MP3 comes from Fraunhofer IIS and dates from 1993, specified as ISO/IEC 11172-3. Audacity, VLC and iTunes all read it.
One of three things. Ogg is a container, and the registry lists Vorbis, Opus and FLAC as the codecs it carries. Vorbis is the historical default and what most `.ogg` files from games, Linux desktops and Wikimedia hold. Opus appears in newer files and normally uses the `.opus` extension, though not always. FLAC inside Ogg is rare but real. Which one you have decides whether converting to MP3 costs you a second round of compression or a first.
VLC will tell you: play the file, open Tools then Codec Information, and the codec line says Vorbis, Opus or FLAC. On Linux, `file` and `ffprobe` both name it in one line. Size is a weaker hint but a usable one — a four-minute FLAC-in-Ogg is twenty to thirty megabytes where the Vorbis equivalent is three to five.
Apple has never shipped Ogg support in iOS, macOS or Safari, and there is no setting that adds it. The registry marks Ogg as having patchy browser support for exactly this reason. It is a licensing-free format that Apple chose not to adopt, and the practical answer has always been to convert or to install a third-party player. MP3 is the conversion that needs no cooperation from anybody.
If the Ogg holds Vorbis or Opus, yes — two lossy encodes in a row, and the second one spends bits describing the first one's artefacts. At Balanced, which writes 160 kbps, that is inaudible for speech and game audio and just about detectable on music with a critical ear. If the Ogg holds FLAC, this is the first lossy encode the audio has ever had, and you should pick High quality at 320 kbps.
Yes. Ogg stores metadata as Vorbis-style comments — TITLE, ARTIST, ALBUM, TRACKNUMBER, GENRE, DATE and so on — and those are mapped onto ID3v2 frames in the MP3. Cover art stored as METADATA_BLOCK_PICTURE comes across as an ID3v2 APIC frame, which is what players read to show a cover. Non-standard comment fields that have no ID3 equivalent are dropped rather than written as junk.
No. Your device decodes the Ogg with the codec it already has, and the MP3 is written by a WebAssembly build of the LAME encoder inside the tab — no browser can encode MP3 on its own, which is the one piece of software this page downloads. There is no server involved, no account and no daily allowance, and the network tab of your developer tools will show you that during a conversion.