Favicon Generator

Upload one SVG, PNG, JPG/JPEG, or WEBP. We emit common PNG sizes (16 through 128, plus Android 192 and 512), a multi-size ICO, and Apple touch icon — then preview each file and download individually or as a ZIP.

Adjust image

Max upload 50.00 MB. Raster PNGs use transparent letterboxing for non-square sources; Apple touch icon is flattened on white. JPEG has no alpha.

Favicon generator for browser tabs, bookmarks, and installs

A favicon is the small image browsers show on tabs, in history, and next to saved bookmarks. PWA and mobile install flows often ask for larger square PNGs in addition to the classic tiny icon. This tool turns one master image into those outputs in a single ZIP download.

Good favicons favor a simple mark, enough padding, and formats that match where the icon appears. For how raster and vector formats behave on the web more broadly, see our best image format for websites guide and optimizing images for the web.

Favicon sizes and roles at a glance

16×16 through 128×128
Tab UI, shortcuts, and Windows tile-style surfaces; intermediate sizes help when the OS picks the closest match
180×180
Apple touch-icon when someone adds your site to the iOS home screen
192×192 and 512×512
Common manifest icons for installable web apps and some launcher surfaces
ICO container
One file can hold multiple embedded PNGs for older favicon discovery patterns

What this generator creates

  • Single upload: start from one source file (SVG, PNG, JPG/JPEG, or WEBP).
  • Raster set: PNGs at 16, 32, 48, 64, 96, and 128 pixels, plus Android 192 and 512, Apple touch 180, and a 16+32 ICO.
  • Safe padding: non-square images are centered with transparent padding on PNG favicons; Apple touch is flattened on white.
  • Tiny sizes: 16×16 is only 256 pixels total — detail loss and softness when scaled up in previews are expected; start from a high-resolution or vector source for the best tab icon.

Tradeoffs: ICO, PNG, and SVG favicons

PNG is predictable, easy to optimize, and supports transparency and alpha for marks that should float on browser UI. ICO remains relevant when you want one HTTP request to cover multiple embedded sizes for legacy clients. SVG favicons scale cleanly but are not universally supported, so pairing SVG with raster fallbacks is still the conservative production pattern.

Tiny icons are not the place for full wordmarks or thin hairlines. If your source is a large banner asset, resize the image to a square master first, simplify shapes, and only then export favicon sizes. After export, you can compress PNG or WebP outputs to keep manifest packages small without reintroducing heavy artifacts—see also how image compression works.

Sharpness, bitmap density, and legibility

Favicons are extreme downsampling: what reads on a business card may vanish at 16×16. Work from a high-resolution square, test in light and dark browser themes, and compare against competitor tabs at actual size. Our image resolution and DPI article explains why metadata like DPI does not fix a sparse pixel grid—pixel dimensions and design simplicity matter more for raster marks.

When not to push a favicon generator alone

  • Regulated brands: marketing and legal may require exact colors; validate hex values outside any automated pass.
  • Complex emblems: coats of arms, dense logotypes, and tiny type rarely survive automatic shrink without a human redraw.
  • Theme-specific marks: if you need different artwork for dark mode, OS tinting, or monochrome notification slots, plan separate assets rather than one generic export.

Favicon Generator Questions, Answered

What image sizes do I need for a modern favicon set?

A practical baseline is a 32×32 PNG for the classic link rel icon, a 180×180 PNG for Apple touch-icon, and optional 192×192 and 512×512 PNGs if you ship a web app manifest. Many sites still ship a multi-resolution ICO for older browsers; the exact checklist depends on your framework and whether you also publish maskable icons for Android.

Should I use ICO, PNG, or SVG for my favicon?

PNG is widely supported for favicons and is easy to preview and optimize. ICO can bundle multiple embedded sizes in one file for legacy tab icons. SVG favicons stay sharp at any size but are not supported everywhere, so most production setups pair SVG or PNG with at least one raster fallback.

Will my favicon look sharp on high-DPI screens?

Raster favicons are bitmaps: a 16×16 source has only 256 pixels, so fine lines can look soft when the OS scales it. Start from a vector master or a larger square master (for example 512×512), simplify the mark, test at 16×16 and 32×32, and export purpose-built sizes rather than relying on automatic downscale alone.

Does transparency work in favicons?

PNG and ICO can carry transparency so the mark can sit on the browser chrome without a solid box. Some contexts flatten icons onto a background anyway. JPEG favicons do not support transparency, so avoid JPEG when you need a cutout mark.

When should I avoid using only an online favicon generator?

Skip generator-only workflows when you need brand-controlled color management, pixel-perfect multi-theme marks (light and dark mode), or hand-tuned 16×16 legibility for complex logos. In those cases, keep a design-source file and export a curated set with manual review in real browsers and devices.