Convert a PNG, JPG or WebP image into a single multi-resolution .ico favicon. Tick the sizes you need — 16, 32, 48, 64, 128 and 256 pixels — and every entry is rendered, previewed and packed into one favicon.ico file that browsers can pick from automatically.
Square artwork works best: the tool crops to a centered square, so a wide logo loses its sides. Transparent PNG keeps its alpha, or you can fill a white or custom background first. All processing runs locally in your browser. Your data is not uploaded to any server. 100% Local
Ctrl/⌘+V; a transparent PNG at 256 px or larger is ideal.<link rel="icon" href="/favicon.ico"> to the head of every page.16 px is the classic browser tab, 32 px is the high-DPI tab and bookmark bar, 48 px covers Windows taskbar shortcuts, and 256 px is used by large icon views and some launchers. 64 and 128 px fill the gap for medium displays and dock-style icons. Because the browser chooses the closest entry, including more sizes costs only a few kilobytes — but always keep 16 and 32 px, since those are the ones users see most.
At 16 px you have 256 pixels in total, so fine detail disappears. Use a single strong shape, two or three flat colors and no thin strokes; drop any text that is not legible at that size. Increase the padding a little if the logo has important edges. You can generate one version with padding for the tab and a tighter version for the 256 px entry, but a single balanced file is usually enough.
A single favicon.ico in the site root is still the most compatible option: every browser requests it by default, and older clients ignore PNG link tags entirely. Generate one file with 16, 32 and 48 px entries, reference it explicitly in the head, and you cover tabs, bookmarks and history entries without extra markup. Add the larger sizes if your brand mark is detailed.
Windows reads the icon embedded in an .exe or in a shortcut's properties, and a 48 or 256 px entry looks correct on the desktop and in the taskbar. Designers and developers therefore keep a multi-size ICO in the asset folder even when the product itself ships PNG icons. Keep the 16 px entry clean, because Explorer uses it in small list views.
Design files usually arrive as SVG or a 1024 px PNG, neither of which a favicon link can use. Export or rasterise to PNG, upload it here, and the tool produces the required container. Transparent backgrounds survive, so a mark that sits on both light and dark browser chrome stays readable without a white box around it.
Documentation sites, internal dashboards and staging environments often reuse the same icon. Generating all your .ico files from one master image keeps proportions and colours identical, instead of relying on screenshots resized by hand. Store the master and this page's settings in the project notes so a future redesign can reproduce the same six entries.
No. 16, 32 and 48 px cover tabs, bookmarks and Windows shortcuts, which is enough for most sites. Adding 64, 128 and 256 px helps desktop shortcuts and large icon views and only adds a few kilobytes, but every entry increases the file a browser must fetch.
Usually because the smallest entry is a downscaled photo rather than a simplified mark. At 16 px, thin lines and small text fall below one pixel and blur. Redraw or simplify the glyph, add a little padding, and make sure a real 16 px entry exists instead of letting the browser scale a 256 px image.
The ICO container stores raster images, so vector input has to be rasterised first. Convert the SVG to PNG at 256 px or larger, then upload that PNG here. Inline SVG favicons work in some browsers through a separate link tag, but they are a different mechanism from favicon.ico.
Only if you choose White or a custom colour. Leaving it on Transparent preserves the source alpha, which is what you want for a mark that should sit on any browser chrome. Opaque fills are useful when the logo is dark and would vanish against a dark tab bar.
No. The file is decoded and every icon size is rendered by canvas inside this tab, then packed into the ICO binary in JavaScript. Results depend on the source resolution and your browser, so check the downloaded file in a private window before publishing it.