How to use the favicon multi-size set guide
A favicon is rarely a single file. Browser tabs, bookmark lists and installed web app icons each read a different size, so most sites export several at once. Give this page your source width and height in px plus the target sizes you plan to export, and it reports how each target compares to the source, whether it requires upscaling and how many px you are short — then writes the link tags for your head and the icons array for a web app manifest.
For tabs, bookmarks and web app manifests the set of 16, 32, 48, 180, 192 and 512 px is widely used. Which size each surface actually wants, and the file naming around it, is something platforms revise regularly, so treat that set as a convention current in October 2026 and confirm it against each platform's official documentation. Entering your own list replaces the set entirely.
The upscaling verdict compares each target against the shorter side of your source in whole px. When the source is not square, the page assumes a center crop and reports how much is trimmed from the longer side. This tool deliberately leaves out app store icon dimensions and per-platform icon tables, and it does not convert image files for you. It plans sizes, nothing more.
Frequently asked questions
One .ico does cover the tab, but bookmark lists and web app install screens often look for larger PNGs instead, which is why the page writes both the link tags and the manifest entries for you.
No. They are a widely used convention as of October 2026. The sizes platforms ask for do change, so check each platform's own documentation and enter your own list if it differs.
The row is marked as needing upscaling and shows how many px you are short. Stretching a small source softens the edges, so re-export from a vector file or a larger image instead.