PicaJet
Search Build shortlist

Reference Formats

OGV

OGV is a free, patent-unencumbered container format from the Xiph.Org Foundation that wraps the Theora video codec with Vorbis or Opus audio, once promoted as a royalty-free alternative for HTML5 video.

Extension

.ogv

Full name

Ogg Video (Ogg container carrying Theora video, typically with Vorbis or Opus audio)

Introduced

2003 (Ogg container); 2004 (Theora video codec)

Vendor

Xiph.Org Foundation

What is inside the container

The Ogg container was released in 2003, with the Theora video codec — derived from On2's VP3 and released to the public domain — following in 2004; the .ogv extension specifically for video was standardized by Xiph.Org in 2007 to distinguish it from audio-only .ogg and .oga files. It carries no patent licensing burden by design, reflecting Xiph.Org's mission to keep core internet multimedia formats free of private patent control.

How to open it

Windows / macOS / Linux VLC Media Player plays OGV natively via its built-in Theora/Vorbis decoder support, the most reliable current playback option.
Command line (any OS) ffmpeg both decodes and encodes OGV: `ffmpeg -i input.ogv output.mp4` converts it to a modern, broadly compatible container.
In-browser playback where native support was dropped ogv.js, a JavaScript-based Theora/Vorbis decoder, can play OGV files inside browsers that no longer support the format natively.
Older browser versions (legacy reference only) Firefox and Chrome supported OGV natively for years during the HTML5-video format debates, before both removed native Theora decoding by 2024 — current browser versions require conversion or a JS decoder.

For archives

Treat any OGV holdings as a migration backlog rather than a stable delivery format — Chrome dropped native Theora support around version 123 in 2024 and Firefox has removed or is removing it as well, so files sitting untouched in a DAM are effectively unplayable in current browsers without conversion. Transcode legacy OGV assets to H.264 or AV1 in MP4/WebM for any content still needed for active delivery, and keep the original OGV only where it's the sole surviving source of a specific asset.

The Ogg container was released by the Xiph.Org Foundation in 2003, a non-profit built specifically to keep core internet multimedia formats free of patent control, and the Theora video codec that most commonly fills it followed in 2004 — derived from On2 Technologies’ VP3 codec, which On2 released to the public domain. The .ogv extension itself, distinguishing video-carrying Ogg files from audio-only .ogg and .oga files, wasn’t formalized as Xiph.Org’s naming convention until 2007.

OGV had a real moment of relevance during the early HTML5 video standardization debates, when browser makers were split between a patent-encumbered option (H.264) and a royalty-free alternative for the new

That niche status turned into a real preservation problem recently: Chrome dropped native Theora decoding starting around version 123 in early 2024, and Firefox has followed the same path, meaning current versions of both browsers no longer play OGV natively at all. For a DAM holding open-source project media or older web archives in this format, that’s a hard deadline rather than a theoretical concern — an OGV file that played fine in a browser two years ago may not play at all today without conversion, making OGV one of the clearer cases where “still technically valid” and “still actually usable” have diverged.

BrowserNative Theora/OGV support
FirefoxSupported for years during HTML5 debates; removed or removing native support
ChromeDropped native Theora decoding around version 123, early 2024
VLC / ffmpegStill decode OGV reliably, independent of browser support

Frequently asked

Can current browsers still play OGV files natively?

No, not reliably — Chrome dropped native Theora decoding around version 123 in early 2024, and Firefox has removed or is removing native support as well, so OGV files that used to play directly in a browser tab generally no longer do without a JavaScript decoder or conversion.

What codec is actually inside an OGV file?

Almost always Theora video, typically paired with Vorbis or Opus audio, all wrapped in the Ogg container developed by the Xiph.Org Foundation.

Why did our project end up with a library of OGV files?

OGV was actively promoted as the royalty-free HTML5 video option during the early 2010s browser format debates, and many open-source projects and web platforms of that era adopted it specifically to avoid H.264's licensing terms before WebM and H.264 ultimately won broader adoption.

Is there a licensing cost to using or converting OGV assets?

No — OGV was built by the Xiph.Org Foundation specifically to be free of patent licensing, and that remains true; there's no royalty consideration involved in transcoding or archiving it.

How do we play an OGV file today if VLC isn't an option?

ogv.js, a JavaScript-based Theora/Vorbis decoder, can play OGV files inside a web page even on browsers that no longer support the format natively — useful for embedding legacy content without a server-side conversion step.

Should we convert our entire OGV archive to MP4 now?

For any content still actively delivered or likely to be accessed by end users, yes — since neither Chrome nor Firefox play OGV natively anymore, converting to H.264 or AV1 in MP4/WebM is the practical way to keep that content actually usable rather than just technically preserved.

Is Theora, the codec inside OGV, still maintained at all?

Yes, in a limited sense — Xiph.Org released a Theora 1.2.0 update as recently as 2025, so the codec itself isn't abandoned even though the major browser vendors have moved on from supporting it natively.

What's the difference between .ogg, .oga, and .ogv extensions?

All three are Ogg-container files, but Xiph.Org's 2007 naming convention reserves .ogv for video content, .oga for audio-only content, and .ogg specifically for Vorbis audio — before 2007, everything was more loosely labeled .ogg regardless of content type.

Sources