What is an OGG file?

OGG is a container: a wrapper that holds streams encoded by something else. It is used for the web and handing a finished file over.

The extension is .ogg, and the full name is Ogg Audio. Both matter less than what the file can hold, which is what the rest of this page is about.

Xiph.Org published it in 2000. The specification is RFC 3533.

Age is worth knowing here for one practical reason: the older a format is, the more programs have had time to learn it.

It is published in full, so anyone can implement it from the document rather than by inspection, which is why it turns up in so many programs and why files written twenty years ago still open. A published specification is not the same thing as a royalty-free one: where a format wraps a codec, the patent licensing is a separate question the standard does not settle.

It usually holds Vorbis, Opus and FLAC. This is the distinction behind most "why will this not play" questions: two files with the same extension can contain entirely different encodings, and a player that refuses one may be perfectly happy with the other.

It also explains why changing container is often fast and lossless while changing codec is neither. Moving the same stream into a different box rewrites the box; re-encoding rewrites the picture.

OGG can hold a layout that lets it start playing before it has finished arriving.

That matters mostly when converting: whatever the target cannot hold is dropped, usually without a warning.

Audacity, VLC and foobar2000 read it, and so do most programs of the same kind.

If a file will not open, the format is rarely the problem — it is more often that the program predates it. Converting to something older is the reliable way past that, and it is what the rest of this site is for.

Current browsers read it; older ones do not.

Where support is uneven, serving a second format alongside it is the usual answer — the browser takes the one it understands and nobody is left out.

OGG can hold document properties.

Whether any of it survives a conversion depends entirely on the target, and the honest answer is usually "some of it".

OGG is meant to be handed over rather than worked in. Editing one is possible and rarely pleasant; the sane approach is to change the source and export again.

The recurring complaints: support outside its home ground is uneven.

None of these is a reason to avoid the format. They are the things worth knowing before you are surprised by one, which is a different claim and a more useful one.

Ogg is a container, not a compression method. A file ending in `.ogg` most often holds Vorbis audio, but it can hold Opus, FLAC, Speex or even video, and nothing in the name distinguishes them. This is the single most common source of confusion around the format.

The Xiph.Org Foundation, which maintains it, asked for `.oga` for audio and `.ogv` for video to reduce the ambiguity. Almost nobody adopted the convention, so `.ogg` remains a file whose contents have to be inspected rather than assumed. If a player refuses one, the codec inside is the thing to check.

Ogg and Vorbis were created in the late 1990s specifically because MP3 was patent-encumbered and every encoder required a licence. That was a genuine obstacle for open-source software and for anyone shipping a product without a legal department.

So the format exists as an answer to a licensing problem rather than a technical one, and it succeeded on those terms. Its descendants are everywhere: Opus is the codec inside every browser call, and the container mechanics developed here fed into WebM.

Vorbis was competitive with and generally better than MP3 at the same bitrate, particularly below 128 kbps. For a decade it was the sensible free choice and it is still perfectly good audio — a Vorbis file from 2008 sounds exactly as it did.

It has been superseded, though, and not narrowly. Opus beats it at every bitrate, comes from the same organisation, and is equally free. There is no remaining reason to encode new audio as Vorbis, which makes a `.ogg` holding it a file to keep rather than a format to choose.

Video games, overwhelmingly. Ogg Vorbis became the standard for game audio because it was free to use commercially, and unpacking the assets of almost any game from the last twenty years turns up folders of them. Unity and Godot still use it by default.

Beyond that: Spotify streamed Vorbis for years, Wikipedia and Wikimedia host audio in it on principle, older Android recordings used it, and a scattering of open-source applications produce it. It is a format encountered rather than chosen.

Ogg uses Vorbis comments — simple name-and-value pairs with no fixed list of permitted fields. Title, artist and album are conventional, but anything can be added, and unlike ID3 there is no fixed-size structure to work around.

Cover art is the awkward part. It is stored as a base64-encoded image inside a comment field, which works but is a convention retrofitted onto a design that did not anticipate it. Some players show it and some do not, which is why an Ogg with artwork sometimes appears to have none.

The container interleaves data into small pages, each self-describing enough that a decoder joining partway can find its footing quickly. It was built for internet radio at a time when connections dropped constantly, and it handles being cut into and resumed well.

A useful consequence is that Ogg files concatenate: joining two together with nothing more than a file copy usually produces a playable file containing both. That is unusual and is why the format persists in streaming and game-audio pipelines where files are assembled programmatically.

Apple, most notably and for a long time — QuickTime and iOS have historically not handled Ogg without third-party software, which is a large part of why the format never reached general consumers. Also most car stereos, older hardware players, and a fair number of upload forms.

Everything else copes: every browser, VLC, Android, Windows since version 10, and essentially all desktop media software. As with the other formats on this site, the question before converting is whether the destination is really on the short list of things that cannot.

To MP3 when the destination is old hardware, accepting that Vorbis to MP3 is lossy to lossy and costs a generation — use 192 kbps or higher so it stays inaudible. To WAV when a transcription tool or an audio editor wants uncompressed input.

To Opus if you simply want the same audio smaller, though be clear about what that is: it is another lossy re-encode, so it makes sense for a file that is too large to store and not for a file that is merely old. A Vorbis file that plays where it needs to play is best left alone.

The most common reason anyone converts Ogg in bulk is extracted game assets — hundreds or thousands of short files, often needed as WAV for use in another engine or as MP3 for something that only reads that.

Because the conversion here runs in the browser, a batch of a thousand short files costs no upload and joins no queue; it costs processor time on your own machine. That is the difference between a job that finishes while you do something else and one that hits a service’s file-count limit at item fifty.