How to use this tool
- Choose a PNG, JPG or WebP image, or try the sample image.
- Choose transparent padding to fit the whole image, or center cropping to fill the square.
- Generate and download the favicon package. Extract the ZIP, publish the files and add the supplied HTML tags to your site.
Quick reference
| Setting | Value / behavior |
|---|---|
| Input | JPEG, PNG or WebP · up to 25 MB |
| PNG sizes | 16, 32, 48, 180, 192 and 512 pixels |
| ICO | 16 / 32 / 48 px embedded PNGs · modern readers |
| Package | ZIP + individual files + manifest + HTML instructions |
Choose an image that reads at small sizes
Start with a square logo or a simple symbol with a clear silhouette. A browser tab can show an icon at only sixteen pixels, so detailed illustrations and long words often become unreadable. Choose a PNG with transparency when you want an irregular outline. JPEG and WebP inputs are also accepted. The tool decodes the selected image in this browser and builds each output size separately from that source. It does not trace a bitmap into a vector drawing, invent missing detail or restore sharpness lost in a small source image. Keep your original design file for future edits.
Fit or crop the square
Fit entire image preserves the complete source and centers it on a transparent square. A wide source will have empty space above and below; a tall source will have space at the sides. Fill square scales the source to cover the square, then crops equally around the center. This can remove the edges of a logo, so inspect the generated preview and the smallest downloaded icons before using the package. Transparent source pixels stay transparent in the PNG outputs. The original file on your device is never overwritten.
What the package contains
The ZIP contains PNG icons at sixteen, thirty-two, forty-eight, one hundred eighty, one hundred ninety-two and five hundred twelve pixels. It also contains favicon.ico with embedded sixteen, thirty-two and forty-eight pixel PNG images. PNG-compressed ICO images target modern icon readers; some older desktop software expects a bitmap-based ICO instead. The apple-touch-icon.png file is the one hundred eighty pixel image, while the android-chrome files match the two largest sizes. A site.webmanifest and an install.html.txt instruction file complete the package. Individual downloads are available alongside the ZIP. Generating these files does not turn an ordinary website into a complete installable application.
Install and verify
Upload the generated files to the root of your website and add the supplied link elements inside the HTML head. The snippet uses absolute root paths, so edit them if you store icons in another folder or publish below a path prefix. Update the manifest site names and colors to match your project before publishing. Browser caches can retain an older favicon; check a fresh session and the actual network response when an update appears missing. Files are limited to twenty-five megabytes, forty megapixels and twelve thousand pixels per side. Animated inputs use the first decoded frame. There is no account, remote image-processing service or automatic publication step.
Frequently asked questions
Can I make a favicon from a rectangular logo?
Yes. Fit preserves the complete image with transparent padding; Fill square crops from the center.
Is the ICO compatible with every old application?
No. This ICO embeds PNG images for modern readers. Older software that requires uncompressed bitmap icons may need a different ICO encoder.
Are my images uploaded?
No. Image decoding, icon creation and ZIP packaging run locally in this browser.
Does the manifest make my website a PWA?
No. A manifest is only one part of an installable application. Review your application requirements separately.
About this tool
Built and maintained by Mihai at Void Fabric. This page documents the behavior of the current implementation. Found an error or an unclear assumption? Send a reproducible example with sensitive values removed.
Reference: Void Fabric field notes · Testing and editorial policy