Initializing... drag & drop files here
Supports: ICO
ICO is a Windows icon container — the small favicon.ico and app-icon format that bundles several sizes in one file. TIFF (Tagged Image File Format) is the lossless raster format that print shops, archives, and editors use for master copies. This converter decodes the icon and writes it back out as a TIFF, which is useful when you need an icon's artwork as a high-fidelity, editable file rather than a tiny icon resource. One thing to set expectations on first: an ICO frame tops out at 256×256 pixels and is often far smaller, so the TIFF you get is a faithful, lossless copy of a small image — the conversion preserves detail but cannot add resolution the icon never had. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, never shared or made public.
| Property | Value |
|---|---|
| Full name | Windows Icon (ICO) |
| Origin | Microsoft, Windows 1.0 (1985) |
| Type | Icon container — holds multiple images in one file |
| Max dimensions | 256×256 pixels per stored image |
| Stored payload | BMP/DIB bitmap, or full PNG per image (PNG frames readable since Windows Vista) |
| Color / bit depth | Up to 32-bit (8-bit RGBA); 32-bit color added in Windows XP |
| Transparency (alpha) | 8-bit alpha on 32-bit images; 1-bit AND mask on older bit depths |
| Best for | Favicons, Windows desktop and app icons, legacy compatibility |
| Native browser role | Universal as a favicon (/favicon.ico); not used to display page content |
| Property | Value |
|---|---|
| Full name | Tagged Image File Format (TIFF / TIF) |
| Origin | Aldus Corporation, first released 12 September 1986 |
| Specification | TIFF 6.0 (3 June 1992); controlled by Adobe since it acquired Aldus in 1994 |
| Compression | None (uncompressed), LZW, PackBits, Deflate (ZIP) — all lossless; optional lossy JPEG |
| Color models | RGB, RGBA, CMYK, grayscale |
| Bit depth | Commonly 8-bit/channel; supports 16-bit/channel and beyond |
| Transparency (alpha) | Yes — RGBA with an alpha channel |
| Best for | Print, archival masters, scanner output, editing handoffs |
| Native browser support | Safari only; MDN advises against TIFF for web content |
.ico onto the page or click "+ Add Files" to browse. Multi-size icon containers are accepted, and you can queue several icons for batch conversion..tif if your other software expects that spelling. No sign-up, no watermark.An ICO file is a container that can bundle 16×16, 32×32, 48×48, and 256×256 versions of the same icon. The converter takes the largest image stored in the file, because it carries the most detail — so a typical multi-size favicon produces a 256×256 TIFF. That mirrors the nearest-/largest-fit logic Windows itself uses when it draws an icon. If you want a smaller output, scale it down with the "Image resolution" controls in step 3.
No. An ICO image is at most 256×256 pixels and frequently just 16, 32, or 48 pixels wide. TIFF is a lossless container, so it preserves every pixel it is given exactly — but it cannot invent detail that was never captured. If you set a large output size, the converter enlarges the same pixels rather than adding sharpness. The honest result of this conversion is a pixel-perfect TIFF of a small image. For a crisp full-size graphic, start from the original artwork, not the icon.
Yes. TIFF supports an RGBA alpha channel, and the 32-bit images inside most modern ICO files carry their transparency across. If your icon uses only the older 1-bit AND mask — fully transparent or fully opaque, with no blending — that maps to hard-edged alpha in the TIFF, which is a limit of the source rather than the conversion. In our testing, a 256×256 RGBA favicon produced a TIFF whose anti-aliased edges stayed clean against a transparent background.
All three are lossless, so the picture is identical; they only differ in file size and compatibility. LZW is the de-facto TIFF standard and is read by virtually every image program, which makes it the safe default. Deflate (ZIP) typically produces a slightly smaller file and is well supported by modern software. None writes the image uncompressed — the largest file, but the most universally readable. For an icon-sized image the difference is a few kilobytes either way, so LZW is a fine choice unless your downstream tool specifically wants one of the others.
Yes — .tif and .tiff are two spellings of the same Tagged Image File Format, and the bytes inside are identical. The three-letter .tif dates to MS-DOS and early Windows, which limited extensions to three characters under the 8.3 filename rule. This tool exposes a TIFF / TIF extension toggle so you can match whatever your other software expects; if you specifically need the three-letter spelling, use ICO to TIF — it produces the same file.
Choose TIFF when the destination is a print pipeline, a digital archive, or an editor who expects the format scanners and DTP software output. TIFF stores pixels losslessly and can carry CMYK and high-bit-depth color that an ICO cannot. If instead you just want a normal, widely viewable image of the icon — to drop into any editor or re-edit — ICO to PNG is the more practical, lossless pick and opens in every browser. And if your goal is actually to make a favicon, neither TIFF nor a converted icon helps; build one the other direction with a PNG-to-ICO tool.
No, and the two formats play opposite roles. An ICO works as a favicon in every browser because that is what the format was designed for, but browsers do not use ICO to display ordinary page images. TIFF is the reverse: it is a working/archival format that, per MDN, only Safari renders natively and which is not recommended for web content at all. Treat the TIFF you get here as a file for editing, printing, or storage — not as something to embed on a web page.
Your file is uploaded over an encrypted connection, decoded and re-encoded to TIFF on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, never shared or made public. The main practical limit is upload size and time rather than your device; because an icon is small, both the upload and the resulting TIFF are tiny.