Android app icons
Prepare launcher density PNGs and a Google Play 512×512 icon from one source.
023 · CONTENT IMAGE
App Icon & Favicon Generator
Turn one image into Android app icons, PWA 192×192 and 512×512 icons, favicon.ico, and organized favicon bundles in your browser.
LOCALPROCESS IN YOUR BROWSER
HOW TO USE
How to use
- 01
Choose a PNG, JPG, or WebP source image.
- 02
Adjust contain/cover, background, position, and zoom while checking Android and PWA mask previews.
- 03
Generate the assets and download the platform bundle or complete ZIP.
USE CASES
Use cases
PWA icons
Create 192×192 and 512×512 regular and maskable icons together.
Website favicons
Generate 16×16, 32×32 and 48×48 PNG files plus a multi-frame favicon.ico.
Brand icon bundle
Use one logo to produce organized Android, PWA and favicon assets in one ZIP.
EXPERT POST
Practical standards for reliable app icons and favicons
This section covers platform safe zones, small-size readability, and ICO/ZIP structure to check before deployment.One source, many output presets
App icons and favicons can share one logo while still requiring different sizes and display rules. Using one normalized layout across presets helps keep scale and positioning consistent between outputs.
Android adaptive safe zone
Android launchers can apply circle, rounded-square, and other masks to adaptive icons. Keeping important logo content inside the central safe area reduces cropping risk; the 108dp/66dp guide is an editing aid for that check.
Regular and maskable PWA icons
Regular and maskable PWA icons can use the same source but serve different display purposes. For maskable output, keep key content in the central safe zone and use a full-bleed background around it.
Check favicons at real small sizes
A logo that looks clear in a large editor can become muddy at 16×16 or 32×32. Review the generated small-size pixels directly before deciding whether the source design itself needs simplification.
Verify ICO and ZIP structure
A favicon.ico can contain multiple size frames, and a project-ready ZIP should make each asset easy to place. TOOLBOX separates Android, PWA, and favicon folders and builds the ICO with 16, 32, and 48 pixel frames.
Local browser processing
Source images and generated assets are processed in the current browser rather than uploaded to a server. After generation, verify the downloaded file sizes, dimensions, and intended destinations before deployment.
Review the smallest outputs before shipping
Checking only 512×512 can hide line merging, disappearing text, and spacing problems introduced by downscaling. Review 16×16 and 32×32 favicons and mask previews first, then compare larger assets for consistent centering and margins.
Separate file replacement from cache refresh
Even when icon files are replaced correctly, browser, OS, and installed-PWA caches can keep older artwork visible. Distinguish generated-file problems from cache behavior, then verify the project paths plus manifest and HTML references.
IMPORTANT NOTES
Important notes
Separate platform masks, small-size readability, and cache behavior to reduce unexpected icon differences after deployment.- Pixels outside the Android adaptive safe zone may be cropped by launcher masks.
- PWA maskable icons serve a different purpose from transparent favicons, so keep the outputs separate.
- Google Play listing requirements can change; verify current official guidance before publishing.
- Complex logos may lose readability at small favicon sizes.
- Browsers and operating systems may cache icons after you update a site.
FAQ
Frequently asked questions
01Why create both 192×192 and 512×512?+
They are widely used core PWA icon sizes and TOOLBOX generates both by default.
02Are regular PWA and maskable icons the same file?+
They can share a source, but their display purpose differs; maskable output accounts for the safe zone and a full-bleed background.
03Why can Android icons appear circular?+
Adaptive icons can be masked differently by launchers, so the tool previews circle, squircle, rounded-square and square shapes.
04What is inside favicon.ico?+
It is generated with 16×16, 32×32 and 48×48 frames in one ICO file.
05Are files uploaded to a server?+
No. Supported image processing runs in the current browser.
Your image and generated assets are processed in the current browser and are not uploaded to a server.