Initializing... drag & drop files here
Supports: DVR
.dvr File Actually Is.dvr is one of the least specific extensions in video. In the overwhelming majority of cases it means a Microsoft DVR-MS recording — the format Windows XP Media Center Edition introduced in 2004 and Vista and Windows 7 carried on using, which wraps MPEG-2 video and MPEG-1 Audio Layer II or Dolby Digital AC-3 audio in an ASF container alongside metadata and, sometimes, protection streams. But several security-camera systems and set-top personal video recorders reuse the same three letters for containers of their own that share nothing with DVR-MS beyond the name.
JFIF, by contrast, is completely unambiguous: it is the JPEG File Interchange Format, the specification that describes the files everyone calls JPEGs. So this page decodes one frame from a recording and writes it as a JPEG-compressed picture named .jfif. Whether that works at all depends on the first paragraph, which is why identification comes before the how-to here.
dvr, so a file named something.dvr-ms needs renaming to .dvr first — the container is identified from the header inside the file, so the rename changes nothing about how it decodes.0. Recorded TV almost always starts on a channel-change flash, a black leader or the tail of the previous programme, so type a real timestamp; decimals such as 240.5 are accepted. "Multiple Screenshots" with a Capture Rate samples across the whole recording instead..jfif. Files are uploaded over an encrypted connection, processed on our servers and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public..dvr File Can Actually Be| What you have | How to recognise it | Frame grab outlook |
|---|---|---|
| DVR-MS from Windows Media Center | Written by XP MCE, Vista or Windows 7; often paired with .dvr-ms naming; ASF header inside |
Decodes normally unless the broadcast was flagged protected |
| DVR-MS with broadcast protection | Recorded from a premium or flagged channel; plays only on the PC that recorded it | Cannot be decoded by any general-purpose converter, online or installed |
.wtv renamed to .dvr |
Windows Media Center TV Pack 2008 onwards wrote WTV, a different container | Convert it as WTV instead — see WTV to MP4 and grab the frame from the result |
| Security-DVR or set-top proprietary container | Only opens in the recorder's own viewer; no standard header | Export a normal video file from that software first |
| Truncated or still-recording file | Playback stops partway; a late timestamp fails where an early one works | Grab a frame from before the damaged point, or repair the file first |
If a file refuses to convert and came off a premium cable or satellite channel, protection is by far the most likely explanation. Microsoft's design binds a protected recording to the machine that made it, so there is no legitimate way around it.
Standard-definition broadcast is not a photographic source, and a freeze frame exposes every compromise that live viewing hides.
| What you will see | Where it comes from | What to do about it |
|---|---|---|
| Comb-like horizontal lines through moving subjects | Interlaced SD broadcast stores two fields captured a fraction of a second apart in each frame | Pick a static shot, or de-interlace the still afterwards — nothing in this pipeline de-interlaces |
| People looking horizontally squeezed | Non-square pixels: a 720 x 480 or 720 x 576 frame is meant to be stretched to 4:3 or 16:9 on display | Set Image resolution to Width x Height and type the display size, such as 640 x 480 or 1024 x 576 |
| A generally soft, blocky picture | MPEG-2 at broadcast bitrates threw detail away before the recording was ever made | Raising the Quality Preset stops the JPEG encoder adding new artefacts; it cannot remove the old ones |
| Smearing around the station logo and captions | Coloured graphics sit exactly where chroma subsampling does its damage | Stay at the High preset or above whenever a logo or caption is in shot |
| A black or garbled opening frame | The tuner was still settling when recording began, so the first moments are rarely usable picture | Move Time (seconds) well into the recording rather than leaving it at 0 |
.jfif the same as a .jpg?Yes, in every way that affects the picture. JFIF is the interchange specification behind the JPEG files everyone uses, and .jfif, .jpg, .jpeg, .jpe and .jif are five names for the same encoded data. Rename the download to .jpg and every viewer and editor opens it identically — worth doing, because some upload forms and photo services filter on the extension and do not recognise .jfif. If you want the common name from the outset, DVR to JPG does the same decode and hands you a .jpg.
Work through the identification table above. The three common causes are broadcast protection on the recording, a .wtv or a proprietary security-DVR container wearing a .dvr name, and a file that is still being written or was cut off mid-record. Only the middle case has a route forward here — convert the file through the page for its real container, then grab the frame from the output.
Because the whole file has to reach our servers before anything can be decoded, and an hour of standard-definition MPEG-2 is typically a couple of gigabytes. The decode and encode take moments; the upload does not. If you want several stills from the same recording, convert it once with DVR to MP4 and grab frames from the much smaller result rather than re-uploading the original each time.
No — it is the recording's non-square pixels showing through. Broadcast SD stores 720 x 480 or 720 x 576 samples that a television stretches to 4:3 or 16:9 on display, and a still keeps the stored numbers because nothing here performs pixel-aspect correction. Set Image resolution to Width x Height and type the display dimensions to correct it in one step.
"Very High (Recommended)" is a sensible default. Drop to "High" if size matters, because that is the last rung where colour stays at full resolution; below it the chroma planes are halved in both directions, which is where a station logo or coloured captions start to smear. Going up to "Highest" mostly spends bytes preserving the MPEG-2 artefacts already in the source.
Set Frame Selection to "Multiple Screenshots" and choose a Capture Rate. The entries are intervals between stills, not frame rates, so "1 second per frame" on a 45-minute recording is 2,700 images. Ten seconds per frame is a reasonable scouting rate; once you have found the moment, re-run with "Specific Frame" and an exact timestamp.
No. DVR-MS keeps electronic programme guide data — title, channel, description, broadcast time — in its metadata streams, and a JPEG has nowhere to put it, so all of that is dropped. Note anything you need from the recording's properties before converting, because the still on its own carries no provenance.
It is discarded; a still image has no audio capability at all. DVR-MS soundtracks are usually MPEG-1 Audio Layer II or Dolby Digital, and if you need the sound as well, run the same recording through DVR to MP3 as a separate job.
JFIF for anything you will share, embed or send — it is small and universally readable. DVR to PNG when you plan to crop, annotate and re-export the still repeatedly, since every JPEG save adds another generation of artefacts on top of the broadcast's own, and PNG at its top setting avoids that entirely.
Files are uploaded over an encrypted connection, processed on our servers and deleted automatically after a few hours, along with every still the job produced. There is no sign-up, no watermark, and nothing is shared or made public. Because recorded television files are large, the upload — not the conversion — is what determines how long a job takes.