Initializing... drag & drop files here
Supports: DVR
A .dvr file is a digital video recorder recording — a captured TV broadcast, a set-top-box dump, or footage from a security or CCTV system. This tool does one specific thing: it pulls a single frame out of that recording and saves it as a TIFF still image — a photo of one moment, not a clip. This guide walks through picking the right frame, the one setting that quietly matters most for an archival or evidence still (the compression type), and the common errors people hit with DVR footage. If you want the whole recording as a playable video instead, use the DVR to MP4 or DVR to MKV converters.
.dvr file onto the page, or click "+ Add Files" to browse. Only recordings that a normal media player can open are reliably decodable — copy-protected and proprietary headerless files may not (see "Common Errors" below).People reach for TIFF when the still has to be kept, not just viewed — a documentation frame, an incident screenshot, an image headed into an editing or preservation workflow. Two settings decide whether you actually get that.
The first is Compression Type. TIFF can hold its pixels several ways: uncompressed (None), the lossless schemes LZW and Deflate/ZIP, or — and this is the trap — lossy JPEG compression inside the TIFF wrapper. A JPEG-compressed TIFF is still a .tif file, but it has thrown away image data exactly the way a .jpg would, which defeats the reason you picked TIFF. If the still matters, the patterns are:
The second is the frame itself. A TIFF preserves the moment exactly as captured — it cannot add detail the recording never held. DVR footage from broadcasts and CCTV is SD-to-HD and already lossy, so pause on a clear, static moment; a frozen frame from fast motion will be soft no matter the format. There is no way to "regain" sharpness a low-resolution source never recorded.
A quick note on "Multiple Screenshots": it returns several stills delivered together as a ZIP, where each one is a separate TIFF file. It does not produce a single multipage TIFF, even though the TIFF format technically allows multiple images in one file.
Want the exact same extraction at the .tif extension? The DVR to TIF page is identical — .tif and .tiff are the same format, just two spellings of the extension.
The page ships with JPEG preselected, and the converter's own note under the dropdown says it plainly: "LZW is the standard for TIFF files and offers the best compatibility. While JPEG or WebP compression can create smaller files, they are often not supported by standard image viewers and professional printing software." Here is the full list you can choose from:
| Compression Type | Lossless? | Typical size | Reader support | Pick it when |
|---|---|---|---|---|
| LZW | Yes | Moderate | Broadest of all TIFF schemes | You want a faithful still that opens anywhere — the safe default |
| DEFLATE (ZIP) | Yes | Usually smaller than LZW | Very good, slightly narrower than LZW | You want lossless with a smaller file |
| NONE | Yes (nothing applied) | Largest | Universal, including very old readers | Maximum portability, size is irrelevant |
| PACKBITS | Yes | Barely smaller on photos | Very good, an original TIFF scheme | A legacy reader chokes on LZW |
| JPEG (preselected) | No | Small | Patchy in print/prepress tools | Size matters and exactness does not |
| WebP | No by default | Small | Narrow — modern libraries only | Never for archival stills |
| ZSTD | Yes | Small, fast to write | Newer libtiff builds only | You control the software reading it |
| JP2K (JPEG 2000) | Can be either | Small | Narrow outside imaging suites | A workflow explicitly asks for JPEG 2000 in TIFF |
| CCITT Fax 4 | Yes, but bilevel | Tiny | Good in fax/document tools | Only for pure black-and-white line art, not photos |
| LOSSY | No | Small | Depends on the encoder used | You are optimizing for size, not fidelity |
For an evidence or archival still from a DVR recording, that table collapses to one line: switch Compression Type from JPEG to LZW (or DEFLATE), because the frame you are preserving should not be re-compressed on its way into the file that is supposed to preserve it.
| Property | TIFF | JPG | PNG |
|---|---|---|---|
| Compression | Selectable — lossless or lossy | Always lossy | Always lossless |
| Re-saving degrades it | No, on a lossless setting | Yes, each save | No |
| Opens in Chrome / Firefox / Edge | No | Yes | Yes |
| Opens in Safari | Yes | Yes | Yes |
| Layers / multiple pages in one file | Yes (the format allows it) | No | No |
| Typical size from one SD frame | Largest | Smallest | Middle |
| Colour depth beyond 8-bit | Yes | No | Yes (16-bit per channel) |
| Best for | Archiving, print, evidence stills | Sharing, email, web | Screenshots, sharp edges, web with transparency |
| xconvert page | this page | DVR to JPG | — |
The honest limit is the source file, not the converter. A simple rule decides it: if a normal media player such as VLC can open the recording, a frame can be extracted from it here; if VLC cannot open it, neither can this tool. The two cases that genuinely fail are broadcaster-flagged copy-protected DVR-MS recordings (encrypted by design) and encrypted or headerless set-top/CCTV dumps that only the manufacturer's player reads. In both cases the fix is the same — export or "back up" the clip to a standard file from the device's own software first, then come back. For evidence work specifically, note that organizations such as NIST publish formal procedures for retrieving footage from CCTV systems; a general-purpose converter is for producing a still, not for establishing chain of custody, so preserve the original recording and document how any still was made.
A single image. This conversion extracts one frame from the recording and saves it as a TIFF still — there is no motion in the output. "Multiple Screenshots" gives you several stills delivered together as a ZIP, but each is a separate still photo, not a single multipage TIFF. To keep the recording as a playable clip, use DVR to MP4 or DVR to MKV instead.
A lossless one — LZW or Deflate/ZIP — so the saved frame is bit-for-bit faithful to the source. The important caution is that TIFF can also store lossy JPEG compression internally; that produces a smaller .tif but discards image data, which is the opposite of what an archival still needs. Pick LZW for the widest software support, Deflate for a slightly smaller lossless file, or None if you need maximum compatibility with old TIFF readers. Treat a converter's output as a still you produced from a preserved original, not as a legal record in itself.
It will be exactly as sharp as that moment in the source — no sharper. DVR recordings from TV and CCTV are SD-to-HD and already lossy, so TIFF faithfully preserves the captured frame but cannot add detail the recording never held. If the footage was blurry, low-light, or motion-smeared at capture, the still will be too. Pausing on a clear, static moment gives the best result.
That is interlacing, a property of the source recording rather than the conversion. Many older broadcast and CCTV captures are interlaced: each frame is built from two fields recorded a moment apart, so freezing one frame on fast motion shows the two fields as a comb pattern. Choosing a frame during a still moment reduces it; heavy combing needs a deinterlacing pass on the video before you extract the frame.
Not easily — that is TIFF's main drawback. Of the major browsers, only Safari renders TIFF natively; Chrome, Firefox, and Edge do not display .tif/.tiff files without an add-on. TIFF is built for editing, printing, and archiving, not for the web. If you need a still that opens in any browser or app, use DVR to JPG instead.
The "Specific Frame" mode is driven by the "Time (seconds)" field, so leaving it at zero grabs the very beginning of the recording. On a DVR capture that is rarely what you want: the opening moments of a recorded broadcast or a set-top dump are often black, a channel-change artifact, or a few frames of noise while the encoder settles. Scrub the recording in a media player first, note the timestamp of the moment you want, and type that number in — or switch to "Multiple Screenshots" and pick the best still from the batch afterwards.
No. A frame grab carries pixels, not the recording's metadata: the channel, the recorder's clock, and any camera identifier live in the source container's own private data, and none of that survives as EXIF in the still. There is one useful exception — most surveillance DVRs burn the date and time into the picture as an on-screen overlay, and because that overlay is part of the image, it is preserved in the TIFF exactly as it appeared. If the timestamp is not visible in the video, it will not be in the still either, so record it separately alongside the extracted frame.
Your file is uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after the conversion finishes. There is no sign-up, no watermark, and your files are never shared or made public.