A favicon generator turns a local source image into exact-size square PNG files and matching HTML link elements for website icons.

A favicon is the small image a browser may use to represent a website. The Favicon Generator follows a deliberately narrow workflow: decode one static PNG, JPEG, or WebP locally, take a centered square crop, render each requested size independently, and provide matching link snippets. It prepares files and markup; it does not upload them to your site or change a deployed page.

favicon generator explained
Favicon Generator Explained: PNG Sizes and Cropping

What the generator actually creates

The available outputs are 16, 32, 48, 64, 128, 256, and 512 pixels square. Each selection produces a separate PNG download and a corresponding HTML icon element. The filename pattern and sizes value stay aligned so that the file referenced in the markup is the file you actually generated.

Selected size Example PNG filename HTML sizes value
16 × 16 pixels favicon-16x16.png 16x16
32 × 32 pixels favicon-32x32.png 32x32
48 × 48 pixels favicon-48x48.png 48x48
64 × 64 pixels favicon-64x64.png 64x64
128 × 128 pixels favicon-128x128.png 128x128
256 × 256 pixels favicon-256x256.png 256x256
512 × 512 pixels favicon-512x512.png 512x512

Each requested output is rendered independently from the decoded source at its natural target dimensions. The tool does not enlarge a small preview and reuse that preview for larger downloads. The on-screen preview is only a visual check; downloading a link gives the exact dimensions named by that link.

Results are PNG blobs, and each file must be downloaded separately. The matching snippets use rel="icon", type="image/png", the exact square sizes value, and a root-relative filename such as /favicon-32x32.png.

Why the center crop changes the frame

Before any size is rendered, the tool takes the largest possible square from the middle of the source. This is a predictable center-cover crop, not a face-detection or manual cropping feature.

Source shape Part removed by the centered square crop
Landscape Equal portions of the left and right edges
Portrait Equal portions of the top and bottom edges
Square Nothing; the full source is used

The consequences depend only on source orientation: a landscape image loses equal portions from the left and right, a portrait image loses equal portions from the top and bottom, and a square source is not cropped. A subject that was near the edge may therefore be partly or completely removed before resizing begins.

The generator is not an interactive crop editor. For an intentionally off-center subject, crop a copy first with the Image Cropper, then use that square or centered version. A simple logo, symbol, initials, or illustration with strong contrast usually survives the reduction better than a detailed scene.

Generate favicons from a local image

  1. Choose a supported source file. Select a static PNG, JPEG, or WebP no larger than 25 MB. Make sure the main subject is near the center. SVG files and animated images are excluded; convert an unsupported format to a supported static raster format before trying again.
  2. Prepare the framing. If the subject is off-center, crop it in advance. Do not expect the generator to reposition the subject after its center-cover crop.
  3. Select the square sizes you need. Choose from 16, 32, 48, 64, 128, 256, and 512 pixels. Select only the files you intend to place on the site; the generated markup should match the assets you publish.
  4. Generate the favicon files. The source is decoded and processed in the current browser tab. Every selected size is rendered from the decoded source independently and exported as a PNG.
  5. Inspect and download each result. Open the 16-pixel and 32-pixel files at 100 percent zoom, where possible, and confirm that the subject is recognizable. Download each icon separately. For transparent or pale edges, also check the appearance against both light and dark backgrounds.
  6. Place the PNG files and copy their links. Upload only the chosen PNGs through your normal hosting process. Put them at the matching root paths, or adjust each href to your real asset directory, and copy the corresponding link lines into the document head. The generator itself does not upload files or edit your site.
  7. Verify the deployed page. Check the page source and network paths for the PNG requests. If an old icon remains visible after a correct deployment, clear site data or browser caches and check again.

A generated 32-pixel link follows this structure: <link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">. The root-relative path assumes the PNG sits at the site's root. If it lives in an asset folder, change the href to that file's actual root-relative location.

Copy only the lines for files that are present on the server. Multiple icon links let a browser choose an appropriate resource, but the final choice remains browser behavior. The tool cannot guarantee which linked icon a particular browser, bookmark surface, or operating system will display. The MDN rel icon reference provides the broader HTML relationship reference.

The markup and assets form a matched set: the type identifies PNG, the sizes attribute states the exact square dimensions, and the href points to the corresponding generated filename. Keep those three parts synchronized when moving files.

Diagnose soft, cropped, or stale icons

Small icons can look soft because the browser smooths pixels during resizing. Thin lines, tiny lettering, and complex edges can lose definition even when the source is sharp. This is why the 16- and 32-pixel downloads deserve an actual-size inspection; a large preview cannot reveal every problem.

A cropped result usually points to the source composition rather than a broken download. Recheck which sides the center-cover rule removes, then start with a more centered, high-contrast source or crop the subject in advance. The generator does not add transparency, remove a background automatically, or rescue detail that is absent from the source.

Transparency is retained when it already exists in a PNG or WebP source, while a JPEG begins without transparent pixels. Review pale or transparent edges on light and dark backgrounds. If a deployed site still shows the previous icon, verify the PNG path and HTML source first, then clear site data or browser caches.

Know the format boundary

This workflow creates PNG browser favicons and matching HTML icon links only. It does not create an ICO container, SVG icon, Apple touch icon, Android icon set, pinned-tab asset, web app manifest, or platform-specific package. Those formats need a different asset-and-markup workflow.

Static raster input is intentional. Animated WebP and other animated inputs are excluded because frame selection would be ambiguous, and SVG is excluded rather than interpreted as scriptable vector content. The result is a deliberately simple set of exact-size PNG icons, not a universal package for every place an icon may appear.

Privacy and processing limits

Image decoding, center cropping, Canvas resizing, and PNG creation all happen in the current browser tab. The source image is not sent to a processing server, which means the tool can prepare favicon files without uploading the original to that workflow.

Two input checks matter. The selected file can be up to 25 MB, and an image above 40 million pixels is rejected after the browser decodes it but before output canvases are allocated. Compressed file size does not fully describe decode memory, so an unusually large or malformed image can still consume memory or fail during its initial decode. The generator prepares assets and markup; it does not modify your website, upload files, or confirm production cache behavior.

If you're weighing options, Invert Image Colors for Instagram: Local PNG Workflow covers this in detail.

If you're weighing options, Crop Image Free, No Sign-Up: Get a Lossless PNG covers this in detail.