Skip to content

TIFF to ICO Converter

Convert TIFF to ICO in your browser. TIFF files usually come from scanners, print and publishing workflows, photo archives and tethered camera capture; ICO is the better fit for favicons and Windows icons. You get a multi-size ICO with PNG-compressed icons (16, 32, 48 and 256 px by default). Nothing is uploaded.

  • Processed locally
  • No upload, no wait
  • No sign-up
  • No watermark

Drop images here

or choose files · paste with Ctrl/⌘ V

TIFF expected · other image formats also work

Files are processed on this device. Nothing is uploaded.0 B uploaded

How to use TIFF to ICO

  1. 1

    Add your TIFF files: drop them here, choose them, or paste from the clipboard.

  2. 2

    Choose the icon sizes to include.

  3. 3

    Click Convert. Each file is decoded and encoded in a background thread on this device.

  4. 4

    Download the .ico files one at a time or together as a ZIP.

Why use Aback Images for tiff to ico

Where the ICO goes next

ICO opens in every browser (as a favicon), Windows and most Linux desktops.

ICO next to TIFF

Both sides are lossless, so the size depends on how well the ICO encoder handles this picture compared with the TIFF's none, LZW, PackBits, Deflate or JPEG, chosen per file.

Written without a lossy pass

The ICO is written losslessly, so the pixels decoded from the TIFF arrive unchanged, apart from precision beyond 8 bits per channel.

Processed on your device

Your images are decoded, edited and encoded inside this browser tab by Web Workers. Nothing is uploaded to a server.

TIFF vs ICO

What changes from TIFF to ICO

Encoding: the TIFF uses none, LZW, PackBits, Deflate or JPEG, chosen per file; ICO uses each size stored as a headerless BMP or as a complete PNG, and the download is a multi-size ICO with PNG-compressed icons (16, 32, 48 and 256 px by default).

Bit depth: 1 to 16 bits per channel, or 32-bit floating point in the TIFF; ICO allows 1 to 32 bits per pixel, set per size, and the ICO written here has 32 bits per pixel. 16-bit and floating-point TIFFs are reduced to 8 bits per channel.

Colour: RGB, CMYK, Lab, greyscale or palette, often with an ICC profile in the TIFF; ICO supports RGB or a palette, per image, written here as 8-bit sRGB.

Transparency: the TIFF stores it as an extra sample declared in the ExtraSamples tag; the ICO keeps it as 8-bit alpha in 32-bit and PNG entries, or a 1-bit mask in old icons.

Other images: the TIFF can hold several pages, each in its own image file directory; only the main image is converted.

Metadata: the TIFF can carry EXIF, XMP, IPTC and ICC, all stored as tags; ICO can carry only a directory of the sizes inside, with no EXIF, but nothing is copied across.

About TIFF

TIFF is the professional archive and print format. It can hold multiple pages, high bit depths and lossless data, and is common in scanning, publishing and GIS.

A TIFF begins with 'II' or 'MM' for the byte order and the number 42, then an offset to the first image file directory (IFD): a table of tags giving the size, compression, colour model and the location of the strips or tiles of pixels. Each further page is another IFD.

TIFF files usually come from scanners, print and publishing workflows, photo archives and tethered camera capture.

About ICO

ICO is a container that bundles several sizes of the same icon (16, 32, 48, 256 px) into one file. It is still the most compatible format for website favicons and Windows app icons.

An ICO starts with a 6-byte ICONDIR (type 1 for icons) and a 16-byte entry per image giving width, height, colour count and offset. Each image is either a BMP without its file header plus an AND mask, or a complete PNG.

When converting TIFF to ICO makes sense

ICO is the better choice for favicons and Windows icons, while TIFF suits printing, scanning and archival masters.

ICO strengths: Multiple sizes in one file; Required by Windows and supported by every browser as a favicon. Drawbacks to weigh: Max 256×256 per image; Not for photos.

Limitations

  • Only the first page of a multi-page TIFF is converted; split the file first if you need every page.
  • CMYK TIFFs from print workflows are converted to RGB, which changes how a print shop's colours are described.
  • Each size inside the ICO is scaled from your image, and detailed artwork loses legibility at 16 and 32 px, so simplify logos first.
  • Non-square images are centred on a transparent square for each icon size.

Frequently asked questions

Does converting TIFF to ICO lose quality?

ICO is written losslessly, so the pixels are stored exactly as decoded. 16-bit and floating-point TIFFs are reduced to 8 bits per channel. Not carried over: any several pages.

Is transparency kept in the ICO?

Yes. TIFF stores it as an extra sample declared in the ExtraSamples tag, and the ICO is written with an alpha channel, so transparent areas stay transparent.

Which icon sizes are included?

16, 32, 48 and 256 px by default, the set Windows and browsers expect. You can choose other sizes. Non-square images are centred on a transparent square.

Which apps open ICO files?

Every browser (as a favicon), Windows and most Linux desktops.

Are my images uploaded anywhere?

No. Processing happens inside your browser with WebAssembly and Web Workers. The site only downloads the app code and codecs; your files never leave your device. You can confirm this with the live upload counter on the tool, or in your browser's network panel.

Can I process many files at once?

Yes. Drop a whole selection or folder. Files are processed in parallel on several worker threads, each result can be downloaded on its own, and everything can be saved as one ZIP.

Is it free? Is there a file limit or watermark?

It is free with no account, no watermark and no daily limit. The only limit is your device's memory: very large images (over roughly 100 megapixels) may be refused to keep the tab from crashing.