DVR to HEIF Converter

DVR to HEIF: What This Tutorial Covers

A .dvr file is a recording — a captured broadcast, a set-top-box dump, or footage off a security or CCTV system. HEIF is a still-image format, so this tool does not convert the recording; it decodes one frame out of it and saves that single picture as a .heif. This guide walks through landing on the frame you actually want, what our encoder writes into the file, and the one thing that catches almost everybody out afterwards: HEIF opens in very few places. If you want the recording itself, DVR to MP4 is the page you need.

How to Convert DVR to HEIF

1. Upload Your DVR File: Drag the .dvr onto the page or click "+ Add Files" to browse. Several recordings can be queued and a frame is pulled from each with the same settings.
2. Set Frame Selection and Time (seconds): Frame Selection opens on Specific Frame with Time (seconds) at 0. Type the moment you want instead — decimals are accepted, so 93.5 is a minute and thirty-three and a half seconds in. Switch to Multiple Screenshots and set a Capture Rate to sample the whole recording instead.
3. Set the Quality Preset and Image resolution: Quality Preset opens on Very High (Recommended) and runs Highest through Lowest. Image resolution opens on Keep original; Resolution Percentage, Preset Resolutions, Width, Height and Width x Height are the alternatives. Switch Image Compression to Specific file size if you have a byte ceiling instead of a quality target.
4. Convert and Download: Click Convert and save the file. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.

Walk-through: Landing on the Frame You Want

The extraction itself is exact — the frame is decoded out of the recording and written to a lossless PNG before the HEIF encoder ever sees it, so the only new compression is the final encode at your chosen preset. What takes practice is choosing which frame.

• Do not leave Time (seconds) at 0 by accident. Frame zero of a recorder's output is frequently the least useful image in the file: a black leader while the tuner locks, a channel bumper, or a camera that has not settled. If your first attempt looks empty, this is nearly always why.
• Read the timecode off a player, then convert seconds. The field is in seconds, not minutes and seconds. For the moment at 2:14, type 134, not 2.14.
• Take a spread and pick the best. Recorder footage is often interlaced and low bitrate, so individual frames vary a lot in sharpness. Running the grab at 134.0, 134.2 and 134.4 and keeping the cleanest one costs almost nothing.
• Use Multiple Screenshots when a timestamp misbehaves. That mode walks the recording from the start at your chosen Capture Rate — from one frame every ten seconds up to ten frames a second — rather than seeking into it, so it succeeds on files where a direct seek does not. Each captured moment arrives as its own separate .heif.

What Our HEIF Encoder Actually Writes

We encoded a frame through the same encoder this page uses and inspected the result:

Two things follow from that table. HEIF and HEVC can both carry 10-bit and richer chroma, but this pipeline does not emit it — which costs you nothing on a .dvr, because broadcast and CCTV recordings are 8-bit 4:2:0 to begin with. And because the file declares the heic brand regardless of the extension you asked for, a .heif and a .heic from the same frame are the same picture in the same encoding; if a program refuses one, renaming it to the other is a legitimate first thing to try.

Where a .heif Will and Will Not Open

This is the single biggest reason a HEIF frame grab disappoints. If the still has to open on an arbitrary machine, in a document, in an email, or on a web page, choose DVR to JPG or DVR to PNG instead. HEIF earns its place when the destination is an Apple device or a storage archive where its compression advantage over JPEG genuinely matters.

Common Errors and How to Fix Them

• "The frame is black" — Time (seconds) is still at 0. Set a real timestamp.
• "My timestamp returned nothing at all" — recorder files are usually transport streams, which carry no seek index. If the recording is truncated, damaged, or has very widely spaced keyframes, a seek can land somewhere with nothing decodable after it and produce an empty result. We reproduced exactly that on a transport stream whose only keyframe was at the start: 0 worked and every later timestamp came back empty. Try a nearby earlier time, or switch to Multiple Screenshots.
• "Nothing on my PC will open the file" — install Microsoft's HEIF Image Extensions on Windows, or convert to PNG instead.
• "There are comb lines through moving objects" — the recording is interlaced and nothing here de-interlaces, so a still pulled during motion keeps the combing. Pick a static moment.
• "The picture is soft and blocky" — that is the recording, not the conversion. Set-top-box and CCTV captures are heavily compressed; extraction preserves what is there and never restores what was thrown away.
• "I wanted the whole recording" — use DVR to MP4, or cut the section you care about first with Video Cutter, which takes .dvr directly.

Frequently Asked Questions

Does this convert my whole DVR recording into a HEIF?

No. HEIF as produced here is a single still image. The server decodes one frame at the timestamp you set and encodes just that frame. If you need several stills, switch Frame Selection to Multiple Screenshots and choose a Capture Rate — you receive one separate file per captured moment, not one file holding a sequence.

Is picking "Highest" worth it over the default?

No. Highest maps to quality 100 and Very High to 95, and on the frame we measured the two files came out within a byte of each other — 101,084 against 101,085. Highest is effectively a no-op on this encoder. The first preset that genuinely changes the output is High at quality 90, which came back about 7% smaller; Medium at 80 took roughly a quarter off. If you want a smaller file, step down rather than expecting Highest to buy you anything.

Why is a frame from a hidden-camera or CCTV file so blurry?

Because of what was recorded, not how it was extracted. Security recorders are tuned to fit days of footage on a disk, so they run low bitrates, often at low frame rates and standard-definition resolutions, and they compress aggressively. Everything the encoder discarded at record time is gone permanently. Choosing a bigger Preset Resolution stretches the pixels but adds no detail — the only real lever is picking a still, well-lit moment rather than one mid-motion.

What is the difference between .heif and .heic here?

Nothing meaningful. Both are defined by ISO/IEC 23008-12: .heic is the branding that specifically signals HEVC-coded content, while .heif is the codec-agnostic structural name. Our encoder always writes HEVC, and we confirmed the file it produces declares the heic brand and reports the image/heic MIME type even when the extension is .heif. So the two are interchangeable in practice, and renaming is a valid fix when software is fussy about the extension.

Can I get several stills without running the conversion repeatedly?

Yes — that is exactly what Multiple Screenshots is for. Set the Capture Rate to control density: the list runs from a frame every ten seconds through to ten frames per second, starting at one frame per second. On a long recording a slow rate gives you a contact sheet you can scan for the moment you want; a fast rate near an event gives you several candidates a fraction of a second apart.

Does the HEIF keep a timestamp or any recorder metadata?

Not in any form you can rely on. A .dvr recording stores broadcast and recorder metadata in container structures that have no equivalent in a still image, and this conversion carries the picture, not the bookkeeping. If the recording burns a timecode into the video itself, that burned-in text survives because it is part of the image — but a machine-readable recording time does not. Note it down before you convert if it matters.

Is any quality lost before the HEIF encode?

No. The frame is decoded out of the recording and written as a lossless PNG first, so nothing is lost between the recording and the encoder — the only new compression is the HEIF encode at your chosen preset. What you cannot escape is the loss the recorder already applied; a frame grab inherits every artefact that is baked into the source.

Can the output hold transparency?

No. The frames in a recording are fully opaque — no broadcast or CCTV codec carries an alpha channel — and our HEIF output has no alpha plane, which we confirmed on the encoded file. If you intend to cut a subject out of the frame, grab it as PNG instead, since PNG is lossless and does store alpha.

What happens to my recording after the conversion?

It is uploaded over an encrypted connection, decoded on our servers, and both the upload and the images it produced are deleted automatically after a few hours. Nothing is shared or made public, there is no sign-up and no watermark, and your original .dvr is never modified — each still is written as a new file for you to download.