Convert ICO to TIFF
TIFF is the format that print shops, scanners and archives agree on, and it is one of the few common raster formats that discards nothing. Converting an icon into it is unusual but sensible when the artwork has to enter a print or document-management workflow that will not look at an ICO. The largest image inside the container is used, and its color is carried across intact.
Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.
Add to Chrome — freeDrop your ICO file here, or click to browse
Up to 50 MB. Deleted automatically after 30 minutes.
What it does
- The largest size inside the container is used
- Lossless: no color is discarded and nothing is re-encoded lossily
- Accepted by print, scanning and document-management workflows
How to use ICO to TIFF
- 1
Upload the .ico
A favicon or an application icon holding one or several sizes. The directory inside the file is read to find out which.
- 2
The biggest frame is selected
Only one image can become the TIFF, so the largest is taken. It is the only one with enough detail to be worth archiving or printing.
- 3
Nothing is thrown away
Unlike a palette format, TIFF holds the full color range, so the frame arrives as an exact copy of what was decoded.
How it works
The ICO's internal directory is read to enumerate the images it holds, each with its own width, height and color depth. The largest is decoded to a full-color raster and written into a TIFF container without any reduction step.
There is no palette stage here, which is what separates this from converting an icon to GIF. TIFF holds full color, so the decoded pixels go in as they came out.
Why the largest frame
An ICO exists so an operating system can pick a size appropriate to where it is drawing. A conversion has no such context, so it has to choose once. Choosing the largest is the option that preserves the most information: a bigger image can be reduced later with good results, while a 16 pixel one cannot be enlarged into anything useful.
Where TIFF is the right destination
Print and archival workflows, almost exclusively. TIFF is the format a prepress operator, a scanning bureau or a records system expects, and it is one of very few raster formats that a long-term archive will accept, precisely because it discards nothing and its structure is well documented.
Where it is not
The web. TIFF files are large, browsers do not display them reliably, and none of the properties that make TIFF good for archives matter in a page. For a favicon, a web graphic or an app asset, PNG is the correct target: lossless, small, with a real alpha channel, and understood everywhere.
What about transparency
TIFF can hold an alpha channel, so a transparent icon does not need to be flattened onto a background the way it would for JPG. Whether the receiving application honors that alpha is a separate question and worth checking before the file goes into a print job.
Why TIFF is an odd but reasonable target
TIFF is a professional imaging format: lossless, high bit depth, and able to hold several images in one file. That last property makes it an unusually good match for an ICO, which is itself a multi-image container.
What happens here is simpler than that suggests — the largest icon in the file is taken and written as a single TIFF image. The size selection matters because an ICO's smaller entries are frequently drawn separately rather than scaled, so they are different pictures rather than smaller ones.
Use this when something in a print or imaging workflow demands TIFF. For anything on a screen, PNG is smaller and equally lossless.
Examples
An application icon for a print asset sheet
The TIFF is larger than the ICO because it is not compressed the same way, and that is the trade being made: bytes for fidelity. Every pixel is exactly what the icon contained.
An old favicon going into a document archive
The 32 pixel version is taken. It is still a 32 pixel image and will not print well at any size; the conversion makes it acceptable to the archive, not larger or sharper than it was.
Frequently asked questions
Why would anyone convert an icon to TIFF?
Because the receiving system demands it. Print production, scanning workflows and document-management systems frequently accept a short list of formats and TIFF is almost always on it while ICO almost never is. The conversion is about acceptance rather than quality, and it is lossless, so nothing is given up by going through it.
Is anything lost compared to the original ICO?
The other sizes in the container are, because only one image can become the TIFF and the largest is chosen. The pixels of that chosen image are carried across without loss: no palette reduction, no lossy re-encoding, no resampling. If you need every size preserved, keep the ICO alongside the TIFF rather than replacing it.
Why is the TIFF so much larger than the ICO?
TIFF stores pixels in a form built for fidelity and predictable reading rather than for the smallest possible file, while an ICO commonly holds its larger entries in a compressed form. A 256 pixel icon that occupied a hundred kilobytes can easily occupy a quarter of a megabyte as a TIFF. That is the expected outcome, not a sign of something going wrong.