Initializing... drag & drop files here
Supports: TS
.ts Transport Stream file or click "+ Add Files" to select one from your computer. Batch uploads are supported, so you can extract icons from multiple captures at once.2.5 to use the frame at 2.5 s), or pick Multiple Screenshots with a screenshot framerate (1 frame per second, every 5 s, etc.) to harvest several candidates from one TS file./favicon.ico or a Windows app icon — no sign-up, no watermark.A TS (MPEG-2 Transport Stream) is a 188-byte-packet container designed for broadcast pipelines — DVB, ATSC, IPTV and Blu-ray all use it, and most HDHomeRun / Plex DVR / OBS Studio / FFmpeg captures save as .ts. The ICO format, in contrast, is Microsoft's icon container introduced with Windows 1.0 and extended with 32-bit alpha in Windows XP and 256×256 PNG-compressed entries in Windows Vista. Converting between the two is essentially a two-step pipeline: extract a frame from the video, then encode it as a multi-size icon. Doing it in one upload saves you bouncing through FFmpeg + ImageMagick + an ICO packer.
/favicon.ico in a single step..ts screen capture and convert directly to a 256×256 ICO for an .exe resource or an Inno Setup installer..ts. Extract a representative frame and produce an ICO icon for a Windows shortcut or KMPlayer playlist..ts segments. Grab a frame from each clip to make per-flight desktop shortcuts on Windows..ts; extract the kill-cam frame as an ICO for use in Steam game-shortcut icons.ffmpeg -ss 00:00:02 -i in.ts -frames:v 1 out.png followed by magick out.png -define icon:auto-resize=256,128,64,48,32,16 favicon.ico. This page collapses that into one upload.| Property | TS (MPEG-2 Transport Stream) | ICO (Microsoft Icon) |
|---|---|---|
| Type | Video container | Multi-image icon container |
| Standardized | ISO/IEC 13818-1, first published 1995 | Introduced Windows 1.0 (1985); 32-bit alpha in XP; 256×256 + PNG in Vista |
| Typical packet/structure | 188-byte packets carrying PES elementary streams | ICONDIR header + ICONDIRENTRY array + image data (BMP or PNG inside) |
| Common codecs / content | H.264, H.265, MPEG-2 video; AAC, AC-3, DTS audio | BMP and PNG bitmaps; one ICO can hold 16, 32, 48, 64, 128 and 256 px sizes |
| Max useful resolution | Up to 8K depending on codec | 256×256 px per entry (Microsoft's official recommended ceiling) |
| MIME type | video/mp2t |
image/vnd.microsoft.icon (legacy: image/x-icon) |
| Where you see it | DVB / ATSC TV, Blu-ray, OBS, FFmpeg, HDHomeRun, IPTV | /favicon.ico, Windows .exe resource icons, desktop shortcuts |
| Editable in browser? | No native HTML5 playback in Chrome/Firefox/Edge | Yes — most modern browsers render ICO favicons natively |
| Size (px) | Use case | Notes |
|---|---|---|
| 16 × 16 | Browser tab favicon, address bar | The single most-rendered icon size on the web |
| 32 × 32 | Windows taskbar at 100% DPI, browser tabs on Retina | Add alongside 16×16 — both are essential |
| 48 × 48 | Windows desktop shortcuts, file-type icons | Recommended for any site users may pin or shortcut |
| 64 × 64 / 128 × 128 | Intermediate DPI scaling (125%, 150%) | Improves crispness on Windows scaling levels |
| 256 × 256 | Windows Vista+ large icons, Explorer "Extra Large" view | Stored PNG-compressed inside the ICO; Microsoft's recommended ceiling |
A typical multi-resolution favicon.ico packs 16, 32, 48 and 256. Generate the master at 256P here, then use PNG to ICO or JPG to ICO for additional sizes if your authoring tool only exports one face at a time.
ICO is a still-image container, not animated. (Microsoft's animated cursor format is .ani, not .ico.) So we have to pick one frame from your TS. Use Specific Frame + a Time (seconds) value if you know exactly where the still is, or Multiple Screenshots to harvest several candidates (e.g., one frame per second) and keep the best one.
256 × 256 pixels (the 256P preset). That's the largest size Microsoft recommends for ICO entries. While the ICO header technically allows larger dimensions since Vista, Windows Explorer and most browsers don't render anything above 256×256 from an ICO, so going bigger just wastes bytes. If you need a larger image, convert TS to PNG instead.
Yes — that's actually what .ico is designed for. A favicon.ico typically packs 16, 32, 48 and 256 px versions, and Windows / browsers pick the best face for the display context. This converter outputs one size per run; for a true multi-size ICO, generate each size and combine them with an ICO-merging tool, or start from a single 256 px master and let downstream tools resize.
The opposite. Downsampling 1920 × 1080 to 256 × 256 keeps a lot of detail per pixel. The pixelation risk runs the other way: tiny source frames (240p captures, for example) upscaled to 256 × 256 will look blocky. Start from the highest-resolution TS source you have.
Drop the file at your site root as /favicon.ico — browsers will auto-request it without any <link> tag. For belt-and-braces support across modern browsers, also add <link rel="icon" href="/favicon.ico"> to the <head>. MDN documents this default behavior as still valid in 2025/2026.
Yes. Chrome, Firefox, Edge and Safari all render ICO favicons natively — that's why the format hasn't been displaced despite SVG and PNG alternatives existing. The legacy MIME type is image/x-icon; the IANA-registered type is image/vnd.microsoft.icon. Both work in browsers today.
Chrome, Firefox and Edge don't ship an MPEG-2 Transport Stream demuxer in HTML5 <video>. VLC, MPC-HC, mpv and FFmpeg do. Conversion still works because we demux server-side. If you want a previewable web file alongside the icon, also convert TS to MP4.
Yes, use ICO to PNG. That's useful if you have a legacy favicon.ico and want the individual size faces as PNGs for a modern <link rel="icon" sizes="..."> setup or for use in app stores that require PNG submissions.