Favicon Generator
Turn a logo or picture into a complete favicon package: favicon.ico for old browsers, PNG icons from 16 to 512 pixels, apple-touch-icon, a web app manifest
Drop your image file here
or click to browse files
Turn a logo or any square picture into the complete set of icons a modern website needs: favicon.ico for older browsers, PNG icons from 16 to 512 pixels, an apple-touch-icon for iOS home screens, a web app manifest and the HTML snippet that references all of them.
You get the files and the markup in one step, so you do not have to remember which sizes to export or which link tags to write. The source image is processed locally, which matters if the logo is not public yet.
How to generate a favicon package
Choose a square logo or image
Generate the icon set
Download the files and copy the HTML snippet
FAQ
Which sizes are generated?
16x16 and 32x32 for browser tabs, 96x96 for shortcuts, 180x180 as apple-touch-icon, 192x192 and 512x512 for Android and PWA installs, plus a multi-size favicon.ico for legacy browsers.
What image should I start from?
A square PNG or SVG rendered at 512x512 or larger with transparent background. A wide logo gets letterboxed, and a small or blurry source produces a soft favicon at 512 pixels.
Do I need all these files?
For a modern site, the .ico plus the 192 and 512 PNGs and the manifest cover almost everything. Upload the whole set if you want maximum compatibility - it is only a few kilobytes.
Where do the files go?
Upload them to the root of your website so /favicon.ico and /icon-192.png resolve, then paste the HTML snippet into the <head> of every page, or link the manifest and let it handle the rest.
Will it work for a web app / PWA?
Yes - the manifest and the 192/512 icons are exactly what an installable web app needs. Keep maskable icons in mind if your logo must survive Android adaptive shapes.
Is my image uploaded?
No, all icons are generated in your browser.
At a glance
| Input | image |
|---|---|
| Multiple files | No |
| Where it runs | In your browser - files are never uploaded |
| Works offline | Yes — once the page has loaded |
| Price | Free, no sign-up, no watermark |
Choosing between JPG, PNG, WebP and AVIF
These formats solve different problems, and picking the wrong one costs you either quality or file size. JPG is the safest choice for photographs and for anything you need to send to someone else, because every device and program opens it - but it is lossy and has no transparency. PNG is lossless and supports transparency, which makes it right for logos, screenshots, diagrams and anything with sharp edges or text, at the cost of a much larger file. WebP typically beats JPG by 25-35% at the same visible quality and supports transparency, but a few older programs still cannot open it. AVIF compresses even further, especially at low quality settings, but encoding is slower and support is the newest of the four. A practical rule: JPG to send, PNG to edit, WebP for your own website, AVIF when every kilobyte counts and you have checked that your audience can open it.
Getting a file under a size limit
Upload forms often demand something like "under 2 MB" or "under 500 KB", and the fastest way to get there is to work in the right order: crop away what you do not need, then reduce the pixel dimensions to roughly what the final use requires (1920 px wide is plenty for a full-screen web image, 1000 px for a blog post), and only then lower the quality. Converting to WebP or AVIF can be the single largest saving if the upload form accepts it. Stripping metadata is harmless for size and can matter for privacy, since photos often carry GPS coordinates, the exact camera model and the date. If a form still refuses the file, check whether it imposes a pixel-dimension limit rather than only a size limit - that catches people out more often than actual megabytes.