Favicon Generator

Continue in the tool

More pages for this tool

PNG to ICO converter

PNG to ICO converter with the sizes you choose

The page opens straight in ICO mode: there is nothing to set up first. Drop the PNG, check the preview of each size and download the file. PNG transparency is kept at every resolution, and the image never leaves your browser.

What happens to the PNG when it becomes an ICO

An ICO is not a PNG with another extension. It is a container with a directory of images: a 6-byte header, 16 bytes per size and then the data of each image. The conversion redraws your PNG at each ticked size and stores each result as a PNG inside the container, keeping the alpha channel. The default sizes are 16, 32, 48, 64, 128 and 256 px; with them the header plus directory take 102 bytes, and the sum of the raw pixels would be 358,400 bytes, which PNG compression cuts down a lot. For a site favicon, the Favicon set (16, 32 and 48) keeps the directory at 54 bytes.
Two details decide the quality. The first is the source size: the format holds 256 px at most per image, and a PNG smaller than that is scaled up, which blurs it. A 128 x 128 PNG with the default sizes has its 256 entry enlarged, and the tool warns you. The second is the proportion: an ICO is square. On a 400 x 200 px logo, Cover mode crops a 200 x 200 square from the center (starting at x = 100), and Contain mode fits the whole image at 256 x 128 inside the 256 square, with 64 px of margin above and below.
The downloaded file takes your PNG name with the extension swapped, from logo.png to logo.ico. For the site favicon, put it at the root as favicon.ico, which browsers request on their own, or point to it with a link tag. On Windows the same file works as a folder, shortcut or app icon. An ICO with PNGs inside works from Windows Vista onward and in every current browser; only Windows XP and some old resource compilers require BMP.

Four conversions and what comes out of each

512 px PNG with the default sizes

Input: logo.png, 512 x 512, 6 tamanhos
Expected output: logo.ico, 102 bytes de cabeçalho e diretório

6 + 6 x 16 = 102 bytes before the PNGs, and no size is scaled up.

Favicon set only

Input: logo.png, tamanhos 16, 32, 48
Expected output: logo.ico, 54 bytes de cabeçalho e diretório

6 + 3 x 16 = 54 bytes; it covers the browser tab and bookmarks.

PNG that is too small

Input: icone.png, 128 x 128, 6 tamanhos
Expected output: Aviso: o tamanho 256 será ampliado

Sizes 16 to 128 come out sharp; only the 256 one starts from a smaller source.

400 x 200 rectangular logo

Input: Preencher versus Conter, tamanho 256
Expected output: Preencher: recorte 200 x 200 do centro. Conter: 256 x 128 com 64 px de margem

Contain keeps the whole logo; Cover fills the entire square and cuts the sides.

Full tool FAQ

Which favicon sizes do I actually need?

The essentials: favicon.ico (16, 32, 48) for browsers, favicon-32x32.png and 16x16.png, apple-touch-icon.png (180) for iOS, and android-chrome 192/512 for PWAs. This tool generates all of them.

Do I need a square image?

Why does the .ico hold several sizes and which ones should I tick?

What is the generated site.webmanifest?

Where do I put the files and the snippet?

Can I use an SVG as the source image?

How do I convert PNG, JPG or SVG to ICO?

Does generation send my image to a server?

Frequently asked questions

Does a transparent PNG stay transparent in the ICO?

Yes. Each size is stored as a PNG with an alpha channel, and the Transparent option comes on. If you want a solid background, turn it off and pick the color.

Which sizes should I tick?

For a website, 16, 32 and 48. For Windows, 16, 24, 32, 48 and 256. When in doubt, keep the defaults: the file gets a bit larger, but the system always finds a size close to what it needs.

Is there a size limit on the input file?

The tool accepts files up to 50 MB. Since the image is processed in your browser, what limits it in practice is the device memory, and a very large image may be refused with a notice.

Is my image sent to any server?

No. Reading, resizing and building the .ico all happen in the browser, so it works with private images and offline once the page has loaded.

Next steps

What happens to the PNG when it becomes an ICO

An ICO is not a PNG with another extension. It is a container with a directory of images: a 6-byte header, 16 bytes per size and then the data of each image. The conversion redraws your PNG at each ticked size and stores each result as a PNG inside the container, keeping the alpha channel. The default sizes are 16, 32, 48, 64, 128 and 256 px; with them the header plus directory take 102 bytes, and the sum of the raw pixels would be 358,400 bytes, which PNG compression cuts down a lot. For a site favicon, the Favicon set (16, 32 and 48) keeps the directory at 54 bytes.

Two details decide the quality. The first is the source size: the format holds 256 px at most per image, and a PNG smaller than that is scaled up, which blurs it. A 128 x 128 PNG with the default sizes has its 256 entry enlarged, and the tool warns you. The second is the proportion: an ICO is square. On a 400 x 200 px logo, Cover mode crops a 200 x 200 square from the center (starting at x = 100), and Contain mode fits the whole image at 256 x 128 inside the 256 square, with 64 px of margin above and below.

The downloaded file takes your PNG name with the extension swapped, from logo.png to logo.ico. For the site favicon, put it at the root as favicon.ico, which browsers request on their own, or point to it with a link tag. On Windows the same file works as a folder, shortcut or app icon. An ICO with PNGs inside works from Windows Vista onward and in every current browser; only Windows XP and some old resource compilers require BMP.

Four conversions and what comes out of each

512 px PNG with the default sizes

Input: logo.png, 512 x 512, 6 tamanhos
Expected output: logo.ico, 102 bytes de cabeçalho e diretório

6 + 6 x 16 = 102 bytes before the PNGs, and no size is scaled up.

Favicon set only

Input: logo.png, tamanhos 16, 32, 48
Expected output: logo.ico, 54 bytes de cabeçalho e diretório

6 + 3 x 16 = 54 bytes; it covers the browser tab and bookmarks.

PNG that is too small

Input: icone.png, 128 x 128, 6 tamanhos
Expected output: Aviso: o tamanho 256 será ampliado

Sizes 16 to 128 come out sharp; only the 256 one starts from a smaller source.

400 x 200 rectangular logo

Input: Preencher versus Conter, tamanho 256
Expected output: Preencher: recorte 200 x 200 do centro. Conter: 256 x 128 com 64 px de margem

Contain keeps the whole logo; Cover fills the entire square and cuts the sides.

Full tool FAQ

Which favicon sizes do I actually need?

The essentials: favicon.ico (16, 32, 48) for browsers, favicon-32x32.png and 16x16.png, apple-touch-icon.png (180) for iOS, and android-chrome 192/512 for PWAs. This tool generates all of them.

Do I need a square image?

Why does the .ico hold several sizes and which ones should I tick?

What is the generated site.webmanifest?

Where do I put the files and the snippet?

Can I use an SVG as the source image?

How do I convert PNG, JPG or SVG to ICO?

Does generation send my image to a server?

Frequently asked questions

Does a transparent PNG stay transparent in the ICO?

Yes. Each size is stored as a PNG with an alpha channel, and the Transparent option comes on. If you want a solid background, turn it off and pick the color.

Which sizes should I tick?

For a website, 16, 32 and 48. For Windows, 16, 24, 32, 48 and 256. When in doubt, keep the defaults: the file gets a bit larger, but the system always finds a size close to what it needs.

Is there a size limit on the input file?

The tool accepts files up to 50 MB. Since the image is processed in your browser, what limits it in practice is the device memory, and a very large image may be refused with a notice.

Is my image sent to any server?

No. Reading, resizing and building the .ico all happen in the browser, so it works with private images and offline once the page has loaded.