Initializing... drag & drop files here
Supports: DV
A .dv file is a bare Digital Video elementary stream — the bytes that came off a MiniDV, DVCAM, DVCPRO, or Digital8 tape over FireWire, with no real container around them. That is why players guess wrong about its frame rate and aspect ratio, and why editors sometimes refuse it outright. MKV (Matroska) is the opposite: an open, royalty-free container designed to carry an unlimited number of video, audio, and subtitle tracks along with chapters, attachments, and proper timing metadata. Wrapping a tape transfer in MKV gives it a home that will still be readable in twenty years, which is the usual reason people convert in this direction.
| Property | Value |
|---|---|
| Standard | IEC 61834 (consumer DV); SMPTE 314M covers the DVCAM and DVCPRO 25/50 Mbit/s variants |
| Launched | 1995, by a consortium of camera makers led by Sony and Panasonic |
| Video coding | Intraframe DCT, fixed rate — every frame compressed independently |
| Video bit rate | About 25 Mbit/s, plus roughly 1.5 Mbit/s of audio |
| Frame size and rate | 720x480 at 29.97 fps (NTSC) or 720x576 at 25 fps (PAL) |
| Scanning | Interlaced; two fields per frame, 13.5 MHz luma sampling per Rec. 601 |
| Chroma subsampling | 4:1:1 on NTSC DV, 4:2:0 on PAL DV (DVCPRO50 and DVCPRO HD use 4:2:2) |
| Audio | 48 kHz 16-bit stereo Linear PCM, or four non-linear 12-bit channels at 32 kHz |
| Container | None in a raw .dv file; commonly also seen wrapped in AVI or QuickTime |
| Typical size | Roughly 13 GB per hour of footage |
| Best for | Being the capture master; almost nothing plays it natively today |
| Property | Value |
|---|---|
| Standard | RFC 9559, published October 2024, built on EBML (RFC 8794) |
| Started | Announced 6 December 2002 by Steve Lhomme; open and royalty-free throughout |
| Structure | EBML — a binary, extensible, tag-length-value structure derived from XML thinking |
| Video coding | Container-agnostic; this converter writes H.264 by default |
| Audio | Container-agnostic; AAC by default here, with FLAC and PCM available for archival |
| Track support | Unlimited video, audio and subtitle tracks, plus chapters and file attachments |
| Related extensions | .mkv for video, .mka for audio-only, .mks for subtitles alone |
| Native browser support | None — MKV is not a web delivery format; use MP4 or WebM for that |
| Best for | Local playback in VLC/mpv/Plex, and as an archival master container |
.dv file onto the page or click "+ Add Files" to browse. The picker here accepts .dv only; queue a stack of digitised tapes and each becomes its own MKV with the same settings.It re-encodes. The DV video is decoded and encoded again — H.264 by default — and the audio likewise, and the results are muxed into the MKV. Matroska can technically carry a raw DV track, but a file like that needs a DV decoder to play, which defeats most of the point of converting. If your priority is avoiding a second lossy generation, set Video Codec to HuffYUV and Audio Codec to a PCM variant: the encode is then mathematically lossless, so nothing new is discarded even though the file is still being re-encoded rather than copied.
MKV is the stronger archival container and MP4 is the stronger distribution one. MKV is an open, royalty-free specification published as RFC 9559, it holds unlimited tracks, chapters and attachments, and it happily carries lossless video and audio codecs that MP4 handles awkwardly or not at all. MP4 wins on reach: phones, browsers, smart TVs, and editing software all take it without argument. The common pattern is an MKV master per tape plus an MP4 copy for everyday watching. The container itself does not affect picture quality — the codec and the quality setting in step 2 do.
Yes. DV from camcorders is interlaced standard-definition video following Rec. 601, and this converter does not apply any deinterlacing filter, so both fields of every frame are carried through. On a computer or phone that shows up as comb-tooth lines along moving edges. That is the right outcome for an archival file, because deinterlacing throws away half the temporal information and cannot be undone. Do it as a deliberate step later if you need a progressive viewing copy.
DV carries Linear PCM — typically 16-bit stereo at 48 kHz, or four non-linear 12-bit channels at 32 kHz in the alternate four-channel mode. By default this converter encodes it to AAC, which is small and plays everywhere but is lossy. Open the Audio Codec dropdown and pick a PCM option to keep the samples bit-for-bit, or FLAC to compress them losslessly at roughly half the size. Matroska handles all three without complaint, which is one of the concrete advantages it has over MP4 for this job.
.dv file?Because DV has no interframe compression and H.264 has a great deal of it. DV encodes every frame independently at a fixed 25 Mbit/s regardless of what is on screen, so a static shot of a wall costs exactly as much as a fast pan. H.264 predicts each frame from its neighbours and spends bits only where the picture changes. On typical camcorder footage that is a very large saving at the same perceived quality — which is also why choosing HuffYUV instead produces a file bigger than the source.
VLC, mpv, MPC-HC, Plex, Jellyfin, Kodi and most modern smart TVs read MKV directly. Windows 10 and 11 play it in the built-in Media Player. What will not play it is a web browser via a plain <video> tag, because MKV was never adopted as a web delivery format — WebM is the Matroska-derived subset browsers actually implement. If you need something that opens by double-clicking on any machine including phones, DV to MP4 is the safer target.
.avi file rather than a .dv. Does that matter?It changes which page you use, not the result. FireWire capture tools on Windows commonly write DV-AVI — the same DV video and PCM audio inside an AVI container — while Mac tools often write DV-in-QuickTime. This page's picker accepts .dv only, so send a DV-AVI file through AVI to MKV instead. The decoded frames are identical, so the MKV you get is the same either way.
Your .dv upload travels over an encrypted connection, is processed on our servers, and is deleted automatically after a few hours along with the MKV we produced. Nothing is shared or made public, there is no sign-up, and no watermark is added. The one thing worth planning around is upload time: at roughly 13 GB per hour of tape, a full reel is a large transfer, so trimming to the section you need — or converting tape by tape — keeps each job comfortable. If you also want a wrapper that older Windows-era editing tools understand, DV to AVI targets that.