Favicon Generator
Create 16-512 px PNG icons, a multi-size favicon.ico, Web Manifest, and ZIP from text or an image
Includes 6 PNG sizes, an ICO with 16/32/48 px frames, and a manifest. Text uses the first 4 complete characters; glyphs depend on installed fonts. Images fit centrally; rounding clips corners. Deploy at the site root and add icon links yourself.
Favicon previews will appear here.
About this tool
Create a favicon package from a local PNG, JPEG, WebP or AVIF logo, or from a text mark. The ZIP contains six square PNGs at 16, 32, 48, 180, 192 and 512 pixels; favicon.ico contains the 16, 32 and 48 pixel PNG frames. A starter site.webmanifest references the 192 and 512 pixel files relative to the manifest. Text rendering uses the first four grapheme clusters where the browser supports segmentation, with a Unicode code-point fallback, and fits them within the icon. Available fonts determine glyph and emoji appearance. Foreground applies to text; the background applies to both modes. Image mode uses proportional contain fitting with possible padding, while rounded mode clips the square corners, including any image content at those corners. Inspect the 16-pixel result before deployment. Place the package at the site root, add icon and manifest links to the page, and adjust manifest names, start URL, paths and cache version for the application. Generating a package does not install it on a website. Each input must be at most 40 MiB, with no edge above 8192 pixels and no more than 32 million pixels. Files are processed in this tab and are not saved as browser drafts.
Scenario Recipes
Create and review a favicon package before a web release
Goal: Catch tiny-icon and manifest problems before cache-heavy deployment
- Generate the package from the approved logo or text mark and inspect every preview, especially 16 and 32 pixels.
- Open the ICO and PNG files in the target browser and operating-system environments, checking padding and contrast.
- Edit manifest names and paths for the application, deploy to staging, and verify cache-busted icon links before production.
Result: A reviewed favicon package with platform, path, and cache assumptions made explicit.
Frequently Asked Questions
What exactly is in the ZIP?
Six PNG sizes, one ICO containing the 16/32/48 PNG frames, and one site.webmanifest: eight files in total.
How is long text handled?
The first four complete grapheme clusters are used when supported, with a code-point fallback. The text is fitted to the icon width; inspect small sizes for readability.
Is image content cropped?
Contain fitting preserves the aspect ratio and may add padding. Rounded mode then clips the square corners, so content touching those corners can be removed.
Why can emoji look different on another computer?
Canvas uses available local fonts. Emoji glyphs and color rendering are not embedded from a fixed font, so inspect your generated PNGs.
Does the manifest automatically configure my website?
No. Deploy the files, add favicon and manifest link tags, and edit application names, start_url and paths as needed. The provided icon paths are relative to site.webmanifest.
What happens when I edit a setting?
The previous package is cleared, and any older asynchronous generation is prevented from replacing the new result.
Keep browsing