PNG/JPG to ICOOn-device processing

Preparing your tool…

How to use it

  1. 01Choose up to 8 supported images. File contents are checked instead of trusting the extension.
  2. 02Keep the required output format and adjust relevant optional settings if needed.
  3. 03Convert, review dimensions and actual file size, then download successful results.

Choose this conversion for the right reason

A favicon or Windows-icon workflow may accept a PNG-backed ICO. Choose one size from 32, 64, 128 or 256 pixels. The image is fitted without distortion or cropping into a transparent square, which can add empty space around a non-square source.

Files are processed one at a time in a worker to limit peak memory. Invalid or unsupported images are reported individually. Conversion changes format; it does not guarantee compression, remove a background or recreate missing source detail.

Practical check: Confirm the destination accepts a single PNG-backed icon rather than a legacy or multi-size ICO.

Useful details and limits

Creates one PNG-backed icon at 32, 64, 128 or 256 pixels. Artwork is fitted inside a transparent square without cropping. Not a multi-size or legacy DIB icon. Limits: 20 MB per file, 40 MB input per batch and 120 MB combined results. General decoding is capped at 20 million pixels and 16,000 pixels per side. Metadata and color profiles are not preserved. Originals are not changed. A failed file receives its own error and does not stop the other conversions.

Questions about this tool

What kind of output does this tool create?

Creates one PNG-backed icon at 32, 64, 128 or 256 pixels. Artwork is fitted inside a transparent square without cropping. Not a multi-size or legacy DIB icon.

What should I check before using the converted file?

Confirm the destination accepts a single PNG-backed icon rather than a legacy or multi-size ICO.

Are my images uploaded or stored?

No. Files, previews, conversion and ZIP creation remain on your device. A codec may load from Tool Fera when needed, but your image bytes are not sent with that request.

Understand the workflow