JPEG to ICO Converter

How to Convert JPEG to ICO Online

1. Upload Your JPEG Files: Drag and drop or click "Add Files" to select JPEG, JPG, or JFIF images — all three extensions hold the same JPEG bytes. Square sources work best because Windows expects square icons; nothing is cropped or padded here, so a non-square photo produces a non-square icon. Batch is supported.
2. Pick an Image Resolution Preset: The Preset dropdown under Image resolution is the only sizing mode on an ICO target — 256P, 192P, 180P, 128P, 64P, 48P, 32P, 24P and 16P. The percentage, "Keep original" and custom width/height modes are hidden here. 256×256 is the maximum size a single ICO entry can hold and is the standard Windows large-icon layer since Windows Vista.
3. Check the Shape Before Converting (Optional): There is no quality preset, colour palette or bit-depth control on this page — the Image Compression group is hidden for ICO output entirely. The preset sets the icon's height and the width follows your photo's aspect ratio, so a 3:2 JPEG at 256P comes out 384×256, wider than the 256 an ICO directory entry can declare. Crop to 1:1 first, or pick 128P.
4. Convert and Download: Click Convert. Files process on our servers and download as .ico — no sign-up, no watermark. Rename to favicon.ico and drop into your site root.

Why Convert JPEG to ICO?

ICO is the icon container Microsoft built for Windows in 1985, and it is still the format every desktop browser will request at /favicon.ico from the site root before parsing any HTML <link> tags. A single ICO file holds multiple square images at different sizes and color depths, so the browser or operating system picks the entry that best matches its display context. The ".jpeg" extension is identical to ".jpg" — same JPEG bytes, just the older three- vs four-letter spelling — so any JPEG photo, logo, or scanned mark is a valid input. Common reasons to convert JPEG → ICO:

• Website favicon (/favicon.ico) — Chrome, Firefox, Edge, and Safari all auto-fetch /favicon.ico from the root before reading <link rel="icon"> tags. A multi-size ICO containing 16×16, 32×32, and 48×48 layers remains the most compatible single-file fallback in 2026.
• Windows desktop shortcut icon — Right-click a .lnk shortcut → Properties → Change Icon — Windows expects an .ico file. JPEGs and PNGs are not selectable in the Change Icon picker.
• Windows Explorer folder customization — A desktop.ini file references a custom folder icon by .ico path. Convert a JPEG cover image to ICO to brand project folders or external drives.
• Custom application icons — Electron, NW.js, and packaged .exe builds (Inno Setup, NSIS, WiX) require an ICO carrying multiple sizes for the taskbar, start menu, and high-DPI displays.
• Bookmarks and browser history — Browsers reuse the favicon for the bookmarks bar, history list, and (on desktop) the active tab. A crisp 16×16 layer in the ICO is what most users actually see all day.
• Legacy software compatibility — Older Win32 tools, IDEs, and installers only accept .ico for icon resources; PNG and SVG support in those toolchains is recent and uneven.

Favicon and Icon Size Cheat Sheet (2026)

The practical 2026 minimum for favicon.ico is a single multi-size ICO containing 16×16, 32×32, and 48×48. Anything beyond 48×48 is better served by PNGs referenced from <link rel="icon" sizes="...">, plus an Apple touch icon (180×180) and a web app manifest with 192 and 512 PNG entries.

ICO vs PNG vs SVG for Favicons

ICO Container Quick Facts

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 — an uncompressed 256×256 32-bit BMP is ~256 KB while the same image as PNG is typically under 30 KB. Per the ICO specification the directory header can address up to 65,535 entries, though real-world favicons rarely exceed 6 sizes. Because JPEG has no alpha channel, the ICO produced from a JPEG carries an opaque background sampled from the JPEG's pixels — there is no transparent favicon path from a JPEG source.

Frequently Asked Questions

Is.jpeg the same as.jpg for this converter?

Yes. JPEG, JPG, and JFIF are the same JPEG-format bytes — the three-letter .jpg extension is a holdover from DOS/Windows 3.x 8.3 filenames; .jpeg is the original four-letter form. The converter accepts all three extensions and treats them identically. You can also drop in a mix and they all encode to ICO with the same settings.

What is the maximum size of an ICO icon?

256×256 pixels per entry. This cap was set when Windows Vista added 256×256 32-bit color support and PNG-compressed entries to the ICO container. You can technically store a larger PNG inside the file, 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.

Should I include every size from 16 to 256 in my ICO?

No. A minimal modern favicon.ico needs 16×16, 32×32, and 48×48. Drop in 256×256 if you want crisp Windows "Extra large" Explorer 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.

Will my JPEG favicon have a transparent background?

No — JPEG has no alpha channel, so the converted ICO carries an opaque background matching the JPEG's pixels. If you need a transparent favicon, start from a PNG with transparency: see PNG to ICO. Alternatively, edit the JPEG in Photopea, Photoshop, or GIMP to knock out the background and re-export as PNG before converting.

How do I install the favicon.ico on my website?

Place the file at the document root so it resolves at https://yoursite.com/favicon.ico. Browsers fetch this path automatically. For explicit control, also add <link rel="icon" type="image/x-icon" href="/favicon.ico"> to the <head>. For a modern setup, add 32×32 and 192×192 PNG <link> tags plus an apple-touch-icon 180×180.

Why is my icon blurry at 16×16?

JPEGs are usually downscaled photographs with fine detail and soft gradients. At 16×16, all of that detail collapses into a smear. Two fixes: (1) start from a clean square source at least 256×256, ideally a flat logo not a photo, and (2) hand-tune 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 shape detail.

Can I convert JPEG to ICO for Windows desktop and taskbar shortcuts?

Yes. The resulting ICO works for Windows shortcuts as long as it contains 32×32 and 48×48 layers (and ideally 256×256 for high-DPI "Extra large" Explorer views). Right-click any shortcut → Properties → Change Icon, browse to your .ico, and Windows reads the appropriate entry per context.

How does JPEG → ICO compare to JPEG → PNG for a favicon?

PNG-as-favicon works in every browser released after roughly 2010, but browsers still automatically request /favicon.ico from the root — without an ICO there, they 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. For the reverse direction (extracting PNGs from an ICO) use ICO to PNG.

Can I batch-convert many JPEGs to ICOs at once?

Yes. Drop a folder of JPEGs into the uploader; 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. For the .jpg extension specifically, the JPG to ICO page is identical — same engine, same options.