Tolz.me

PNG to ICO Converter (Favicon Maker)

Turn one PNG, JPG, WebP, or SVG into a multi-size favicon.ico file, plus the PNG sizes a website needs.

Source image

PNG, JPG, WebP, or SVG. The file is read in your browser and never uploaded.

About this tool

A favicon.ico file holds several image sizes in one container, and browsers pick the one that fits the tab, the bookmark bar, or the shortcut. This PNG to ICO converter builds that file from any image you upload, with a crop or pad option for the square and your choice of sizes from 16 to 256 pixels. You also get the individual PNGs, including the 180 pixel apple-touch-icon and the 192 and 512 pixel icons a web app manifest uses, plus the link tags to paste into your HTML. Everything runs on your device, so the image is never uploaded.

Browse more image tools or explore all Tolz.me tools.

Try other relevant tools

Frequently asked questions

What image formats can I turn into a favicon.ico?+

PNG, JPG, WebP, and SVG all work. The image is decoded by your browser and drawn onto a canvas, so any format your browser can display can be converted.

Which favicon sizes should I include in the .ico file?+

16, 32, and 48 pixels cover the browser tab, the favorites list, and the Windows taskbar, and that is the set most sites use. Add 64, 128, and 256 when the same file also has to work as a Windows shortcut or an installer icon.

Why do I need apple-touch-icon.png and manifest icons as well?+

They serve different places. iPhone ignores the favicon and uses the 180 by 180 apple-touch-icon for the home screen shortcut. Chrome and Android read the 192 and 512 pixel PNGs from your web app manifest when someone installs your site. The .ico file still matters for Windows.

Does the .ico file really contain an ICO, or is it a renamed PNG?+

It is a real ICO container. The file has the six byte ICO header, one sixteen byte directory entry per size, and the image data after that. The entries themselves are PNG images, which Windows Vista and later and every current browser read. Very old software may need an uncompressed ICO instead.

My new favicon does not show up. What should I check?+

Start with caching. Browsers keep favicons for a long time and some hold on to the old file until you clear site data, so test in a private window first. Then check that the file is named favicon.ico and sits in the root folder of your site, and that the link tags are inside the head element.

Is my image uploaded to a server?+

No. The file is read with the browser's own file API, drawn on a canvas, and encoded into the .ico inside this tab. Nothing is sent anywhere and nothing is stored after you close the page.

Why does my 16 by 16 icon look blurry while the 256 one looks fine?+

A 16 pixel icon has 256 pixels in total, so fine detail cannot survive the trip down. Simplify the mark, drop thin strokes, and make sure it has a solid silhouette. If the source is a wide wordmark, crop to fill so a recognizable piece of it fills the small square.

Use cases

  • Ship a favicon.ico for a new site or a client project without opening a design app.
  • Create the apple-touch-icon that iPhone puts on the home screen when someone adds your site to their phone.
  • Generate the 192 and 512 pixel icons that Chrome needs before it offers the install prompt.
  • Turn a logo into the Windows icon for a shortcut, an installer, or a packaged desktop app.
  • Prepare every favicon size in one pass, then paste the link tags straight into the head of your HTML.

PNG to ICO Converter (Favicon Maker)

A favicon is the small image a browser shows next to your page title, and favicon.ico is the file format that holds it. This tool turns one PNG into a real multi-size .ico file plus every PNG size a site usually needs, all inside your browser.

What a favicon.ico file actually is

favicon.ico is a container, not a single image. It holds a small directory of image entries, and the browser picks whichever one fits the place it is drawing: a 16 by 16 pixel image for a tab, a 32 by 32 for a bookmark bar, a 64 by 64 for a desktop shortcut. One file can carry all of them, which is why .ico survived while dozens of other favicon formats came and went.

The file starts with a six byte header. Two bytes are reserved and always zero. Two bytes hold the type, where 1 means icon and 2 means cursor. Two bytes hold the number of images that follow. After the header comes one sixteen byte directory entry per image, then the image data itself.

Each directory entry describes one image. The first byte is the width and the second is the height, and the value 0 stands for 256 because a byte cannot hold it. The remaining bytes cover the palette size, a reserved byte, the color plane count, the bits per pixel, and a four byte length and offset that point at the image data.

Older .ico files stored uncompressed Windows bitmaps. Windows Vista added support for PNG data inside an .ico entry, and every current browser reads it. That is what this tool produces: one real .ico file whose entries are PNG images, which keeps the file small and keeps the pixels sharp.

How to build the favicon set

Upload a PNG, JPG, WebP, or SVG. The file is decoded with the browser's own image decoder and drawn onto a canvas, so it never leaves the tab.

Choose between two square treatments. Crop to fill scales the image until it covers the square and trims whatever hangs over the edge. Pad to fit scales the image until it fits entirely inside the square and leaves the rest empty. The preview next to the options updates as you switch.

Pick the sizes that go inside the .ico file. A useful default is 16, 32, and 48. Add 64, 128, and 256 when the same file is also used for Windows shortcuts or a site builder that asks for a large icon.

The extra PNG exports cover the sizes that live outside the .ico file. A 180 by 180 apple-touch-icon is what iPhone puts on the home screen after someone adds your site to their screen. A 192 and a 512 pixel icon belong in your web app manifest, which is what Chrome and Android read when someone installs your site as an app.

Press the build button. Every size is rendered, encoded as PNG, and packed into one .ico file. You can then download the .ico on its own, download each PNG separately, and copy the link tags for your HTML.

Crop to fill or pad to fit

A wide wordmark, say 1200 by 400 pixels, has a hard time at 16 by 16. Cropped to fill, the middle of the word fills the square and the ends disappear, which usually destroys the meaning of the logo. Padded to fit, the whole wordmark survives but shrinks to about 16 pixels wide and turns to mush.

Both problems come from the same cause: the source is not square. The cleanest fix is to start from a square image that already looks right small. A single letter, a mark, or an icon drawn inside a square frame survives downscaling far better than a word.

If you only have the wide version, crop to fill is usually the better choice for a small tab icon, because a viewer recognizes a fragment of the mark faster than a blurred full word. Use pad to fit when the background matters, such as a photo or a badge with a border.

Padding can stay transparent or use a solid color. A light logo on a transparent background disappears on a white page, so switch off transparent padding and pick a background that gives the mark an edge.

Which sizes you actually need

For a normal website, 16, 32, and 48 pixels cover the browser tab, the favorites list, and the Windows taskbar. Those three sizes inside one .ico file is the setup most sites have used for years without problems.

Windows still expects .ico for shortcuts and pinned taskbar items. If your project is a desktop application, an Electron app, a packaged installer, or a file you email to someone, that .ico file is the icon they will see in Explorer.

Safari does not use your favicon for pinned tabs. When someone pins your page in Safari, the tab keeps a screenshot of the page instead, so no favicon size will change that behavior.

Chrome and Android ignore the .ico file when the site has a web app manifest. In that setup the 192 and 512 pixel PNGs listed in the manifest are what gets drawn on the install prompt and on the home screen, so they matter more than the .ico does.

SVG favicons work in Chrome, Firefox, and Edge with a link tag like rel="icon" type="image/svg+xml". Safari has not supported them, so keep the PNG and .ico versions too.

The link tags to paste into your head

Put these lines inside the head element of your HTML, before the closing head tag. The first line points at the .ico file, which browsers also request on their own when a file named favicon.ico sits in the root folder of your site. The tool generates the tags to match the sizes you actually built, so a file you never downloaded never appears in the list.

<link rel="icon" href="/favicon.ico">
<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" sizes="180x180" href="/apple-touch-icon.png">
<link rel="manifest" href="/site.webmanifest">

Worked example: a 512 by 512 logo

Here is a complete run with a square source file. The source is a 512 by 512 PNG named logo.png, a dark teal mark on a white background.

With crop to fill and the default sizes 16, 32, and 48, the build produces a single favicon.ico holding three PNG entries, one per size. PNG compresses flat color well, so a simple mark usually lands at a few kilobytes rather than tens of kilobytes.

Adding 180, 192, and 512 as extra exports adds three more PNG files, named apple-touch-icon.png, icon-192.png, and icon-512.png, which are the names the common manifest examples use. Put the files in the root of your site or in a folder of your choosing, and change the paths in the link tags if you use a folder.

logo.png  512 x 512

favicon.ico          ~3 KB     entries: 16, 32, 48
favicon-16x16.png   ~0.3 KB
favicon-32x32.png   ~0.4 KB
favicon-48x48.png   ~0.6 KB
apple-touch-icon.png  ~7 KB   180 x 180
icon-192.png       ~7 KB
icon-512.png       ~42 KB

Exact byte counts depend on the artwork.

Limits, edge cases, and troubleshooting

A .ico directory entry can only describe sizes up to 256 pixels, because the width and height are stored in single bytes where the value 0 means 256. Larger icons have to be separate PNG files, which is exactly why the 512 pixel export exists.

If the icon does not change after you upload a new version, that is usually caching rather than a broken file. Browsers keep favicons around for a long time, and some keep the old one until you clear site data. Test in a private window before you assume the file is wrong.

If an old tool shows the .ico as blank, it is probably reading only the 256 pixel entry, or it does not understand PNG inside an .ico file. Current browsers and Windows Vista and later handle it, so this mostly affects old software.

If the icon looks blurry at 16 by 16, the source is too detailed. Simplify it, remove thin strokes, and make sure the mark has a solid silhouette. Detail that looks good at 256 pixels will not survive the trip down to 16.

If a site builder rejects the .ico file, check that the file was written as a binary .ico and not renamed from something else. The name must end in .ico and the content must be the ICO container, which is what the download button produces.

Very large source images are fine, but a 12 megapixel photo makes every resize slower on a phone. Cropping your source down to roughly 512 by 512 first gives the same result in a fraction of the time.

Explore more image tools on Tolz.me.

Related tools