Wide SVG mark
- Input
- 640 byte transparent SVG at 320×180 with a panel, circle, curve, and text.
- Output
- 13,874 byte ICO with one 256×144 RGBA image. It was not a square favicon and did not include smaller entries.
SVG to ICO rasterizes vector art and stores one thumbnail-sized icon entry, so it is not yet a full multi-size favicon generator.
From real runs
| Element | Result | What happens |
|---|---|---|
| Icon entries | Changed | The 320×180 SVG wrote a 13,874 byte ICO containing one 256×144 RGBA entry, not 16, 32, 48, and 256 sizes. |
| Aspect ratio | Kept | Our image engine thumbnailed the wide SVG to fit within 256 pixels, so the ICO entry stayed 16:9 rather than square. |
| Transparency | Kept | The ICO entry opened as RGBA, so transparent regions from the SVG raster survived the icon save. |
| Vector scalability | Lost | Once inside ICO, the SVG paths are just bitmap pixels at the single stored size. |
| Inline SVG style | Kept | Embedded style rules were applied before the icon was generated, matching the colors from the SVG preview run. |
| Small favicon sizes | Lost | Browsers or Windows cannot choose 16×16 or 32×32 renditions because this output did not include them. |
The 320×180 SVG wrote a 13,874 byte ICO containing one 256×144 RGBA entry, not 16, 32, 48, and 256 sizes.
Our image engine thumbnailed the wide SVG to fit within 256 pixels, so the ICO entry stayed 16:9 rather than square.
The ICO entry opened as RGBA, so transparent regions from the SVG raster survived the icon save.
Once inside ICO, the SVG paths are just bitmap pixels at the single stored size.
Embedded style rules were applied before the icon was generated, matching the colors from the SVG preview run.
Browsers or Windows cannot choose 16×16 or 32×32 renditions because this output did not include them.
We converted our SVG sample (389 B) with Image engine on 2026-10-20. It took 17 ms and produced a 5 KB ICO file, 14× larger than the input. The engine raised 1 warning, listed below.
Input · sample.svg · 389 B
SVG viewBox 0 0 320 200, 0 paths
Output · sample.ico · 5 KB
256 × 160 px, 1 size: 256×160
ImageMagick 7
magick in.svg -background none -define icon:auto-resize=256,48,32,16 favicon.icoThis command creates the multi-size ICO that the current API output did not create in our test.
The HTTP API and the MCP server run the exact engine this page uses (Image engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=svg&to=ico.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.svg" -F "from=svg" -F "to=ico" \
-F 'options={"dpi":96}' \
--output output.ico| Key | Applies to | Type | Default |
|---|---|---|---|
| dpi | Reading SVG | number | 96 |
| width | Writing ICO | number | 0 |
| height | Writing ICO | number | 0 |
| fit | Writing ICO | contain · cover · fill | contain |
| quality | Writing ICO | number | 90 |
| background | Writing ICO | string | #ffffff |
| stripMetadata | Writing ICO | boolean | true |
No in the tested path. The output contained one 256×144 entry, so make a separate multi-size favicon if browser fallback sizes matter.
The writer preserves the rendered aspect ratio while fitting inside 256 pixels. A wide SVG can therefore become a wide ICO entry.
Yes for the tested SVG. The output entry opened as RGBA, which kept transparent canvas pixels around the artwork.