Images

Favicon Generator

Turn a local image into a useful icon pack, with real PNG and ICO files and the markup to use them.

Result

One image. A useful icon set.

Generate six PNG sizes, a real ICO file and manifest, all together in a local ZIP.

Choose an image or load the local sample.

Generated head markup
HTML

Generated icon manifest
JSON

Generate a real favicon pack

  1. Choose a still PNG, JPEG or WebP. A simple square mark usually stays clearer at 16 and 32 pixels.
  2. Set the site name, local asset folder, fit, padding and background. Contain preserves the whole image; cover crops the center to fill the square.
  3. Generate the pack, review it, then download the ZIP. Place its files together and add the supplied link elements to your document head.

What is inside the archive?

The ZIP contains PNG images at 16, 32, 48, 180, 192 and 512 pixels. The 180-pixel file is named apple-touch-icon.png. The favicon.ico file contains three PNG-compressed ICO entries at 16, 32 and 48 pixels, with actual icon headers and offsets. It is not a PNG renamed to .ico. An icon manifest, head snippet and README complete the ten-file pack.

Manifest and platform limits

The manifest describes the 192- and 512-pixel images with purpose “any”. This is not a maskable-icon generator and it does not make a website installable. There is no service worker, splash-screen set or platform certification. Opaque backgrounds can work better for Apple touch icons. PNG-compressed ICO entries target modern readers; very old software may require bitmap-based ICO files instead.

Safe local generation

No image is uploaded. Inputs share the 20 MiB, 8,192-pixel edge and 16,777,216-pixel limits of the image converter. Animated images and unsupported types are rejected before decoding where the header identifies them. The source is decoded in a cancellable worker; each PNG and ICO dimension is checked. Packs are capped at 5 MiB of file data and 6 MiB of ZIP output, with a 20-second job limit. Changing any option removes the stale download until you regenerate.

Use the files on your website

Keep the icon files beside site.webmanifest, whose icon URLs are relative to that manifest. The head snippet uses your chosen local folder path. Serve the manifest with an appropriate JSON or application/manifest+json content type. Browser favicon caches can retain an earlier icon, so verify the actual files and reload carefully when testing. A download request is not proof that the browser saved a file.

Read the official link element reference , manifest icon reference and Microsoft’s explanation of PNG entries in ICO files .

Related Tools