Initializing... drag & drop files here
Supports: TIFF, TIF
.tiff or .tif image. Batch conversion is supported, and Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared..ico file at the size you picked. To build a multi-resolution favicon, run the conversion once per size and merge externally, or start from a PNG to ICO workflow if your source is already raster-flat.TIFF (Tagged Image File Format) is the print and archival workhorse — 16- and 32-bit color, lossless LZW or ZIP compression, alpha channels, and multi-page support make it the default output of professional scanners and Adobe Photoshop's "save as archive" workflow. ICO is the Windows icon container that has shipped since Windows 1.0 (1985) and remains the single format every desktop browser still recognizes for favicon.ico at a website's root. Converting TIFF to ICO bridges high-fidelity source art to a 256×256-capped icon target.
/favicon.ico even when no <link rel="icon"> tag is set..exe resources all expect .ico. TIFF source art keeps alpha-channel cutouts intact through the round-trip..ico for the installer EXE and Start Menu entry. Designers commonly hand off layered TIFFs, and the conversion produces the asset the installer toolchain expects.| Property | TIFF | ICO |
|---|---|---|
| Introduced | 1986 (Aldus) | 1985 (Windows 1.0) |
| Primary use | Print, archival, scanning | Windows icons, browser favicons |
| Max dimensions | 4 GB per file, no pixel cap | 256×256 (since Windows Vista) |
| Bit depths | 1, 4, 8, 16, 24, 32-bit + float | 1, 4, 8, 16, 24, 32-bit |
| Alpha channel | Yes (via extra samples) | Yes (32-bit with 8-bit alpha) |
| Compression | LZW, ZIP, JPEG, PackBits, none | BMP or PNG internally |
| Multi-image | Yes (multi-page) | Yes (multi-resolution in one.ico) |
| Typical file size | 5-200 MB | 4-100 KB |
| Browser support | None for <img> direct |
All major browsers via favicon.ico |
| Size | Preset | Primary use |
|---|---|---|
| 256×256 | 256P | Windows Vista+ "Extra large icons" view, high-DPI displays, app store listings |
| 192×192 | 192P | Android home-screen-style PWA assets (export separately as PNG too) |
| 128×128 | 128P | Large toolbar icons, Mac-style large views |
| 64×64 | 64P | Medium icon view, retina taskbar |
| 48×48 | 48P | Windows desktop "Medium icons" default, Windows site tiles |
| 32×32 | 32P | Windows taskbar pinning, high-DPI browser tabs, bookmarks bar |
| 16×16 | 16P | Standard browser tab favicon, address bar, system tray |
For a complete favicon set, the favicon.ico that sits at a site's root should ideally contain 16×16, 32×32, and 48×48 — browsers pick the closest match automatically. Apple Touch (180×180) and Android/PWA (192×192, 512×512) are delivered as separate PNGs, not stored in the ICO.
ICO doesn't expose user-adjustable compression. Internally each image inside the ICO is stored as either a BMP bitmap (pre-Vista standard) or a PNG block (Vista and later). Both modes are lossless. To shrink the output, drop to a lower resolution preset or reduce color depth in your source TIFF before converting.
The browser-side converter outputs a single-resolution ICO per run. To build a multi-resolution favicon.ico, convert your TIFF three times (at 16P, 32P, and 48P), then merge the outputs with a desktop tool like ImageMagick (magick convert 16.ico 32.ico 48.ico favicon.ico) or a dedicated icon editor such as IcoFX or Greenfish Icon Editor. Most modern browsers also accept three separate PNGs via <link rel="icon" sizes="..."> tags as an alternative.
Yes, provided the TIFF carries a real alpha channel (extra samples flagged as "associated alpha"). ICO supports a full 8-bit alpha channel at 32-bit color depth, so soft edges and drop shadows survive the conversion. If your TIFF uses a white or checkerboard background instead of true alpha, the converter has no transparency to keep — you'll need to mask the background in an editor like Photopea or GIMP first.
Multi-page TIFFs (common output from document scanners) get reduced to their first page on conversion. ICO can hold multiple images, but they're meant to be different resolutions of the same icon, not different documents. If you need every page, convert TIFF to PNG first and pick the page you want, or split the TIFF in a tool that handles multi-page output.
Start with a TIFF at 256×256 or larger. Downscaling from a higher source gives the converter more pixel data to work with, and the result at 16×16 retains sharper anti-aliasing than upscaling from a smaller original. For logos with thin strokes (a 1-pixel stroke at 256×256 vanishes at 16×16), consider supplying a simplified "favicon-grade" TIFF that's been hinted for tiny rendering.
Strongly preferred. ICO icons are square by definition — every browser, Windows shell, and macOS tool that reads an .ico assumes a square aspect ratio. If you feed a 1200×800 landscape TIFF and pick a single dimension, the converter will stretch or letterbox depending on which dimension you set. Crop to square in an editor or use xconvert's crop image tool first.
Not directly. macOS uses .icns for application bundles, not .ico. For a Mac desktop shortcut (alias), you can drag any image into the "Get Info" preview box, but the system stores it as .icns internally. Browsers on macOS (Safari, Chrome, Firefox) do read favicon.ico files served from a website, so the ICO works fine for web favicons regardless of the visitor's OS.
No — they're the same format with two extensions. The 3-letter .tif dates back to DOS / Windows 3.x filename limits; .tiff is the modern 4-letter version. The xconvert tool accepts both and produces identical ICO output either way.
Upload the resulting favicon.ico to your site root so it's served at https://example.com/favicon.ico. Modern browsers fetch this automatically. For best coverage, also add <link rel="icon" type="image/x-icon" href="/favicon.ico"> and <link rel="apple-touch-icon" href="/apple-touch-icon.png"> (separate 180×180 PNG) inside <head>. Hard-refresh (Ctrl+F5 or Cmd+Shift+R) — favicons are aggressively cached, sometimes for weeks.