Loading
Loading tool
Preparing the tool. The remaining time is not yet known.
All processing for this tool happens in your browser. Your input is not sent to a server.
About this tool
Build a multi-size ICO or complete favicon ZIP with browser/touch PNG icons, webmanifest, HTML links and deployment notes.
Common uses
- Build a multi-size ICO file from a PNG image.
- Select a real PNG and enter up to eight distinct icon sizes from 1 to 256 pixels.
- Create browser favicon sizes plus a 180px touch PNG and 192/512px web app icons from one local PNG.
How to use it
- 1.Choose a real PNG and up to eight distinct ICO sizes from 1 to 256 pixels.
- 2.Optionally enable the favicon ZIP package, enter your site name and choose an opaque touch-icon background.
- 3.Generate, inspect dimensions and link/manifest text, then download the ICO or ZIP and adapt deployment paths.
Limits and notes
- PNG input is limited to 20 MiB, 8192 pixels per edge and 32 million pixels. Each square entry contains PNG data; nonsquare artwork is centered with transparent padding rather than stretched.
- ZIP includes your multi-size favicon.ico; PNG 16/32/180/192/512; site.webmanifest, links.html and README.txt. Artwork fits without stretching; transparent padding remains except the opaque 180px touch icon. PNG input: 20 MiB, 8192 edge, 32 million pixels. Output: 2 MiB per PNG / 32 MiB total; each job has a 30-second deadline.
- Manifest icons use purpose "any". They are not maskable icons. For a separate maskable design, keep important artwork inside the centered circle of radius 40% of the icon size and use an opaque background; review platform masks yourself.
- Extract all files together and paste links.html into your page head. Relative links resolve from the page; icon paths resolve from site.webmanifest. Adjust deployment paths, start_url/scope and site settings. Serve .webmanifest as application/manifest+json. This package does not verify installation, caching, browser/platform compatibility or deployment.
- Each PNG entry is natively decoded before export; ICO uses PNG-backed entries, which older BMP-only readers may not support. Small sources may upscale. Animated PNG is rejected. Only static PNG is accepted; at most 4096 chunks, chunk lengths and CRCs are checked before native decode. Animation, metadata and color profiles are not preserved.
Frequently asked questions
What does this tool do?
Build a multi-size ICO file from a PNG image.
What should I check before using the result?
PNG input is limited to 20 MiB, 8192 pixels per edge and 32 million pixels. Each square entry contains PNG data; nonsquare artwork is centered with transparent padding rather than stretched.
Which files does the favicon ZIP contain?
favicon.ico, favicon-16x16.png, favicon-32x32.png, apple-touch-icon.png (180x180), icon-192x192.png, icon-512x512.png, site.webmanifest, links.html and README.txt. The manifest uses relative icon paths with purpose any.
Is this a maskable icon or an installable PWA?
No maskable asset is declared. Important maskable content must fit the centered circle of radius 40% with an opaque background. Installation and platform appearance still depend on the website and browser; this package does not test them.