Initializing... drag & drop files here
Supports: CR3
CR3 is Canon's current RAW format, introduced with the EOS M50 in March 2018 and used across the EOS R mirrorless system, recent DSLRs (like the EOS 90D), and several PowerShot models. It stores 14-bit unprocessed sensor data via Canon's crx codec inside an ISO Base Media File container, and most non-Canon software needs a RAW pipeline to read it. TIFF (Tagged Image File Format, Adobe's specification last revised as TIFF 6.0 in 1992) is the universal lossless container for finished images — every prepress RIP, layout app, photo lab, and museum archive accepts it.
| Property | CR3 (Canon RAW v3) | TIFF (output) |
|---|---|---|
| Type | RAW sensor data | Rendered raster |
| Codec / spec | Canon crx inside ISO BMFF |
Adobe TIFF 6.0 (1992) |
| Bit depth | 14-bit per channel | 1, 8, or 16-bit per channel |
| Compression | Lossless RAW or lossy C-RAW | LZW, DEFLATE/ZIP, PackBits, ZSTD, JPEG, JP2K, WebP, or none |
| Editable RAW (exposure, WB) | Yes — non-destructive | No — settings are baked in |
| First-class app support | Canon DPP, Adobe Camera Raw, Lightroom Classic, Capture One | Photoshop, GIMP, Affinity, InDesign, QuarkXPress, every print RIP |
| Typical 24 MP file size | 25–35 MB lossless, 15–22 MB C-RAW | 70 MB (8-bit LZW) to 140 MB (16-bit uncompressed) |
| Multi-page / layers | No | Yes (multi-page TIFF, alpha, layers in some implementations) |
| Compression | Lossless? | Best for | Notes |
|---|---|---|---|
| NONE | Yes (uncompressed) | Maximum compatibility, scientific imaging | Largest file size; opens in legacy software |
| LZW | Yes | 8-bit print masters | The TIFF default; can actually enlarge 16-bit files |
| DEFLATE / ZIP | Yes | 16-bit archival | Same algorithm as PNG; better than LZW on 16-bit data |
| PACKBITS | Yes | Simple line art, fax-like content | Run-length encoding; required by Baseline TIFF readers |
| ZSTD | Yes | Faster lossless on modern systems | Newer; not yet universally supported in legacy RIPs |
| JPEG | No (lossy) | Web previews, contact sheets | Defeats the point of choosing TIFF for archive |
| JP2K | Optional (lossless or lossy) | Specialty archival workflows | JPEG 2000 inside TIFF; uneven app support |
CR3 stores raw sensor data in a packed 14-bit-per-pixel layout with Canon's crx lossless codec, so a 24 MP file is typically 25–35 MB. TIFF stores fully decoded RGB pixels — three channels of 8 or 16 bits each. A 24 MP 16-bit uncompressed TIFF is roughly 144 MB; with LZW it lands around 80–100 MB, and DEFLATE on 16-bit data usually beats LZW. The TIFF is bigger because it is the rendered image, not a recipe to render it.
Pick 16-bit if the TIFF will see further editing, color grading, soft-proofing, or print output — it preserves the smoother gradients carried over from the 14-bit CR3 and avoids posterization when you push curves. Pick 8-bit if the TIFF is a final deliverable for the web, email, or any pipeline that will downsample to JPEG anyway. 8-bit cuts file size roughly in half.
DEFLATE (also called ZIP in some apps) is generally the best choice for 16-bit TIFFs — it uses the same zlib algorithm as PNG and compresses noisy 16-bit photographic data better than LZW. LZW was designed for 8-bit imagery and can actually make a 16-bit file larger than uncompressed in some cases. Use NONE only if the receiving software is older than the late 1990s.
Yes, via Adobe Camera Raw, but only on supported camera models and only with a recent enough Camera Raw version. Adobe added CR3 support in Camera Raw 10.3 (April 2018) starting with the EOS M50, and each subsequent Canon body needed a Camera Raw update. If your CR3 won't open, update Camera Raw, or convert via Canon's free Digital Photo Professional (DPP) first.
Yes for 16-bit; partly for 8-bit. The CR3 captures 14 bits per channel of sensor linear data. When you export a 16-bit TIFF, the converter upsamples those 14 bits into 16-bit gamma-corrected RGB and you keep the full tonal range. An 8-bit TIFF reduces 16,384 tones per channel down to 256 — fine for output, but you will see banding if you try to lift shadows or recover highlights afterward.
xconvert renders to sRGB, which is the safe default for web, email, social, and most consumer prints. If you need a wider gamut for fine-art prints or further color work — Adobe RGB for commercial print, ProPhoto for an archival master — process the CR3 in Canon DPP, Adobe Camera Raw, or Lightroom and export the TIFF from there with the gamut you want. RAW developers expose color-space choice that an online converter cannot.
Every Canon EOS R-series mirrorless body (R, R3, R5, R5 C, R6, R6 II, R7, R8, R10, R50, R100), several recent DSLRs (EOS 90D, EOS Rebel SL3 / 250D, EOS M6 II, EOS M50 / M50 II), and PowerShot G5 X Mark II / G7 X Mark III. Older Canon DSLRs (5D Mark IV, 1D X Mark II, etc.) write the older CR2 format — for those, see CR2 to TIFF.
Yes. Load every CR3 from the shoot at once; the same Quality, Compression, Bit Depth, and Resolution settings apply to all of them. For typical wedding or commercial volumes, work in batches sized to your machine's memory — 16-bit TIFFs balloon quickly and processing happens in your browser.
Yes. Treat the CR3 as your digital negative — it carries the unprocessed sensor data and full editing latitude. The TIFF is a rendered output, fine as a deliverable but with editing decisions baked in. If you ever need to re-grade, recover blown highlights, or change white balance, you'll want the CR3. Storage is cheap; reshoots are not.
Use the equivalent converters — NEF to TIFF for Nikon RAW or ARW to TIFF for Sony. The TIFF output specs (compression, bit depth, resolution) work the same way across all RAW sources.