Artwork that survives 16 pixels
At favicon size a wordmark is unreadable and thin strokes disappear. Test the smallest export, and simplify the source if it does not survive.
Favicon and App Icon Resizer
A favicon set is a ladder of sizes rather than one file: 16, 32 and 48 pixels for browser tabs, 180 for an Apple touch icon, and 192 and 512 for Android and web app manifests. This page resizes onto those squares from your largest artwork, so the mark stays recognisable at tab size instead of being shrunk once and shrunk again.
Choose Files
Upload the logo artwork to cut into icon sizes
or click the button below to browse · paste an image with Ctrl+V
JPG, PNG, WEBP · up to 10 images · 20 MB each · processed in your browser
Selected Images (0)
Frequently Asked Questions About Favicon and App Icon Resizer
What sizes do I need for a favicon?
Commonly 16, 32 and 48 pixels, plus 180 for Apple touch and 192 and 512 for a manifest — all squares from the same artwork.
Should a favicon have a transparent background?
Tabs render small, so a solid or contrasting background usually reads better than transparency that vanishes in dark mode.
Will my original file be changed?
The result is downloaded as a separate file. Keep your original until you have checked the Icon sizes from 16 to 512.
What should I check before using the result?
Open the Icon sizes from 16 to 512 in the application that consumes it and spot-check the parts that matter to you; the original file stays untouched if you need to re-run with different options.
About this workflow
Before downloading the result
Open the Icon sizes from 16 to 512 next to the original at full size and check text edges, faces, and flat backgrounds; re-encoding softens detail long before it looks wrong in a thumbnail.
What this favicon and app icon resizer does
Create common square PNG icon sizes from one source image. The tool packages the selected sizes into a ZIP file and includes a simple site.webmanifest that points to those PNG files. It is useful when preparing a small icon set for a website, PWA prototype, app shortcut, or design handoff.
This workflow exports PNG files. It does not promise an ICO binary because browser Canvas APIs do not create every ICO variant consistently. If a platform specifically requires an ICO file, use its documented conversion step after downloading the PNG pack.
How to create an icon pack
- Upload a square logo, illustration, or other image with clear subject edges.
- Select the PNG sizes you need, such as small browser icons, shortcut icons, or larger app icons.
- Choose Create & Download.
- Open the ZIP file and review each icon at its actual size. Small icons may need a simplified logo or higher contrast.
Preparing a good source image
Start with a sharp image that has enough detail for the largest selected size. A square source avoids unexpected cropping. Keep important marks away from the outer edge because some browsers and operating systems display icons with their own masks or rounded shapes.
What is inside the download
The ZIP contains one PNG for every checked size, using names such as icon-192x192.png, plus a site.webmanifest with matching icon entries. The manifest is a starting point for a web project; review its name, start URL, display mode, and other site-specific values before publishing it.
Privacy and file handling
The source image is processed locally in the browser. The PNG files and manifest are assembled into a ZIP on your device. No account or image upload is required for this workflow.
Frequently Asked Questions
Does this tool create an ICO file?
No. It creates PNG icon sizes and a web manifest. Use the PNG pack directly when the destination accepts PNG, or convert it with a platform-specific tool when an ICO file is required.
Which icon sizes should I choose?
Choose the sizes required by your site or app. Selecting only the sizes you need keeps the download smaller and makes the asset handoff easier to review.
Does the tool make a low-resolution image sharper?
Resizing can change the pixel dimensions, but it cannot recreate detail that was not present in the source. Use a clear, high-resolution source and inspect the smallest icon before publishing.