Favicon Generator
Drop in one image and get the icons a site needs for browser tabs, the iOS home screen, and Android. A favicon.ico comes with it, along with the HTML to paste into your head element.
Your file never leaves your device. Reading, resizing and zipping all happen in your browser. At 16 pixels an image with text in it is unreadable — the simpler the shape, the better it survives.
What you get
Six PNGs (16, 32, 48, 180, 192 and 512 pixels), a favicon.ico, and four link lines for the head. The .ico holds only the 16, 32 and 48 versions — the places that read it are tabs and bookmarks, which never need a large image, and including one only inflates the file. The images inside the .ico are stored as PNG, which every current browser reads. The zip download also includes the HTML snippet as a text file.
How the image is scaled
The image is drawn onto a canvas and the browser encodes the PNG. A non-square image is cropped to a centered square on its shorter side before scaling, so the edges along the longer side are lost. If your logo touches an edge, pad it to a square first. Start from at least 512 pixels; anything smaller means the 512 version is being enlarged and comes out soft.
Why the white background option exists
A transparent background shows whatever it is placed on. iOS fills the transparent parts of a home-screen icon with black, so a dark logo on transparency becomes a dark shape on a black square. Choosing the white background regenerates all six images with white filled in.
Frequently asked questions
My icon is unreadable at 16 pixels
Anything with lettering turns to mush at that size; the simpler the shape, the better it survives. Non-square images are cropped from the center — padding them would leave only a few pixels of recognizable content.
Why so many sizes?
Different places use different ones. Browser tabs take 16 and 32px, the iOS home screen 180px, Android 192 and 512px. Ship only a large one and it blurs when scaled down; ship only a small one and the home screen looks soft.
Is .ico still needed?
Most browsers read PNG, but some places — bookmarks, the address bar — still look for /favicon.ico first. One extra file costs little, so it is generated alongside.
Can I use an image with a transparent background?
Yes. Transparency survives in the PNG outputs, and .ico carries it too. Bear in mind a dark-on-transparent icon disappears against a dark tab, so check it reads on any background.
Can I upload an SVG?
If the browser can open the file as an image, yes. An SVG without explicit dimensions opens differently — or not at all — depending on the browser, so export it to PNG first if it fails.
Does it generate manifest.json?
No. The 192 and 512 images are produced, but for Android to use them on the home screen a web app manifest has to point at them, and that file carries things this page cannot know — name, theme color, start URL. Put the images in place and add the two entries under icons yourself.
Does anything I paste get sent to a server?
No. Everything runs inside your browser and nothing is uploaded or stored. That is why you can use it on things you would not normally paste into a web page, like an internal config file or a production query. It also works with your network disconnected.