ICO to JSON Converter: Free, Private, No Upload

Convert ICO files to JSON in your browser. Smaller output file, batch up to 20 files at once, no upload, no account, no watermark. Your files never leave your device.

ICO to JSON
Batch up to 20 files
No upload, no account
Metadata stripped

1Add up to 20 images
2Pick from 18 formats
3Download or copy the code

Processed on your device. Your images are never uploaded, and metadata is stripped. How we keep it private

How do I convert ICO to JSON for free?

Drop your ICO files into the tool above, choose JSON as output, and download the result. Everything runs in your browser, so nothing is uploaded and there is no limit or watermark. It works on Windows, Mac, Linux, ChromeOS, iOS and Android — anywhere you have a modern browser.

Price: Free, no credits and no daily cap
Account required: No
File uploaded to server: No, processed locally in your browser
Batch limit: Up to 20 files at once
Input format: ICO
Output format: JSON
Best for: JSON workflows, smaller files, faster sharing
Works on: Chrome, Edge, Firefox, Safari, iOS and Android browsers
Privacy: No upload, no tracking, metadata stripped
Output quality: Adjustable 1-100, defaults to 90

How to convert ICO to JSON

1
Drop your ICO files
Drag up to 20 ICO files onto the page or click to choose them. Everything runs in your browser.
2
JSON is preselected
Output is already set to JSON. Adjust quality, resize or batch if you want.
3
Download
Save each JSON, or download all of them together as a ZIP.

ICO to JSON: what changes and when it makes sense

ICO is an Windows icon format. It is best known for packing several sizes (16, 32, 48, 256 pixels) into a single file. The main drawbacks are a maximum size of 256 by 256 pixels and little use outside icons.

JSON is not an image format. It is a JSON value that wraps the image data as text. Its main appeal is carrying an image alongside other fields in a single payload. The main drawbacks are a size about a third larger than the original and slow parsing for large payloads.

ICO vs JSON at a glance

Property	ICO	JSON
Type	Container format	Text encoding of an image
Compression	A container holding one or more bitmaps, each stored as BMP or PNG data	The image bytes are written out as Base64 text, which adds about 33 percent to the size
Transparency	Full alpha channel with soft edges	Same as the embedded image
Animation	No	Same as the embedded image
Colour depth	Up to 32-bit colour with an 8-bit alpha channel	Same as the embedded image
Support	Supported by Windows and by browsers as a favicon, but most image viewers and editors do not open it directly	Readable by every language and API client
History	Introduced by Microsoft with Windows 1.0 in 1985. The modern 32-bit alpha version became standard with Windows XP (2001). Windows Vista (2007) added PNG compression inside ICO for icons larger than 48x48.	JSON (JavaScript Object Notation) was specified by Douglas Crockford in 2001. Embedding images as base64 strings in JSON became common with REST APIs and AI model inputs (OpenAI vision, Anthropic Claude, Google Gemini).

What actually changes in this conversion

JSON is an encoding of the image data, not a new compression scheme. The text is about a third larger than the binary file, so what you gain is portability rather than a smaller size.
Transparency follows the image data being encoded. JSON itself is only a text wrapper.
EXIF, GPS and camera data are stripped on every conversion. That is good for privacy, but you lose capture dates.

About ICO: history and technical details

Introduced by Microsoft with Windows 1.0 in 1985. The modern 32-bit alpha version became standard with Windows XP (2001). Windows Vista (2007) added PNG compression inside ICO for icons larger than 48x48.

Technical: Container holds 1-65535 images. Each entry has a 16-byte directory: width, height, colour count, planes, bit count, data size, data offset. Images are BMP (DIB) or PNG. Max dimension 256x256. Typical Windows icons use 16, 32, 48, 64, 128, 256.

Real-world size: A 6-size favicon.ico is typically 15-40 KB. A single 256x256 PNG favicon is 8-15 KB. Modern best practice uses separate files for 16, 32, 180 (Apple), 192, 512 (PWA).

Popular tools: IcoFX, GIMP, Adobe Photoshop (with plugin), ImageMagick, Favicon Generator, RealFaviconGenerator.

Alternatives: PNG (single size, widely accepted), SVG (sharp at any size), favicon.ico (still needed for legacy).

About JSON: what you get

JSON (JavaScript Object Notation) was specified by Douglas Crockford in 2001. Embedding images as base64 strings in JSON became common with REST APIs and AI model inputs (OpenAI vision, Anthropic Claude, Google Gemini).

Technical: { "image": "iVBORw0KGgo...", "name": "photo.png" }. The base64 string can be escaped differently per language. Some APIs require no prefix, others require data:image/png;base64, prefix.

Real-world size: A 1 MB image as JSON base64 is ~1.33 MB. Parsing 10 MB JSON is 100-500ms in most languages. This is why vision AI APIs often recommend URL uploads for large images.

Popular tools: OpenAI API, Anthropic API, Google Gemini API, Postman, any JSON parser.

Alternatives: Multipart upload, Object storage + URL, Signed URL, Base64 in headers (rare).

Browser and software compatibility

ICO: Supported by Windows and by browsers as a favicon, but most image viewers and editors do not open it directly. JSON: Readable by every language and API client.

JSON with an encoded image works with any parser. Large payloads parse slowly.

Why people move away from ICO

ICO is capped at 256 by 256 pixels, so it is of no use as a general-purpose image format.
Many image viewers and design tools cannot open ICO directly, so you need a PNG to edit it.

Why people choose JSON

JSON with an encoded image is useful for API fixtures, config files and mock data.
The image travels together with the other fields as a single payload.

Common mistakes with ICO

Creating a favicon.ico with a single 16x16 size — looks blurry on Retina
Using ICO for general images — 256x256 limit makes it useless
Forgetting the .ico fallback — some old browsers still request it automatically

Best practices for keeping quality

ICO files are tiny, often 32 by 32 pixels. Scaling them up blurs, so start from a larger original when possible.
Large payloads are slow to parse and send. Store files in object storage and keep a URL in the JSON for anything over a few hundred KB.
Resize before converting if the image will be shown small. A 4000 pixel photo displayed at 800 pixels wastes bytes in any format.
Check the result at 100 percent zoom, especially around text, edges and gradients, before you replace any originals.
Keep your original files. Conversions to a lossy format cannot be undone.
When you convert a set of images, use the same quality setting for the whole batch. The converter handles up to 20 files at once.

ICO to JSON questions

Quick answers about privacy, quality, supported formats, file limits and how JSON works.

Why convert ICO to JSON?

JSON files are typically smaller than ICO, which makes them faster to share, send and load. The trade-off is a small amount of image detail at low quality settings.

Will converting ICO to JSON lose quality?

At 90% quality, most people cannot tell the difference. Use 85-95% for photos and you are fine.

Does JSON keep transparency?

JSON is only a text wrapper around the image data, so transparency depends on the image format inside it.

Are my files uploaded?

Never. Everything runs in your browser. Your files never leave your device. Open DevTools Network tab while processing — you will see no upload request.

Can I convert many files at once?

Yes, up to 20 files at once. Download them individually or all together as a ZIP.

Does the converter strip metadata?

Yes. Browsers do not pass EXIF data through a canvas, so GPS, camera model and dates are removed on every conversion. That is good for privacy.

Is it free?

Yes. No credits, no daily cap, no account, no watermark. The practical limit is your device memory.

Do AI vision APIs accept base64 images?

Yes. OpenAI, Anthropic, and Google all accept base64 images in their API requests, either as a raw string or as a data URL depending on the provider. Check the specific API docs for the exact format.

Your files never leave your device

No upload, no account, no tracking. Everything happens in your browser using the Canvas API and WebAssembly. You can confirm this in your browser's DevTools Network tab while the tool runs — no request carries your file. See why ToolDeck is different.