Initializing... drag & drop files here
Supports: DV
A .dv file is what comes off a MiniDV, DVCAM or DVCPRO tape over FireWire — the DV codec standardised as IEC 61834 for consumer gear and SMPTE 314M for the professional variants. It compresses every frame independently with intra-frame DCT at 25 Mbit/s, which makes it unusually good raw material for still extraction: any timestamp decodes cleanly on the first pass, with no rewind to a distant keyframe.
This tool decodes one frame (or a series of frames) and saves each as a JFIF image. A .jfif holds ordinary baseline JPEG data under the image/jpeg MIME type, so it opens anywhere a .jpg does and can be renamed freely. Internally the frame is extracted as a lossless PNG first and only then encoded as JPEG, so the single lossy step you control is the final one.
.dv capture onto the page or click "+ Add Files". A whole digitised tape can be queued alongside others and processed with the same settings.0, which grabs the opening frame. Type 47 for the frame at forty-seven seconds; the field accepts decimals, so 2.100 is two seconds and 100 milliseconds in.This is the one thing that surprises people extracting stills from tape, and it is worth knowing before you print or publish anything.
DV does not use square pixels. The picture is stored as 720 columns regardless of whether the camcorder was framing 4:3 or 16:9, and the aspect is signalled separately as a pixel aspect ratio that a player applies at display time. A still image has no such signal — a JPEG is a grid of square pixels and nothing else — so the extracted frame arrives at the stored dimensions with the aspect information dropped. We confirmed this: a 720x480 clip flagged 16:9 and a 720x480 clip flagged 4:3 both produced 720x480 stills.
| Source | Stored frame | Pixel aspect | How it should display | What the still measures |
|---|---|---|---|---|
| NTSC DV, 4:3 | 720x480 | 8:9 | 640x480 | 720x480 — slightly wide |
| NTSC DV, 16:9 anamorphic | 720x480 | 32:27 | 853x480 | 720x480 — noticeably squeezed |
| PAL DV, 4:3 | 720x576 | 16:15 | 768x576 | 720x576 — slightly narrow |
| PAL DV, 16:9 anamorphic | 720x576 | 64:45 | 1024x576 | 720x576 — noticeably squeezed |
The fix is to set the display width yourself. Under Image resolution choose Width x Height and type the figure from the "How it should display" column — 853 x 480 for a 16:9 NTSC capture, 1024 x 576 for 16:9 PAL. If the tape was shot 4:3, the distortion is mild enough that many people leave it alone; if it was shot anamorphic, correcting it is the difference between a usable still and one where everyone looks thin.
| Property | DV (NTSC) | DV (PAL) |
|---|---|---|
| Stored frame | 720 x 480 | 720 x 576 |
| Frame rate | 29.97 fps | 25 fps |
| Chroma subsampling | 4:1:1 | 4:2:0 |
| Video bitrate | 25 Mbit/s | 25 Mbit/s |
| Compression | Intra-frame DCT — every frame is a complete I-frame | Intra-frame DCT |
| Audio | 16-bit PCM at 48 kHz (discarded here — a still has no audio) | 16-bit PCM at 48 kHz |
| Standards | IEC 61834 (consumer); SMPTE 314M (DVCAM, DVCPRO) | IEC 61834; SMPTE 314M |
| Scanning | Usually interlaced (60i); progressive on later prosumer models | Usually interlaced (50i) |
.jpg; the data is unchanged.| Property | Value |
|---|---|
| Standard | ISO/IEC 10918-5, JPEG File Interchange Format |
| Also published as | ITU-T Recommendation T.871 |
| Payload | Baseline JPEG image data (ISO/IEC 10918-1) |
| MIME type | image/jpeg — the same type registered for .jpg |
| Extensions carrying it | .jfif, .jpg, .jpeg, .jpe |
| Compression | Lossy; there is no lossless mode |
| Transparency | None — no alpha channel |
| Colour | 8 bits per channel, YCbCr |
In every way that matters, yes. JFIF is the standard wrapper around JPEG-compressed image data, and .jpg, .jpeg and .jfif all carry the same kind of bytes under the same image/jpeg MIME type. Rename a .jfif to .jpg and it behaves identically in every viewer and editor. The extension differs; the file format does not. Windows itself sometimes writes .jfif where you expected .jpg, which is how most people first encounter the extension.
Because of how it compresses. DV encodes each frame independently with intra-frame DCT, so every single frame is a complete picture that decodes on its own. Most MP4 files use long-GOP H.264, where the majority of frames store only the differences from their neighbours and extracting an arbitrary moment means decoding forward from the last keyframe. With DV, any timestamp you name gives a clean, full-quality frame on the first pass. That property is also why DV files are so large — 25 Mbit/s buys you frame independence.
At the default Capture Rate of one frame per second, a 60-minute capture yields 3,600 images. At one every 5 seconds you get 720, and at one every 10 seconds you get 360 — usually enough to skim a tape's contents visually and find the sections worth revisiting. The fastest setting, one frame every 0.1 seconds, produces 36,000 images from the same hour, which is rarely what anyone wants outside frame-by-frame analysis.
Neither. A JFIF is a still image, so the 48 kHz PCM soundtrack DV carries has nowhere to go and is discarded. DV's locked timecode is part of the tape's data structure rather than something that maps onto a JPEG, so it does not appear in the still either. If the audio is what you are after, extract it separately with DV to MP3 or DV to WAV for an uncompressed copy.
Not with the resolution presets, no. Enlarging a 720x480 frame to 1080 lines does not add detail the tape never recorded — it interpolates, which produces a bigger file that looks softer under close inspection. What is worth doing is correcting the pixel aspect, since that fixes a genuine distortion rather than inventing information. For small prints a corrected standard-definition frame holds up reasonably; for anything large, the tape simply does not carry the resolution.
"Very High" for general use and "Highest" when the still matters. The reasoning is that the source is already the bottleneck: DV's 4:1:1 chroma subsampling on NTSC and its standard-definition raster mean there is not much detail for JPEG to preserve, so there is no sense in throwing any of it away at the compression stage. Reserve the lower presets for bulk work — building contact sheets from a shelf of unlabelled tapes, where you want 3,600 small thumbnails rather than 3,600 archival stills.
No. The frame is extracted from the DV stream as a lossless PNG and only then encoded to JPEG, so there is exactly one lossy step in the conversion itself. What you cannot avoid is the compression already baked into the tape: DV's own DCT encoding happened in the camcorder and its artefacts are part of the picture before this tool ever sees it. Choosing a high quality preset keeps the JPEG stage from stacking a visible second generation on top.
Yes — convert to PNG rather than JFIF. DV to PNG writes the frame without JPEG compression, which is the right choice for an archival master or for a still you intend to edit further, since repeated JPEG saves compound their artefacts. The files are considerably larger. JFIF is the better pick when the still is going straight into a document, a web page or a print of ordinary size.
Your .dv capture is uploaded over an encrypted connection, decoded on our servers, and both it and the extracted images are deleted automatically a few hours later. Nothing is shared or made public and no account is required. DV runs at 25 Mbit/s, so an hour of tape is roughly 13 GB — for long captures the upload over your own connection is by far the slowest part of the job, and trimming to the section you care about beforehand saves real time.