Initializing... drag & drop files here
Supports: CR3
CR3 is Canon's RAW image format, introduced in 2018 with the DIGIC 8 processor (first appearing in the EOS M50). RAW files capture the full 14-bit sensor data needed for serious post-processing, but they're huge — a single CR3 from a 45MP EOS R5 typically runs 35–70 MB depending on subject and ISO. HEIC (High Efficiency Image Container), Apple's HEVC-based image format, delivers visually similar quality at roughly half the size of JPEG and a tiny fraction of RAW.
This conversion is the right move once your edits are baked in and you just need a compact archive or share-ready file.
For maximum cross-platform compatibility (older Android, web embeds, email), consider CR3 to JPG instead. For lossless export with no compression artifacts, CR3 to PNG or CR3 to TIFF preserve every pixel. Older Canon bodies that produce CR2 instead of CR3 can use CR2 to HEIC.
| Property | CR3 (Canon RAW) | HEIC |
|---|---|---|
| Origin | Canon, 2018 (DIGIC 8) | Apple/MPEG, 2015 (HEIF + HEVC) |
| Compression | Lossless or C-RAW (lossy) | HEVC, lossy or lossless |
| Typical size (45MP R5) | 35–70 MB | 2–6 MB at high quality |
| Bit depth | 14-bit | 8, 10, or 12-bit |
| Editing latitude | Full RAW — recover ±3 EV, white balance | Baked-in — limited recovery |
| Built-in viewers | Canon DPP, Lightroom, Photoshop, macOS Preview | iOS/macOS native, Android 10+, Win 11 with extension |
| Web browser support | None | Safari 17+ only; no Chrome/Firefox |
| Best for | Sensor-data archive, deep editing | Final share, iPhone-side storage |
| Preset | Visual loss vs CR3 | Typical output (45MP) | Use case |
|---|---|---|---|
| Highest | Imperceptible | 6–10 MB | Print archive, gallery delivery |
| Very High (default) | Negligible at 100% view | 3–6 MB | Personal archive, iCloud backup |
| High | Tiny artifacts in deep shadows | 1.5–3 MB | AirDrop, iMessage, family share |
| Medium | Visible on detailed pixel-peep | 700 KB–1.5 MB | Social media before re-encode |
| Low / Lowest | Noticeable softness, banding | 200–600 KB | Web thumbnails, proofs |
CR3 came in with the DIGIC 8 processor and is used by Canon's newer bodies: EOS R5, R5 Mark II, R6, R6 Mark II, R7, R8, R10, R50, R100, RP, M50, M50 Mark II, M6 Mark II, M200, EOS 1D X Mark III, EOS 90D, EOS 250D / Rebel SL3, EOS 850D / Rebel T8i, and the EOS SX70 HS superzoom. Older Canon DSLRs (5D Mark IV, 7D Mark II, 80D, etc.) save CR2 — use CR2 to HEIC for those.
Yes, some — but probably less than you'd guess. CR3 stores 14-bit sensor data; HEIC tops out at 12-bit and typically encodes at 10-bit with HEVC compression. At the "Very High" or "Highest" preset, the difference is invisible at 100% viewing distance for normal shots. Where you'd notice loss: extreme shadow lifts, banded skies pushed +3 EV in post, or fine high-ISO grain. For zero compression artifacts, use CR3 to TIFF instead.
It's faster for one-off conversions. Lightroom and Canon DPP both export HEIC, but they require importing the CR3 into a catalog first, then setting up an export preset. For someone who just wants to hand a relative a folder of HEICs from yesterday's shoot, dropping the CR3s into a browser tool finishes in under a minute with no catalog clutter. The browser conversion also runs locally — files don't get uploaded to a server.
Windows 11 needs two free Microsoft Store extensions: "HEIF Image Extensions" (the container) and "HEVC Video Extensions" (the codec). The HEIF extension is free; HEVC is $0.99 in the Microsoft Store but free on most OEM PCs that ship with a manufacturer HEVC license. Once both are installed, HEIC opens in File Explorer thumbnails and the Photos app. Windows 10 needs the same two extensions. If you want zero-extension compatibility, CR3 to JPG opens everywhere by default.
Yes. EXIF (camera model, shutter speed, aperture, ISO, focal length, GPS coordinates if recorded) carries over into the HEIC file. Canon-proprietary maker notes (Picture Style, Auto Lighting Optimizer settings) typically do not survive the conversion since they're stored in a Canon-specific section of the RAW file. Lens model, body model, and date/time always transfer.
HEIF is the container spec (ISO/IEC 23008-12); HEIC is the specific file extension Apple uses when the container holds HEVC-encoded images. A .heif file might use HEVC, AV1, or other codecs; a .heic file is always HEVC. In practice the two extensions are used interchangeably, and most viewers handle both. Apple devices save photos as .heic.
Yes — drop the whole folder of CR3s in. There's no fixed file-count cap; the practical limit is your browser's memory. A typical desktop browser handles 200–500 CR3 files per batch comfortably. For very large shoots (1,000+ files), split into 2–3 batches so the browser doesn't hold everything in RAM simultaneously.
Either works for HEIC delivery, but full CR3 gives you more editing headroom before the conversion. C-RAW already throws away some highlight and shadow data with lossy compression; stacking HEIC's lossy compression on top of that compounds the loss. If storage on your CF Express card is the bottleneck, C-RAW is fine. If your edits include heavy shadow recovery or exposure correction, shoot full CR3 and convert to HEIC only after the edit is locked.
A few likely causes: you picked "Highest" instead of "Very High" (Highest is near-lossless and runs 2–3× larger), you kept the full 45MP resolution when a 4K resolution preset would be plenty for screen viewing, or the source CR3 contains very fine detail (foliage, fabric textures, high ISO grain) that HEVC can't compress as aggressively. Try Quality Preset "High" with a 2160p resolution preset for typical share use — that usually lands under 1.5 MB.