No. Every size is rendered in your browser and the .ico is assembled locally. Nothing is transmitted or stored.

What is inside the .ico?

The 16, 32 and 48 pixel versions, which is what browsers request from favicon.ico. Larger sizes ship as separate PNGs, which is how modern sites reference them.

My logo is a wide wordmark — what happens?

A centred square crop will cut the ends off. Crop to the symbol yourself in the Image Cropper first, or use a compact mark designed for small sizes.

Make a favicon from your logo

Runs in your browser

Drop your logo in below. It is cropped to a centred square, then rendered as favicon.ico plus PNGs at 16, 32, 48, 180, 192 and 512 pixels.

Drop images hereor click to choose — nothing is uploaded

A favicon is not one file

Browsers still request /favicon.ico by default. iOS wants a 180-pixel apple-touch-icon for home screens. Android and PWA manifests reference 192 and 512 pixel PNGs. Each is fetched in different circumstances, so shipping only one means a blurry or missing icon somewhere you will not see.

Design for 16 pixels

At favicon size a detailed logo becomes noise. High-contrast marks with one clear shape survive; wordmarks almost never do. Most brands maintain a simplified symbol purely for this purpose — worth doing before you generate anything.

Where the files go

Put them in your site root and reference them from the head. Keeping the generated file names means the standard snippets and manifest examples work unchanged.

Why the old favicon will not go away

Browsers cache favicons unusually aggressively, and often separately from ordinary page assets, so a new icon can take days to appear for returning visitors and may survive a hard refresh. To check your work, open the icon URL directly rather than trusting the tab, and test in a private window. If a stale icon persists after deployment, the file is almost certainly cached rather than missing — confirm by requesting /favicon.ico and looking at what actually comes back.

FAQ

Is my logo uploaded?: No. Every size is rendered in your browser and the .ico is assembled locally. Nothing is transmitted or stored.
What is inside the .ico?: The 16, 32 and 48 pixel versions, which is what browsers request from favicon.ico. Larger sizes ship as separate PNGs, which is how modern sites reference them.
My logo is a wide wordmark — what happens?: A centred square crop will cut the ends off. Crop to the symbol yourself in the Image Cropper first, or use a compact mark designed for small sizes.

The tools behind this

Doing this regularly? The Favicon From a Logo recipe runs the whole job in one pass.