DVR to ICO Converter
A .dvr recording is a video file and ICO is a Windows icon container, so this conversion is not a format swap — it decodes one frame out of the recording and writes that single still as an icon. The usual reason to do it is to give a folder, shortcut, or small utility an icon taken from a specific moment of recorded TV or camera footage.
This page is a reference for both sides of that conversion: what a .dvr file actually contains, what ICO can and cannot hold, and exactly what dimensions come out the other end. If you want a normal picture rather than an icon, DVR to PNG keeps the full frame size.
The DVR-MS Source Format at a Glance
| Property | Value |
|---|---|
| Full name | Microsoft Digital Video Recording (DVR-MS) |
| Introduced | 2004, with Windows XP Media Center Edition; also used by Windows Vista and Windows 7 |
| Container | ASF (Advanced Systems Format), with the .dvr-ms extension |
| Video codec | MPEG-2 |
| Audio codec | MPEG-1 Audio Layer II, or Dolby Digital AC-3 (ATSC A/52) |
| Extra streams | Program metadata and digital rights management |
| Copy protection | If the broadcast was flagged copy-protected, the recording plays back only on the device that made it |
| Superseded by | WTV, starting with Windows Media Center TV Pack 2008 |
| Direction here | Input only — xconvert reads .dvr but does not write it |
Note the extension mismatch: this page accepts files named .dvr, and the check is a literal extension match. A file still named recording.dvr-ms is rejected before it uploads, so rename it to recording.dvr first. The container itself is identified from the ASF header inside the file, not from the name, and FFmpeg's ASF demuxer — the component that reads it — is documented as handling ASF files generally.
The ICO Target Format at a Glance
| Property | Value |
|---|---|
| Full name | Microsoft Windows Icon |
| Designed for | Desktop, shortcut, and application icons on Windows |
| Maximum dimensions | 256 x 256 pixels (per MDN) |
| Browser support | All versions of Chrome, Edge, Firefox, Opera, and Safari |
| Transparency | Supported by the format, but a decoded video frame has no alpha to carry |
| Multi-size icons | The format allows several sizes in one file; this converter writes one image per output |
| Web use | MDN advises against ICO in web content; favicons have largely moved to PNG plus a <link> element |
How to Convert DVR to ICO
- Upload Your DVR File: Drag your
.dvrrecording onto the page or click "+ Add Files" to browse. Several recordings can be queued and they all convert with the same settings. - Pick the Frame Under Frame Selection: "Specific Frame" is preselected with "Time (seconds)" set to
0, which grabs the very first frame. Type a decimal time such as12.5to land on a better moment, or switch to "Multiple Screenshots" and set a Capture Rate to sample icons across the whole recording. - Choose the Icon Size Preset: ICO is the one image target where sizing is preset-only — the percentage, keep-original, and width/height modes are hidden. The Preset dropdown runs 256P, 192P, 180P, 128P, 64P, 48P, 32P, 24P and 16P, and 256P is what applies if you change nothing. Read the next section before accepting that default.
- Convert and Download: Click Convert and save the
.ico. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours. No sign-up, no watermark.
What Dimensions You Actually Get
The preset is a height, not a bounding box. The frame is resized so its height matches the number you pick and its width follows from the aspect ratio — nothing is cropped and nothing is padded. Because recorded video is landscape, the width always ends up larger than the height, and on a widescreen source at 256P it overshoots the 256-pixel ceiling that ICO itself imposes.
| Source frame shape | 256P | 192P | 128P | Widest preset staying within 256 px |
|---|---|---|---|---|
| 1280 x 720 (16:9 HD broadcast) | 455 x 256 | 341 x 192 | 228 x 128 | 128P |
| 720 x 480 (stored NTSC standard definition, 3:2) | 384 x 256 | 288 x 192 | 192 x 128 | 128P |
| 640 x 480 (4:3) | 341 x 256 | 256 x 192 | 171 x 128 | 192P |
| 480 x 480 (square) | 256 x 256 | 192 x 192 | 128 x 128 | 256P |
The practical rule: for a 16:9 or standard-definition recording, pick 128P rather than leaving it at 256P, so the resulting width stays inside what the icon format can describe. Only a square source can safely use the full 256P.
If you want a genuinely square icon at the full 256 pixels, crop the still square before it becomes an icon: export the frame with DVR to PNG, crop it in an editor, then run PNG to ICO.
When This Doesn't Work
Two source problems stop this conversion cold. The first is copy protection: a DVR-MS file recorded from a broadcast marked as protected is bound to the PC that recorded it, and no external tool can decode it. The second is the extension being generic — .dvr is also used by standalone security recorders and set-top PVRs for entirely unrelated proprietary containers that are not ASF or MPEG-2 at all. If a file only opens in the recorder's own software, export or back it up to a standard video file from there first, then convert that. A quick sanity check: if VLC plays the recording, a frame can be pulled from it.
Frequently Asked Questions
Why is my ICO not square?
Because the size preset sets the height and lets the width follow the source aspect ratio, rather than cropping the frame to a square. That is deliberate — cropping would silently discard part of the picture you chose. A 16:9 broadcast frame at 256P therefore comes out 455 x 256, not 256 x 256. If you need a square icon, crop the still to a square yourself before converting it.
Can one .ico file hold 16, 32, 48 and 256 pixel versions at once?
The ICO format supports that, but this converter writes a single image per output file. In practice one reasonably large icon is enough, because Windows scales it down on the fly for smaller display contexts — 128P for a widescreen frame, or the full 256P if you have cropped the still square first. If you specifically need a multi-resolution icon bundle, build it in a dedicated icon editor from a set of exported stills.
Why does the ICO page have no quality or file size setting?
Because ICO output does not use one. On this page only three control groups render — the fixed ICO output, Image resolution, and Frame Selection. There is no quality preset, no target file size, and no colour palette control, unlike the JPG, PNG and TIFF targets. Size is governed entirely by the resolution preset you pick.
What size should I use for a Windows shortcut icon?
32P or 48P match the sizes Windows Explorer renders for shortcuts and desktop items, and 16P matches small list views. For an icon that also has to look right on a high-DPI display, 128P is the largest preset that keeps a widescreen frame inside the format's 256-pixel limit — that is a better choice than 256P for anything shot in 16:9.
Will the icon have a transparent background?
No. The frame extracted from the recording is fully opaque video, so there is no alpha channel to preserve. ICO itself supports transparency, so you can add it: export the frame as a PNG, erase the background in an editor such as GIMP or Photopea, then convert that PNG to ICO.
Why does my icon look blocky or soft?
DVR-MS stores MPEG-2, which is a lossy encoding of a broadcast signal, so the frame already carries macroblock artifacts before any resizing. Standard-definition recordings also start with far fewer pixels than a photo. Pick a frame from a low-motion, well-lit shot — MPEG-2 spends the most bits on stable scenes, so those frames hold the most detail.
My frame has comb-like horizontal lines. What causes that?
Interlacing. Broadcast standard-definition video stores each frame as two fields captured a fraction of a second apart, so freezing a frame during motion shows them as alternating comb lines. It is far more visible in a still than during playback. Choosing a static moment is the simplest fix; there is no deinterlace control on this page.
Why was my .dvr-ms file rejected before it even uploaded?
Because the page matches the file extension literally, and .dvr-ms is not .dvr. Rename the file so it ends in .dvr and it will be accepted — the container is recognised from the ASF header inside the file, so renaming does not affect decoding. This is only about the name check.
Are my uploaded recordings kept private?
Yes. Your file is uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours. There is no sign-up, no watermark, and your recordings are never shared or made public.