🌐 Favicon Generator

Turn a logo or image into a practical favicon package for browser tabs, bookmarks, Apple home-screen icons and PWA installs. Generation happens locally in your browser, and the package includes ready-to-copy HTML.

Choose Your Source Image

Use a PNG, JPG or WebP image up to 10 MB and 40 megapixels. A square source of at least 512Γ—512 pixels usually gives the best result.

No image selected.
Used only inside the generated manifest and README.
Contain is usually safest for logos. Cover may crop wide or tall artwork.
Apple touch and PWA icons are flattened onto this solid background.
Added to the generated manifest and HTML theme-color tag.
10%
Adds breathing room around the artwork. Maskable icons get extra safe-area padding automatically.
PNG and ICO browser icons can stay transparent; Apple/PWA icons use a solid background.
Privacy: the selected image is decoded and resized in your browser for this tool's main operation. ToolStrive does not need to upload the image to generate the favicon files.

Your Favicon Package

Browser tab
32 pixel favicon preview
Search / bookmark
48 pixel favicon preview
Apple touch
Apple touch icon preview
PWA icon
192 pixel PWA icon preview

How to Generate a Favicon Package

  1. Choose a PNG, JPG or WebP logo or image.
  2. Select how the artwork should fit inside a square and adjust the padding if needed.
  3. Choose the solid background used for Apple/PWA icons and the theme color for the manifest.
  4. Click Generate Favicon Package and review the small-size previews.
  5. Download the complete ZIP, upload the files to your website root, then copy the generated link tags into your page head.

If the original artwork needs different dimensions before you create the icon set, use the Image Resizer. If you need to convert a source file to PNG, JPG or WebP first, use the Image Format Converter.

What the Favicon ZIP Includes

The package is designed to cover common browser, mobile and installable-web-app use cases without creating dozens of nearly identical files.

  • favicon.ico containing 16Γ—16, 32Γ—32 and 48Γ—48 PNG-compressed icon frames.
  • favicon-16x16.png, favicon-32x32.png, favicon-48x48.png and favicon-96x96.png for browser/search contexts.
  • apple-touch-icon.png at 180Γ—180 with a solid background for iPhone/iPad home-screen use.
  • icon-192x192.png and icon-512x512.png for the generated web app manifest.
  • icon-512-maskable.png with extra safe-area padding for maskable PWA launchers.
  • site.webmanifest, favicon-links.html and README.txt so the output is easier to install correctly.

Choosing a Good Favicon Source

Favicons are displayed very small, so simple shapes and strong contrast usually work better than detailed photographs or long text. A square logo at 512Γ—512 pixels or larger gives the generator enough detail for the larger app icons, while the 16/32/48 previews help you check whether the mark still reads clearly at tab size.

Google can use a site's favicon in search results when the favicon is crawlable, square and associated with the site's home page. A 48Γ—48 or larger square source is a practical target for search surfaces, while a higher-resolution original helps the same artwork look cleaner on mobile home screens and PWA launchers.

For a complete size reference, copy-ready HTML, Apple touch guidance, PWA manifest examples and a launch checklist, read the Favicon Sizes & Browser Support Guide.

This tool creates raster favicon assets. It does not vectorize a bitmap or create an SVG favicon from a PNG/JPG source. If you already have a carefully designed SVG logo, keeping a hand-authored SVG favicon can preserve vector sharpness in browsers that support it.

Limits and Compatibility

  • Input is limited to 10 MB and 40 megapixels to reduce the chance of browser memory problems.
  • PNG, JPG and WebP input are supported when the browser can decode the selected format.
  • Small source images can be upscaled, but upscaling cannot recreate missing detail.
  • Browser favicon caches can be stubborn. If a new icon does not appear immediately, hard-refresh the page or clear the site's cached data.
  • The generated manifest assumes the icon files are stored at your site root. Edit the paths if you upload them somewhere else.
  • ICO output uses PNG-compressed frames, which is appropriate for modern browsers and current Windows versions but is not intended for very old legacy software.

Frequently Asked Questions

Is my logo uploaded to ToolStrive?

No. The favicon generation itself runs in your browser using standard image, canvas and file APIs. The image bytes do not need to be sent to ToolStrive to create the files.

Why are Apple and PWA icons given a solid background?

Home-screen and launcher icons are commonly masked or displayed against system UI. Flattening them onto a deliberate background gives more predictable results than relying on transparent pixels.

Do I need every generated file?

No. The package gives you useful coverage across classic favicons, modern PNG icons, Apple touch icons and PWA installs. A simple site can use only the ICO/PNG and Apple files; installable apps benefit from the manifest icons too.

Why does my old favicon still appear after upload?

Browsers and search engines cache favicons aggressively. Confirm that the new files are reachable at the paths in your HTML, then allow time for caches and crawlers to refresh.

Related Image Tools