How to generate a complete favicon package
- Choose image mode for an existing logo, or text mode for initials and emoji.
- Adjust the background, padding, image fit and corner radius while checking previews at small and large sizes.
- Enter the site name and theme color used by the generated web manifest.
- Download an individual PNG or ICO, or download the complete ZIP.
- Upload the assets to your site root and paste the generated markup inside the page head.
Which favicon files do websites need?
A 16×16 and 32×32 browser favicon cover common tabs and bookmarks. A multi-size favicon.ico helps older browsers and integrations. Apple devices use a 180×180 touch icon, while installable web apps commonly reference 192×192 and 512×512 PNG icons through a web manifest.
Design tips for small icons
- Use a simple silhouette with strong contrast and avoid thin details that disappear at 16 pixels.
- Leave some breathing room around the mark, but preview padding carefully because excessive whitespace makes the icon look small.
- Test against both light and dark browser chrome.
- Use square source artwork of at least 512×512 pixels when possible.
Frequently Asked Questions
Is the generated favicon.ico a real ICO file?
Yes. It contains PNG-compressed 16×16, 32×32 and 48×48 frames inside a standards-compatible ICO container.
Are uploaded logos sent to ZeeSharp?
No. Resizing, rendering and packaging run locally in your browser. Only generic tool-usage information may be recorded for subscription limits.
Why does a favicon look blurry?
Small icons have very few pixels. Start with a clean high-resolution square source, simplify fine detail, add suitable padding and inspect the 16×16 preview.
Can SVG be used as the source?
Compatible browsers can decode many SVG files for local rendering. Avoid SVG files that reference external images or fonts; a self-contained PNG is the most predictable source.