Annual plan: $79.90 USD/year, billed annuallyView pricing

Batch-convert ICO icons into high-quality SVG paths.

Trace legacy favicons and Windows icons into real SVG paths. Control colors and detail, inspect each result, and export individual files or a complete ZIP.

Image contents are processed temporarily and discarded after conversion.

Add ICO images and control the result.

Drop or choose up to 10 images.

模式

Converted files

0

Converted images will appear here.

How it works

How do you convert an image to SVG?

  1. ICO files being added to the converter
    01

    Upload ICO icons

    Grab the favicon.ico from an old site or the icon files from a legacy Windows app and drop them into the converter.

    Modernize an aging favicon.ico into an SVG favicon for current browsers.

  2. Tracing mode and color controls set for ICO sources
    02

    Keep the palette tight

    Icons are usually flat artwork — a low color count of 4 to 8 gives the cleanest, most faithful vector result.

    Extract old Windows app icons as vectors for a rebranding project.

  3. Preview of the SVG traced from a ICO source
    03

    Replace many sizes with one file

    Download an SVG that covers every tab, bookmark, and home-screen size a browser might ask for.

    Archive legacy icon sets in a format today's design tools can open.

Format guide

Why convert ICO to SVG?

ICO is a Windows container format from the 1990s that bundles several fixed-size bitmaps — typically 16×16, 32×32, and 48×48 — into one file. Each embedded image is only sharp at its own size, which is why old favicons look crunchy on modern high-density displays and in large bookmark tiles.

Every current major browser accepts SVG favicons, and a single SVG covers all sizes and pixel densities at once. This converter reads an image from the ICO container and traces it into standard SVG paths you can reference from a single <link> tag.

Set expectations by the source: an ICO that only contains a 16×16 frame holds very little detail, so the result will look blocky if enlarged far beyond favicon size. Whenever possible, convert from the largest icon you have, and keep the original .ico around as a fallback for very old browsers.

“SVG is a language for describing two-dimensional graphics in XML. SVG allows for three types of graphic objects: vector graphic shapes (e.g., paths consisting of straight lines and curves), images and text.”

W3C, Scalable Vector Graphics (SVG) 1.1, §1.1

Where can I read more?

The output is standard SVG markup, defined by the following public specifications and references:

Favicon workflow

One vector in place of a bitmap container.

Trade a .ico full of 16×16 and 32×32 frames for a single SVG that every current browser renders sharply at any size.

  • Whole legacy icon sets

    Drop in a folder of .ico files pulled from an old site or a Windows application and convert them in one pass.

  • One file, every size

    A single SVG covers the tab, bookmark, and home-screen sizes the ICO container had to store as separate bitmaps.

  • Vector shapes out of pixels

    The frame read from the container is traced into editable paths rather than embedded as an image inside SVG markup.

  • Tight palettes for flat icons

    Icon artwork is usually flat, and 4 to 8 colors reproduces it most faithfully with the fewest paths.

  • No retained copies

    Icon files are processed for the conversion and discarded afterwards; nothing is kept or reused.

Before you convert

What an ICO source can actually give you.

  • Detail is capped by the frame

    A 16×16 image holds very little information. Start from the largest icon in the container if the result has to enlarge cleanly.

  • Keep favicon.ico as a fallback

    SVG favicons work in every current browser, but very old clients and a few integrations still expect the .ico to be there.

  • Inspect it before you ship it

    Preview the traced icon at full size, re-run it on its own if the edges look off, then download.

FAQ

Common questions.