Favicon generator
Drop your logo: out comes a zip with the icons today’s browsers actually use, the manifest and the five tags to paste. The image never leaves your device.
Your file stays on your device: nothing is uploaded
How it works
Every size is derived from the original image, not from the one produced before: resizing in a chain adds up the errors, and at sixteen pixels that is the whole difference between a crisp icon and a mushy one. The .ico file holds three of them and browsers pick what they need; the 192 and 512 pixel ones are for people who add the site to their phone’s home screen. If your logo is not square you can keep it whole or fill the square by cropping.
Frequently asked questions
- How big should the starting logo be?
- At least 512 pixels: on the long side if you keep it whole, on the short side if you fill the square by cropping. Below that, the larger icons are scaled up without gaining any detail, and the result tells you so. A PNG, JPG, WebP or AVIF up to 30 MB will do, one logo at a time.
- Which folder of my site do the files go in?
- The main one, where the home page lives: the tags in favicon.html and the manifest look for the icons there — /favicon.ico, for example. If you put them somewhere else, fix the paths in those two files. Then paste the five lines of favicon.html into the head of every page.
- What site name ends up in the manifest?
- The name of the file you dropped in, without its extension: “my-site.png” becomes “my-site”, and the short name takes its first twelve characters. To change them, open site.webmanifest in a text editor and rewrite “name” and “short_name”.
- Does the background colour I pick show up anywhere else?
- Yes: if you turn on “Fill the transparency with a colour” under “Advanced options”, that colour also goes into the manifest, as the background a phone shows while opening the installed site. Left off, no colour is declared at all, and the background around the logo stays transparent.
Your files are never uploaded. Anywhere.
Your file stays in your browser’s memory: it is read, processed and written back here. There is no server to send it to.
- Processed locallyEverything happens on your device.
- Nothing to upload, nothing to wait forNothing to upload, no waiting.
- No files to deleteWe keep nothing: nothing reaches us.