Prepare a simple mark that works small
The Favicon Generator turns one JPEG, PNG, or WebP image into a downloadable icon package. A simple shape with clear empty space generally survives small sizes better than a detailed photograph or a long wordmark. Inspect the 16-pixel version rather than judging only the largest icon.
The generator fits the image into a square without cropping and leaves unused space transparent. A transparent PNG source is useful when your mark needs an irregular outline. The PNG specification describes its optional alpha channel; transparency is part of the pixel data rather than a white background painted behind it.
Check a square-source example
Upload an opaque 512 × 512 PNG containing a centered symbol and select Generate result. The expected download is erithra-favicons.zip. Inside it are PNG files at 16, 32, 48, 180, 192, and 512 pixels square, plus favicon.ico, site.webmanifest, and installation.txt.
The ICO contains PNG image entries for the 16-, 32-, and 48-pixel sizes. It is a multi-size PNG-based ICO rather than a single PNG merely renamed with an .ico suffix. The 180-, 192-, and 512-pixel assets remain separate PNG files.
If the source were 800 × 400, fitting it into a 32-pixel square would produce a 32 × 16 image area with transparent space above and below. Use Image Cropper first if your desired mark instead needs a deliberate square crop.
Install and personalize the package
Copy the icon files into your site’s public assets and follow installation.txt to add the icon, Apple touch icon, and manifest links to the document head. The HTML Standard describes the icon link relationship.
Edit name and short_name in site.webmanifest; the generated placeholders say “Your site.” The included icon paths start at the site root, so adjust them if your deployment serves assets under a different base path. The package does not modify your website or install itself.
Verify the deployed assets
Open each deployed asset path directly, inspect small icons against light and dark surroundings, and check the browser tab after refreshing. Browser caching can obscure an icon change, so confirm the served file as well as the visible tab.
Input is limited to 20 MB and 40 megapixels. Processing stays in the browser. The exported assets are static images; an animated source does not become an animated favicon package through this workflow.