Convert DV to WTV — Free Online Tool
Convert DV camcorder footage to WTV format for playback and archiving in Windows Media Center. This tool re-encodes DV's intra-frame DCT video stream into H.264 (libx264) and transcodes the raw PCM audio to AAC, producing a broadcast-style DVR container compatible with Windows Vista and later Media Center systems.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your DV file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
DV files store video as a sequence of independently compressed intra-frames using the dvvideo codec, with uncompressed 16-bit PCM audio — a format designed for camcorder tape recording rather than long-term PC playback. Converting to WTV requires full re-encoding of both streams: the dvvideo frames are decoded and re-encoded as H.264 using libx264 with CRF 23 (a visually near-lossless quality level for typical DV footage), and the PCM audio is compressed to AAC at 128k. The output is wrapped in the WTV container, which Windows Media Center uses natively for DVR recordings and supports metadata embedding and multiple audio tracks — features absent from the original DV format.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg tool, which handles the decoding of the DV input, re-encoding of both video and audio streams, and muxing into the WTV output container. |
-i input.dv
|
Specifies the input DV file. FFmpeg automatically detects the dvvideo video codec and pcm_s16le audio codec from the DV container header. |
-c:v libx264
|
Re-encodes the dvvideo intra-frame video stream into H.264 using the libx264 encoder, which is the standard and best-supported video codec for WTV files in Windows Media Center. |
-c:a aac
|
Transcodes the uncompressed PCM audio from the DV source into AAC, the default and widely supported audio codec for WTV, replacing the raw 16-bit PCM that the WTV container does not natively store. |
-crf 23
|
Sets the H.264 Constant Rate Factor to 23, the libx264 default, which produces good visual quality for standard-definition DV footage at a much lower bitrate than the original ~25 Mbps dvvideo stream. Lower values (e.g., 18) increase quality and file size. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second, which is appropriate for the mono or stereo camcorder audio typically found in DV recordings and represents a significant size reduction from the uncompressed PCM source. |
output.wtv
|
Specifies the output filename with the .wtv extension, which causes FFmpeg to mux the encoded H.264 video and AAC audio into the Windows Television container format used by Windows Media Center. |
Common Use Cases
- Importing old camcorder DV footage into a Windows Media Center library so it appears alongside recorded TV content and can be browsed with the same interface
- Archiving family or event DV tapes in a more space-efficient format — H.264 in WTV significantly reduces file size compared to the high-bitrate dvvideo codec while retaining visual quality
- Preparing DV footage for playback on a Windows Home Theater PC (HTPC) that uses Media Center as its front-end, since WTV is the native DVR format it recognizes
- Converting DV interview or documentary footage into a format that supports multiple audio tracks in WTV, allowing separate language or commentary tracks to be added post-conversion
- Consolidating DV source material into a WTV archive with embedded metadata (title, description, date) for better catalog organization in a Media Center library
- Reducing storage overhead of raw DV files captured from a tape deck, where the fixed ~25 Mbps dvvideo bitrate is far higher than needed for finished archival copies
Frequently Asked Questions
Yes, this is a lossy-to-lossy conversion — DV footage is already lossy due to its intra-frame DCT compression, and re-encoding to H.264 introduces a second generation of compression. However, with CRF 23 (the default used here), libx264 produces output that is visually very close to the DV source at a fraction of the bitrate. The most noticeable quality loss occurs in fast-motion scenes or high-frequency detail, which are already weaknesses of the dvvideo codec. For archival purposes where maximum fidelity is critical, lowering the CRF value (e.g., to 18) will preserve more detail.
DV uses a fixed bitrate of approximately 25 Mbps for standard-definition footage, regardless of scene complexity, because it compresses each frame independently with no inter-frame prediction. H.264 in WTV uses motion compensation and temporal compression across frames, allowing it to represent the same footage at 3–8 Mbps while maintaining comparable visual quality. This is why a one-hour DV tape (~13 GB) can convert to a WTV file of 2–4 GB at CRF 23.
Yes — WTV with H.264 video and AAC audio is a standard configuration supported by Windows Media Center on Windows Vista, 7, and 8. The file will appear in the Media Center video library and can be played back directly. However, since the source is camcorder footage rather than a broadcast recording, DVR-specific metadata fields like channel, program title, and air date will be empty unless you add them separately using a tool like MCEBuddy or directly editing the WTV metadata.
Yes. The CRF value controls H.264 quality: lower values mean higher quality and larger files (CRF 18 is near-visually-lossless, CRF 28 is noticeably compressed). Replace '-crf 23' with your preferred value in the range 0–51. For audio, replace '-b:a 128k' with a higher value like '-b:a 192k' or '-b:a 256k' if the DV source contains music or high-fidelity audio that benefits from a higher AAC bitrate. For typical speech-heavy camcorder audio, 128k AAC is already very clean.
The PCM audio is re-encoded — it is not copied. DV stores audio as pcm_s16le (signed 16-bit little-endian PCM), which is uncompressed and not compatible with the WTV container's expected audio streams. FFmpeg decodes the PCM audio and re-encodes it to AAC at 128k. The quality difference between 16-bit PCM and 128k AAC is minimal for typical camcorder audio (usually recorded at 32 kHz or 48 kHz), but if you want higher fidelity, you can increase the AAC bitrate with '-b:a 256k'.
On Windows, you can run a batch loop in Command Prompt: 'for %f in (*.dv) do ffmpeg -i "%f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "%~nf.wtv"'. On macOS or Linux, use: 'for f in *.dv; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "${f%.dv}.wtv"; done'. This processes each DV file in the current directory and outputs a corresponding WTV file with the same base name. Be aware that DV files are large and H.264 encoding is CPU-intensive, so batch processing multiple files will take significant time.
Technical Notes
DV's dvvideo codec uses a fixed 25 Mbps (for DV25/DVCAM) or 50 Mbps (for DVCPRO50) bitrate with 4:1:1 chroma subsampling (NTSC) or 4:2:0 (PAL), which means color information is already heavily subsampled before this conversion begins. When re-encoding to H.264, libx264 will default to yuv420p pixel format, which matches the PAL DV chroma layout but involves a chroma conversion step for NTSC DV. The WTV container supports embedded subtitles (unlike DV), but this conversion does not generate or pass through subtitle data since none exists in the source. DV files also lack chapter markers and container-level metadata beyond basic timestamps, so the WTV output will have minimal metadata unless added via post-processing. The intra-frame nature of DV makes it easy to seek within, but the resulting H.264 WTV file uses keyframe intervals (GOP structure), which slightly limits frame-accurate seeking in some editors. If you intend to further edit the footage after conversion, consider using a lower CRF or an intra-only H.264 profile ('-x264-params keyint=1') to preserve edit-friendliness.