Question 1

My ICO file has multiple sizes — which one do I get?

Accepted Answer

ICO is a container that holds several PNG/BMP icons at different sizes. Browsers automatically pick the largest version when decoding, so you get the sharpest image (typically 256 × 256 for modern favicons, 32 × 32 for older ones). If you need a specific smaller size afterwards, run our Resize Image tool.

Question 2

Is transparency preserved?

Accepted Answer

Yes — ICO supports full alpha and so does PNG, so cut-out icons stay transparent. This is essential for favicons, which are usually drawn on whatever background colour the browser tab happens to be.

Question 3

Why convert ICO to PNG?

Accepted Answer

PNG is a far better format for modern use cases: editable in any image editor, supported in mobile and PWA manifests, viewable on every platform without special tooling, and easier to embed in documents or websites that need a single specific resolution.

Question 4

Does this work for .CUR cursor files?

Accepted Answer

Some browsers will decode .cur files since the file format is essentially the same as ICO with a hotspot field. If your browser refuses, rename the .cur to .ico and try again — the binary structure is compatible.

Question 5

Can I convert PNG back to ICO?

Accepted Answer

Browsers cannot natively encode ICO via canvas, so we offer the one-way ICO → PNG conversion only. To create an ICO from a PNG, use a desktop tool like ImageMagick (`magick convert input.png -define icon:auto-resize=256,128,64,48,32,16 favicon.ico`).

Question 6

Why is in-browser image processing slower than online editors?

Accepted Answer

Server-side editors run on dedicated CPUs and GPUs with native code paths and parallel workers. Our engine uses the HTML5 Canvas API running single-threaded inside your browser tab, which is typically 2–5× slower than a backend pipeline. The trade-off is total privacy: your image is never uploaded, never logged, never stored on a third-party server. Closing the tab erases everything from memory immediately. For most photos, screenshots, and graphics the wait is small, and for sensitive material — work documents, ID scans, private photos — the privacy gain is well worth the few extra seconds.

Question 7

Is my image uploaded to a server?

Accepted Answer

No. Everything runs entirely inside your browser tab using the HTML5 Canvas API and JavaScript. The file is decoded into local memory only, processed in the same tab, and the result is offered as a direct download. Nothing is transmitted to any server, no account is required, no analytics are tied to your file, and closing the tab discards every byte from memory.

Question 8

How big a file can I process?

Accepted Answer

Up to 25MB and roughly 64 megapixels by default. The limit exists because every pixel needs to fit inside your tab's memory. Most phone photos, screenshots, and design exports sit comfortably under that ceiling. If your image is larger, resize or compress it first (try our Resize Image or Compress Image tools) before re-running the effect.

Question 9

Which input image formats work?

Accepted Answer

JPG, PNG, WebP, GIF, BMP, AVIF, HEIC, and most other formats your browser can decode natively are supported. Output is typically PNG (lossless, preserves transparency) or JPG (smaller file size for photos). Some tools expose a format picker so you can match the file type your downstream app expects.

Question 10

Does the effect lose quality?

Accepted Answer

PNG output is lossless — every pixel the canvas wrote out is encoded exactly as drawn. JPG output is recompressed (visually near-lossless above 85% quality). The effect itself works on raw pixels, so there is no double-encoding penalty as long as you keep the default PNG output.

Question 11

Which browsers are supported?

Accepted Answer

Recent Chrome, Edge, Firefox, Safari, and other Chromium-based browsers all work. The tool only relies on the standard HTML5 Canvas API, which has been universally supported for over a decade. Mobile browsers work too, although large images may take noticeably longer because phone CPUs are weaker than desktop CPUs.

Question 12

Is there a watermark or sign-up wall?

Accepted Answer

No. The tool is completely free, requires no account, attaches no watermark, applies no rate limits, and shows no popup ads on your output. The download is the file you would get from running the same canvas operation locally — nothing more, nothing less.

Question 13

Does ICO to PNG Converter reduce quality of the result?

Accepted Answer

ICO to PNG Converter is built to preserve quality wherever the underlying image format allows it. Operations that are mathematically lossless (e.g. structural transformations, lossless re-encoding) round-trip with no perceptible change. Operations that involve a lossy codec inevitably introduce small artefacts at the byte level, but the defaults aim at the sweet spot where output looks or sounds the same to a normal viewer or listener while still being meaningfully smaller or faster than the input.

Question 14

Does ICO to PNG Converter work with screen readers?

Accepted Answer

ICO to PNG Converter uses native HTML controls wherever possible, which means keyboard navigation, focus rings, and screen-reader labels work the way the platform expects. The drop zone accepts files via the keyboard-accessible file picker as well as drag-and-drop, and result downloads use standard browser download flows. If you spot an accessibility gap, Favtoo treats it as a bug worth fixing.

Question 15

How is ICO to PNG Converter different from desktop apps that do the same thing?

Accepted Answer

Desktop apps usually have more advanced features but require installation, maintenance and (often) a licence. Paid online tools are convenient but route your file through their servers and gate downloads behind accounts. ICO to PNG Converter sits in between: free, instant, and private, but intentionally narrow in scope. For one-off jobs and the common image editing and conversion operations, it is usually the lowest-friction choice; for highly specialised work, a dedicated app is still the right answer.

Question 16

Are jobs run with ICO to PNG Converter stored anywhere?

Accepted Answer

Favtoo keeps no copy of your file because Favtoo never receives your file. ICO to PNG Converter runs entirely in your browser, the input is held only in your tab's memory, and closing the tab discards it. There is no opt-in cloud history, no "recent jobs" panel synced to an account, and no server-side retention to configure — the architecture simply has nowhere for your file to be stored.

Question 17

Can I use ICO to PNG Converter on documents that contain personal data?

Accepted Answer

Your file is processed inside your browser by standard browser APIs. The engine reads the file's bytes from your tab's memory, computes the result, and writes the result back into the tab. You can confirm what the page does by opening developer tools and watching the Network tab during a run — the requests you see are for the tool's static assets only.

Question 18

Are there any usage limits on ICO to PNG Converter?

Accepted Answer

Inputs are capped at 100 MB per file, which keeps memory usage stable across phones, tablets and older laptops. You can run ICO to PNG Converter as often as you need; every run produces a full-quality result.

Question 19

Does ICO to PNG Converter match what professional tools produce?

Accepted Answer

ICO to PNG Converter is built on standard browser APIs, which is the same class of engine used by professional image editing and conversion pipelines. For deterministic operations, the output is byte-identical to what an equivalent CLI run would produce; for operations involving a codec or a model, the result is well within the range of what comparable tools generate. If you have a specific reference output you need to match, run a small test job first to confirm the configuration produces what you expect.

Explore more Image Tools