Initializing... drag & drop files here
Supports: DV
.dv and DV-in-AVI files both work. Batch is supported, including multi-tape archive jobs.DV (Digital Video) is the tape format used by MiniDV camcorders from roughly 1995 to 2010 — the era of Sony Handycam, Canon Optura, Panasonic PV-GS, and JVC GR-D. When you captured a tape via FireWire (IEEE 1394) into Windows Movie Maker, iMovie HD, Adobe Premiere, or Sony Vegas, the result was a raw .dv or DV-in-AVI file at a locked ~25 Mbps intraframe-only bitrate — about 13 GB per hour of footage. HEVC (H.265) is the natural archival target: it's roughly 40-50% smaller than H.264 at the same visual quality, which collapses that 13 GB hour to ~600 MB - 1 GB without visible quality loss for SD content. For a tape collection, the storage difference adds up fast.
.dv is rejected outright by every consumer photo library.| Property | DV | HEVC (H.265) |
|---|---|---|
| Origin | DV consortium (Sony, Panasonic, JVC), 1995 | ITU-T / ISO/IEC, 2013 |
| Typical use | MiniDV / DVCAM / DVCPRO tape capture | Streaming, archival, Apple ecosystem |
| Compression | Intraframe-only DCT (~5:1) | Inter-frame, ~40-50% smaller than H.264 |
| Bitrate | Locked at ~25 Mbps SD | Variable — typically 1-4 Mbps for SD source |
| File size (1 hour SD) | ~13 GB | ~600 MB - 1 GB at CRF 20-22 |
| Resolution | 720×480 NTSC / 720×576 PAL | Up to 8K (8192×4320) |
| Audio | Uncompressed PCM (16-bit / 48 kHz) | AAC / AC3 / EAC3 / Opus / FLAC / PCM (in container) |
| Hardware decode | FireWire-era only | iPhone 6s+, Apple Silicon, 2018+ smart TVs |
| Edit-friendly | Yes — every frame is a keyframe | Yes in modern editors (Final Cut, Resolve, Premiere) |
| Best for | Lossless editing master | Smallest archive playable on modern devices |
| Setting | Recommended | Notes |
|---|---|---|
| Video codec | H.265 / HEVC | Default — ~40-50% smaller than H.264 at the same visual quality |
| Audio codec | AAC | Universal compatibility; FLAC / PCM for an uncompressed audio master |
| Quality preset | High | "Highest" / CRF 18 doubles size with no perceptible gain on SD source |
| CRF | 20-22 | Visually transparent on SD; CRF 18 for archival, CRF 26-28 for smallest |
| Resolution | Original (720×480 / 720×576) | Don't upscale — DV is locked to SD |
| Bitrate target | 1-2 Mbps | Sweet spot for SD camcorder footage in HEVC |
HEVC plays natively on iPhone 6s and later, every iPad Pro, every Apple Silicon Mac, every Apple TV 4K, and on most 2018-and-newer Android phones, Windows 10/11 PCs (Windows ships an HEVC extension), and smart TVs from LG, Samsung, Sony, and TCL. Older Windows 7 PCs, pre-2018 smart TVs, and devices without an HEVC license may need a player like VLC. If a friend or family member is on an older setup, DV to MP4 with H.264 is the safer sharing copy.
DV uses a fixed ~25 Mbps intraframe-only bitrate — every single frame is fully encoded, so each second is the same size regardless of how much motion there is. HEVC uses inter-frame compression with much larger coding tree units than H.264, which lets it store only the differences between frames more efficiently. A typical SD camcorder hour drops from 13 GB to ~700 MB - 1 GB at CRF 20-22 with no visible quality loss.
H.265 if you want the smallest archive that still plays on iPhones, modern Macs, 2018+ smart TVs, and most current Android devices — files are typically 40-50% smaller than H.264 at the same visual quality. H.264 if your audience is on older Windows PCs, pre-2018 smart TVs, or any device without an HEVC license, since H.264 is decoded by everything made since 2010. Many archivists encode HEVC for personal storage and H.264 for sharing.
CRF 20-22 is visually transparent on SD camcorder footage — almost nobody can tell the HEVC apart from the DV source at this level. Use CRF 18 if you want extra headroom for re-edits or future re-encodes (the file roughly doubles versus CRF 22). CRF 26-28 produces noticeably smaller files that still look fine for casual playback but compresses motion-heavy scenes more aggressively.
Both work. NTSC DV is 720×480 at 29.97 fps (North America, Japan); PAL DV is 720×576 at 25 fps (Europe, Australia, most of Asia). The converter detects and preserves the original frame rate. If your tape was shot interlaced (most consumer MiniDV cameras shipped interlaced by default), the HEVC stays interlaced unless you explicitly choose a progressive resolution preset — modern players handle interlaced HEVC fine, but for YouTube uploads it's worth converting to progressive.
Generally no. DV is locked to SD resolution and upscaling won't add detail — it just makes the file larger and slower to decode. Keep the original 720×480 / 720×576 unless a specific platform requires HD input. Some users do upscale to 720p for unified playlists where everything else is HD, which is fine; just expect the upscaled output to look softer than native HD content.
Yes — drop in dozens of DV captures at once. A typical use case is a 50-tape MiniDV box: capture each tape via FireWire to a single .dv file, then queue all 50 in one batch. They process within your browser session and download individually. Settings apply uniformly across the batch, so you can pick H.265 + CRF 22 once and apply it to the whole archive.
Yes. DV stores uncompressed PCM audio at 48 kHz / 16-bit (or 32 kHz / 12-bit on some older cameras), and the converter re-encodes that to AAC while preserving sync. Long FireWire captures (multi-tape stitched files) sometimes have drift in the original DV — if so, the drift carries through to the HEVC but isn't introduced by conversion. For an uncompressed audio master, pick FLAC or PCM 16-bit instead of AAC.
Yes. The date / time overlay that many MiniDV camcorders burn into the picture (when "Date Display" was enabled in-camera) is part of the visible video frame, not metadata, so it survives conversion exactly as it appears in the original. If you'd rather not see it, you'd need to crop or letterbox in a video editor before converting.
Yes — use the Trim section to set a start time and duration (seconds, e.g. 12.5, or HH:MM:SS.sss, e.g. 00:00:08.500). MiniDV tapes captured via FireWire often include a few seconds of blue-screen, color bars, or static at the head before the actual footage starts, and trimming those out at conversion time saves a manual step in a video editor later.