Zellio.io

Favicon Generator

Turn any image into favicon.ico plus all the PNG sizes you need.

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

What sizes should a favicon include?

A classic favicon.ico bundles 16, 32 and 48px. For modern sites, also add a 180×180 Apple touch icon and 192/512px PNGs for web app manifests — all of which this tool exports.

Do I need a square image?

Yes, ideally. Favicons are square, so a square source (PNG or SVG) gives the cleanest result. Non-square images are scaled to fit each square size without distortion, but you may lose content at the edges if the source has a very different aspect ratio. A square logo or icon (1:1 aspect ratio) ensures your favicon looks good at all exported sizes from tiny 16×16px tabs to large 512×512px app icons. If you only have a rectangular logo, use an image editor to square-crop or pad it before uploading to get the best result.

Is my image uploaded?

No. Everything runs locally in your browser using standard web APIs — your text, files and inputs are never uploaded to a server, so the tool works even offline once the page has loaded.

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.

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

  • Developers finishing a site launch and generating the full icon set from a single logo in one pass.
  • Designers checking whether a new brand mark is still legible at tab size before it is signed off.
  • Anyone building a progressive web app that needs the 192 and 512-pixel icons a manifest requires for an install prompt.
  • Agencies producing consistent icon sets across several client sites without a desktop editor.
  • Owners of an older site adding an Apple touch icon so a bookmarked page stops showing a blurred screenshot.
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.