Convert OPUS to OGG

Converting OPUS to OGG changes the extension and very little else: both names describe an Opus stream in an Ogg container, and this page re-encodes to produce one from the other. Before you convert a batch, read the first section — for most readers a rename is the correct and lossless answer.

  • Where it runs In your browser. The file is never uploaded.
  • Lossy Some detail is traded for size. OGG cannot hold everything an OPUS can.
  • File size limit Up to 100 MB per file, free, without an account.
  • Worth knowing Both formats are compressed, so this is a second round of compression on audio that has already lost detail. Pick the highest quality band if the result is going to be edited or converted again.

Up to 100 files at once. Mixed formats are fine.

The two extensions describe the same file

Ogg is a container and Opus is a codec that lives inside it. A `.opus` file is an Ogg container holding an Opus stream, and so is the `.ogg` file this page produces — the targets are defined identically in the converter and use the same muxer. Nothing structural distinguishes the input from the output.

The names diverged by convention rather than by specification. RFC 7845 defines Opus in Ogg and permits either extension; practice settled on `.opus` for Opus and `.ogg` for the older Vorbis pairing, because `.ogg` had already meant Vorbis for a decade by the time Opus appeared. So a program that accepts one and refuses the other is following a naming habit, not reading the file.

Rename it first, and only convert if that fails

Change the extension from `.opus` to `.ogg` and try again. This is not a workaround: the resulting file is a correctly named, entirely valid Ogg file, and it is bit-for-bit the audio you started with. Upload forms, asset importers, build scripts and content-type checks are the usual offenders, and they all pass once the name matches the list they were written against.

If the software then plays or accepts the file, you are finished and you have lost nothing. If it fails a second time with a message about the codec rather than the format, the problem is genuinely Vorbis and the next section applies. Converting first and discovering afterwards that a rename would have done is a generation of loss paid for nothing.

This page re-encodes, and cannot do otherwise

It would be reasonable to expect that producing an Ogg from an Opus file could merely relabel the container without touching the samples, and some command-line tools can do exactly that. This converter cannot. A bitrate is supplied to the encoder for every compressed target, which disables the library's packet-copy shortcut, so the audio is decoded to samples and encoded again on every run.

The consequence is a second round of lossy compression on audio that was already lossy — real, usually inaudible at the top band, and completely avoidable by renaming. Where a bit-exact repackaging is genuinely needed, a tool that can copy packets is the right instrument. That is a limitation of this path and it is better stated than discovered.

If the tool needs Vorbis, nothing here will satisfy it

A minority of readers have a real codec problem rather than a naming one. Some older game engines, some archival ingest validators and some free-software build checks look inside the file and require a Vorbis stream specifically. For them, an Ogg holding Opus is the wrong file however it is named.

This converter has no Vorbis encoder, so no page on this site can produce one. The honest answer is a desktop encoder that can — the reference tools, or any general-purpose media converter — and it is worth confirming that Vorbis really is the requirement first, since a surprising number of "Vorbis only" claims turn out to be extension checks that a rename resolves. Read the error message rather than the documentation.

Where the .opus files came from, and why the lists are stale

Messaging platforms record voice notes in Opus. Download tools produce it because it is the best stream available without re-encoding. Web video carries it, so audio extracted from a browser is usually Opus. All three have become common in the last decade, and all three write the `.opus` name.

The software refusing them is generally older than that. An extension allow-list written in 2012 has `.ogg` on it and cannot have `.opus`, and nobody revisits such a list until somebody complains. That is why the rename works so reliably: the decoder underneath has supported Opus for years, and the only thing standing in the way is a string comparison written before the format existed.

If you convert anyway, take the top band

The three bands resolve inside the encoder: Small file writes 38 kbps, Balanced 64 and High quality 128. For this pair the choice is not really open. You are re-encoding audio that has already been compressed, and the only defence against the second pass being audible is to give the encoder enough room that it adds almost nothing of its own.

Choosing a lower band would compound the loss to save bytes you were not short of, since the reason for the conversion is a file name. If the original was itself encoded above 128 kbps, the output will be slightly larger than the input as well as slightly worse, which is a fair summary of what this conversion is. Renaming remains the better answer wherever it works.

Tags cross unchanged, which is the one free part

Both sides of this conversion carry metadata as Vorbis comments — a plain list of uppercase keys with text values in the Ogg stream header. Title, artist, album, date, licence, description and any custom field you invented arrive spelled exactly as they were, because nothing has to be translated between two different schemes.

Embedded artwork travels as a METADATA_BLOCK_PICTURE comment at both ends, which is the standard encoding and what foobar2000, VLC and the media servers read. It is the one aspect of this pair where nothing is lost and nothing has to be re-entered, and it applies equally to a renamed file, which keeps everything by definition.

The content type a server should send for either name

If the destination is a web server rather than a program on your desk, the type header matters more than the extension. The registry records `audio/ogg` for `.ogg` and `audio/opus` for `.opus`, and a browser picking between source elements uses the declared type to decide what to attempt before it downloads anything.

A misconfigured server sending `application/octet-stream` will cause exactly the symptom that brought most readers here — a file that plays locally and does nothing on a page — and no conversion fixes it. Check the header the server actually sends before assuming the file is at fault, because renaming and re-encoding are both irrelevant if the type is wrong.

Converting a batch, with nothing downloaded and nothing sent

Opus is the only audio target here that fetches no encoder, since every browser implemented it for calls, and it is also the decoder for the source. A conversion therefore begins the moment a file lands and the network stays idle throughout, which is easy to confirm in developer tools.

Files are capped at 100 MB each and a hundred can be dropped in one pass, coming back as a ZIP. For this pair the more useful advice is still the cheapest one: rename a copy of a single file, feed it to whatever rejected it, and only reach for the batch converter if that genuinely fails.

How to turn an OPUS file into an OGG file

  1. Rename one file from .opus to .ogg and try it — this works far more often than not.
  2. If it is still refused, drop the OPUS files here and pick High quality.
  3. Download the OGG, or take the batch back together as a ZIP.

OPUS and OGG: one codec, one container, two file names

OPUS compared with OGG
OPUSOGG
Full nameOpus AudioOgg Audio
File extension.opus.ogg, .oga
Media typeaudio/opusaudio/ogg
CompressionLossy — file size is bought with qualityLossy — file size is bought with quality
First published20122000
Published byXiph.OrgXiph.Org
SpecificationRFC 6716RFC 3533
LicensingOpen standardOpen standard
Standing todayCurrentCurrent
Audio channelsup to 255
Opens in a browserCurrent browsersCurrent browsers
Considered insteadAAC, MP3MP3, AAC

Opening the result

OGG is a container rather than a single format. What actually plays is the codec inside it — usually Vorbis, Opus and FLAC — which is why two files with the same extension can behave differently on the same device.

VLC and Audacity read both OPUS and OGG, so there is a way to check the result against the original without a second tool.

What each format is for

OPUS is Xiph.Org's format, published in 2012. The specification is RFC 6716, and it is worth reading if the file has to outlive the tool that wrote it.

OGG comes from Xiph.Org and dates from 2000, specified as RFC 3533. Audacity, VLC and foobar2000 all read it.

OPUS to OGG: renaming, Vorbis and what changes

Can I just rename the file from .opus to .ogg?

Usually, yes. Opus inside an Ogg container is exactly what RFC 7845 describes, and both extensions are valid for it. If the software is refusing the file on its name rather than its contents — which is what most upload forms and asset importers do — changing three characters is the entire fix and costs nothing. Try that before converting anything.

What does this conversion actually change?

The extension, and the generation. Both the .ogg and .opus targets here write an Opus stream inside an Ogg container with the same encoder, so the output is the same kind of file as the input — decoded and re-encoded, which adds a round of loss that a rename would not. There is no case where this produces a better file than the one you started with.

Will this give me Ogg Vorbis?

No. This converter writes Opus into Ogg and has no Vorbis encoder. If a tool genuinely requires Vorbis — some older game engines, some archival ingest paths, a validator that reads the codec rather than the name — no conversion on this site will satisfy it, and a desktop encoder that can produce Vorbis is the correct instrument. Saying so is more useful than letting you find out afterwards.

Why do programs reject .opus at all?

Because .ogg is twenty-five years old and .opus is not. Software written around a fixed list of extensions inherits that list from whenever it was written, and .ogg has been on every such list since 2000. It is a convention problem rather than a decoding problem — the same code path usually plays the file perfectly once the name gets past the check.

If I do convert, which quality band should I use?

High quality, which writes 128 kbps. You are re-encoding audio that has already been compressed once, and the only defence against the second pass being audible is to leave the encoder room. Choosing a lower band here compounds the loss for no benefit, since the reason you are converting is a file name rather than a size problem.

Does the file leave my machine?

No. Opus is the one audio target on this site that needs no encoder download, because every browser had to implement it for calls, and the decoder is the same one. The conversion starts immediately and the network stays idle throughout. Files are capped at 100 MB each and a hundred can be dropped at once.

More about these formats