Icon Generator
Generate favicons and app icons from a single image
Upload Image (256x256+ recommended)
0.0B / 0.00%
Output Settings
Turn one square image into the whole set of favicons and app icons a site needs — ICO, PNG at standard sizes, Apple touch icon, Android and Windows tiles — packaged for download.
Shipping an app or a site means producing the same artwork at a dozen sizes, and each platform has its own list: favicons at 16, 32 and 96 pixels, an Apple touch icon at 180, Android launcher icons at 192 and 512, and the maskable variant that Android crops to whatever shape the launcher uses.
One source image here produces the whole set, downscaled in the browser rather than uploaded. The reason to start from a large square — 1024 pixels or more — is that downscaling keeps detail and upscaling invents it; a 64-pixel source enlarged to 512 will look soft no matter what the tool does.
The maskable icon is the requirement most often missed. Android does not display a launcher icon as you supply it — it crops the image to whatever shape the current launcher uses, which may be a circle, a rounded square or a squircle depending on the device. An icon designed to fill its canvas therefore loses its corners, and a logo with text near the edge loses the text. The convention is a safe zone: keep everything essential inside the middle 80% of the image and treat the outer band as background that may or may not survive.
ICO is a container rather than an image format, which is why a favicon.ico can hold several sizes at once and why that is worth doing. A browser picks the size closest to what it needs, and a single 16-pixel entry scaled up for a bookmark bar or a pinned tab looks noticeably worse than a file that also carries 32 and 48. The same reasoning applies to the touch icon at 180 pixels and the Android pair at 192 and 512: each exists because something specific asks for that size, and supplying it is cheaper than letting the platform guess.
Downscaling keeps detail and upscaling invents it, which is the one rule that decides how good the output can be. A 1024-pixel square source produces a clean 16-pixel favicon; a 64-pixel source enlarged to 512 will look soft no matter what any tool does with it. Transparency is worth deciding deliberately too — a transparent background is right for a favicon that will sit on both light and dark browser chrome, and wrong for an Android maskable icon, where the platform expects the artwork to fill the canvas and will otherwise crop into empty space.
An SVG favicon is the modern addition worth including alongside the raster set. Browsers that support it scale one file to any size, and a media query inside the SVG can swap the artwork between light and dark browser chrome — something a PNG cannot do at all. It does not replace the ICO, because a bookmark export, an older browser or an operating system shortcut will still ask for a raster file. The two coexist: the SVG declared first for browsers that understand it, the ICO left at the site root for everything that simply requests /favicon.ico without being told to.
No. Resizing happens on a canvas in your browser and nothing is transmitted.
PNG favicons cover every current browser, but favicon.ico at the root is cheap and still requested by some clients, so it is worth including.
512×512 or larger. Upscaling a small source produces soft icons at the large sizes, and the tool warns you when the input is too small.