Favicon Generator

Turn any square image into a full set of website favicons in seconds.

For best results use a square image at least 512×512px.

Your images are processed entirely in your browser and never uploaded to a server.

Free to use — premium coming soon

FREE
  • Unlimited use
  • No watermark
  • 100% private
PREMIUM
  • Remove ads
  • Larger batches & presets

About the Favicon Generator

The Favicon Generator turns a single source image into the full set of icon files a website needs to look correct in browser tabs, bookmarks, and on mobile home screens. Instead of manually resizing one graphic over and over in an image editor, you upload one square picture (a logo, monogram, or symbol) and get back the standard sizes browsers and operating systems expect: a 16x16 and 32x32 for desktop tabs, a 180x180 apple-touch-icon for iOS, and 192x192 plus 512x512 PNGs for Android and Progressive Web App installs. The tool also gives you the exact HTML link tags to paste into your page head.

Reach for this tool whenever you ship a new site, rebrand, or notice your tab showing a blank document icon or a stretched logo. A favicon is the smallest piece of branding you control, but it shows up everywhere a user keeps your site: pinned tabs, history, bookmark bars, search suggestions, and the home screen if someone saves your site as an app. Getting the sizes right matters because each platform pulls from a different file. Desktop browsers prefer the small 16/32 icons, iOS Safari uses the 180x180 apple-touch-icon, and Android and PWA install prompts read 192 and 512 icons listed in a web manifest.

Under the hood the generator scales your source image down to each required dimension and exports them as PNG, plus a multi-resolution favicon.ico that bundles the small browser sizes. For the sharpest result you should start with a square image at least 512x512 pixels so the largest icon is not upscaled, and keep the design simple: fine detail and small text turn to mush at 16x16. The tool then assembles the matching link tags and a minimal site.webmanifest snippet so the icons are wired up correctly rather than left as orphaned files in your project.

This generator runs entirely in your browser, so your image is processed on your own device and never uploaded to a server. That keeps unreleased logos and brand assets private, and it means there is nothing to store or expire on our end. Accuracy note: the pixel dimensions and the HTML this tool outputs follow the long-standing conventions browsers and OS vendors document (16/32 for tabs, 180 for Apple, 192/512 for Android/PWA). Rendering can still vary slightly between browser versions, so always preview your favicon in a real tab and on a phone after deploying.

Frequently asked questions

What favicon sizes do I actually need?

For broad coverage use 16x16 and 32x32 for desktop browser tabs (bundled in a favicon.ico), 180x180 for the Apple touch icon on iOS, and 192x192 plus 512x512 PNGs for Android home screens and PWA install prompts. A 48x48 is sometimes added inside the .ico for Windows.

What is an apple-touch-icon and why is it 180x180?

It is the icon iOS uses when someone adds your site to their iPhone or iPad home screen. 180x180 is the size Apple's highest-resolution devices request, and iOS downscales that single file for smaller screens, so providing one 180x180 PNG covers current devices.

How do I add the favicon to my HTML?

Place the generated files in your site root and add these to the <head>: <link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">, <link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png">, <link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">, and <link rel="manifest" href="/site.webmanifest">. The 192 and 512 PNGs are referenced from inside the manifest.

Do I still need a favicon.ico file?

It is no longer strictly required since modern browsers read PNG and SVG icons, but a favicon.ico at the site root is the universal fallback that older browsers and some tools request by default. Keeping one 32x32 (or multi-size) .ico avoids occasional blank-icon requests.

My favicon does not update after I changed it. Why?

Browsers cache favicons aggressively. Hard-refresh the page, clear the site cache, or load the icon URL directly to confirm it deployed, then revisit the page. Bumping the filename or adding a query string like favicon.ico?v=2 forces a fresh fetch.

From our blog

Blur vs. Redact: How to Hide Sensitive Information in an Image Without Leaking It

By the Super Simple Digital Tools Team · Updated June 2026

Most people blur a photo by instinct: there is a face, a plate, or an account number they would rather not broadcast, so they smear it and hit share. That instinct is right, but the execution often is not. Blurring and pixelation look final to the eye while quietly preserving a mathematical trace of what was underneath, and a growing set of tools can read that trace back out. Understanding the difference between hiding something visually and removing it permanently is the whole game when you are protecting real secrets.

Here is why blur leaks. A blur replaces each pixel with a weighted average of its neighbors; pixelation replaces a square block of pixels with one averaged color. Neither throws information away cleanly. Researchers at Bishop Fox demonstrated this with Unredacter, an improvement on the earlier Depix tool: it walks through possible characters, renders each in the same font and size, pixelates that guess, and compares it to the redacted area until the math lines up. Short, predictable strings such as card numbers, dates, or check fields are the easiest to recover because there are so few plausible permutations.

That does not make blur useless. For low-stakes clutter, blur is perfectly reasonable: a stranger's face in the background of a vacation photo, a street sign, a messy desk behind your video call, or a neighbor's car in a real-estate listing. The goal there is courtesy and reducing incidental identifiability, not defeating a determined attacker with a depixelation script. A strong Gaussian blur of 30 pixels or more, or a coarse pixelation, comfortably handles those cases and keeps the picture looking natural.

When the content actually matters, switch tactics. Passwords, government ID numbers, bank details, API keys, signatures, and anything you would be harmed by losing should be covered with a solid, opaque block, not a blur. A solid mask leaves no averaged pixels to reconstruct, which is why every redaction guide lands on the same advice: black bars, nothing fancier. Draw the block generously so it overhangs the text on every side; partial letters or a stray digit poking out can be enough for a reconstruction tool, or a sharp-eyed human, to fill in the rest.

Finally, mind the export and the original. Because this tool processes images in your browser, your file stays on your device, but you still need to save the flattened output, the version with the obscuring baked into the pixels, and share only that. Never send the unedited original, and remember that screenshots of formatted documents can hide text under matching colors that copies right back out. Blur for tidiness, mask for secrets, double-check the exported file, and you will share photos without sharing what you meant to keep.

  • For passwords, ID numbers, or card details, choose the solid-block mode, not blur or pixelate, then make the block extend past the text on all four sides.
  • When blurring faces or license plates for privacy, push the blur strength to 30 pixels or higher so no feature or character stays legible.
  • Always export and share the flattened PNG or JPEG, and keep the unedited original off-line so you never accidentally post the version without redactions.
  • Zoom in before exporting and check that no partial letters, digits, or reflections peek out from the edges of the blurred or masked region.

Read the full guide →

Tool by the Super Simple Digital Tools Team. Reviewed by our editorial team. Free to use, no signup required.

Related tools