DV to ASF Converter

Converting DV Tape Footage to ASF: What This Covers

DV is the format your MiniDV camcorder wrote — launched in 1995, standardised in the IEC 61834 family, and stubbornly enormous because it was designed for tape rather than disk. ASF is Microsoft's Advanced Systems Format, the container behind WMV and WMA.

This walkthrough is aimed at the specific job of getting captured DV footage into an ASF that a Windows-centric workflow will accept, without quietly destroying the widescreen geometry along the way — which is the mistake that costs most people a re-run.

How to Convert DV to ASF

1. Upload Your DV File: Drag the .dv onto the drop zone or click "Add Files". Raw DV files are large — a three-second clip is over 10 MB — so expect the upload itself to be the slow part.
2. Check the Video Codec: The resolved default on this page is H.264, not WMV. The dropdown also offers WMV 1 and WMV 2 along with MPEG-4, Xvid, MPEG-2 and others if a legacy Windows decoder is the target.
3. Set Width × Height If Your Footage Is 16:9: This is the step that matters. DV stores widescreen using non-square pixels, and only an explicit Width × Height reliably bakes the correct geometry into the output.
4. Convert and Download: Click Convert. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours. No sign-up, no watermark.

Why DV Files Are So Large

DV is a constant-bitrate, intra-frame format: every frame is compressed on its own with a DCT, and no frame refers to any other. That makes it wonderful to edit and terrible to store. We measured a 720 × 480 NTSC test file:

Because the rate is fixed, a tape of static talking heads costs exactly as much disk as a tape of fast motion. That is the whole reason to re-encode: our measured DV clip became a 404,193-byte ASF at the default settings, and none of that saving was available inside DV itself.

Walk-through: Getting the Widescreen Geometry Right

This is where DV conversions go wrong, so it is worth doing carefully.

A 16:9 DV frame is not 16:9 on the pixel grid. It is 720 × 480 with a sample aspect ratio of 32:27, which multiplies out to a 16:9 display aspect. The picture is stored horizontally squeezed and un-squeezed at playback time by a player that reads the aspect metadata. Probing our test file confirms it: sample_aspect_ratio=32:27, display_aspect_ratio=16:9, on a 720 × 480 raster.

Any encode that writes square pixels loses that metadata, and a 720 × 480 frame with square pixels displays as 3:2 — noticeably narrow, everyone slightly too tall. We measured exactly that outcome and the fix:

• If your footage is 16:9 widescreen — set Width × Height to 854 × 480 (NTSC) or 1024 × 576 (PAL). Our 854 × 480 encode came back with a display aspect of 427:240, which is 16:9 to within a rounding error.
• If your footage is 4:3 — set Width × Height to 640 × 480 (NTSC) or 768 × 576 (PAL). Same principle, different target.
• If you are not sure which you have — play the DV in VLC and look at the shape of circles and faces. Anamorphic 16:9 material looks correct in a player that honours the metadata and squashed in one that does not.
• If you genuinely do not care — leave Video resolution on Keep original and accept whatever the players decide.

Baking the geometry in with an explicit Width × Height removes the ambiguity for every downstream tool, which is the point.

Common Errors and How to Fix Them

• "Everybody looks too tall and thin" — the anamorphic squeeze survived into a square-pixel output. Re-run with Width × Height set to 854 × 480 for 16:9 NTSC footage.
• "Moving edges have horizontal comb lines" — SD DV is interlaced, and there is no deinterlacing step anywhere in this pipeline. The two fields are captured milliseconds apart and stay woven together. Deinterlace in an editor before uploading if the artefact matters.
• "The quality slider suddenly has a different range" — you switched the Video Codec to WMV 1 or WMV 2. Those are quantiser-scale codecs, so Constant Quality re-ranges to 1–31 where lower is better, instead of H.264's 16–51. It is the same control with an inverted, differently scaled meaning.
• "The output has no sound" — check the Audio Codec group. The resolved default here is WMA v2, which our test encode wrote at 48,000 Hz stereo, 128 kbit/s. If you changed it to something the ASF container cannot carry, the audio can be dropped.
• "The file is still huge" — you probably left Quality Preset alone with a low-motion source. Use Specific file size or Constant Bitrate under File Compression to pin an actual budget rather than a quality level.

When This Doesn't Work

ASF is a Microsoft container with a long tail of decoder quirks, and a modern H.264-in-ASF file is not what a 2003-era Windows Media Player expects. Match the codec pairing to what the destination was built for:

Switching to WMV 2 and WMA v2 costs compression efficiency and buys compatibility with software from the era ASF was designed for.

Going the other way, if the destination is anything modern — a website, a phone, a video editor, cloud storage — ASF is the wrong container entirely and you are inheriting its problems for no reason. DV to MP4 gives you the same H.264 video in a container everything opens. DV to WMV is the better choice if the requirement is specifically "a Windows Media file" rather than "an ASF".

Frequently Asked Questions

Is ASF the same thing as WMV?

Nearly. ASF is the container; WMV and WMA are the codecs Microsoft designed to live in it. A .wmv file is an ASF file that happens to hold WMV video, and a .asf file can hold almost anything. That is why this page's video codec dropdown offers H.264, MPEG-4 and Xvid alongside WMV 1 and WMV 2.

Why is the default video codec H.264 rather than WMV?

Because H.264 gives a far better picture per byte, and ASF is perfectly capable of carrying it. WMV 2 is there for genuine legacy targets. If nothing in your workflow specifically needs a Microsoft codec, leaving H.264 selected is the better result.

Will converting to ASF fix the interlacing from my camcorder?

No. There is no deinterlacing filter anywhere in this pipeline, so interlaced fields pass straight through into the output. We verified this on a synthetic test whose fields were solid blue and solid red: the resulting frame alternates blue, blue, red, red down the scan lines. Deinterlace before you upload if it matters.

How much smaller will the ASF be than the DV?

A lot, but the exact ratio depends entirely on your footage. DV spends a fixed ~28.8 Mbit/s whether or not the picture is moving, so static material compresses spectacularly and fast action much less. Our short synthetic test clip went from 10,680,000 bytes to 404,193 bytes; real camcorder footage will not match that figure, so use Specific file size if you need a predictable result.

What resolution should I use for PAL DV footage?

PAL DV is 720 × 576 with 4:2:0 chroma. For 16:9 PAL set Width × Height to 1024 × 576; for 4:3 PAL use 768 × 576. The principle is identical to NTSC — you are converting the anamorphic frame into square pixels so no downstream player has to guess.

Does the audio stay uncompressed?

No. DV carries PCM audio at around 1.5 Mbit/s, and the default ASF encode re-encodes it to WMA v2 — our test output measured 48,000 Hz stereo at 128 kbit/s. The server always re-encodes; there is no path that copies the original audio bytes through untouched. Choose PCM 16-bit under Audio Codec if you need to stay uncompressed.

Can I convert only part of a long DV capture?

Yes. The Trim group on this page takes a start time and a duration, in seconds or as HH:MM:SS.sss. Trimming before encoding is much faster than converting an hour of tape and cutting it afterwards, and it keeps the upload smaller too.

Why does my quality setting seem to do nothing when I pick MPEG-2?

MPEG-2 handles quality differently from the CRF codecs. On this page the reliable levers for MPEG-2 output are Constant Bitrate, Specific file size and the resolution controls. If a quality slider is not moving your file size, switch to a bitrate or size mode instead of hunting for a value that works.

What is the difference between Keep original and 100% Resolution Percentage?

Keep original passes the source dimensions straight through. Resolution Percentage computes new dimensions and rounds them to a multiple of 16 for encoder alignment, so even at a high percentage it can land a few pixels short of the source. For an exact match, Keep original or an explicit Width × Height is the safer choice.