Skip to main content

WebP to ICO converter

Convert WEBP images to ICO format

No watermarkFree & unlimited
All processing happens in your browser. No data is sent to any server.

Site assets increasingly ship as WebP, which leaves one awkward gap: the favicon a browser still requests at /favicon.ico. This page closes it. Your WebP is drawn into a 32-pixel square canvas and written out as a single-entry icon in uncompressed 32-bit form, alpha byte included, so a logo with transparent surroundings stays transparent in the tab bar. Because the geometry is fixed there are no options to set - no quality slider, no resize presets - and every file that comes out is the same length.

Key facts about WebP to ICO converter

Key facts about WebP to ICO converter
What is writtenOne icon entry, 32 by 32 pixels, stored as an uncompressed bottom-up DIB with four bytes per pixel.
Constant size4,158 bytes for every conversion - 4,096 bytes of pixels plus 62 bytes across the directory, entry and DIB headers.
AlphaPreserved from the WebP, which is the main reason to start from one: transparent corners and anti-aliased edges carry through.
DownscaleA single smoothed draw into the small canvas, so fine strokes blur together rather than being redrawn for the size.
ProportionsNot maintained - a rectangular source is squeezed into the square, so crop to 1:1 before converting.
AnimationAn animated WebP yields its first frame; the icon format holds a still image only.
Entries omittedNo 16x16, 48x48 or 256x256 image is included, so systems wanting a larger icon will enlarge this one.
Icon flavourThe classic uncompressed variant rather than the PNG-in-ICO form, which keeps older Windows tooling happy.
Where it is usedThe default /favicon.ico request, Windows shortcuts and application icons, and installers that require an .ico path.

What happens to your file

Everything is assembled locally: the browser decodes the WebP, a 32-pixel canvas takes the scaled image, getImageData returns the RGBA values, and the page writes the icon directory, the entry record and the bottom-up BGRA pixel block into an ArrayBuffer before wrapping it in a Blob typed image/x-icon. No favicon generator sees your artwork, and the only thing your browser fetches during the process is nothing at all.

About this tool

  1. 1

    Square the artwork first

    Crop the WebP to equal width and height in any editor, since the conversion stretches rather than crops.

  2. 2

    Drop it on the page

    A blue panel confirms the fixed 32x32 output before you convert; the usual image options are hidden because none of them apply.

  3. 3

    Convert

    The scale and the icon assembly complete almost instantly, regardless of the source resolution.

  4. 4

    Publish it

    Rename the file to favicon.ico at your site root, or reference it from a link rel=icon tag in the page head.

Specs & compatibility
Input and outputTakes .webp only (image/webp) and returns .ico with the image/x-icon type; any other extension is refused before decoding.
Conversion pathWEBP to ICO runs in three steps: an <img> element decodes the WebP and passes frame one to the canvas; the pixels land on a 2D canvas in this tab; then the canvas is redrawn at 32x32 and an icon writer in the page emits the directory and the DIB.
Browser supportThe WebP side needs Chrome 32, Firefox 65, Edge 18 or Safari 14 to decode, while writing the ICO needs nothing from the browser, the icon being assembled in the page.
Controls for this pairNo quality slider and no resize presets: WEBP to ICO is pinned to 32x32 pixels, which the page says above the convert button.
Batch, caps and namingTwenty WEBP files per run at 500 MB each; one result downloads as a single ICO, several as converted-ico-files.zip, zipped by JSZip 3.10 in page memory.
Device ceilingThe canvas caps it: past roughly 16,384 px a side Chromium refuses the bitmap and iPhone Safari gives up sooner, so an oversized WEBP fails before any ICO bytes exist.
  • Preview the icon on both light and dark browser themes - a mark that depends on a light background vanishes in dark tab bars.
  • Simplify before you shrink: at 32 pixels a wordmark becomes a smudge, while a single letter or symbol stays legible.
  • Many sites need only a PNG plus a manifest entry these days, so confirm an .ico is actually required before adding one.
  • If the icon does not update in the browser, clear the favicon cache or open a private window - the file itself changes with every conversion.
  • Producing the legacy favicon.ico for a site whose graphics are already stored as WebP.
  • Creating a Windows shortcut or application icon from an existing web asset.
  • Generating an icon for an internal dashboard without sending the brand mark to a third-party service.
Yes. Pixels are stored as 32-bit BGRA and the alpha byte is copied directly from the canvas, so transparent and partially transparent areas survive. That makes a WebP with alpha a much better icon source than a JPEG, which arrives opaque and produces a solid square.
No. The output is always 32 by 32, and the resize presets are hidden on this page because the dimension is fixed in the encoder. It is the size browsers and Windows request most commonly, and it downsamples acceptably to 16 pixels when a system needs the smaller variant.
Because an uncompressed icon of fixed dimensions has a fixed length: 32 times 32 pixels at four bytes each is 4,096 bytes, and the icon directory, the entry record and the DIB header add 62 more. The content of your image cannot change that total.
Redesign rather than reconvert. The browser's smooth downscale averages detail that has no room to exist at 32 pixels, which turns thin strokes into grey haze. Convert a simplified mark - fewer elements, thicker shapes, higher contrast - and the icon will read clearly.
It will display, but it will be scaled up, because the file contains only the 32-pixel image. A multi-resolution .ico with a 256-pixel entry looks sharper in large-icon views and on high-DPI displays; this converter writes a single entry and does not build those.
View all

Need the opposite? Try ICO to WEBP

Updated

We use anonymous analytics to improve ToolChamp. No personal data is stored or sold. Privacy Policy