Turn an image, an emoji, or a couple of letters into a complete favicon set — favicon.ico, every PNG size, an Apple touch icon, a web manifest, and the HTML tags — packaged in one ZIP. All generated in your browser.
PNG, JPG, SVG or WebP — square works best
A favicon is the tiny icon that shows up in the browser tab, the bookmark bar, search results, and on a phone's home screen when someone saves your site. Getting it right used to mean exporting a dozen sizes by hand and hunting down the correct HTML tags. This tool does all of it at once: give it an image, an emoji, or a few letters, and it produces a complete, modern favicon package ready to drop into your site.
It runs entirely in your browser. Your logo or artwork is rendered on a local canvas and packaged on your device — nothing is uploaded, so unreleased branding stays private.
favicon.ico — a real multi-resolution ICO (16, 32 and 48 px) for maximum browser compatibility.favicon-16x16.png, favicon-32x32.png, favicon-48x48.png — modern PNG icons.apple-touch-icon.png (180 px) for iOS home screens.android-chrome-192x192.png and android-chrome-512x512.png for Android and PWAs.site.webmanifest wired to the Android icons.favicon-tags.html — the exact <link> tags to paste into your page <head>.No account, no upload, no watermark — design it, download the ZIP, paste the tags.
Start from your logo image, an emoji, or styled text, and download the complete kit: favicon.ico, all the PNG sizes, apple-touch-icon, and a web manifest, plus the exact HTML tags to paste into your head.
Modern sites want a multi-size favicon.ico (16 and 32 px), a 180 px apple-touch-icon, and 192/512 px PNGs referenced by a web manifest for Android and PWA use. The generator produces all of them so you never have to remember this list again.
Yes, and it is a great look for side projects: pick any emoji and the generator renders it into every required size and format.
Upload the files to your site (the root is simplest) and paste the provided link tags into your HTML head. The tags in the ZIP match the file names exactly.
Browsers cache favicons aggressively. After deploying, hard-refresh, try a private window, or bump the file name. The generated set is correct; the cache just needs convincing.