Favicon Generator

Upload an image or logo to generate PNG favicon sizes, favicon.ico, and Apple Touch Icon candidates.

◴ No data stored ⌁ Free

Concept

A favicon is the icon identity for browser tabs, bookmarks, and PWA home screens

Generate a favicon set from one source image for tab icons, bookmark icons, and installable PWA icon scenarios.

Tab icons are usually read at 16~48px, while bookmarks and PWA manifests commonly need 180px/192px/512px PNG variants.

Use transparent PNGs with dark-mode contrast checks, then preview the rendered icon in real tabs and bookmark states to confirm readability.

When to use

Use favicon and manifest outputs together when preparing deploy assets: browser tab icon, favicon.ico, and Apple Touch Icon.

Output set

Generate PNG in 16/32/48/180/192/512px, favicon.ico, and optionally SVG depending on your deployment needs.

Release check

Before shipping, confirm transparent background variants, dark-mode contrast, base path in href, and actual display in tab, bookmark, and mobile install views.

A complete favicon setup is not only icon files; it includes HTML link code and manifest wiring so the real browser UI shows the expected icon.

Favicon Generator Favicon generation workspace

Source image
Favicon result
Generated favicon previews will appear here.

How to use

  1. 1 Select or drop an image close to a square shape.
  2. 2 Click generate to create multiple PNG favicon sizes and favicon.ico.
  3. 3 Download files individually or as a ZIP, then check the relative paths or base path in the HTML link code for your deployment.

Common use cases

  • Generate favicon PNG/ICO files
  • Make a favicon from a logo image
  • Create an Apple Touch Icon candidate
  • Prepare favicon HTML link code

Frequently asked questions

Does this generate ICO files too?

Yes. V2 generates PNG favicon sizes, favicon.ico, and HTML link code, with a ZIP download for the full set. The HTML example uses relative paths by default, so add a base path before each href when deploying under a subpath. Browser generation is the default, while server optimized generation uses Cloud Run resizing.

Related workflow