Initializing... drag & drop files here
Supports: DV
An .ogv file is an Ogg container with a video stream in it, and on this page that stream can be one of two very different things. The Video Codec dropdown opens on VP8 and also offers Theora, and the choice changes what the file is — not just how it compresses. It also decides which of the quality controls on the page actually work. Everything else about converting a DV tape capture is straightforward; this one decision is not, so it goes first.
| VP8 (opens here) | Theora | |
|---|---|---|
| Stream identifier written into the Ogg header | OVP80 |
theora |
| Standardisation of this mapping | An implemented but never widely adopted Ogg mapping — Google took VP8 to Matroska/WebM instead | The original Ogg video codec, bitstream frozen June 2004 |
| Software that reliably reads it | ffmpeg-based players (VLC, MPV) and little else | Anything that has ever supported Ogg video |
| Constant Quality slider | Renders but does nothing — see below | Works. A real 0–10 libtheora scale, opening at 7 |
| Constraint Quality / Constant Bitrate | Offered | Not offered when Theora is selected |
| Size on our 4-second DV test clip | 1,030,261 bytes at a 2 Mbit/s target | 1,035,180 bytes at quality 7 |
| Browser playback in 2026 | None — no browser implements the Ogg VP8 mapping | None — Chromium removed Theora in 123, Firefox disabled it by default in 126, Safari never shipped it |
Two things fall out of that table. First, at comparable settings the two codecs produced files within half a percent of each other on our test, so size is not the deciding factor. Second, neither choice gives you a browser-playable file, which is worth knowing before you build a workflow around this format. Theora is the safer pick for compatibility with desktop and open-source tooling; VP8 is the default and encodes faster.
When VP8 is selected, the Constant Quality mode shows a CRF slider running 16–63 and opening at 30. It looks exactly like the working CRF control on an H.264 or AV1 target. It is not one.
VP8 has no CRF mode in this pipeline, so selecting Constant Quality emits neither a quality value nor a bitrate — and libvpx, given nothing, falls back to its own default. The encoder log says so out loud: "Bitrate not specified for constrained quality mode, using default of 256kbit/sec." On our 4-second DV clip that produced 221,994 bytes against 1,030,261 bytes for the same source at a real 2 Mbit/s target — roughly a fifth of the size, with the picture quality to match.
Use Quality Preset, Constraint Quality, Variable Bitrate, Constant Bitrate or Specific file size instead. Or select Theora, where the quality slider is genuinely wired up.
.dv capture onto the page or click "+ Add Files"; several clips can be queued and share the same settings. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.HH:MM:SS.sss, which is useful for pulling one scene out of a full tape capture. Click Convert to download.DV is one of the formats where "just leave the resolution alone" is real advice rather than laziness. A widescreen NTSC DV frame is stored as 720 × 480 with a pixel aspect ratio of 32:27, which is what makes it display as 16:9 despite its 3:2 pixel grid. PAL DV does the same thing at 720 × 576.
We measured both paths on a 720 × 480 anamorphic source:
| Setting | Output frame | Stored pixel aspect | Displayed aspect |
|---|---|---|---|
| Video resolution → Keep original | 720 × 480 | 32:27 (preserved) | 16:9 — correct |
| Video resolution → 540 × 360 | 540 × 360 | 1:1 (flattened) | 3:2 — squashed |
Any resize flattens the pixel aspect ratio to square, so the picture ends up horizontally compressed. If you need a smaller frame from anamorphic DV, do the arithmetic yourself and enter an explicit Width × Height that already accounts for the stretch — for 16:9 NTSC DV that means something like 854 × 480 rather than 720 × 480 scaled down proportionally.
This is the honest summary. Theora was the codec the Ogg video format was built for, and no current browser decodes it: Chromium removed it in version 123 after disabling it by default in 120, Firefox disabled it by default in 126, and Safari never implemented it at all. The VP8-in-Ogg mapping never got browser support either — Google shipped VP8 in Matroska as WebM specifically to avoid a proliferation of container-codec combinations, and browser vendors followed that instead.
So if the destination is a web page, use DV to WebM, which defaults to VP9 (with VP8 and AV1 also offered) in the container browsers actually implement, or DV to MP4 for the H.264 file that plays on everything including phones. Reach for OGV when a specific piece of open-source software, a Wikimedia-style archive requirement or a legacy pipeline asks for it by name.
It is the raw DIF stream a MiniDV camcorder or capture card writes: intra-frame DCT-compressed video with uncompressed PCM audio interleaved into the same data blocks. The consumer specification is IEC 61834; the professional DVCAM and DVCPRO variants are SMPTE 314M, which defines 25 Mbit/s and 50 Mbit/s data structures. Our PAL test capture measured a 28.8 Mbit/s stream rate overall — the video payload is 25 Mbit/s and the rest is audio, subcode and auxiliary data.
Yes. DV carries uncompressed PCM audio, usually 48 kHz 16-bit stereo, and the conversion re-encodes it to whatever you choose in the Audio Codec dropdown — Vorbis by default, with FLAC, Opus and Speex also listed. Vorbis is the conventional partner for Ogg video and is what most software expects to find. Pick FLAC if you want the audio kept lossless and do not mind the size, and avoid Speex: in our testing that encoder produced a stream with no audio data in it.
No. There is no deinterlacing step in this pipeline, so a DV capture shot in an interlaced mode arrives in the OGV with its fields woven together and the combing visible on anything that moved. This is the single most common complaint about converting tape footage, and the fix is upstream: deinterlace in a video editor and convert the progressive result, rather than expecting the converter to guess.
Almost certainly because the player is ignoring the pixel aspect ratio rather than because the conversion broke it. DV stores non-square pixels — 32:27 for widescreen NTSC — and a player that assumes square pixels will show a 720 × 480 frame as 3:2 instead of 16:9. ffmpeg-based players read the flag correctly. If a specific target ignores it, enter an explicit Width × Height that bakes the correction into the pixel grid.
Yes, and it is a better codec at the same bitrate — but note one detail about sample rates. Opus has no 44.1 kHz mode at all; the format is defined for 8, 12, 16, 24 and 48 kHz. The pipeline handles this for you by snapping a 44.1 kHz request to 48 kHz rather than failing, and DV audio is normally already 48 kHz, so in practice this conversion never hits the issue.
On our test they were effectively tied: 1,030,261 bytes for VP8 at a 2 Mbit/s target versus 1,035,180 bytes for Theora at quality 7, on the same 4-second 720 × 480 clip. VP8 is the more modern codec and should win at low bitrates on longer, more varied material, but for standard-definition tape footage the difference is not the reason to pick one. Compatibility is — and there Theora, being the codec Ogg video was designed around, is the safer choice.
Not directly, and it is worth knowing what you are starting from. NTSC DV samples colour at 4:1:1 — a quarter of the horizontal colour resolution — while PAL DV uses 4:2:0. Both VP8 and Theora encode in 4:2:0 here, so PAL material passes through at matched chroma while NTSC material is resampled from 4:1:1. Neither reconstructs detail the tape never held, which is why DV footage keys and chroma-corrects badly regardless of what you convert it to.
There is no per-file cap on the page, and DV is bulky — our PAL capture measured a 28.8 Mbit/s stream rate, which works out at roughly 13 GB per hour of tape — so the real constraint is upload size and time rather than anything on our side. For a full tape it is usually faster to trim first: use the Trim → Time Range fields to take the section you need, or split the capture locally and upload the part that matters.
Not on this page — the upload validator matches on the extension, so a DV-in-AVI capture needs to go through an AVI tool instead. The stream inside is the same DIF data, so the conversion result is equivalent. If you have a choice at capture time, writing a raw .dv file rather than an AVI wrapper keeps the timecode and audio-lock information that the DV format carries natively.