Initializing... drag & drop files here
Supports: MJPEG
This tool takes one frame out of a Motion JPEG capture — a webcam recording, an IP or security-camera export, a capture-card clip — and writes it as a Windows .ico icon. The extraction is the straightforward part, because every MJPEG frame is already a complete, independent JPEG and comes out without the inter-frame smearing you can hit when grabbing from H.264 or HEVC. The part worth reading before you convert is the sizing, which does not behave the way most people expect from an icon tool: the preset list sets the icon's height, and the width follows your video's aspect ratio. A widescreen frame therefore produces a wide, non-square icon, and above a certain preset it produces one the ICO format cannot describe properly. The sections below cover how to stay inside that limit and what to do when you need a true square.
.mjpeg or .mjpg clip onto the page, or click "Add Files" to browse. Several clips can be queued and an icon taken from each..ico. Uploads travel over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours. No sign-up, no watermark.This is the one thing that catches people out, so it is worth being explicit. When you select 256P, the converter scales your frame to 256 pixels tall and lets the width land wherever the source aspect ratio puts it. On a 1920×1080 capture that is 455 pixels wide.
That matters because of how the ICO container describes its contents. Each image in an icon file is catalogued by an ICONDIRENTRY structure, and in Microsoft's icon format documentation the bWidth and bHeight members are single BYTE fields. A byte cannot hold 455. Anything wider than 255 pixels cannot be catalogued correctly, which is why 256 is the ceiling everyone quotes for icon dimensions — and why a preset that looks safe on paper is not safe once the aspect ratio multiplies it.
The practical rules that fall out of this:
| Preset | Width from a 16:9 frame | Width from a 4:3 frame |
|---|---|---|
| 256P | ~455 — too wide to declare | ~341 — too wide to declare |
| 192P | ~341 — too wide to declare | 256 — right at the limit |
| 180P | ~320 — too wide to declare | 240 |
| 128P | ~228 | ~171 |
| 64P | ~114 | ~85 |
| 48P | ~85 | 64 |
| 32P | ~57 | ~43 |
| 24P | ~43 | 32 |
| 16P | ~28 | ~21 |
| Property | MJPEG (source) | ICO (output) |
|---|---|---|
| Type | Video — a run of complete JPEG frames | A single still icon image |
| Compression | Intra-frame JPEG, every frame independent | Bitmap or PNG-compressed image inside the icon container |
| Typical dimensions | Capture resolution, e.g. 1280×720 | Small, and rectangular unless your source is square |
| Maximum declarable size | n/a | 255 px per side in the directory entry, 256 by convention |
| Transparency | None — JPEG has no alpha channel | Supported by the format, but nothing here supplies it |
| Timing metadata | Absent from a raw stream | n/a |
| Best for | Surveillance, machine vision, frame-exact review | Windows app icons, shortcuts, favicons |
If you need a proper square icon — which is what Windows shortcuts, taskbar pins and favicons really want — this page cannot produce one on its own, because the only resolution control it exposes is the preset height. The reliable route is three steps: extract the frame with MJPEG to PNG, square it up with crop PNG so the subject sits in a 1:1 frame, then run PNG to ICO on the result. That also gives you the chance to add a transparent background, which a video frame can never supply, and to compose the artwork so it stays legible once it is 32 pixels tall. It is more clicks, but it is the difference between an icon that happens to be a video still and one that works as an icon.
Because the preset list on this page sets height only, and the converter derives the width from your source's aspect ratio. A 1280×720 frame at 128P becomes roughly 228×128, not 128×128. The controls that would let you force exact dimensions — width, height and percentage inputs — do not render on the ICO target, so there is no way to square the image at this stage. Crop the frame to 1:1 before it reaches the icon step, using the PNG route described above.
Not the largest number in the dropdown. The icon directory stores each image's width and height as single bytes, so 255 pixels is the hard ceiling for what can be catalogued (256 is addressable only by convention). Since the preset controls height and the width follows the aspect ratio, a 16:9 frame at 256P works out around 455 pixels wide and cannot be described correctly. For widescreen sources, treat 128P as the practical maximum; for 4:3 sources, 180P.
Browsers commonly request 16 and 32 pixel icons for tabs and bookmarks, and Windows uses 48 for shortcuts and larger sizes for taskbar pins. For a favicon specifically, 32P is the sensible single choice with 16P as the low-DPI fallback. Bear in mind that a favicon really should be square, so the PNG-crop route is worth the extra two steps if the icon is going onto a live site rather than into a quick internal tool.
Two reasons. First, precision: addressing a frame by timestamp is repeatable, whereas a manual screenshot captures whatever the player happened to be displaying and is tied to your screen's scaling. Second, fidelity: every MJPEG frame is a complete, self-contained JPEG, so it decodes exactly as recorded — there is no inter-frame reconstruction that might introduce blocking, which is the risk when you pull a frame from H.264 footage between keyframes.
No, and it cannot. JPEG has no alpha channel, so every frame in a Motion JPEG stream is fully opaque and there is simply nothing transparent to carry across — the icon's background will be whatever the camera was pointed at. The ICO format itself handles 8-bit alpha perfectly well, but that has to come from a source that already has it. Start from a transparent PNG via PNG to ICO if you need a cut-out subject.
Yes. Set Frame Selection to Multiple Screenshots and choose a capture rate, which runs from one frame every 0.1 seconds up to one every 10 seconds. That returns a set of stills sampled across the clip so you can pick the sharpest, best-composed candidate, then re-run with Specific Frame at that timestamp. It is the practical approach when the subject is moving, since a small icon is unforgiving of motion blur.
Barely. Only the frame you asked for is decoded, so a two-hour surveillance export converts about as fast as a ten-second clip once it has finished uploading. The real cost with a long capture is transferring it to our servers in the first place — the file is processed server-side, so upload time, not clip length, is what you will be waiting on. Trimming the recording beforehand is the quickest way to cut that down.
It is uploaded over an encrypted connection, decoded on our servers to extract the frame you selected, and both the upload and the resulting icon are deleted automatically after a few hours. Nothing is shared or made public, no account is required, and no watermark is applied to the output. If you would rather keep the frame as a full-size, editable image instead of an icon, MJPEG to PNG preserves the original frame dimensions and gives you something to work from.