Initializing... drag & drop files here
Supports: MPEG2
This page decodes a frame out of your MPEG-2 program stream and writes it as a Windows ICO. It is a still-image conversion — the file you get is an icon, not an animation — and it is worth two minutes of reading first, because ICO is the most constrained target on this site and video frames are the least icon-shaped source you can feed it.
Two constraints drive everything below. First, an ICO directory entry stores each image's width and height in a single byte each, so 256x256 is the largest size the format can describe, with a stored value of 0 standing in for 256. Second, the only sizing control on this page is a preset list, and those presets set the height — the width follows the shape of your video frame. A 4:3 frame at the 256P preset is roughly 341 px wide, and a 16:9 frame is roughly 455 px wide. Both are wider than an ICO entry can honestly declare.
.mpg, .mpeg or .mpeg2 file onto the page or click "Add Files." Several files can be queued and each produces its own icon.The preset is a height. Width is derived from your frame's aspect ratio, so the same preset gives different widths for 4:3 and 16:9 material. Figures below are approximate because the scaler rounds.
| Preset | Height | Width from a 4:3 frame | Width from a 16:9 frame | Width an ICO entry can declare |
|---|---|---|---|---|
| 256P | 256 | ~341 | ~455 | No — both exceed the 256 px ceiling |
| 192P | 192 | ~256 | ~341 | 4:3 only, and only as the special 0 byte |
| 180P | 180 | ~240 | ~320 | 4:3 yes, 16:9 no |
| 128P | 128 | ~171 | ~228 | Yes for both — the safe ceiling |
| 64P | 64 | ~85 | ~114 | Yes |
| 48P | 48 | ~64 | ~85 | Yes |
| 32P | 32 | ~43 | ~57 | Yes |
| 16P | 16 | ~21 | ~28 | Yes |
256P is a sensible default for a square source image, where 256x256 is exactly the maximum an ICO can describe and the size Windows uses for large-icon views. It is the wrong default for a video frame, because a video frame is not square. Pushing the height to 256 pushes the width past 256, and the directory entry has nowhere to put a number that large — the byte that should say "341" cannot, so the entry ends up declaring a width the bitmap does not have. Icon consumers that trust the directory then draw the image wrong or skip the entry.
Pick 128P or lower. At 128P a 4:3 frame lands near 171x128 and a 16:9 frame near 228x128 — both comfortably inside what the format can describe. If your icon is destined for a browser tab or a shortcut, you want 32P or 48P anyway, and at those sizes the constraint never comes up.
There is also no width, height, percentage or keep-original control on ICO targets, and no quality or bit-depth setting either. The preset list is the entire sizing surface, which is why choosing the right entry from it is most of the work on this page.
| Property | Value |
|---|---|
| Structure | ICONDIR header plus one ICONDIRENTRY per image — an ICO is a directory of images |
| Width field | 1 byte, 0–255, where a stored 0 means 256 |
| Height field | 1 byte, 0–255, with the same 0-means-256 rule |
| Largest describable image | 256x256 |
| Frame encoding | BMP/DIB, or PNG-compressed — Windows Vista added PNG frame support, which is what made 256x256 icons practical |
| Sizes Windows 10 and 11 ship system icons at | 16, 20, 24, 32, 40, 48, 64 and 256 px |
| Common favicon sizes | 16 and 32 px |
| Transparency | Supported by 32-bit icons; a decoded video frame has no alpha, so the output is fully opaque |
| Animation | Not supported — ICO is a still format |
If what you actually want is a clean, square favicon or app icon, going straight from video to ICO is the wrong route, because nothing on this page can crop. Take the three-step path instead: grab the frame with MPEG-2 to PNG, which has the same frame picker and no shape constraints, crop it square with the PNG cropper, then convert the square result with PNG to ICO. That gives you a genuinely square icon at whatever size you choose, and it sidesteps the width-byte problem entirely.
Because ICO targets expose only the preset list. The width, height, Width x Height and percentage controls that appear on other image conversions are hidden here, so the preset — which sets height — is the only sizing input available. To land on an exact square size, crop the frame square first and then convert; the preset height then equals the width because the shape is 1:1.
In practice 128P. The format's ceiling is 256x256, and because the preset sets height while the width follows your frame's aspect ratio, a 256-pixel-tall video frame is 341 px wide at 4:3 or 455 px wide at 16:9 — beyond what a one-byte width field can express. 128P keeps both shapes inside the limit. If you need a true 256x256 icon, the source has to be square before it reaches an ICO encoder.
No. ICO is a still-image format with no animation support at all, so what you get is a single captured frame. If you wanted movement, MPEG-2 to GIF produces a looping animation instead. The ANI format Windows uses for animated cursors is a different container and is not produced here.
Set Time (seconds) under Specific Frame to the timestamp you want — decimals are accepted, so 12.5 is valid. This matters on DVD material more than most sources, because rips habitually begin on black, a distributor card or menu artwork, and the default of 0 captures exactly that. If you are not sure which moment you want, switch to Multiple Screenshots and pick a Capture Rate to sample the file at intervals.
No. A decoded video frame is fully opaque — there is no alpha channel in MPEG-2 video to carry — so every pixel of the icon is filled. The ICO format itself does support transparency in 32-bit icons, so if you need a transparent icon, cut the background out of a PNG first and convert that with PNG to ICO.
Not from one conversion here. An ICO is structurally a directory that can hold several sizes, and Windows picks the right entry per context, but assembling that multi-size file is a job for a dedicated icon editor. Produce the individual sizes you need — or better, produce one square PNG master — and combine them there.
Two reasons stack. A DVD frame is only 720x480 or 720x576 to begin with and is already lossy, and then it is scaled down hard — to 32 px, that is a reduction of more than 20:1 in area. Fine detail simply cannot survive that. Icons work best from graphic sources with bold shapes; a photographic frame from footage will always read as mushy at small sizes.
Less than at full size, but it is not always invisible. There is no deinterlacing anywhere in this pipeline, so an interlaced frame is captured with both fields woven together; at 128P you can still see the serration on a moving edge, while at 32P it usually blurs away in the downscale. Choosing a frame where the subject is still avoids the question.
No. It is uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours, along with the ICO that was produced. There is no sign-up, no watermark, and nothing is shared or made public. Only the frame you selected is written out — the rest of the stream is decoded in passing and discarded.