Zellio.io

PNG to ICO Converter

Turn an image into favicon.ico and every PNG size.

Runs locallyWorks offlineShare link carries settings, never your data
Send output toImage ResizerImage CompressorWebmaster File GeneratorBuild a workflow from thisOutput stays on this page until you send it.

Frequently asked questions

Which sizes does a favicon actually need?

16x16 and 32x32 cover browser tabs and bookmarks, 48x48 helps on Windows, and 180x180 is the Apple touch icon for home screens. A single .ico can hold several sizes so the browser picks what fits.

Why not just use one large PNG?

Because browsers downscale it on the fly, and a detailed logo shrunk to 16 pixels usually turns to mush. Providing a purpose-made small version — often a simplified mark rather than the full logo — looks far sharper.

Where do the files go?

favicon.ico belongs at your site root, where browsers look for it automatically. The PNG sizes are referenced from link tags in your head, or from a web manifest for installable apps.

Pro tips

  • Design for 16 pixels first and scale up. A mark that survives at tab size almost always works larger; the reverse is rarely true.
  • Test against both a light and a dark tab bar — a dark logo with a transparent background disappears entirely for half your visitors.
  • Simplify rather than shrink: drop gradients, fine strokes and any text longer than a couple of characters before generating.
  • Use a square source image. A rectangular one will be padded or cropped, and neither choice is likely to be the one you wanted.
  • If an updated icon does not appear, load the icon file's URL directly to confirm the new bytes are being served before debugging anything else.

About Favicon Generator

Almost nothing survives at 16 pixels — fine detail, gradients and text below a few characters all turn to mush. Icons that read at that size are usually one bold shape, so it pays to simplify the artwork before generating rather than after.

Convert a PNG into a multi-size favicon.ico (16, 32 and 48px) plus the Apple touch and web-manifest PNG sizes browsers expect. It is rendered locally in your browser, never uploaded.

A favicon is the small icon shown in browser tabs, bookmarks and history. This generator turns any square image into a multi-resolution favicon.ico containing the 16, 32 and 48-pixel sizes browsers use, plus individual PNGs from 16 up to 512 pixels — including the 180×180 Apple touch icon and the 192/512 sizes referenced by web app manifests.

Upload a logo or icon, preview it at real favicon sizes, and download exactly the files you need. Previewing at 16 pixels before committing is the entire point — most logos that look fine in a header dissolve at tab size.

The modern set is smaller than most guides imply. An SVG icon covers current browsers at any size and can adapt to dark mode; a 32-pixel ICO covers older ones and the bookmark bar; a 180-pixel PNG covers the iOS home screen; and 192 and 512-pixel PNGs cover Android and the install prompt. Everything beyond that is legacy weight for platforms almost nobody is running.

Favicons are cached unusually aggressively, which is why a replacement so often appears not to have worked. Browsers keep the old icon well past a normal refresh, and the reliable way to check a change has shipped is to request the icon URL directly rather than reloading the page and trusting the tab.

Where the files live matters as much as generating them. Browsers request /favicon.ico from the site root by default even when nothing references it, so placing the ICO there covers the fallback path; everything else is declared with link tags in the document head, and the manifest icons are referenced from the manifest rather than the HTML. Getting the paths right is the step most often missed when an icon works locally and not in production.

Common use cases

  • Creating a full favicon set from a single logo file
  • Producing an Apple touch icon for home-screen bookmarks
  • Generating manifest icons for an installable web app
How it comparesRealFaviconGenerator produces a more exhaustive set with platform-specific tuning and requires uploading your artwork. This covers the sizes that actually get requested in 2026 and keeps the source image on your machine, which is the trade most projects should take.