Generate a Favicon Set From an Image
Turn a square logo into the standard 16, 32, 48, 64, 128, 180, 192 and 512 px PNG icons plus one multi-size .ico. No upload.
What this page does
Crops a square from the centre of your image, scales it to every icon size a site needs, and packs the small sizes into one .ico file. The PNG set covers modern browsers, iOS and the web manifest.
How to use it
Choose a file, set the options and press Render. Example: a 1024 × 1024 PNG logo becomes eight PNGs from 16 to 512 px plus one 16/32/48/64 .ico.
How it works
The centre square is copied once, then scaled with the browser's smooth downscaler to each size. The .ico is assembled byte by byte with PNG-compressed frames, which every current browser reads, and the 180 px PNG is the apple-touch-icon.
What it refuses
A source smaller than 512 px on its short edge is refused because upscaling would invent detail, and a non-square source is cropped from the centre rather than stretched.
Where it runs
The picture is decoded and redrawn on a canvas in this tab: there is no upload, no network request and no model, so the pixels never leave your device. It opens PNG, JPEG, WebP, GIF, BMP and AVIF up to 16,000,000 pixels (16 MP) and 25 MB per file; anything larger is refused with its measured size rather than drawn blank.
Crops a square from the centre of your image, scales it to every icon size a site needs, and packs the small sizes into one .ico file. The PNG set covers modern browsers, iOS and the web manifest.
The centre square is copied once, then scaled with the browser's smooth downscaler to each size. The .ico is assembled byte by byte with PNG-compressed frames, which every current browser reads, and the 180 px PNG is the apple-touch-icon. The picture is decoded and redrawn on a canvas in this tab: there is no upload, no network request and no model, so the pixels never leave your device.
Worked example: a 1024 × 1024 PNG logo becomes eight PNGs from 16 to 512 px plus one 16/32/48/64 .ico.
How to use the generate a favicon set from an image
Choose an image file, set the options, and press Render. The result appears below the form.
Example: a 1024 × 1024 PNG logo becomes eight PNGs from 16 to 512 px plus one 16/32/48/64 .ico.
The picture is decoded and redrawn on a canvas in this tab: there is no upload, no network request and no model, so the pixels never leave your device.
- Fill behind transparency — one of transparent, white, black
What the canvas draws
Crops a square from the centre of your image, scales it to every icon size a site needs, and packs the small sizes into one .ico file. The PNG set covers modern browsers, iOS and the web manifest.
The centre square is copied once, then scaled with the browser's smooth downscaler to each size. The .ico is assembled byte by byte with PNG-compressed frames, which every current browser reads, and the 180 px PNG is the apple-touch-icon.
- Every option is declared by this page, so an unknown choice or an out-of-range number is refused by name before any pixel is drawn.
- The preview and the download are the same canvas: what you see is the file you get.
What it refuses, and what it leaves out
A source smaller than 512 px on its short edge is refused because upscaling would invent detail, and a non-square source is cropped from the centre rather than stretched.
It opens PNG, JPEG, WebP, GIF, BMP and AVIF up to 16,000,000 pixels (16 MP) and 25 MB per file; anything larger is refused with its measured size rather than drawn blank.
- Not the right page for: designing the logo itself
- Not the right page for: a full set of maskable Android icons with safe-zone preview, which this page does not model
What to Expect
Best for
- a site that needs favicon.ico and the manifest icons in one go
- an app icon set from one square source
- replacing a placeholder favicon
Not ideal for
- designing the logo itself
- a full set of maskable Android icons with safe-zone preview, which this page does not model
What this tool keeps
- The centre square of the source
- Transparency in the PNGs when chosen
- A real multi-size .ico, not a renamed PNG
What may need cleanup
- Adding the files to the site's head and manifest by hand
- Checking the 16 px icon still reads at that size
Common errors
- A non-square source is centre-cropped, not stretched
- A source below 512 px is refused rather than upscaled
- The .ico carries at most 256 px frames by format limit
Example use cases
- Setting up a new site's icons
- Replacing a generic favicon with a logo
Sample input
a 1024 × 1024 PNG logo
Sample output
eight PNGs from 16 to 512 px plus one 16/32/48/64 .ico
Who this is for
- Web developers shipping a site
- Designers handing off an icon set
Frequently asked questions
Does my image get uploaded anywhere?
The picture is decoded and redrawn on a canvas in this tab: there is no upload, no network request and no model, so the pixels never leave your device.
What is the maximum image size?
It opens PNG, JPEG, WebP, GIF, BMP and AVIF up to 16,000,000 pixels (16 MP) and 25 MB per file; anything larger is refused with its measured size rather than drawn blank. The limit exists because a browser tab has to hold the decoded bitmap in memory.
What happens if the file cannot be decoded?
The page refuses it by name — unsupported type, decode failure, zero pixels, or above the pixel cap — and shows the measured size rather than drawing a blank canvas. The file you chose stays selected so you can correct one option and try again.
Which file do I actually need?
Most sites want favicon.ico at the root plus a 32 px PNG and the 180 px apple-touch-icon. The 192 and 512 px files are for the web app manifest, and the 16 px file is for browser tabs that still prefer PNG.
Why not upscale my small logo?
Upscaling cannot add detail; it only smooths or invents pixels, and an icon is exactly where that shows. The page refuses a source under 512 px and names the size you gave it.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.