CR2 to ICO Converter
Initializing... drag & drop files here
Supports: CR2
Advanced Options - Our defaults are optimized for the best results. We recommend you keeping the defaults unless you have a specific need.
Reset to defaults
Need help?Convert CR2 to ICO: What This Tutorial Covers
This takes a Canon raw photograph and writes it out as an ICO, the Windows icon container behind favicons, application icons and desktop shortcuts. The whole exercise is governed by one number: an ICO directory entry stores width and height in a single byte each, with zero standing in for 256, so no image inside an icon can exceed 256 x 256 pixels. A 20-megapixel CR2 is roughly three hundred times that pixel count. This tutorial covers how to pick the target size, what happens to a 3:2 photo when it lands in an icon, and when you should be reaching for a different tool entirely.
How to Convert CR2 to ICO
- Upload Your CR2 File: Drag your
.cr2onto the page or click "+ Add Files". Several raws can be queued at once and they all use the same settings. - Choose the Size under Image resolution: Image resolution is the only group that matters here. Pick Preset Resolutions and the dropdown offers icon sizes only — 256P, 192P, 180P, 128P, 64P, 48P, 32P, 24P and 16P.
- Know What the Preset Controls: The preset sets the icon's height; the width follows the photo's aspect ratio automatically. There is no width box, height box or "keep original" mode on this page — the preset list is the entire sizing surface.
- Convert and Download: Click Convert and save the
.ico. Files are uploaded over an encrypted connection, converted on our servers and deleted automatically a few hours later — no sign-up, no watermark.
Walk-through: Sizes, Shape and What Actually Comes Out
Two things happen in order. First the raw is rendered: a CR2 holds mosaiced 12- or 14-bit sensor values, so it is demosaiced and given a white balance and tone curve to become a viewable picture. Then that picture is scaled down into the icon. You control the second step; the first is automatic.
The scale is aspect-preserving and never crops — the preset sets the height and the width follows the photo's shape. That surprises people. A 5472 x 3648 photo at 256P comes out 384 x 256, not 256 x 256 — and since an ICO directory cannot declare a dimension above 256, that landscape icon is wider than the format can honestly record, so many readers misinterpret it. Nothing is thrown away to force a square; for a landscape photo, 128P (192 x 128) is the largest preset that stays inside the limit. If the icon is going into a slot that expects a square, crop the photo square first with the image cropper, which accepts .cr2 directly, and then convert the crop.
There is no "Keep original" mode here and no full-resolution icon, because no such thing exists — the preset list is the only control, and it opens on 256P. Pick the preset for the destination whenever it has a size in mind:
- A favicon in a page's
<head>: 32P, with 16P as the classic small size. - A Windows taskbar or shortcut icon: 48P, which is one of the nominal sizes Windows works in.
- An application icon that will be scaled by the system: 256P, the largest an ICO can hold and the size Windows Vista made practical by allowing PNG-compressed frames inside the container.
One more limitation worth knowing before you start: this conversion writes one image into the .ico. Real Windows icon files often carry several sizes in the same container so the system can pick the right one, and building that takes a dedicated icon tool rather than a format conversion.
Icon Sizes and What Uses Them
| Size | Preset here | Typical use |
|---|---|---|
| 16 x 16 | 16P | Classic favicon, small list and menu icons |
| 24 x 24 | 24P | One of the nominal sizes Windows works in; compact toolbars |
| 32 x 32 | 32P | The common favicon size, and small desktop icons |
| 48 x 48 | 48P | Windows shortcut and taskbar icons |
| 64 x 64 | 64P | A higher-DPI companion to the 32-pixel icon |
| 128 x 128 | 128P | Intermediate size for scaled and larger icon views |
| 256 x 256 | 256P | The format ceiling; application icons, high-DPI displays |
What an ICO Can and Cannot Store
| Capability | ICO | Notes |
|---|---|---|
| Maximum image size | 256 x 256 | Width and height are single bytes in the directory entry, with 0 meaning 256 |
| Non-square images | Allowed | Width and height are stored separately, so 192 x 128 is a legal entry — but neither may exceed 256 |
| Multiple sizes per file | Allowed by the format | This conversion writes a single image; multi-size icons need an icon builder |
| Transparency | Yes | A 1-bit mask in every frame, plus 8-bit alpha in 32-bit frames since Windows XP |
| PNG-compressed frames | Yes | Added in Windows Vista, which is what made 256 x 256 icons practical |
| Photographic detail | Poor by nature | At 32 pixels there is no room for fine detail, whatever the source resolution |
Common Errors and How to Fix Them
- "The icon is rectangular, not square" — Expected. The preset sets the height and the width follows the source aspect ratio, so a 3:2 photo at 256P becomes 384 x 256. Crop the CR2 to a square with the image cropper before converting.
- "It looks blurry or muddy" — Also expected, and no setting fixes it. A photograph reduced to 16-48 pixels has almost no pixels left for detail. Pick a bolder, simpler, higher-contrast subject rather than a scene.
- "The colours or exposure are off" — The raw was rendered with a neutral interpretation, not your camera's Picture Style. Edit the CR2 in raw software, export, and build the icon from that export.
- "There is no transparent background" — A camera frame is fully opaque; there is no alpha channel in a CR2 to preserve. Transparency has to come from the artwork you start with.
- "Windows still shows the old icon" — That is the Windows icon cache, not the conversion. Renaming the file or refreshing the cache forces an update.
- "My icon file only has one size in it" — Correct, that is what this conversion produces. Use an icon builder if you need 16, 32 and 48 in one container.
When This Doesn't Work
If your goal is a proper favicon kit rather than a single icon file, start from artwork instead of a photograph. Convert the raw once with CR2 to PNG, then feed that PNG to the favicon generator, which takes a square PNG, JPG or SVG and emits a multi-size favicon.ico alongside the PNG and Apple touch icon sizes a modern site wants. And if you are here because you simply wanted your Canon photo in a normal format, ICO is the wrong destination entirely — CR2 to JPG keeps the whole picture at full size.
Frequently Asked Questions
Why is 256 x 256 the largest icon I can make?
Because of how the format records dimensions. Each entry in an ICO's directory stores width and height as a single byte, and a stored value of 0 is defined to mean 256 — so 256 is the largest size the structure can describe. It is a limit of the container, not of this converter or of your source file, and it applies to every ICO ever written.
What size should I use for a favicon?
32 x 32 covers the common case, and 16 x 16 is the traditional small size that browsers have fetched from a site's root for decades. If the same icon has to work as a Windows shortcut too, add 48 x 48. Pick the preset that matches — 32P, 16P or 48P — rather than converting large and letting something else downscale it, because the scaler here is working from the full-resolution raw and has more information to work with.
Why did my 3:2 photo come out 384 x 256 instead of square?
Because the scale preserves the source's aspect ratio and does not crop. ICO permits rectangular entries, so a 3:2 frame stays 3:2. Whether that is a problem depends on what consumes the icon: some contexts letterbox it, some stretch it. Crop the CR2 square first if the destination expects a square, then convert.
Does the ICO keep any of the raw file's quality?
Essentially none of it, by design. A CR2 holds mosaiced sensor data at 12 or 14 bits across tens of megapixels; an ICO entry is at most 256 x 256 of ordinary 8-bit-per-channel pixels. The render and the downscale together discard well over 99% of the original pixel count. That is the correct outcome for an icon and a terrible one for a photograph, so keep the original raw.
Can the icon have a transparent background?
Only if transparency exists in the source, and a Canon raw has none — it is an opaque rectangular frame from a sensor. The ICO format itself handles transparency well: every frame carries a 1-bit mask, and 32-bit frames have carried 8-bit alpha since Windows XP. To use that, start from artwork with a real alpha channel, such as a logo exported to PNG.
Will the file contain several sizes like a real Windows icon?
No. This conversion writes one image into the container at the size you chose. The format allows several, and Windows uses that to pick an appropriate size per context, but assembling a multi-size icon is a different job from converting a file. Build the artwork once and use an icon builder for the multi-size version.
Which photographs actually work as icons?
Bold, centred, high-contrast subjects: a logo, one object on a plain background, a tight head-and-shoulders crop. Anything with detail that matters at small scale — a landscape, a group, text in the frame — becomes unreadable once it is 32 pixels across, because there are simply not enough pixels left to carry it. Crop tight before converting; framing decides the result far more than camera resolution does.
What happens to my CR2 after the conversion?
It is uploaded over an encrypted connection, rendered and packaged into ICO on our servers, and deleted automatically a few hours later. Nothing is shared or made public, and there is no sign-up or watermark. Because raw files are large, upload time is the main thing you will wait on — the icon itself is small and quick to write.