PicaJet
Search Build shortlist

Reference Formats

CR2

Canon's TIFF/EP-based RAW format used from 2004 until superseded by CR3 in 2018, storing raw sensor data alongside an embedded JPEG preview and Exif/MakerNotes metadata.

Extension

.cr2

Full name

Canon Raw version 2

Introduced

2004, with the EOS-1D Mark II

Vendor

Canon

What is inside the container

CR2 is structurally a TIFF file (TIFF/EP compliant) with a Canon-specific IFD holding MakerNotes such as lens data, white balance, and Picture Style settings. It embeds a full-size or near-full-size JPEG preview inside the file, which is what lets a DAM's thumbnail generator display a fast preview without running a full RAW decode.

How to open it

Canon native Canon Digital Photo Professional (DPP)
Cross-vendor commercial Adobe Camera Raw / Lightroom Classic
Cross-vendor commercial Capture One
Open source RawTherapee and darktable

For archives

CR2 is stable and well documented after two decades of continuous use, so keeping it as-is is low risk for now. Since Canon has fully moved to CR3 for current cameras, still budget for a DNG conversion pass on very long-term archives, or periodically re-verify that current raw processors still open older CR2 files correctly.

Canon introduced CR2 in 2004 with the EOS-1D Mark II, replacing its earlier CRW format, and kept it as the standard RAW format across the EOS line — DSLRs from the 20D through later Rebel and 1D-series bodies — for the better part of fourteen years. Being TIFF/EP-based made CR2 relatively easy for third-party software to support from the start, since it followed a documented structural convention rather than an entirely bespoke container.

In a DAM, CR2’s embedded JPEG preview is the workhorse feature: it lets a system generate a usable thumbnail instantly rather than waiting on a full raw-processing pass, which matters at the scale of a photo library with tens of thousands of RAW files. The metadata that actually matters for search and rights tracking — capture settings, lens, camera body — lives in Canon’s MakerNotes block, which most mainstream raw processors parse correctly given CR2’s age and ubiquity. The main archival consideration is generational: Canon’s current cameras all shoot CR3, so CR2 is now a legacy format from a support standpoint, even though it remains widely readable today.

Frequently asked

What lets a DAM generate a fast preview from a CR2 file?

CR2 embeds a full-size or near-full-size JPEG preview directly inside its TIFF-based IFD structure, alongside a smaller thumbnail JPEG. A DAM's indexing engine — via libraries like ExifTool or LibRaw — extracts that embedded JPEG instead of decoding the raw Bayer sensor data, so thumbnails and grid previews render in milliseconds even across archives holding hundreds of thousands of CR2 masters.

Is CR2 structurally a standard TIFF file?

Yes. CR2 follows the TIFF/EP baseline (ISO 12234-2): a standard TIFF header, multiple Image File Directories, and tag-based metadata that any TIFF-aware parser can walk. Canon appends a short proprietary header right after the TIFF header, pointing to the IFD that stores the raw sensor data in lossless-JPEG compression, plus a Canon MakerNotes IFD carrying lens data, white balance, and Picture Style settings that only Canon-aware software fully decodes.

Should a DAM convert CR2 masters to DNG right away?

Not urgently. CR2 is stable and well documented after two decades of continuous use, so keeping it as-is is low risk for now, though very long-term archives should still budget for an eventual DNG conversion pass.

Is CR2 still Canon's current RAW format?

No. Canon replaced CR2 with CR3, introduced with the EOS M50 in 2018, and CR3 is now standard across the EOS R mirrorless line. Unlike CR2's TIFF/EP structure, CR3 is built on the ISO Base Media File Format — the same container family used for MP4 and HEIF — and adds a compressed CRAW variant. A DAM ingesting current Canon captures will increasingly see CR3, while CR2 stays relevant mainly for archives of older EOS bodies' output.

When was CR2 introduced?

2004, debuting with the Canon EOS-1D Mark II, where it replaced Canon's earlier proprietary CRW format. CR2 went on to serve as Canon's primary RAW format for roughly fourteen years, used across both consumer EOS Rebel bodies and professional 1D- and 5D-series cameras, before Canon introduced CR3 in 2018. That long production run is why CR2 masters still make up a large share of legacy DAM archives.

What native Canon software opens CR2?

Canon Digital Photo Professional (DPP), the company's free raw converter bundled with EOS cameras, is the reference tool — it applies Canon's own Picture Style presets and in-camera lens corrections as Canon intends. Because CR2's TIFF/EP structure is openly documented, third-party converters read it too: Adobe Camera Raw, Lightroom Classic, Capture One, RawTherapee, and darktable all support it, which is what makes CR2 practical as a DAM archive format rather than a vendor lock-in.

What metadata does CR2 carry beyond the pixel data?

Standard Exif fields — camera model, exposure settings, date/time, and GPS coordinates when recorded — sit alongside a Canon-specific MakerNotes IFD holding lens identification, as-shot white balance, and the applied Picture Style. The embedded JPEG preview and thumbnail carry their own copy of key tags too. For a DAM, this is the metadata pool that populates searchable fields — lens, camera body, exposure — without needing to decode the raw sensor data itself.

What ongoing risk should a DAM watch for with CR2 archives?

Format rot is the main risk: since Canon's active development has moved to CR3, continued CR2 support in raw-processor updates depends on third-party maintenance rather than vendor investment. The TIFF/EP baseline should stay decodable indefinitely, but the proprietary MakerNotes IFD is reverse-engineered by tools like ExifTool and could lose fidelity over time. A DAM should periodically re-test that current software still opens CR2 masters correctly, and treat DNG conversion as a fallback if support visibly narrows.

Sources