Secure server conversion
Favicon Generator
Turn one image into a complete favicon set. You get a multi-size favicon.ico, the
PNG sizes browsers and phones expect, a web manifest, and the exact HTML to paste into your
pages — all in one ZIP. A favicon has not been a single file for a long time, and this generates
every piece rather than leaving you to work out which ones you need.
Drag and drop your PNG image here
Add several at once. Each file is processed and then deleted from our server.
Up to 20 MB per file Batch ready
Conversion queue
→
Your browser could not read this file, so it was converted on our server and deleted there straight away.
Your file had frames or pages. Only the first is in this download.
Step by step
How to use this tool in 4 steps
-
Add your logo
Square works best, ideally 512×512 or larger. PNG, JPG, WebP and SVG all work — an SVG is ideal, since it renders crisply at every size.
-
Wait a moment while the set is generated
-
Download the ZIP and unpack it
-
Upload every file to your site's root
Upload every file to your site's root, then paste the HTML from the included README into your
<head>.
Good to know
About this format
Once upon a time a favicon was one 16×16 file called favicon.ico in your site
root. That still works, and it still looks wrong nearly everywhere, because the contexts an icon
appears in have multiplied.
What you get in the archive, and why each exists:
favicon.ico— the classic file, containing 16, 32, 48 and 256 pixel versions in one. Browsers look for it automatically, Windows uses it for shortcuts, and many link-preview and feed tools expect it.favicon-16x16.pngandfavicon-32x32.png— modern browsers prefer PNG when offered, and 32 is what a high-density tab uses.apple-touch-icon.png(180×180) — iOS home screen. Without it, iPhone users who save your site get a blurry screenshot instead of your logo.android-chrome-192x192.pngand512x512— Android home screens and splash screens.site.webmanifest— tells Android which icons to use and how to display your site when saved. Open it and fill in your site's name, which we leave blank because we do not know it.README.txt— where each file goes and the HTML to paste. Included because the files are useless without it, and because whoever opens this archive in six months will not have this page in front of them.
Older generators produce twenty or more files chasing devices that no longer exist — Windows tile images, a dozen Apple sizes, browserconfig.xml. This set is deliberately small: these cover every context that still matters in practice.
Quality
Quality and file size
The source image matters more than any setting here, and three things about it decide whether the result looks good.
Start large, or start with a vector. An SVG is ideal, because every size is rendered from the shapes rather than scaled from a bitmap. Otherwise use 512×512 or bigger — the Android icon alone needs 512.
Make it square. Icons are square everywhere they appear. A wide logo will be fitted into a square with space around it and will look small and lost. Crop to a square first, or design a square mark.
Simplify. This is the one most people skip, and it matters more than resolution. At 16×16 you have 256 pixels in total — a full company logo with a tagline is unreadable, no matter how good the source. Look at the favicons of sites you use daily: almost every one is a single letter, a simple mark, or a bold shape, and far simpler than the same company's actual logo.
If your logo is detailed, make a separate simplified version for the icon. It is normal and it is what large organisations do.
Transparency is preserved. Usually what you want — an icon with a baked-in white background looks like a white square against a dark browser theme.
Installing the set
Upload everything to your site's root, so the files are reachable at
https://example.com/favicon.ico and so on. Subdirectories will not do: browsers look
for /favicon.ico specifically, and the paths in the manifest assume the root.
Then add this to your <head>:
<link rel="icon" href="/favicon.ico" sizes="any">
<link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png">
<link rel="apple-touch-icon" href="/apple-touch-icon.png">
<link rel="manifest" href="/site.webmanifest">Finally, open site.webmanifest and fill in name and
short_name.
"I uploaded it and nothing changed"
This is by far the most common problem, and it is almost never the files.
Browsers cache favicons very aggressively — often more aggressively than any other asset, and sometimes ignoring a normal refresh entirely. Before concluding something is wrong:
- Try a hard refresh, or an incognito window, or a browser you have never visited the site in.
- Load the file directly —
https://example.com/favicon.ico— to confirm it is actually there and being served. - Give it time. Some browsers only re-check the icon after a while, or after a restart.
If the file loads directly but the tab still shows the old icon, it is caching. If the file 404s, it is in the wrong place.
Do you also want an SVG icon?
Modern browsers accept an SVG favicon, which stays sharp at every size and can respond to dark mode:
<link rel="icon" href="/icon.svg" type="image/svg+xml">It is a good addition, not a replacement. Keep the ICO as the fallback — Windows shortcuts, older browsers and many third-party tools still look for it.
Beyond websites
The favicon.ico in this archive is a normal multi-size Windows icon, so it also
works for application icons, desktop shortcuts and folder icons. Anywhere Windows displays an icon
it will pick whichever size suits the view, which is exactly why the file contains four.
Privacy
What happens to your file
This tool runs on our server, so it works the same on every phone and computer. Your file is uploaded, and this is exactly what happens to it:
- Stored outside the public web root under a random name, never under your file's name.
- Processed, with the original upload deleted immediately — whether it succeeded or failed.
- The result sits behind a signed link that only you receive, which stops working after 20 minutes, and the file is deleted the moment you download it.
- Anything never collected is deleted automatically within 30 minutes.
- The image itself is never logged or kept. If a conversion fails, we record the formats involved and the error — not the file.
- Camera metadata, including any GPS coordinates recording where a photo was taken, is removed from the result. Only the rotation needed to show the image the right way up is kept.
Questions & answers
Favicon Generator: frequently asked questions
What size should my source image be?
512×512 or larger, and square. An SVG is better still, since every size is rendered from the shapes rather than scaled from pixels. The Android icon alone needs 512, so anything smaller will be enlarged.
Which files do I actually need to upload?
All of them, to your site's root — not a subdirectory. Browsers look for /favicon.ico specifically, and the manifest references the Android icons by root-relative path. The included README lists what each file is for.
I uploaded the files but my browser still shows the old icon.
Almost certainly caching, not the files. Browsers cache favicons very aggressively and sometimes ignore a normal refresh. Try an incognito window or a browser you have not visited the site in, and load /favicon.ico directly to confirm it is being served. If it loads but the tab does not update, it is cached; if it 404s, it is in the wrong place.
Why does my logo look like a blur at small sizes?
Because at 16×16 you have 256 pixels in total, and no amount of resolution helps. Make a simplified version for the icon — a single letter, a simple mark, or a bold shape. Look at the favicons of sites you use daily: nearly all are far simpler than the company's real logo.
Do I still need favicon.ico if I have PNG icons?
Yes, keep it. Browsers request /favicon.ico automatically even without a link tag, and Windows shortcuts, older browsers and many feed and link-preview tools look for it specifically. The PNGs are what modern browsers prefer when offered both.
Why so few files? Other generators produce twenty or more.
Because most of those target devices that no longer exist — Windows tile images, a dozen legacy Apple sizes, browserconfig.xml. These six cover every context that still matters, and a smaller set is easier to install correctly.
Keep going
Related image tools
PNG to ICO Converter
Convert PNG to a proper multi-size ICO containing 16, 32, 48 and 256 pixel versions. Transparency preserved.
ICO to PNG Converter
Convert Windows ICO files to PNG, keeping transparency. Extracts the largest image the icon contains.
SVG to PNG Converter
Convert SVG to PNG at any resolution, with transparency preserved. Rendered from the vector so edges stay crisp at every size.
Resize Image
Change an image to any pixel size. Keep the proportions or set both dimensions, with presets for social media. Free, no sign-up.