Initializing... drag & drop files here
Supports: CR2
This is the question for Canon DSLR shooters moving rendered photos into an Apple Photos library: keep the bulky .cr2 RAW or save a compact HEIF. Short answer — convert to HEIF when you want the iPhone-photo-native, space-efficient format that Photos and iOS handle natively; keep the original CR2 (or archive it) if you still need to re-edit exposure and white balance later, because HEIF bakes those in.
| Property | CR2 (Canon RAW) | HEIF |
|---|---|---|
| Introduced | 2004, with the Canon EOS-1D Mark II | 2015 (ISO/IEC 23008-12, MPEG-H Part 12) |
| Type | Camera RAW capture (TIFF-based container) | Still-image / image-sequence container |
| Encoding | Canon lossless JPEG over raw sensor data | HEVC-coded stills most commonly |
| Bit depth | 12 or 14 bits per channel (sensor-dependent) | 8-bit here; the format supports 10/12-bit |
| Edit latitude | High — exposure/WB still adjustable | Low — render is baked in at conversion |
| File size | Large (tens of MB per frame) | Roughly half an equivalent-quality JPEG |
| Native browser support | None | Safari 17+ only; ~14% global (per caniuse) |
| Best for | Editing masters, archival originals | Apple Photos / iOS libraries, storage-tight stills |
.heic extension rather than .heif — use CR2 to HEIC; it's the same HEVC-coded image under the Apple-branded extension..cr2 files straight off a Canon DSLR card. Batch upload works — each file is rendered and returned separately.Yes — that is the main trade-off. A CR2 holds the raw sensor data, so exposure, white balance, and highlight recovery stay adjustable. Converting renders the photo (demosaic plus your white-balance and exposure) and encodes it with HEVC, baking those choices in. The HEIF still looks great and edits non-destructively like any finished photo, but the deep RAW latitude is gone. Keep the original CR2 if you might re-grade later.
It depends on where the photos go. HEIF stores a still at roughly half the bytes of an equivalent-quality JPEG and is the format Apple Photos and iOS use natively, so it wins for Apple-ecosystem libraries and storage-tight collections. JPG wins anywhere the image must be shared or shown on the web, because only Safari 17+ renders HEIF (about 14% of browsers per caniuse). For broad sharing, CR2 to JPG is the safer pick.
Yes. This is an image-to-image conversion, so leaving Keep original selected preserves the camera's full pixel dimensions — there's no video-style downscale. A Canon DSLR file in the 20-megapixel class comes out at the same dimensions in HEIF unless you deliberately choose a Preset Resolution or scale it down to save space.
HEIC is HEIF carrying HEVC-coded stills — the specific subset Apple ships on iPhones and Macs under the .heic extension. HEIF is the broader container. This page outputs standards-compliant HEVC-coded HEIF, so the file opens wherever HEIC does; if a tool insists on the .heic extension, use CR2 to HEIC for that exact naming.
The render reflects the white balance and exposure applied during conversion, and standard EXIF (camera model, lens, focal length, ISO, capture time) carries through. What HEIF cannot carry is the raw, re-interpretable sensor data — a HEIF white balance is the one that was baked in, not a setting you can dial later as you can in the CR2.
Native support covers macOS High Sierra (10.13) and later, iOS 11+, iPadOS, Android 10+, and Windows 11 22H2+ out of the box (older Windows 10 needs the free HEIF Image Extension from the Microsoft Store). Among browsers, only Safari 17+ shows HEIF in an <img> tag. Editors like Photoshop 2022+, Affinity Photo, and Lightroom open them too. In our testing, a 20-megapixel Canon CR2 rendered at the Very High preset produced a HEIF in the low-single-digit megabytes — comfortably under half what the same render cost as a quality-matched JPEG.
Yes. RAW conversion needs demosaicing that a browser can't do on its own, so this runs through our server-backed pipeline: the file is uploaded over an encrypted connection, rendered and re-encoded on our servers, and deleted automatically a few hours after conversion. No account, no watermark, and the file is never shared or made public.