CR2 to HEVC Converter

Convert CR2 to HEVC: What This Tutorial Covers

CR2 is Canon's second-generation RAW photo — the unprocessed 14-bit sensor data a Canon DSLR wrote before any white balance or exposure was baked in — and .hevc names a codec rather than a container: H.265, High Efficiency Video Coding. This converter encodes your photo as H.265, writes it into a Matroska structure, and gives the file the .hevc extension. This is an unusual target, and two things trip people up. First, a still photo becomes one motionless frame held for a set time, with no audio. Second, almost no consumer software recognises .hevc as a video extension, so phone galleries, the Windows Photos app, and many editors refuse the file by name even though there is an ordinary video inside it. This tutorial walks through the conversion, explains both surprises, and points you to the conversions almost everyone actually wants instead.

How to Convert CR2 to HEVC

1. Upload Your CR2 File: Drag and drop your .cr2 file onto the page or click "+ Add Files" to browse from your computer. You can queue several Canon photos at once.
2. Set Duration and Merge Strategy: Open Advanced Options. Use "Duration" to control how long the still shows — from 1/60s per frame up to 10 seconds, with "5 seconds per frame" the default — and use "Merge strategy" to pick "Merge images" (combine several photos into one file) or "Video per image" (a separate file each).
3. Pick Quality and Background (Optional): Keep "Quality Preset" on "Very High (Recommended)", and set a "Background Color" (White by default) to fill any letterbox area where your photo's shape doesn't match the output frame. Under "Show All Options" the "Video Codec" is set to H.265 (listed as H.265 / HEVC), which is what gives the download its .hevc name.
4. Convert and Download: Click "Convert" and download your .hevc file. No sign-up, no watermark.

Walk-through: What "Render", "Still Frame", and the .hevc Name Mean Here

Three one-way facts shape what you get, and all three are easy to miss:

• The RAW gets rendered first. A CR2 stores raw sensor data with wide editing latitude — you can recover highlights, shift white balance, and push exposure long after the shot. To encode it as video, it has to be demosaiced into ordinary RGB pixels, and the current white balance and exposure are baked in. The default H.265 Main profile is 8-bit 4:2:0, so the 14-bit latitude does not survive into the encoded video. Render once and keep the original CR2 as your master.
• The output is one frame held still, not a clip. The file shows your single photo as a steady image for the duration you set — no panning, no zoom, no transition, and no audio. Setting "Duration" to 5 seconds simply presents the same frame for 5 seconds. Because a motionless frame barely changes between samples, H.265 compresses it heavily.
• The .hevc extension is the obstacle, not the file's contents. Because .hevc is a codec name rather than a registered container extension, the pipeline muxes the encoded H.265 into a Matroska structure and then labels the download .hevc. The picture, frame timing, and seek information are all present. What is missing is recognition: software that decides what to do from the extension alone has no rule for .hevc and will not even try. Players that identify a container by inspecting its contents — VLC and mpv, for instance — open it without complaint, and renaming the file to .mkv makes the rest of your software recognise it too.

A few patterns cover most real needs once you accept those facts:

• If something downstream only cares that the video is H.265, this is the shortest route to it, and ffmpeg -i input.hevc -c copy output.mp4 re-wraps it into MP4 without touching a single pixel — -c copy remuxes rather than re-encodes, so there is no second generation of loss.
• If you want something that simply plays, stop here and use CR2 to MP4 instead — same H.265-capable pipeline, but the result is packaged in a container that opens everywhere.
• If you are converting a batch into one file, "Merge images" concatenates each rendered photo in upload order; "Video per image" outputs a separate file per photo.

CR2 at a Glance

.hevc Output vs an Ordinary MP4

Both files hold the same rendered photo. The difference is the wrapper and, more importantly, the name your software reads.

Common Errors and How to Fix Them

• "The .hevc file won't open / my player shows an error" — Expected, and usually fixed in one step. QuickTime, the Windows Photos app, mobile galleries, browsers, and most editors match files by extension, and .hevc is not on their list, so they stop before reading the file. Rename the download to .mkv and the identical bytes open in anything that plays Matroska; VLC and mpv identify the container by content and generally play it without renaming. If you want a file that works everywhere with no renaming, use CR2 to MP4 instead.
• "There is no audio" — Correct. A still-image-to-video conversion writes no audio track, so the "Audio Codec" option does not appear for this conversion. If you need sound, rename or remux the file to .mkv or .mp4 and lay a track over it in an editor.
• "The photo has white bars" — Your CR2's aspect ratio doesn't match the chosen output size, so the encoder pads the gap with the "Background Color" (white by default) rather than stretching or cropping. Pick another color, or match the output resolution to your photo's shape.
• "Colors or exposure look off versus my RAW editor" — The stream uses the baked-in 8-bit render, not your editor's interpretation of the RAW. Adjust white balance and exposure in a RAW editor first, export a rendered image, and convert that.
• "My file is .cr3, not .cr2" — This page is tuned for CR2, which Canon DSLRs recorded from around 2004 through the mid-2010s. Newer mirrorless EOS R bodies record .cr3; use a CR3 converter for those.

When This Doesn't Work — and What to Use Instead

For almost everyone, .hevc is the wrong target for a Canon photo. If you only want a viewable, shareable picture, convert to an image with CR2 to JPG and keep the original .cr2 as your editable master — no video at all, and a far smaller file. If you want a video clip that actually plays, use CR2 to MP4: the same H.265 encoding can sit inside that MP4 container, but the file opens on phones, browsers, TVs, and editors instead of only in players that probe file contents. Pick .hevc only when something downstream specifically asks for a file with that name — an encoder benchmark, a codec-conformance check, or a low-level pipeline that keys off the extension. And if you picked it by accident, you do not have to convert again: rename the download to .mkv, or remux it with ffmpeg -c copy, and the video is immediately usable.

Frequently Asked Questions

Why won't my .hevc file play in QuickTime or my phone's gallery?

Because of the extension, not the contents. .hevc is a codec name, and QuickTime, the Windows Photos app, phone galleries, browsers, and most editors decide whether to attempt a file from a list of container extensions they recognise. .hevc is not on that list, so they refuse it before ever looking inside. The download itself is a Matroska-structured file holding an H.265 video track. Rename it to .mkv and it opens in anything that plays MKV; VLC and mpv identify the container by inspecting the file and generally play it as-is. For something that opens everywhere without renaming, use CR2 to MP4.

Can I just rename the .hevc file to .mkv?

Yes, and that is the quickest fix. This converter muxes the H.265 video into a Matroska structure and then applies the .hevc name, so changing the extension to .mkv matches the file to what is actually inside it — no re-encoding, no quality change, no re-upload. If you would rather have an MP4, remux instead of converting: ffmpeg -i input.hevc -c copy output.mp4 copies the encoded frames straight across into the MP4 container, which is instant and lossless because nothing is decoded and re-compressed.

What is the difference between a .hevc file and an MP4 with H.265 inside?

They share the same video codec — H.265/HEVC — and differ only in the wrapper and the name. This tool's .hevc output is H.265 video muxed into a Matroska structure and given a codec-shaped extension. An MP4 puts the same encoded frames into the ISO base media container that Apple, Google, Microsoft, and every browser register by default. The pixels are identical; the MP4 is simply the one your software will agree to open, which is why CR2 to MP4 is the better pick for anything you intend to watch or share.

Does the HEVC output have any motion or sound?

No. The conversion takes one CR2 photo and encodes it as a static image held for the duration you set. There is no panning, zoom, or animation, and the stream carries no audio track. If you choose "Merge images" with several photos, they encode back to back, but each frame is still a static image shown for its set duration, with no transitions between them.

Do I lose the RAW editing latitude when I convert CR2 to HEVC?

Yes. A CR2 stores unprocessed 14-bit sensor data, which is why you can recover highlights, shadows, and white balance after the shot. To encode the photo as H.265, the converter renders it first — demosaicing the sensor data and baking in white balance, exposure, and tone — and the default Main profile is 8-bit. Once that rendered frame is inside the stream, the latitude is gone. Keep your original .cr2 if you may still want to edit it.

Which codec and profile does this use, and how does H.265 compare to H.264?

It uses H.265 (HEVC), the codec the .hevc extension implies; under "Show All Options" the "Video Codec" is set to H.265 by default. H.265 was standardized by ITU-T and ISO/IEC in 2013 as the successor to H.264/AVC, and it reaches roughly the same visual quality at about half the bitrate. For a single motionless frame the bitrate savings barely matter, but the codec choice is why the output carries the .hevc name instead of being an H.264 file. The default Main profile encodes 8-bit 4:2:0; Main 10 would carry 10-bit, but a rendered CR2 here is delivered as 8-bit.

What size will the output be, and how do I change how long the photo shows?

"Duration" controls the hold — options run from 1/60s (a single frame at 60 fps) through whole seconds up to 10 seconds per frame, with 5 seconds the default. Picture size follows "Video resolution", which starts on "Keep original" so a full-resolution Canon frame is encoded at its native size; switch to "Preset Resolutions" for a standard target such as 1080p or 4K UHD, or "Width x Height" for an exact figure. If your photo's shape does not match the chosen frame, the gap is filled with the "Background Color" rather than being stretched or cropped. Because the picture never changes between samples, a longer duration adds far less to the file than the same duration of real footage would.

How are my files handled during conversion?

In our testing, a single full-resolution Canon CR2 held for 5 seconds at the "Very High" preset produced a .hevc file only a couple of megabytes in size, because a motionless H.265 frame compresses heavily. Your file is uploaded over an encrypted connection, rendered and encoded on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, never shared or made public. The main practical limit is upload size and time, not your device.