Initializing... drag & drop files here
Supports: CR2
An .ogv is an Ogg bitstream carrying video, registered by the IETF as the video/ogg media type in RFC 5334 back in September 2008. Turning a Canon raw into one means rendering the photograph and encoding it as a clip that is held on screen for a duration you choose. The choice that actually matters here is the codec inside: VP8, which is preselected, or Theora, which is the codec the Ogg video type was originally registered around. Both are royalty-free and openly published, so the decision comes down to what is going to open the file.
| Property | Theora | VP8 |
|---|---|---|
| Developed by | The Xiph.Org Foundation | On2, then Google, which released it openly in 2010 |
| Derived from | On2's VP3 codec, which Theora is directly based on | On2's later VP-series work |
| Specification | Bitstream frozen after libtheora 1.0 alpha 3 in 2004 | Documented by the IETF as RFC 6386, November 2011 |
| Licence | BSD-style, free for commercial and non-commercial use | Royalty-free and openly published |
| Named in the video/ogg registration | Yes, alongside Dirac | No — it postdates RFC 5334 |
| Native home container | Ogg | WebM, though Ogg carries it as well |
| Compression efficiency | Lower; it is a codec of the early 2000s | Higher at the same visual quality |
| Selected here by default | No | Yes |
| Quality controls available here | Quality Preset and Constant Quality | Quality Preset, Constant Quality and Constraint Quality |
.ogv, which historically meant Theora video with Vorbis audio..cr2 onto the page or click "+ Add Files". With several queued, Merge strategy picks between one combined clip ("Merge images") and one file per photograph ("Video per image")..ogv. It is uploaded over an encrypted connection, converted on our servers and deleted automatically a few hours later — no sign-up, no watermark.| Container | Codecs it normally carries | Worth choosing when |
|---|---|---|
| OGV (Ogg) | Theora or VP8 video with Vorbis or Opus audio | Something specifically asks for Ogg, or you are feeding a Xiph-based workflow |
| WebM | VP8, VP9 or AV1 with Vorbis or Opus | The clip is going into a web page — MDN's own guidance is that you are typically better off with WebM than Ogg |
| MP4 | Usually H.264 with AAC | The file has to play on phones, in messaging apps and on social platforms |
| MPG | MPEG-1 or MPEG-2 in a program stream | DVD authoring or legacy broadcast equipment |
Because it is the better codec of the two and is decoded by every current browser. Theora's bitstream was frozen in 2004 and it is directly derived from On2's VP3, so it carries the efficiency of that era; VP8 came later, was documented by the IETF as RFC 6386, and produces noticeably smaller files at the same quality. Theora remains one click away for the cases that genuinely need it.
Yes. Ogg is a container and is agnostic about what it transports, and VP8 in Ogg is a combination current browsers handle. It is worth knowing that the video/ogg registration in RFC 5334 predates VP8 and names Theora and Dirac in its list of video codecs, so a very old or very strict Ogg tool may expect Theora specifically. If you are handing the file to something ancient, switch the codec.
For the open web, WebM is the more sensible default — Mozilla's own container guidance is that Ogg never gained the breadth of support that would make it a first choice, and that you are typically better off with WebM unless you need to reach very old browser versions. Ogg is the right answer when a specification, an institution or an existing pipeline asks for it by name. If the web is your target, CR2 to WebM is the direct route.
Because a photograph has no motion to sample. The picture is encoded once, looped, and stopped after the duration you set, so a five-second clip is five identical frames. Any editor will re-time it to a conventional rate if something downstream wants one, and re-encoding identical frames costs almost nothing.
There is nothing to encode. A still image carries no audio, so no audio stream is written rather than a silent one. The Audio Codec list still shows what Ogg expects — Vorbis by default, with Opus, Speex and FLAC alongside it. If you add a soundtrack later, Vorbis or Opus are the codecs an Ogg file should be carrying.
Because that mode does not apply to the Theora encoder, so the interface removes it rather than offering a control that would be ignored. With Theora selected you have the Quality Preset and Constant Quality; with VP8 selected, Constraint Quality is available as well. This is normal behaviour across the site — the option list reflects what the chosen codec can actually do.
The photograph's own dimensions unless you set otherwise, with the frame prepared at no more than 4096 pixels on its long edge before encoding — so a high-resolution modern raw is scaled down to fit. For web use you almost certainly want something far smaller: pick a Fixed Resolution such as 1920 x 1080, or set Width x Height in Pixels, rather than publishing a clip made from a full-size sensor frame.
Yes, and for most purposes you should. CR2 to MP4 produces a clip that plays on phones, in browsers and on social platforms without anyone thinking about codecs, and OGV to MP4 converts an Ogg file you already have. Reach for OGV when something has asked for it specifically; reach for MP4 when the file simply has to work.