Initializing... drag & drop files here
Supports: JPG, JPEG, JFIF
.ico — no sign-up, no watermark. Rename to favicon.ico and drop into your site root.ICO is the icon container Microsoft built for Windows in 1985, and it is still the format every browser will look for at /favicon.ico before parsing any HTML link tags. A single ICO file can hold multiple square images at different sizes and color depths, so the browser or operating system picks the entry that best matches its display context. Common reasons to convert JPG → ICO:
/favicon.ico) — Chrome, Firefox, Edge, and Safari all request /favicon.ico from the site root before reading <link rel="icon"> tags. An ICO containing 16×16 and 32×32 layers is still the most compatible single-file fallback in 2026..lnk shortcut → Properties → Change Icon — Windows expects an .ico file. JPGs and PNGs are not accepted in the icon picker.desktop.ini references a custom folder icon by .ico path. Convert a JPG cover image to ICO to brand project folders..exe builds (Inno Setup, NSIS) require an ICO with multiple sizes for the taskbar, start menu, and high-DPI displays./favicon.ico for the bookmarks bar, history list, and (on desktop) browser tabs. A 16×16 layer in the ICO renders crisply at standard DPI..ico for icon resources; PNG and SVG support is recent and uneven.| Context | Recommended size(s) | Best format |
|---|---|---|
| Browser tab (standard DPI) | 16×16 | ICO or PNG |
| Browser tab (HiDPI / Retina) | 32×32 | ICO or PNG |
| Windows taskbar / pinned site | 32×32, 48×48 | ICO |
| Windows desktop shortcut, Explorer large icons | 48×48, 256×256 | ICO |
| Apple touch icon (iOS home screen since iOS 8) | 180×180 | PNG |
| Android Chrome home screen | 192×192 | PNG (manifest) |
| PWA install / splash | 512×512 | PNG (manifest) |
| SVG-capable browsers | any (vector) | SVG |
The practical 2026 minimum for favicon.ico is a single multi-size ICO containing 16×16 and 32×32. Add a 48×48 layer if you want crisp Windows site-pinning. Anything beyond 48×48 is better served by PNGs referenced from <link rel="icon" sizes="..."> and an Apple touch icon and web app manifest.
| Property | ICO | PNG | SVG |
|---|---|---|---|
| Multi-size in one file | Yes (up to 256 entries) | No (one per file) | N/A (vector scales) |
| Transparency | Yes (32-bit, since Windows XP) | Yes (8-bit alpha) | Yes |
| Max image size per entry | 256×256 (PNG-embedded since Vista) | Unbounded | Unbounded |
| Color depth | 1, 4, 8, 24, 32-bit | 1-16 bits/channel | Vector |
| Browser support as favicon | Universal incl. legacy IE | Modern browsers (Edge, Chrome, Firefox, Safari 9+) | Chrome 80+, Firefox 41+, Safari 13.1+ (per caniuse) |
Required at /favicon.ico |
Yes, browsers fetch it by default | No | No |
ICO is a Microsoft container, not a codec. Each entry inside an ICO is either a BMP image (with separate XOR color mask and AND transparency mask for legacy formats) or, since Windows Vista, an embedded PNG. Microsoft recommends PNG-embedded entries for any 256×256 layer to keep the file size reasonable — uncompressed 256×256 32-bit BMP is ~256 KB, the same image as PNG is typically under 30 KB. Per the ICO specification, a single file's idCount header holds up to 65,535 directory entries, though real-world favicons rarely exceed 6 sizes.
256×256 pixels per entry. This cap was set when Windows Vista added 256×256 32-bit color support and PNG-compressed entries. You can technically store a larger PNG inside the container, but Windows Explorer, File Explorer, and every mainstream browser will not render entries above 256×256 — they fall back to the next-largest valid size.
No. A minimal modern favicon.ico needs 16×16 and 32×32. Add 48×48 if you care about Windows pinned-site rendering. Sizes 64, 96, and 128 are rarely picked by any browser or OS — they bloat the file without improving the rendered icon. Use PNGs (Apple touch 180, Android 192/512) for the larger contexts.
No — JPG has no alpha channel, so the converted ICO will carry an opaque background matching the JPG's pixels. If you need a transparent favicon, start from a PNG with transparency: PNG to ICO. Alternatively, edit the JPG in Photopea, Photoshop, or GIMP to knock out the background, export as PNG, then convert.
Place the file at the document root so it resolves at https://yoursite.com/favicon.ico. Browsers fetch this path automatically. To be explicit, also add <link rel="icon" type="image/x-icon" href="/favicon.ico"> to the <head>. For modern setups, add 32×32 and 192×192 PNG <link> tags plus an apple-touch-icon 180×180.
JPG sources are usually downscaled from a much larger photo. At 16×16, fine detail and gradients collapse into a smear. Two fixes: (1) start from a clean square source at least 256×256, and (2) hand-design the 16×16 and 32×32 layers in an icon editor rather than rely on auto-downscaling — small icons benefit from manual anti-aliasing and reduced detail.
.jpg?Yes. JPG, JPEG, and JFIF are the same JPEG-format bytes with different file extensions — the converter treats them identically. Drop in any mix and they all encode to ICO.
Yes, as long as the ICO contains 32×32 and 48×48 layers (and ideally 256×256 for high-DPI "Extra large" Explorer views). Right-click a shortcut → Properties → Change Icon, browse to your .ico, and Windows reads the appropriate entry per context.
PNG-as-favicon works in every browser released after roughly 2010, but browsers still request /favicon.ico from the root automatically — without an ICO there, they will log a 404 and fall back. The robust modern setup is both: a small multi-size ICO at /favicon.ico plus 32×32 and 192×192 PNGs referenced via <link> tags. If you only want PNG, try JPG to PNG first, or go the other direction with ICO to PNG.
Yes. Drop in a folder; each file becomes its own ICO with the same settings. Useful when you maintain icons for multiple Windows shortcuts, side-project favicons, or a documentation site with per-section icons. Downloads come individually or as a single ZIP.