Make a favicon: convert a PNG to an ICO

The favicon can only be as good as the image you feed the converter, so the work starts before any conversion. Use a square source: a favicon is displayed in a square slot, and a non-square image is either distorted or padded when the browser scales it down. Keep the background transparent so the mark sits cleanly against light and dark browser chrome rather than carrying a stray colored box. PNG is the right source format for both of these because it is lossless and keeps an alpha channel.

Design for the size the icon will actually appear at, not the size you are editing at. A favicon is often rendered around 16 by 16 pixels, where a detailed logo, fine text, or thin strokes collapse into an unreadable smudge. Pick one bold, simple shape — a single letter, a monogram, or a compact symbol — and make sure it still reads when you preview it small. Simplify ruthlessly; the version that works as a favicon is usually plainer than a full logo.

If you do not already have a suitable transparent PNG, the NSS Background Remover can produce one: cut the subject out of its background and export a transparent PNG, then bring that file here. Starting from a genuinely transparent source is what lets the favicon blend into any tab color instead of announcing a hard rectangle.

Novus Convert exposes a large matrix of image routes — hundreds of active input-to-output pairs — and the conversion directory at /conversions is the always-current list of every one of them. Before you queue anything, open /conversions and confirm that the PNG source to ICO output pair is present and active. ICO is a listed image output and PNG is a listed image input, so this route is exactly the kind the converter is built to serve, but confirming the specific pair first means you are never guessing at what the current release can do.

Checking the directory also sets the right expectation for the result. The converter only surfaces an upload and output control where it can create a genuine, validated file, so a pair that appears in /conversions is one the app can actually produce and verify — not merely a page describing a format. That distinction matters across Novus Convert, where reference-only format guides sit alongside the routes that truly convert.

Open convert.novusstreamsolutions.com/convert and drag your PNG in, or pick it with the file chooser. Novus Convert identifies the file by its signature rather than its filename, so a PNG that was misnamed along the way is caught here instead of producing a broken favicon later. Once the file is recognized, the outputs the route can genuinely produce appear for that row.

Choose ICO as the output for the PNG row. Because this is a single-file job, there is no batch to manage — you are converting one prepared source to one favicon. If you happen to be preparing icons for more than one site at once, each PNG gets its own row and its own ICO output, and a failure on one row never removes the successful results from the others.

Transparency is the property that makes a favicon look native in the tab, and the PNG-to-ICO route keeps it. Novus Convert only flattens transparency onto a white background when the destination format cannot store an alpha channel, and that applies to JPG and BMP — not to ICO. Converting your transparent PNG to ICO therefore carries the alpha through, so the mark stays cut out rather than gaining a white square behind it.

This is the practical reason the earlier steps insisted on a transparent PNG source. If the source already had a solid background baked in, the ICO would faithfully preserve that background too, because the converter does not invent transparency that was never there. Get the alpha right at the source and the favicon inherits it.

Run the conversion and let the row finish. The download control stays locked until the result matches its expected signature, container, and decodability, so a favicon that reaches your downloads folder is a structurally real ICO rather than a renamed PNG. A conversion can still fail after processing if the output does not pass that final check; that gate is deliberately stricter than trusting a file extension, and it is what lets you trust the result without opening it in a hex editor.

Save the file promptly. Everything runs in browser memory, and each result lives behind a temporary object URL that is revoked when you remove the job or close the page, so download the ICO before you navigate away. The remaining daily download count for that input format shows beside the download control — the app is free, but the allowance is finite and resets by your local calendar day.

Name the downloaded file favicon.ico and put it at the root of your website, because most browsers automatically request /favicon.ico from a site even without any markup. That single placement covers the common case: a browser that finds the file at the root will use it for the tab and bookmarks.

For control and clarity, also reference the icon explicitly in the head of your pages with a link element such as <link rel="icon" href="/favicon.ico">. An explicit reference documents the intent, works when the file lives somewhere other than the exact root, and avoids relying on the default lookup alone. After deploying, load the site in a fresh tab or a private window, since browsers cache favicons aggressively and an old icon can linger until the cache clears.