Initializing... drag & drop files here
Supports: CR3
CR3 is Canon's current RAW format, introduced in 2018 with the EOS M50 and rolled out across the EOS R mirrorless lineup. Unlike its predecessor CR2 (which wraps a TIFF/EP container), CR3 is built on the ISO Base Media File Format (ISO/IEC 14496-12) — the same box-based container family used by MP4 and HEIF — with Canon's proprietary "crx" codec layered on top. That makes CR3 fast for cameras to write at high burst rates, but it also means almost no image viewer outside Canon's Digital Photo Professional, Adobe Camera Raw, Capture One, and a handful of other RAW editors can open the file. PNG (ISO/IEC 15948) gives you the opposite: a universally readable, lossless raster format that every browser, OS, and editor handles natively.
| Property | CR3 (Canon RAW 3) | CR2 (Canon RAW 2) | PNG | JPG |
|---|---|---|---|---|
| Introduced | 2018 (EOS M50) | 2004 (EOS-1D Mark II) | 1996 (W3C); ISO 2004 | 1992 (JPEG) |
| Container | ISO Base Media (ISO/IEC 14496-12) | TIFF/EP | PNG datastream (IDAT/IEND) | JFIF / Exif |
| Codec | Canon "crx" (JPEG-LS + JPEG-2000 hybrid) | Lossless Canon TIFF compression | DEFLATE (LZ77 + Huffman) | DCT + Huffman |
| Bit depth | 14-bit (most bodies) | 14-bit | 1-16 bit per channel | 8-bit (Baseline) |
| Compression | RAW; optional C-RAW | RAW only | Lossless | Lossy |
| Typical size (24 MP) | 25-35 MB (RAW) / 12-20 MB (C-RAW) | 28-40 MB | 30-55 MB | 5-10 MB |
| Editable WB / exposure | Yes (RAW workflow) | Yes (RAW workflow) | No (baked in) | No (baked in) |
| Transparency | No | No | Yes (alpha channel) | No |
| Universal viewing | No (RAW editor needed) | No (RAW editor needed) | Yes | Yes |
| Preset | What it does | Best for |
|---|---|---|
| Highest | Maximum DEFLATE optimisation, slowest encode | Archival masters, print-bound deliverables |
| Very High (Recommended) | Strong compression with reasonable speed | Default for most exports |
| High | Balanced compression, faster | General-purpose web and editing handoff |
| Medium | Looser compression, smaller filter search | Quick proofs, contact sheets |
| Low / Very Low / Lowest | Minimal compression effort, fastest | Bulk previews, throwaway exports |
PNG quality is always lossless — the preset only changes encoder effort and final file size, not pixel fidelity. For lossy size savings on photographic content, convert to JPG or WebP instead.
Every Canon body released since the EOS M50 (Feb 2018) writes CR3 by default: EOS R, RP, R3, R5, R5 C, R6, R6 Mark II, R7, R8, R10, R50, R100, EOS 90D, EOS M50/M50 Mark II, EOS M6 Mark II, plus the PowerShot G5 X Mark II, G7 X Mark III, and SX70 HS. Older Canon DSLRs (5D Mark IV, 6D Mark II, 7D Mark II, 80D, etc.) still shoot the legacy CR2 format — for those, use CR2 to PNG.
Both are CR3 container files; the difference is the codec inside. Standard CR3 stores 14-bit RAW data with mathematically lossless Canon "crx" compression. C-RAW (Compressed RAW) keeps the same pixel dimensions and 14-bit depth but uses a visually lossless lossy codec that yields roughly 30-40% smaller files, per Canon's documentation. For most exports you won't see a difference; if you push exposure +3 EV in heavy shadow recovery, full RAW retains slightly more headroom.
Usually yes. A 24 MP CR3 lands around 25-35 MB because it stores compressed sensor-pattern data at 14-bit. A PNG stores the fully demosaiced 8-bit-per-channel RGB image (16-bit if you select that depth), which DEFLATE compresses well on smooth areas but poorly on the per-pixel noise typical of photographs. Expect 30-55 MB for an 8-bit PNG at full resolution, or roughly double for 16-bit. If size matters more than perfect fidelity, JPG at quality 90 will be 5-10 MB.
The camera's JPG engine bakes in white balance, picture style, sharpening, and noise reduction at the moment of capture. A CR3-to-PNG workflow lets you re-process the RAW with corrected exposure, custom WB, and modern noise-reduction algorithms first, then export to a lossless container. You get the colour decisions you actually want, locked into a format every tool can read.
Only if you export at 16-bit PNG. Most online converters (and the default here) decode CR3 to an 8-bit-per-channel intermediate before encoding PNG, which is fine for screen viewing and web delivery but discards roughly 6 bits of tonal headroom per channel. For exposure-critical work — astrophotography, HDR base layers, print prep — keep the CR3 master and only export PNG for delivery, not as your editing intermediate.
Yes. Upload all the CR3 files together; the same Quality Preset, resolution, and colour settings apply to every file in the batch, and you'll get a ZIP of PNGs back. If you need different settings per image, run separate batches.
PNG supports text and EXIF chunks (tEXt, iTXt, eXIf since PNG 1.5 / ISO 15948 amendment). Most converters will carry over basic EXIF — capture date, camera model, lens, ISO, shutter, aperture — but Canon-specific maker notes (Picture Style, Dual Pixel data, lens corrections) are stripped because no PNG reader understands them. If you need that metadata, keep the CR3 archive separately.
Yes. C-RAW files use the same .cr3 extension and are decoded the same way; the converter handles both standard RAW and C-RAW transparently. The only practical difference is that C-RAW inputs are smaller, so they upload and process faster.
Different jobs. PNG is a delivery format — it locks in your edit decisions and is universally readable, but you can't recover "I want to lift the shadows 1.5 stops" from it. DNG (Adobe's open RAW container) is an archival RAW format that preserves the original 14-bit sensor data and lets future editors re-process. Many photographers do both: DNG for the archive, PNG (or TIFF) for delivered masters.