Initializing... drag & drop files here
Supports: CAVS
A .cavs file is video — a raw Chinese AVS (AVS1) elementary stream. ICO is the Windows icon container, where each stored image tops out at 256 x 256 pixels because the directory entry records width and height in a single byte apiece. So this is not "turning a clip into an animated icon": the converter freezes one frame and writes that single picture as an icon. This tutorial covers picking the frame, picking the size, and the one aspect-ratio trap that catches people converting widescreen footage.
.cavs file onto the page or click "+ Add Files" to browse. Several clips can be queued and each yields its own icon.0. Type the moment you want — the field takes decimals, so 2.1 is two and a tenth seconds in. "Multiple Screenshots" samples the whole clip instead..ico file. No sign-up, no watermark.Everything outside the single captured frame is discarded, so the timestamp matters more than any other setting. The default of 0 grabs the opening frame, which on a broadcast capture is usually a black lead-in, a fade or a channel ident — rarely what you want staring back at you from a taskbar.
1.5 is one and a half seconds, 12.25 is twelve and a quarter.2 and 5 and adjust once you see the result.Also remember that a raw AVS stream carries no index, so the seek lands on the nearest decodable frame at or after the offset you asked for rather than on a guaranteed exact one.
Microsoft's guidance is that an app should ship 16, 24, 32, 48 and 256 pixel icons as a bare minimum, because Windows looks for an exact size match first and only scales when it cannot find one.
| Size | Where it shows up on Windows 11 at 100% scaling | Available as a preset here |
|---|---|---|
| 16 px | Context menus, title bars, the system tray | Yes |
| 24 px | Taskbar, search results, the all-apps list | Yes |
| 32 px | Start menu pins | Yes |
| 48 px | The taskbar at 200% scaling and the system tray at 300% | Yes |
| 64 px | The system tray at 400% scaling | Yes |
| 128-192 px | Not Windows sizes — 180 px is Apple's touch-icon size and 192 px is the Android launcher size | 128, 180 and 192 |
| 256 px | Start pins at 400% scaling, the ICO maximum, and the size Windows scales down from | Yes |
| Control | Effect on the output | Worth knowing |
|---|---|---|
| Frame Selection → Specific Frame | Freezes one frame at your Time (seconds) value | Starts at 0; a raw AVS stream carries no index, so the seek lands on the nearest decodable frame |
| Frame Selection → Multiple Screenshots | Samples the clip at the Capture Rate you pick | Every sampled frame is written as its own .ico |
| Image resolution → Preset | Sets the icon's pixel height | The width follows the frame's aspect ratio — nothing is cropped or stretched |
| The 256-pixel ceiling | Applied automatically | The ICO directory stores each side in one byte, with 0 meaning 256, so no larger image can be written |
| Motion and sound | Discarded | ICO is a still format, and a raw .cavs has no audio track to begin with |
The consequence worth planning around: a widescreen frame does not become a square icon, because the aspect ratio is preserved rather than cropped away. If you need a true square, extract the frame with CAVS to PNG, square it up with Crop PNG, then run PNG to ICO.
If what you want is a viewable still rather than a tiny icon, convert to a normal image format instead — PNG for a lossless full-resolution frame, or CAVS to JPG for a small photographic one. If you want the clip to stay playable, an icon is the wrong target entirely and CAVS to MP4 is the right one. And if you are building a complete favicon package for a website rather than a one-off icon, our Favicon Generator produces a multi-size .ico plus the PNG and manifest files browsers and mobile launchers expect, which is more than a single-frame conversion can give you.
No. ICO stores still images, so the output is one frozen frame with no animation. There is no sound either, and in this case there never was: a raw .cavs is a video-only elementary stream, because AVS broadcast workflows coded audio separately and muxed it in only when the transport container was built.
The frame at time 0, the first one in the clip. That is frequently a black lead-in on broadcast captures, so setting Time (seconds) to a later moment is usually the difference between a usable icon and a black square.
Because of how the ICO directory is defined: each entry records the image width and height as a single byte, with the value 0 meaning 256. That caps any single image in the file at 256 pixels per side, and the converter clamps your requested size to match rather than writing something Windows would reject.
No, it is the aspect ratio being respected. The size preset sets the icon's height and the width follows from the shape of the video frame, so a 16:9 capture produces a wide icon rather than a square one. Nothing is cropped or stretched to force a square. If you need a conventional 1:1 icon, crop the frame to square before the ICO step — extract a PNG, crop that, then convert the cropped square.
No — this conversion writes one image at the size you selected. A shipping Windows app icon usually bundles 16, 24, 32, 48 and 256 pixel versions in a single .ico, and a website favicon commonly bundles 16, 32 and 48. Use the Favicon Generator when you need that multi-size bundle.
Two things stack up. The source is a standard-definition broadcast frame that was already compressed before you received it, and it is then reduced to a 256-pixel height at most — often an eight-fold reduction. Pick a frame with a simple, high-contrast subject; fine detail and busy backgrounds simply do not survive at icon scale.
Yes. A 32 or 16 pixel .ico works as a classic favicon.ico, and browsers still request that path. For a modern site you generally also want PNG icons for high-DPI tabs, an Apple touch icon and a web manifest, which is what the Favicon Generator produces in one pass.
Yes, and it is the efficient way to work with a format you cannot preview. Switch Frame Selection to "Multiple Screenshots" and choose a Capture Rate — anywhere from one frame every 0.1 seconds to one every 10 seconds. Each captured frame is written as its own icon, so you can look through them and keep the best.
It is uploaded over an encrypted connection, decoded and converted on our servers, and deleted automatically a few hours later — no sign-up, no watermark, never shared or made public.