Favicon generator. Every size. Every platform.
Upload one square image. Download a ZIP with 6 PNG sizes, a web manifest, and copy-ready HTML head tags. Every modern browser, iOS, and Android target covered. Browser-only.
Square PNG, 512×512 or larger.
One image in. Six files out.
A modern favicon is not a single file. It is a stack of six PNG sizes, a web manifest, and a set of HTML link tags that tell browsers and devices which file to load where. The generator above takes a single square source image and emits all of that as one ZIP, preserving transparency, and bundles a ready-to-paste HTML head block so the operator does not have to learn the rel-attribute taxonomy.
Three places favicons break. First, source image too small — upscaling a 64-pixel logo to 512 pixels yields blurry tabs. Start at 512 or larger. Second, source image without padding — browser tabs and iOS home-screen grids crop different amounts; leaving 10 to 15 percent safe margin prevents critical shapes from being clipped. Third, missing apple-touch-icon — iOS home-screen adds loading your site renders as a lo-res favicon scale-up, which looks unprofessional.
For Progressive Web Apps on Android, the 192 and 512 pixel icons plus a valid web manifest are the minimum to earn the install-to-home-screen prompt. The manifest also controls theme color (the browser chrome tint on mobile) and the splash screen background. The generator emits a complete manifest.json as part of the ZIP.
Tools in the same cluster: Color Contrast Checker for WCAG verification of the favicon background vs. browser chrome. Meta Tag Generator for the full head-tag block the favicon lines belong in.
Five answers.
Which favicon sizes do I actually need?
Six PNG sizes cover modern browsers and devices. 16 by 16 and 32 by 32 for desktop browser tabs. 48 by 48 for legacy Windows shortcuts. 180 by 180 for the apple-touch-icon on iOS home screens. 192 by 192 and 512 by 512 for Android Chrome and the Progressive Web App install prompt. The legacy ICO format is still supported but has been deprecated in favor of PNG by Chrome, Firefox, and Safari for several years.
Should my favicon be SVG?
Only as a supplement. Chrome 80+ and Firefox 94+ support SVG favicons, but Safari on iOS and older browsers still require raster PNG. Ship both: a single SVG as the primary (vector, dark-mode adaptive) and the six PNG sizes as fallback. The generator above produces the PNG stack; export a separate SVG from your design tool and add it as rel favicon type image/svg+xml in the head.
What should the source image look like?
Square, at least 512 by 512 pixels, high contrast, and readable at 16 pixels. A single symbol or one or two characters works; full wordmarks become unreadable at 16. The shape should have breathing room around it (10 to 15 percent padding) because browser tabs and app grids crop differently. PNG with transparency is ideal; the generator preserves transparency across all output sizes.
What goes in the web manifest?
The manifest.json tells Android Chrome how to render the site as a Progressive Web App. It lists the 192 and 512 icon paths, theme_color (browser chrome tint), background_color (splash screen), display mode (standalone hides browser UI), and the short_name that appears on the home screen. The generator above emits a valid manifest you can drop at /site.webmanifest; link it in the HTML head with rel manifest.
Does this tool save my data?
No. Your image never leaves this browser tab. All resizing happens client-side via the HTML5 canvas element; the downloaded ZIP is built in memory and never transmitted. Close the tab and everything is gone.
Favicon is one surface.
Our brand engagements ship a full mark system: primary logo, responsive variants, favicon stack, social avatars, and app icon with platform-specific masks. Scoped quote in 48 hours.