Initializing... drag & drop files here
Supports: CR3
This tutorial takes a Canon .cr3 raw photograph and produces a Windows .ico icon file — the format used for desktop shortcuts, application icons, and classic browser favicons. The two formats sit at opposite extremes: a CR3 is 20-45+ megapixels of unprocessed sensor data, while a single ICO image tops out at 256 x 256 pixels. Everything below is about controlling that enormous downscale so the result still reads as something at icon size.
.cr3 onto the page or click "+ Add Files" to browse. You can queue several raw photos and convert them all with the same setting..ico. Files are uploaded over an encrypted connection, converted on our servers, and deleted automatically after a few hours. No sign-up, no watermark.The preset you pick sets the output height; the width follows your photo's aspect ratio. A CR3 from a 3:2 Canon body at the 256 preset therefore renders 256 pixels tall and wider than that, not a 256 x 256 square. That matters more than it would in any other format, because an ICO directory entry stores each image's width and height in a single byte apiece — which is why 256 is the ceiling and why a wide crop at the largest preset is asking for something the header cannot express. In practice:
.cr3 directly and can write ICO as its output format, so you can square the frame and produce the icon in one pass..ico file; the format itself can hold many, but combining them is a separate packaging step.| Property | CR3 (source) | ICO (output) |
|---|---|---|
| What it is | Canon raw photograph | Windows icon image container |
| Standard | ISO/IEC 14496-12 (ISO BMFF) + Canon crx codec |
Microsoft icon resource format |
| Introduced | April 2018, with the Canon EOS M50 | Long-standing Windows format; PNG-compressed frames added in Windows Vista |
| Maximum size | Full sensor resolution (20-45+ MP) | 256 x 256 per image (a stored 0 means 256) |
| Colour depth | 12-14 bit sensor data, lossless raw or lossy C-RAW | 1, 4, 8 or 32 bits per pixel |
| Transparency | None — a raw capture is a solid rectangle | Yes, via the AND mask or a 32-bit BGRA alpha channel |
| Multiple images per file | No | Yes — one ICONDIRENTRY per size |
| Best for | Editing and archiving the original photo | Shortcuts, application icons, favicons |
| Preset | Pixels tall | Typical use |
|---|---|---|
| 16 | 16 | Browser tab favicon, small list icons |
| 32 | 32 | Default favicon size, Windows small icons |
| 48 | 48 | Windows Explorer medium icons |
| 64 / 128 | 64 / 128 | Larger shell views and dialogs |
| 180 / 192 | 180 / 192 | Non-standard sizes, for tools that ask for them specifically |
| 256 | 256 | Installer art and Explorer extra-large icons |
If you generate only one, use 32 — it is the size most browsers request first, and it downsamples acceptably to the 16-pixel tab rendering. Generate 16 as well if the artwork has fine detail that muddles when the browser scales it. 48 and 256 matter for Windows shortcuts and installers rather than for the web.
Because the preset sets the height and the width is derived from your photo's aspect ratio. A 3:2 Canon frame at the 256 preset comes out 256 pixels tall and proportionally wider. Icons are conventionally square, and cropping is the only way to get a square result from a rectangular photo without stretching it — Crop Image takes .cr3 input and offers ICO as an output format, so a square crop and the icon can happen in the same step.
A 24-megapixel frame is roughly 6000 x 4000 pixels. At 32 pixels tall you are keeping about one pixel in every 125 across, so faces, text, and texture collapse into a smear of colour. Icons work from bold shapes and strong contrast, not from photographic detail. Crop tightly to a single high-contrast subject before converting, or accept that only the overall colour survives.
Because none of them apply to ICO output. The Image Compression group — quality preset and file-size targeting — is hidden for ICO, as is the Colors palette control (which appears for GIF output, and for PNG at the highest quality preset) and the Bit Depth control (PPM output only). Resolution is the only thing left that meaningfully changes an icon, so it is the only control the page renders.
The format can: an ICO begins with an ICONDIR structure followed by one ICONDIRENTRY per stored image, which is how a single favicon file serves crisp 16, 32, and 48 pixel renderings. This converter writes one image per file, so run it once per preset if you need several sizes and combine them with a dedicated icon packer afterwards.
There is nothing to keep. A CR3 is sensor data for a solid rectangular frame with no alpha channel, so the icon is fully opaque edge to edge. ICO itself supports transparency — through the AND mask on paletted frames or a full alpha channel on 32-bit BGRA frames — but you need a source that already has transparency, such as a logo exported as PNG, to make use of it.
No. The .cr3 on disk holds unprocessed sensor data plus the develop settings your editor stores separately; converting it here renders the raw with a baseline interpretation instead of your adjustments. If a specific look matters at icon size, export a finished JPG or PNG from your raw editor and convert that image to ICO instead.
It is uploaded over an encrypted connection, converted on our servers, and deleted automatically after a few hours — never shared, never made public, no sign-up and no watermark. In our pipeline the icon is written with ImageMagick and the requested size is clamped to 256 pixels, the largest value an ICO directory entry can express, before the file is written. If you want the photograph itself rather than an icon, CR3 to PNG keeps it viewable at full resolution.