How pngtoico.app makes icons on your device

The evidence behind the claims on the PNG to ICO converter: what happens to your image, how each size is made, stored and tested, and how to check that your image stays on your device.

Updated

What happens to your image

Your browser opens the image with its own decoders and hands the pixels to the site's code, which resizes and encodes them in a background worker on your device. Nothing is sent anywhere. ICO files you add are read with decode-ico 0.4.1, an open-source ICO reader.

How each size is made

Every size is computed from your original image, never from another size. To shrink it, each icon pixel takes the average color of the patch of your image it covers (area averaging), with every source pixel weighted by its share of the patch and by how opaque it is. Weighting by opacity keeps transparent edges clean: fully transparent pixels can hold any color, often black, which a plain average would turn into a dark fringe. An image smaller than a chosen size is enlarged by blending the nearest pixels (bilinear), and its tile says so.

An SVG is drawn again by your browser at each size. Every other image is resized by the site's code, not by the browser's image scaling, so the same decoded pixels give the same icon in every browser.

How the ICO file is stored

The file follows the layout Microsoft documents: a directory with one entry per image (width, height, length and position), then the images, each stored in one of two ways:

OptionSizes under 256 px256 px
Default32-bit bitmap with an alpha channel, plus the 1-bit maskPNG
Smaller filePNGPNG

The default follows Microsoft's icon guideline to compress only the 256 px image. Windows has read PNG images inside an ICO since Windows Vista.

How every file is checked

Every ICO the engine tests write is read back by three programs: decode-ico (the same pixels, exactly), ImageMagick's identify (the same list of sizes) and Pillow, the Python imaging library (the same pixels in each image). The reader is tested on ICO files made with ImageMagick, from 1-bit and 8-bit palette images to a 256 px PNG image and a .cur cursor, on a 24-bit bitmap with its mask and an older 32-bit icon whose transparency is only in the mask, and on damaged files (cut off, offsets past the end, a count of 65,535 images, a 0 × 0 entry), each of which must give an error.

Browser tests drive each page with a script and check the downloads with ImageMagick or Pillow: a PNG with the Windows icon preset (its sizes, a center pixel, a transparent corner), a wide JPG made square, an SVG whose 16 px image must have the exact colors of a drawing made at 16 px, a tile with its own image, an ICO taken apart into five PNGs, the favicon ZIP and its manifest, WebP, BMP, GIF and AVIF files, and a batch of three next to a file of the wrong type and two damaged files, each with its own message.

Last tested: November 22, 2026. Result: the 5 engine tests passed, and the 11 browser tests passed in Chrome, in Firefox and in WebKit, the engine of Safari.

Known limits

The largest size is 256 px, the largest Microsoft gives for an icon. An ICO you open can hold up to 64 images and be up to 32 MB. An image you add can be up to 32 MB and 32 megapixels, with no side longer than 16,384 pixels, and an SVG up to 2 MB. The tool takes up to 32 files at a time. AVIF works only where the browser can open it, and only the first frame of an animated GIF is used.

The tool does not write macOS icons (ICNS) or cursors, read icons out of EXE or DLL files, trace an ICO into an SVG, or edit pixels.

Not tested yet: phones in hand, and opening the icons in Windows itself (File Explorer and the desktop). The ICO files are checked instead by reading them back with three other programs, as described above.

How to check that nothing is uploaded

You do not have to take this on trust. Three checks, from quickest to most thorough:

  1. Go offline. Load the tool, turn off Wi-Fi, then convert an image. It works, which it could not do if the image had to reach a server.
  2. Watch the network. Open your browser's developer tools, go to the Network tab and add an image. The page fetches its own code from pngtoico.app and, if analytics is on, sends small requests to Google Analytics and Microsoft Clarity. None contains your image, its name or its contents.
  3. Read the security policy. Every page's Content-Security-Policy header tells the browser to block the page from sending data anywhere except pngtoico.app and the two analytics services.

Before each release, tests use the tool offline, and add images with a marker in their names (and type one into the site name field) while both analytics services run: a marker in any request fails the test. What the services do receive is on the privacy page.