Initializing... drag & drop files here
Supports: CR2
CR2 is Canon's RAW format: it holds the unprocessed 14-bit sensor readout from an EOS DSLR, with white balance and exposure stored as adjustable metadata rather than baked into the pixels. BMP is Microsoft's Windows bitmap — finished, display-ready RGB pixels with no compression on top. Converting CR2 to BMP renders the RAW into a fixed, uncompressed image: you get a plain bitmap any Windows tool can read, but you trade away the editing latitude that made the RAW worth keeping. This page lays out that tradeoff, then converts the file.
| Property | CR2 (Canon RAW) | BMP (Windows Bitmap) |
|---|---|---|
| Full name | Camera RAW 2 (Canon Raw v2) | Bitmap / device-independent bitmap (DIB) |
| Origin | Canon, EOS DSLRs (roughly 2004–2018) | Microsoft, for the Windows graphics subsystem |
| Built on | The TIFF specification (multiple image directories) | Its own simple header + raw pixel rows |
| Stores | Unprocessed sensor samples, not RGB | Finished RGB (or palette) pixels |
| Bit depth | Up to 14-bit per channel from the sensor | Commonly 8-bit per channel (24-bit color) |
| White balance / exposure | Held as adjustable metadata | Baked into the rendered pixels |
| Compression | Lossless compression on the RAW data | Typically none — pixels stored uncompressed |
| Native browser support | None — needs conversion to view | Limited; most browsers don't render BMP in <img> |
| Best for | A photographic master you'll still edit | Plain uncompressed bitmaps for Windows tooling |
.bmp and won't accept PNG or JPG.Yes — that's the main thing to understand. The RAW stores unprocessed 14-bit sensor data with white balance and exposure as adjustable settings. Rendering to BMP bakes those decisions into fixed pixels, so you can no longer non-destructively recover blown highlights or re-do the white balance the way you could in the RAW. Keep the original CR2 as your master and treat the BMP as a finished export. If you want an editable high-bit file instead, CR2 to TIFF preserves more headroom.
Because BMP applies no compression to the rendered pixels. A 20-megapixel Canon RAW (around 5472 × 3648) becomes a 24-bit BMP of about 5472 × 3648 × 3 bytes ≈ 60 MB of raw pixel data — and that's deterministic math, not an estimate. The CR2 itself is smaller because it stores losslessly compressed sensor data. If that size is a problem, CR2 to PNG is lossless too but compressed, usually a fraction of the BMP.
No new compression loss after the render — BMP stores the rendered pixels exactly, with nothing thrown away on top. The loss that matters happens earlier, at the render step: the converter demosaics the RAW and bakes in white balance and exposure, which collapses the RAW's adjustable latitude into one fixed interpretation. The pixels you get are exact; what you lose is the ability to re-render them differently later.
The output is a standard 24-bit true-color BMP — 8 bits each for red, green, and blue. The CR2 sensor captures up to 14 bits per channel, so the conversion maps that down to 8-bit per channel for the bitmap. If you specifically need to retain more than 8 bits of tonal data in an editable file, BMP isn't the right target; CR2 to TIFF can hold 16-bit data instead.
For most people, PNG is the better choice: it's lossless like BMP but compressed, so you get the same pixel-exact render at a much smaller size and with native browser support. Pick JPG when you just need a small, shareable photo. Choose BMP specifically when a Windows tool or imaging pipeline requires a plain uncompressed bitmap and won't take anything else.
On the desktop, yes — BMP opens in Windows Photos, Paint, and essentially every image editor (Photoshop, GIMP, IrfanView). But most web browsers don't render BMP inside an <img> tag, and many phone galleries support it only partially. In our testing, a full-resolution 20 MP BMP also runs near 60 MB, which is awkward to send or post. If you plan to view it on mobile or share it online, PNG is the safer and far smaller format.
Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, never shared or made public.