CR3 to HEIF Converter

CR3 to HEIF — Two Formats Built on the Same ISO Container

This is a less exotic conversion than it looks, because the two formats are relatives. Canon's CR3 raw file is built on the ISO Base Media File Format — ISO/IEC 14496-12, the box structure that also underlies MP4 — with Canon-specific boxes and a proprietary crx payload codec. HEIF is built on exactly the same tools: ISO/IEC 23008-12 defines the Image File Format "built on tools defined in ISO/IEC 14496-12". So the conversion swaps the payload and the metadata conventions while the underlying box grammar stays in the same family.

What changes completely is what the pixels are. A CR3 holds undeveloped mosaic sensor data with real editing latitude; a HEIF holds a developed, HEVC-compressed picture. That step is one-way, and it is the only thing on this page that cannot be undone.

CR3 at a Glance

HEIF at a Glance

The consequence worth stating plainly: a .heif from this page and a .heic from the sibling route are the same file. We wrote identical source pixels to both extensions and compared them byte for byte — they matched exactly, brand heic and all. Pick the extension your destination recognises. If something rejects .heif, rename it to .heic or use CR3 to HEIC; nothing inside changes.

How to Convert CR3 to HEIF

1. Upload Your CR3 Files: Drag them onto the page or click "+ Add Files" to browse. Whole shoots can be queued; batch conversion runs every file with the same settings.
2. Pick a Quality Preset: The list runs Highest, Very High, High, Medium, Low, Very Low and Lowest, with Very High (Recommended) pre-selected. Each rung sets a numeric quality value on the HEVC encoder — the table below gives the exact mapping.
3. Or Target a Size Instead: Switch Image Compression to Specific file size and enter a figure in bytes, KB or MB; it starts at 8 MB, and the Auto Scale toggle lets the converter reduce dimensions as well as quality to reach the target.
4. Set Image resolution, Then Convert: It opens on Keep original, which keeps the full sensor resolution — nothing is downscaled unless you ask. You can also scale by percentage, take a preset height, or enter an exact Width x Height. Click Convert. Files are uploaded over an encrypted connection, developed and encoded on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.

What Each Quality Preset Sets

Two notes on reading that ladder. The values are HEVC encoder quality settings, not percentages of anything, so an equal step in the number is not an equal step in what you see. And the top of the scale is coarse: an encoder maps a range of high quality values onto the same internal quantiser, so Highest frequently produces a file barely distinguishable in size or appearance from Very High. Very High is the practical ceiling.

Note also that there is no bit-depth or chroma control on this page. A CR3 records far more tonal precision than the output can hold, so the conversion is a delivery step rather than an archival one — keep the .cr3 if the picture might be edited again.

Frequently Asked Questions

Is a .heif file different from a .heic file?

Not the one this page produces. HEIF is the container standard, ISO/IEC 23008-12; .heic is the filename convention for a HEIF whose payload is HEVC, and HEVC is exactly what gets written here. We converted the same source to both extensions and compared the bytes — identical files, both carrying the heic brand and reporting image/heic as their MIME type. In theory a .heif could hold AV1 or another codec; in practice, from this converter, it does not.

Will I lose the raw editing latitude?

Yes, entirely. A CR3 stores undeveloped sensor data — that is what lets you recover highlights, lift shadows and change white balance long after the shot. To be encoded as HEVC the file must first be developed into ordinary picture pixels, and the render bakes in the camera's recorded white balance. Once that is done the latitude is gone, exactly as it would be in a JPEG. Keep the .cr3 as your master and treat the HEIF as a delivery copy.

Does the HEIF keep my EXIF, GPS and lens data?

Standard EXIF fields do survive. We put a file carrying Make, Model, DateTimeOriginal, F-number, ISO and GPS coordinates through the same write path and read every one of them back out of the HEIF. Canon-proprietary maker notes — Picture Style, Auto Lighting Optimizer, Dual Pixel data — are stored in Canon-specific structures and generally do not carry across, because there is no standard place to put them in a HEIF.

Which quality preset should I use for a photo archive?

Very High, which is already selected, and which maps to encoder quality 95. It is close enough to the top of the scale that the difference from Highest is rarely visible or even measurable in file size, while producing a noticeably smaller file than a lossless export would. Step down to High for anything that will be shared rather than kept, and reach for Highest only when a client or a print workflow specifically asks for maximum quality.

What opens a HEIF file?

Apple platforms handle it natively — Photos, Preview, Finder thumbnails and every Apple imaging app read HEVC-coded HEIF without any extra software. Windows 10 and 11 need two components from the Microsoft Store — "HEIF Image Extensions" for the container and "HEVC Video Extensions" for the codec — and Microsoft's own guidance is that you need both even if you only intend to open photographs. Once they are installed, File Explorer thumbnails and the Photos app handle HEIF normally. Android has supported HEIF since Android 10 (2019). Browsers are the weak spot: Safari reads it and the others generally do not, so CR3 to JPG remains the answer for anything going on a web page.

Does the converter downscale my full-resolution files?

No. Image resolution opens on Keep original and the full sensor resolution is preserved — a 45-megapixel frame comes out at 45 megapixels. If you do want it smaller, the options are Resolution Percentage, a preset height, or an exact Width x Height, and reducing the pixel count is by far the most effective way to shrink a HEIF once the quality preset is already high.

Can I target an exact file size instead of a quality level?

Yes. Switch Image Compression to Specific file size, enter a figure and choose bytes, KB or MB — it opens at 8 MB. Leaving Auto Scale on lets the converter reduce the pixel dimensions as well as the encoder quality to reach your target, which usually produces a better-looking result than forcing quality down alone. Turn Auto Scale off if the output must keep its original dimensions.

Should I shoot C-RAW if my plan is HEIF export?

It works, but full CR3 gives you more room before the conversion. C-RAW is the lossy craw mode inside the same container: it applies a wavelet transform with quantisation to shrink the file, which costs some of the latitude you would otherwise use for shadow recovery and exposure correction. Stacking HEVC compression on top of that compounds the loss. If card space is the constraint C-RAW is fine; if your edits involve heavy recovery, shoot full CR3 and convert only after the edit is locked.

Why not convert to TIFF or PNG instead?

Because of size, mostly. CR3 to TIFF is the right choice when the file is going into further editing or a print pipeline — but read its Compression Type control before you convert, because it opens on JPEG, which is lossy. Switch it to LZW, Deflate or None for a genuinely artefact-free file. Either way a full-resolution TIFF from a modern Canon body runs to tens or hundreds of megabytes. HEIF at the Very High preset is a small fraction of that and visually very close. Choose TIFF for an intermediate you will edit again, HEIF for something you will keep or send.

My camera writes CR2, not CR3 — is this the right page?

No. CR2 is the older Canon raw format, TIFF-based rather than ISO-BMFF-based, and written by bodies before the DIGIC 8 generation — the 5D Mark IV, 7D Mark II, 80D and their contemporaries. The uploader matches on the extension, so a .cr2 belongs on the CR2 route. Renaming a CR2 to .cr3 does not work; the internal structures are genuinely different formats.

What happens to my photographs after the conversion?

Each CR3 is uploaded over an encrypted connection, developed and encoded on our servers, and both it and the HEIF output are deleted automatically after a few hours. Nothing is shared or made public and no account is required. Canon raws are large, so the upload is the slow part of the job — convert in modest batches rather than queueing an entire card at once.