Favicon Generator

It prepares six PNGs: 16, 32, 48, 180, 192 and 512 pixels square. It also creates a favicon.ico with PNG-compressed 16, 32 and 48 px entries, a site.webmanifest, HTML tags and README notes. An optional separate 512 px maskable icon brings the package from 10 to 11 files.

Choose one non-empty PNG, JPG/JPEG or WebP file up to 10 MiB. File signatures and browser decoding are checked. The decoded image must be no larger than 20 MP or 16,384 px on either side. SVG, GIF, HEIC, PDF and TIFF are not accepted. Animated WebP becomes a decoded still image. Decode limits reduce workload but are not a total-memory guarantee.

Fit whole logo keeps the entire image inside the square, leaving space when its proportions differ. Fill and crop uses a square portion of the image; horizontal and vertical crop position choose which part remains. Padding is measured on each side as a percentage of the output square. These settings affect the regular icons and Apple touch icon.

Regular PNGs and the ICO preserve rendered transparency unless Fill regular icon backgrounds is selected. The Apple touch icon is always composited over the chosen background color. The optional maskable icon also uses an opaque background. A transparent source can still contain faint or partially transparent artwork, so inspect the generated files.

It creates a separate opaque 512 px icon with the full logo rectangle inside a central safe circle whose diameter is 80% of the image. Padding adds more space inside that area. Crop position and Fill and crop do not apply to this icon. Its manifest entry uses purpose maskable. Review the result on your intended devices; the tool does not certify platform acceptance.

Enter a same-origin URL folder that starts and ends with a slash, such as / or /icons/. Each segment can contain letters, numbers, hyphens and underscores. Upload the icons and site.webmanifest to that folder on your website. The generated HTML and manifest use that path; they do not upload files or set your website favicon automatically.

Use the generated 512 by 512 PNG in WordPress Site Icon settings. Settings > General is one entry point; themes and editors may offer another. Use your site’s supported controls instead of pasting HTML into an ordinary page body. If adding tags through a theme or plugin, check for duplicate favicon declarations and correct public file paths.

No. It supplies the website name, short name, icon paths, colors and selected display preference. This tool does not generate a service worker, start_url, scope or id, or validate browser installability. Further site configuration and testing may be needed. A manifest is not an Android application package.

No. Smaller sources can be resized to the requested icon dimensions, but resizing does not create missing detail. A square source of at least 512 by 512 pixels avoids upscaling for the largest regular output. Fine text and complex artwork can be hard to recognize at 16 px even when the original is large.

First open the generated icon URLs directly and check they return the expected files. Check your theme or plugin for competing icon tags and confirm the configured folder is correct. Browser, website and CDN caches can delay updates. Clear relevant caches and try a fresh browser session; a hard refresh alone may not replace a cached icon.

Changing an icon or manifest setting discards the previous package and HTML so stale files cannot be downloaded. Select Generate icons again. Stop is checked after image reading or decoding, between PNG encodes and before publishing the full package. It cannot interrupt a native browser decoder or encoder mid-call. A stopped generation publishes no partial package; stopping ZIP packaging keeps the prepared icons.

The favicon workflow reads and processes the selected image in this browser, and packages the files locally. It does not send the selected image contents to a conversion service. This does not describe unrelated website analytics or plugins. Only the theme preference is stored by this tool. Images, settings and generated files are not saved as a reusable project.

No. The source is drawn and resized into raster PNG outputs; source bytes and original metadata are not copied. The ICO wraps three of those PNGs and may not work in very old software that requires BMP/DIB icon entries. Generated artwork stays based on your source; the tool does not verify ownership, trademark rights or suitability for every platform.