You can turn an AI-generated logo into a favicon in about five minutes: crop it to a square, simplify it to one bold shape, export small PNG sizes, and add a few <link> tags. The step most people skip is the second one. A logo that looks great at 1024 pixels usually turns into a grey smudge at 16 pixels, because every pixel of the favicon has to stand in for thousands of pixels of the original.
This guide shows the math behind that, a worked example with a 1024×1024 AI logo, the sizes Google Search and browsers actually ask for, and the exact HTML to paste into your site.
Why AI logos break at favicon size
AI image generators love detail: gradients, fine outlines, small lettering, soft shadows and a full scene behind the mark. None of that survives the trip to a browser tab.
Take a square logo that is 1024×1024 pixels. Shrinking it to a 16×16 favicon divides each side by 64, so each favicon pixel averages a 64×64 block, or 4,096 original pixels. Any detail smaller than that block blends into its neighbours.
| Favicon size | Shrink factor from 1024 px | Original pixels per favicon pixel | A 4 px outline becomes | Stroke needed to stay 1 px wide |
|---|---|---|---|---|
| 16×16 | 64× | 4,096 | 0.06 px (gone) | 64 px |
| 32×32 | 32× | 1,024 | 0.13 px (gone) | 32 px |
| 48×48 | 21.3× | 455 | 0.19 px (faint) | 21 px |
| 64×64 | 16× | 256 | 0.25 px (faint) | 16 px |
| 128×128 | 8× | 64 | 0.5 px | 8 px |
| 256×256 | 4× | 16 | 1 px | 4 px |
The practical rule from that table: if a line, letter or gap in your 1024 px logo is thinner than about 64 px, it will not be readable at 16×16, and anything thinner than about 32 px is gone at 32×32. That is why the favicons you recognise instantly are a single letter, a single shape or a single bold symbol.
Worked example: from AI logo to favicon
Say you generated a logo for a bakery called "Maple & Crumb": a 1024×1024 image with a brown circular badge, a small maple leaf, the full name in a script font and a cream background with a soft shadow.
- Pick the one element that can carry the brand. The script name is out: the letters are maybe 15-25 px thick, which rounds to nothing at 16 px. The leaf is the best candidate.
- Crop to a square around that element. Use the Image Crop Tool to cut a square around the leaf with a small margin (roughly 10% of the width on each side). Google Search requires a square, 1:1 favicon, so do not leave it rectangular.
- Remove the busy background. If the leaf sits on a textured or shadowed background, run it through the Image Background Remover and place it on one flat colour, or keep it transparent.
- Thicken and simplify. Ask the AI tool for a "flat, single-colour icon version, thick shapes, no text, no gradients", or simplify it yourself. Aim for main shapes at least 64 px thick at 1024 px, based on the table above.
- Check contrast. Browser tabs can be light or dark. A brown leaf on a transparent background can disappear on a dark tab bar, so a solid cream rounded square behind the leaf is often safer.
- Export the sizes. Load the square image into the Favicon Generator, keep 16, 32 and 48 ticked, add 64, 128 and 256 if you want larger files, and click Generate & Download. You get one PNG per size, named like
favicon-32x32.png. - Look at the 16 px file at 100% zoom. If you cannot tell what it is, go back to step 4. This check takes five seconds and catches most bad favicons.
If your logo came out as an SVG (some AI and design tools offer vector export), convert it to a large PNG first with the SVG to PNG Converter, then follow the same steps. If the source is not square or is huge, the Image Resizer can bring it to a clean 1024×1024 or 512×512 before you start.
Which sizes do you actually need?
There are many favicon size lists online, most of them copied from older guides. Here is what the primary sources say today:
- Google Search: Google's favicon documentation says the favicon must be square (1:1) and at least 8×8 px, and recommends using one larger than 48×48 px so it looks good on different surfaces. Supported formats include PNG, ICO, GIF, JPEG, BMP, PPM and TIFF.
- Browser tabs: 16×16 and 32×32 PNGs cover standard and high-density tab icons; 48×48 is a useful middle size.
- Installable web apps (PWA): web.dev's manifest guide says Chromium needs at least a 192×192 and a 512×512 icon in the web app manifest. These are only needed if your site has a manifest and can be installed.
- iOS home screen: Google lists
apple-touch-iconas a supported link type. Use a larger square PNG for it rather than the 16 or 32 px file.
Honest note on our tool: the Toolspedia Favicon Generator outputs PNG files at 16, 32, 48, 64, 128 and 256 px. It does not create a multi-size .ico file or the 192/512 px manifest icons. For most sites the PNGs are enough, because modern browsers and Google accept PNG favicons. If you need manifest icons, export your square master at 192 and 512 px with the Image Resizer.
The HTML to paste into your site
Upload the files to your site root (or any stable folder) and add these lines inside <head>:
<link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png">
<link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="48x48" href="/favicon-48x48.png">
<link rel="apple-touch-icon" href="/favicon-256x256.png">
Google's guidelines add a few rules that matter for search results:
- Put the link on your home page. Google supports one favicon per hostname.
- Do not block the home page or the favicon file in
robots.txt; Googlebot-Image must be able to fetch the icon. - Keep the favicon URL stable. Changing the file name often can delay updates.
- The icon should visually represent your brand.
- Updates are not instant. Google says recrawling can take several days to several weeks, and you can request indexing of your home page in Search Console's URL Inspection tool to speed it up. Even then, a favicon is not guaranteed to appear.
If you are setting up other head tags at the same time, the Meta Tag Generator builds title, description and social preview tags you can paste next to the favicon links.
Common mistakes with AI-made favicons
| Mistake | What you see | Fix |
|---|---|---|
| Shrinking the whole logo with text | A blurry rectangle in the tab | Use one letter or symbol only |
| Non-square crop | Squashed icon or Google ignores it | Crop to exactly 1:1 before exporting |
| Gradients and soft shadows | Muddy brown or grey pixels | Flat colours, 2-3 at most |
| Thin outlines | Shape disappears at 16 px | Strokes at least 64 px thick on a 1024 px master |
| Transparent dark icon | Invisible on dark tab bars | Add a solid light or coloured background |
| Renaming the file on every update | Old icon stays in Google for weeks | Keep one stable URL |
A quick check before you publish
- Is the icon square?
- Can you recognise the 16 px version at 100% zoom?
- Does it read on both a white and a dark background?
- Are the
<link>tags on the home page, pointing at files that load? - Is the favicon allowed in
robots.txt?
AI tools are great for getting a logo idea in minutes. Turning it into a favicon is a design step, not a resize step: one bold shape, a square crop, flat colours, then export. For related reading, see the best image size to upload to ChatGPT, Claude and Gemini and how big you can print an AI-generated image.