Do I still need a .ico file?

Modern browsers prefer PNG favicons referenced via . .ico is only needed if you have to support very old browsers.

favicon · pwa · manifest · local

Generate every favicon from one source

Produce 16, 32, 48, 96, 192, 512, and apple-touch-icon PNGs plus a ready-to-paste webmanifest and head snippet. Runs locally.

Favicon Generator

Source

—

no file

Sizes

PNG

Manifest

.webmanifest

Outputs

—

ready

input · image

image/* · runs locally · nothing uploaded

output · preview

Favicons appear here

Quick Start

How it works

Pick an image, tune the options, then download the result. Everything runs in your browser.

01
Upload a source
A square 512×512 master gives the cleanest output at every target size. Smaller sources upscale poorly — the 512 and 192 outputs will look soft.
Vector shapes? Export your SVG as a high-resolution PNG (Inkscape or Figma) before dropping it in. The browser does not rasterise SVG into canvases natively in every codec path.
512×512square masterPNGvector
input · master512×512
```
logo.png · 512 × 512
```
loadedready
02
Auto-scale every size
One source, seven outputs: 16×16, 32×32, 48×48, 96×96, 192×192, 512×512 PNGs plus the 180×180 apple-touch-icon.png for iOS home-screen pins.
The browser uses high-quality smoothing (imageSmoothingQuality = "high") for every drawImage downscale so small sizes stay legible.
16×1632×3264×64apple-touch-icon
config · sizes7 outputs
```
drawImage(img, 0, 0, s, s)
imageSmoothingQuality = "high"
```
rasterisedhigh-quality
03
Grab the snippets
Copy the generated site.webmanifest (PWA-ready, listing all icon sizes) and the matching <link rel="icon"> HTML head snippet — including the apple-touch-icon link iOS Safari requires.
An .ico file is no longer strictly necessary; modern browsers prefer PNG, but pair with a PNG→ICO tool if you need Windows legacy support.
icosite.webmanifestapple-touch-iconPWA
config · snippetshead + json
```
<link rel="icon" sizes="32x32" …>
<link rel="apple-touch-icon" …>
<link rel="manifest" …>
```
copiedPWA-ready
04
Drop into /public
Put every PNG at the root of /public, save site.webmanifest alongside, paste the head snippet into your layout, and deploy. The whole pack downloads as a batch with one click.
Source decoding and resizing happen locally — nothing is uploaded.
/publicdeploybatch downloadprivacy-first
export · favicon packready
```
✓ Downloaded 7 PNGs
✓ Saved: site.webmanifest
✓ 100% client-side
```
ready to shipsuccess

Pro tips

Browser-only image work that scales

Convert with quality control

JPEG/WebP let you pick a 0–1 quality. Default 0.92 is a good compromise of size and visible quality.

PNG isn’t free

Use PNG only for transparency or sharp edges. For photos, WebP is smaller at the same perceived quality.

Strip EXIF for privacy

Photo EXIF often contains GPS, camera model, and timestamps. Strip before sharing public uploads.

Watch the colour profile

Convert to sRGB before web export. Wide-gamut images render oversaturated in non-managed browsers.

AVIF when it’s available

AVIF beats WebP on size at the same quality. Detect support via <picture> with fallbacks.

Lazy-load below the fold

Add loading="lazy" on <img>. The browser handles scheduling — no IntersectionObserver needed.

Use Cases

When to use this tool

Common workflows it speeds up.

New site bootstrap

One drop, every browser tab covered. Decoded into a Canvas 2D context — original bytes never leave the tab, so you can process customer-uploaded photos, internal screenshots, or sensitive diagrams without privacy concerns.

px-perfect

Rebrands

Swap the source and re-generate the full pack. Encoders expose quality 0–1 where the format supports it (JPEG, WebP); PNG and AVIF stay perceptually lossless. Pick 0.85 for web, 0.95 for archival, 0.7 for thumbnails.

quality-tunable

PWAs

Includes the 192 and 512 sizes manifest needs. Pair with the EXIF Stripper before sharing user-uploaded photos publicly. Camera serial numbers, GPS coordinates, and timestamps often hide in image metadata and leak more than the picture itself.

format-aware

Static sites

Drop the snippet into Hugo, Jekyll, Astro. Output preserves colour profile (sRGB) so it renders consistently across browsers, monitors, and print pipelines. Wide-gamut workflows can opt into Display P3 for modern Apple devices.

EXIF-safe

Dev portals

Distinct favicons for staging vs prod. Re-runs only on option changes, never on window resize, so the canvas stays responsive on large images. drawImage uses the browser's bilinear filter for fast resampling.

client-side

Multi-tenant apps

Per-customer favicons from one pipeline. Downloads as .png, .jpg, .webp, or .avif with the correct MIME so editors apply native handling on save. The filename inherits a sensible suffix derived from the input.

compression-ready

FAQ

Frequently asked questions

What source size should I use?

512×512 or larger. Smaller sources upscale poorly at the 512 size.

Do I still need favicon.ico?

Modern browsers prefer PNG, but pair with the PNG to ICO tool if you need legacy Windows support.

What's apple-touch-icon for?

iOS uses it when you save the page to the home screen. 180×180 is the recommended size.

Are the icons square?

Yes — every output square crops the source. Crop in a separate tool first if you need padding.

Is anything uploaded?

No. The source image is read by FileReader and resized in your browser — nothing leaves the device.

Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

47 in queue·8 shipped this month

Request queued. Thanks!