Initializing... drag & drop files here
Supports: CRW
.crw (Canon Raw version 1) and processes the camera's raw sensor data into a finished image. Batch is supported — drop in a folder of CRWs from an old EOS shoot and each one converts in parallel.CRW is Canon Raw version 1 — the company's original digital raw format, written in the Camera Image File Format (CIFF) container that Canon released in 1997. It carries the unprocessed 12-bit sensor readout from a handful of early Canon bodies made roughly between 2000 and 2004: the EOS D30, D60, and 10D, the Digital Rebel (300D), and PowerShot models like the G1–G6, S30–S70, and Pro1. In 2004 Canon replaced CRW with the TIFF-based CR2 format (starting with the EOS-1D Mark II), and CIFF was never adopted by anyone but Canon — which is exactly why CRW compatibility is so poor today.
That orphaned-format problem is the whole reason people convert CRW. A raw file is not a picture; it is sensor data that needs to be developed into a viewable image. Common reasons to convert:
| Format | Type | Bit depth | Native support today | Best for |
|---|---|---|---|---|
| CRW (source) | Canon raw, CIFF container | 12-bit sensor data | Poor — legacy Canon software only | The original capture; not directly viewable |
| JPG | Lossy compressed | 8-bit | Every device, browser, and OS | Sharing, email, web, prints |
| PNG | Lossless compressed | 8 / 16-bit | Every modern browser and editor | Edits, crops, no-artifact copies |
| TIFF | Lossless / uncompressed | 8 / 16-bit | Editors, print labs, archives | 16-bit archival and print masters |
| WebP | Lossy or lossless | 8-bit | Chrome, Firefox, Edge, Safari 16+ | Smaller web images than JPG |
| Document wrapper | n/a | Universal | Bundling frames into one shareable file |
Very few modern ones. CRW uses Canon's old CIFF container rather than the TIFF-based structure of CR2, so most apps that read a CR2 still cannot decode a CRW. Canon's own legacy Digital Photo Professional, older Lightroom builds, and a few raw utilities like RawTherapee or darktable can still handle it, but mainstream viewers and recent Photoshop/Lightroom releases generally cannot. Converting to JPG or PNG is the reliable way to make the image openable everywhere without hunting for legacy software.
No — they are two generations of Canon raw. CRW (Canon Raw version 1) uses the CIFF container and came from early bodies like the EOS D30/D60/10D and PowerShot G-series, roughly 2000–2004. Canon replaced it in 2004 with CR2 (Canon Raw version 2), which is built on the TIFF structure and shipped first on the EOS-1D Mark II; CR3 followed in 2018. They share Canon raw DNA but are not interchangeable, and a tool that reads CR2 will often reject CRW.
Some, but it is controllable. CRW holds 12-bit raw sensor data; JPG is 8-bit and lossy, so the conversion bakes in white balance and tone curve and discards the extra editing headroom raw gives you. With the Quality Preset on "Very High" the visible loss is minimal and the image looks identical at normal viewing sizes. If you want to keep the full editing latitude, convert to a 16-bit TIFF or PNG instead — those preserve far more of the original tonal range than a JPG can.
A 16-bit TIFF. TIFF stores the developed image losslessly and supports a 16-bit depth that preserves the wide dynamic range of the raw capture, which is why print labs and archives accept it as a master. Set the Image File Extension to TIFF and Bit Depth to "16-bit (High Precision)" before converting. Keep your original CRW too if you can — it remains the only file with the untouched sensor data — but a TIFF is the practical, openable archival copy.
The standard shooting metadata that matters to most people — capture date, camera model, exposure, ISO, and focal length — is carried into the output where the target format supports it, so a converted JPG or TIFF generally retains its EXIF block. Some Canon-proprietary maker-note fields specific to CIFF may not survive the format change, since they have no equivalent in the destination. In our testing, a CRW from an EOS D60 converted to JPG kept its date, camera, and exposure fields intact in the resulting EXIF.
Yes. Drop a whole batch of CRWs onto the uploader and each one is processed independently in parallel, then handed back individually or as a single ZIP — useful for developing an entire old shoot in one pass. If you would rather not commit to a single output type, the broader image converter accepts CRW alongside other raw formats and lets you pick the target per job.
Yes. Files travel over an encrypted (TLS) connection, are processed on our servers, and are deleted automatically after a few hours — there is no sign-up, no watermark, and nothing is shared or made public. For one-off old family photos that often means the safest path is simply to convert, download the JPG or TIFF, and let the originals expire from the server on their own.