creatorvalet
Files Convert, compress and reshape files — without uploading them anywhere. Metadata See what your files quietly carry, then strip exactly what you choose. Text & data Formatters, converters, and the character-encoding fixes nobody else gets right. Publishing Check how your pages read to crawlers, to people, and to language models. Codes Barcodes, QR and identifiers that keep working after you publish them. Characters Find the character you can draw but cannot name — and the font you cannot place.

Favicon generator

Turn one image or SVG into a complete local favicon package, with real-size previews before you download the ZIP.

  • SECURE
  • NO UPLOADS
  • NO SIGNUP
  • BROWSER BASED
  • FREE
  • FOREVER.

Support us with a link or a share

Drop an image or SVG here

or paste Ctrl+V

PNG, JPEG, WebP, GIF, AVIF or SVG. The source is decoded and rendered in this tab — never uploaded.

What this favicon generator builds from one source

A favicon is no longer one sixteen-pixel file. A browser tab, a saved bookmark, an iPhone Home Screen shortcut, an installed web app and a search result can all ask for different declarations and different pixel sizes. This generator turns one raster image or SVG into a package for those surfaces: a multi-image favicon.ico, three browser PNGs, an Apple Touch Icon, two ordinary web-app icons, a separate maskable icon, a web manifest, copy-ready HTML and a short installation note. The ZIP is assembled only after every PNG and the ICO directory have been read back and checked in this browser.

The narrow PNG to ICO converter remains useful when an existing project asks for one Windows-style container and nothing else. This page solves the broader publishing task. It deliberately does not make a dozen near-identical conversion routes or pretend that one 512-pixel PNG is the same thing as a complete favicon setup.

Small previews matter more than a large logo preview

A logo that looks immaculate at 512 pixels can turn into an unrecognizable fleck at sixteen. Thin strokes disappear, counters in letters close, and several colors merge into one dark patch. That is why the receipt shows the real sixteen- and thirty-two-pixel images at actual CSS size. The larger Apple and installed-app cards answer a different question: whether the source still feels centered and intentional when an operating system gives it a tile.

The browser PNG at 96 × 96 is also intentional. Google’s current favicon guidance requires a square image of at least 8 × 8 and recommends a source larger than 48 × 48. A generated file can satisfy that technical size rule, but it cannot prove that Googlebot can crawl the home page, that a cached result has refreshed, or that Google will select the file. Those are publishing and crawler questions, not image-generation questions. The favicon checker keeps those boundaries visible after the files are deployed.

Contain, crop and padding are different decisions

Contain keeps the complete source and scales it until both edges fit inside the square. A wide wordmark therefore gets empty space above and below it. Center crop fills the square by removing equal amounts from opposite edges; it works when the subject is centered and the outside area is disposable. Neither operation is hidden. Padding then scales the resulting artwork inward by the exact percentage shown beside the control, whether the source began square or rectangular.

Regular browser and Apple files may keep transparency, because a transparent mark can sit cleanly in light and dark interfaces. The ordinary web-app files follow that same choice. Maskable icons have a stricter job. The Web App Manifest specification allows a platform to apply circles, squircles and other masks, and guarantees only a centered circle whose radius is 40 percent of the icon size. The separate maskable PNG therefore uses a solid background and fits the complete rendered mark inside that circle. It can look smaller than the ordinary 512-pixel file; that difference is the protection, not a rendering mistake.

The package files and where they go

Copy the generated files into the public root of the site, then paste the generated link declarations inside the home page’s <head>. The snippet names each browser PNG with its real size, names the ICO with all three sizes in its directory, points Apple to its 180-pixel file and links the web manifest. If the site is intentionally hosted below a path rather than at the hostname root, edit the leading slashes in both the snippet and the manifest before publishing.

The manifest includes the site or app name, short name, theme and background colors, and separate any and maskable icon declarations. It does not invent a service worker or claim that the site is installable. Installation behavior depends on the rest of the application, the browser and its current criteria. The file describes the icon resources honestly; it does not manufacture capabilities the generator cannot inspect.

What is preserved, changed and omitted

The image pixels are decoded, centered according to the selected fit, scaled and encoded as fresh PNG streams. Camera metadata, editing history, color-profile attachments and the source filename do not travel into those canvases. Animation is reduced to the frame the browser decodes for drawing. SVG input is parsed and sanitized before rendering: scripts, event handlers, embedded documents, animation elements and external resource references are removed, so an SVG that depends on remote fonts or CSS can look different. The generator reports that sanitization rather than silently packaging active markup.

If a raster source is smaller than 512 pixels, the largest outputs are enlargements. They remain correctly sized files, but they cannot acquire detail that was absent from the source. Start with a larger mark or simplify the artwork when that warning appears. If the original is unnecessarily enormous, the image compressor can make a separate delivery image, but compressing the source is not required here: favicon output is always rendered to small fixed dimensions.

Local generation, with a way to verify it

The source file never goes to a CreatorValet upload endpoint. Decoding, canvas rendering, ICO assembly and ZIP creation happen inside the open tab. Very large inputs can still use a great deal of local memory, so the page gives the shared size warning before reading them and lets the user decide whether to continue. It does not reject an image merely because it is large. The local-processing verification guide explains what the browser’s Network panel can and cannot prove about that claim.

After publishing, run the checker on the exact hostname home page. If the site already has icon files that should be preserved before replacement, use the favicon downloader first. For a compact textual copy of a generated PNG during development, the image to Base64 tool is available, though normal public favicon files should remain stable URLs so browsers and search crawlers can cache and revisit them.

Standards used for the generated defaults

The link markup follows the HTML Standard’s icon relation. Search sizing and home-page placement follow Google Search Central’s favicon documentation. The 180-pixel touch file follows Apple’s archived web application configuration guide. The purposes and safe-zone geometry follow the Web Application Manifest specification. Defaults can age; the generated receipt makes every size and declaration explicit so they can be reviewed rather than trusted as an invisible preset.

Questions

What files does the favicon generator create?

The ZIP contains a multi-size favicon.ico; 16, 32 and 96 pixel browser PNGs; a 180 pixel Apple Touch Icon; 192 and 512 pixel web-app icons; a separate 512 pixel maskable icon; site.webmanifest; copy-ready HTML; and a short installation README. The preview and receipt report the real bytes produced in your browser.

Should I crop my logo or add padding?

Contain keeps the complete source and fits it inside the square; crop fills the square by removing equal amounts from opposite edges. Padding then scales the visible artwork inward by the exact percentage you choose. Check the sixteen-pixel preview before shipping: fine type and thin detail often disappear even when the large icon looks clean.

Why is the maskable icon different?

A platform may cut a maskable icon into a circle, squircle or rounded square. The manifest specification guarantees only a centered circle with a radius of 40 percent of the icon size. This generator places the complete source artwork inside that circle and fills the outer area with your chosen solid background, so no important source pixels need to be cut away.

Can Google still choose a different favicon?

Yes. The package creates a square 96 pixel browser PNG, which is above Google Search’s current larger-than-48-pixel recommendation, but a file cannot prove crawler access, policy eligibility, cache state or eventual selection. Publish the files at stable URLs, put the link tags on the hostname home page, and then use the favicon checker for the source-visible rules.

Can I use an SVG as the source?

Yes. Choose an SVG file or paste SVG markup and the browser rasterizes it locally into each required PNG and ICO size. The ZIP does not silently copy the source SVG: all generated surface files match the crop, padding and background choices shown in the previews.

Is my logo uploaded?

No. The source is decoded, squared, resized, PNG-encoded and packed into ZIP entirely in this browser tab. There is no upload request and no account. Very large source files can consume substantial tab memory, so the tool warns before reading them but never rejects them merely for size.