How to Convert CR2 to JPEG on a Mac (2026 Guide)

Published September 16, 2026 · Daniel Tello · RevelRaw

A print shop, a client portal or a forum upload just refused your .CR2 file, and now you need a JPEG. Your Mac can make one without installing anything, and it can do a whole card in a few minutes. To find out exactly what you get, we converted 11 real CR2 files from five Canon bodies on macOS 27 and logged every number: how long each took, how big the JPEGs came out at three quality settings, what happened to the color profile and the EXIF, and the one kind of CR2 that macOS quietly gets wrong.

One thing to know before you pick a method. A CR2 is the RAW file Canon's DSLRs wrote from 2004 until the CR3 took over in 2018; our CR2 explainer has the details, and if your camera writes .CR3 instead, the CR3 guide is the one you want. Every CR2 already contains a full-size JPEG, made by the camera with your Picture Style applied. So "converting" is really choosing whose rendering you want: the camera's, Apple's, or your own.

The short version

Method 1: Preview

1. Double-click the .CR2 file. It opens in Preview.
2. Choose File > Export…
3. Set Format to JPEG, drag the Quality slider toward Best, and save.

Preview exports at full resolution. It renders Apple's interpretation of the RAW data: not your Picture Style, and none of your intent. It works for every CR2-era Canon on Apple's support list as of July 2026: the 5D Mark II through Mark IV, the 6D and 6D Mark II, the 7D and 7D Mark II, the 70D, 77D and 80D, the 800D and 2000D (Rebel T7i and T7) and the EOS M family. If Preview refuses a file, our guide to opening CR2 files on a Mac covers the fixes.

Method 2: Photos

1. Drag the CR2 files into Photos.
2. Select them, then choose File > Export > Export Photos…
3. Pick JPEG, set JPEG Quality to Maximum, and choose a destination.

Photos handles a batch and remembers every file in your library, which you may want or may resent. The import copies every RAW into the library, so a 400-shot card costs the disk space twice. Same rendering as Preview: Apple's, unedited. If you ever want the untouched CR2 back out, File > Export > Export Unmodified Original writes the original file.

Method 3: sips, for whole folders

macOS ships with a command-line image tool called sips. Open Terminal, cd into the folder with your RAW files, and run:

sips -s format jpeg -s formatOptions 90 photo.CR2 --out photo.jpg

To convert every CR2 in the folder into a new folder called jpeg, no loop required:

mkdir jpeg
sips -s format jpeg -s formatOptions 90 *.CR2 --out jpeg/

sips prints a warning per file that the output suffix changed to .jpg. That is the point; ignore it. The formatOptions number is JPEG quality from 0 to 100, and best means the same thing as 100. We checked: the two produce byte-identical files.

Two things the other guides don't mention. First, sips doesn't officially list RAW as an input at all; its manual names JPEG, TIFF, PNG and a few others. It converts CR2 because the same macOS RAW rendering behind Preview sits underneath it, which is also why it inherits Apple's camera list and Apple's look. Second, the JPEG it writes is tagged Display P3, not sRGB, on every standard CR2 we tried. Phones and browsers mostly cope, but if the file is headed for a platform that strips profiles, ask for sRGB as you convert:

sips -s format jpeg -s formatOptions 90 -m "/System/Library/ColorSync/Profiles/sRGB Profile.icc" photo.CR2 --out photo.jpg

Speed, measured on an Apple-silicon Mac running macOS 27.0 (one file per command, quality 90):

JPEG size follows the scene more than the megapixels, which is why the 30-megapixel snow scene came out smaller than the 24-megapixel ones. Six files from five bodies in one command took 2.2 seconds. A 400-shot card is under three minutes. Nothing installs, nothing uploads, nothing leaves your Mac.

Method 4: Pull out the JPEG the camera already made

Every CR2 carries a finished JPEG inside it, at full sensor resolution, rendered by the camera with your Picture Style and white balance exactly as the back-of-camera screen showed them. On our samples it ran from 2.0 MB (5D Mark II) to 5.5 MB (Rebel T7). Pulling it out recompresses nothing, so there is no quality decision to make.

Our free RAW to JPEG converter does exactly this in your browser: drop the CR2 in and it hands back the embedded JPEG. Nothing uploads. If you have exiftool installed, the same thing from Terminal is:

exiftool -b -PreviewImage photo.CR2 > photo.jpg

Two catches. The extracted JPEG carries no EXIF at all, not even the camera model or the date, so if you need metadata this is the wrong route. And it is the camera's rendering at the camera's JPEG quality, which you cannot change after the fact. It is the honest answer to "fastest", and the only honest answer to "without losing quality". It is not the answer to "best".

Method 5: Edit first, then export

Our app, so judge accordingly. The four methods above convert the file; none of them let you decide how the photograph looks first. RevelRaw is a native macOS editor for every major camera brand. It opens the .CR2, ranks 40+ presets against the scene it detects in your photo, gives you the standard controls to fine-tune, and exports JPEG, PNG, TIFF or HEIF at full resolution with presets for Instagram, web and print. Everything stays on your Mac. The download is free and includes one full-quality export. It edits one photo at a time, so for a whole card of straight conversions it is the wrong tool; use sips.

Canon's own Digital Photo Professional is the other editor worth naming. It is free, it renders your Picture Style the way the camera would, and it batch-converts to JPEG or TIFF. Version 4.21.30 from July 2026 runs on macOS 26, 15 and 14. It is slow and it looks its age, but it is the converter Canon built for Dual Pixel RAW files, which sips treats as an ordinary 30-megapixel RAW.

What we found converting 11 CR2 files

We pulled public-domain sample files from raw.pixls.us for five bodies (5D Mark II, 5D Mark IV, 6D Mark II, 80D, Rebel T7), including Canon's smaller sRAW and mRAW flavors, a Dual Pixel RAW file and an in-camera multiple exposure, and ran every one through sips on macOS 27.0 on September 16, 2026. Everything below comes from that run.

Quality 100 costs three to five times the space of quality 90

The 80D file came out at 31.5 MB at quality 100, 10.7 MB at 90 and 8.5 MB at 80. The 5D Mark IV Dual Pixel RAW file: 20.9 MB, 4.3 MB and 3.1 MB. The 5D Mark IV sRAW2 file: 5.9 MB, 1.1 MB and 0.8 MB, the same shape at a quarter of the pixels. On every body the quality-100 file was roughly three to five times the quality-90 file: closest to three on the 80D and the Rebel T7, a little over five on the sRAW2 file. Quality 100 is not lossless; JPEG has no lossless mode. It is the same compression with the discarding turned nearly off, which is why the file balloons for detail you will struggle to find. Use 90 for anything you will look at on a screen. Dropping to 80 saves roughly another 20 to 30 percent.

macOS writes Display P3, and Adobe RGB for sRAW

Every source file was set to sRGB in camera. In our September 2026 test on macOS 27, every standard-RAW JPEG that sips produced came out tagged Display P3, and every sRAW or mRAW JPEG came out tagged Adobe RGB (1998), across all three bodies that shoot those flavors. Apple doesn't document why, and we won't guess. It is harmless anywhere the profile is honored, and it is the reason some exports look dull after an upload strips the profile. The -m flag above fixes it at conversion time; our Instagram export guide has the rest of the recipe.

The JPEG keeps your camera and lens, loses your Picture Style

The sips JPEG kept the make, model, capture time, lens, focal length, exposure, orientation, and the camera's serial number. It dropped Canon's MakerNotes, the maker-specific block where the Picture Style, sharpness and color tone settings live: converting the 80D file with sips took its metadata from 349 tags to 124. We did not test Preview's or Photos' exports separately. None of our samples carried GPS, so we cannot tell you whether location survives; check one file with our EXIF viewer before you send a batch anywhere.

sRAW and mRAW convert at their smaller size, but the preview inside is still full-size

If you shot in Canon's reduced-size RAW modes, sips outputs the size the camera actually recorded: 3360×2240 for a 5D Mark IV sRAW2, 5040×3360 for mRAW, 3000×2000 for an 80D sRAW2. The embedded preview is still the full 6720×4480 or 6000×4000 on those files. So on an sRAW file, method 4 hands you more pixels than method 3. That preview is the camera's own JPEG of the same exposure, and it is the only full-resolution image left in an sRAW file.

Dual Pixel RAW: twice the file, same result

The 5D Mark IV Dual Pixel RAW sample was 62 MB against 34 MB for a standard RAW from the same body. sips converted it at the same 6720×4480, in the same 0.4 seconds, to a JPEG within 100 KB of the standard one (4.3 MB against 4.4 MB at quality 90), and the result was identical on a second run. The embedded preview inside it is the same full-size camera JPEG as in any other CR2. sips does nothing with the second image Canon stores in that file; it treats it as an ordinary 30-megapixel RAW. Canon's DPP is the tool built to use it.

The one CR2 that macOS gets wrong: in-camera multiple exposures

A 5D Mark IV CR2 shot as an in-camera multiple exposure (two frames combined additively, a mode many EOS bodies offer) came out of sips as a black frame when converted alone and as a smear of neon color blocks when converted in a batch, with the file size changing on every run. Quick Look showed the photo correctly, and so did the embedded JPEG. If a CR2 converts to black on your Mac, check the file for a "Multi Exposure" entry in the EXIF viewer, then use method 4 or Canon's DPP for that frame. We have not tested Preview or Photos on that file.

"Without losing quality," honestly

Every guide on the subject promises it, and most admit in their own FAQ that it isn't true. Here is what you actually lose. A CR2 stores 12 to 14 bits per color channel; a JPEG stores 8. Those extra bits are not more colors, they are headroom: the room to pull a stop or two out of the shadows, or to change the white balance after the fact, without the image falling apart (DPReview, 2017). Once you are in the JPEG that latitude is gone, and the compression discards fine detail on top. The quality setting controls the second part. The first part is unavoidable, and it is the reason to keep the CR2. As long as the negative exists, the JPEG is disposable and you can re-export at any settings later.

Online converters, if you must

You do not need one. Every method above runs on your Mac, and the free web tools worth using run inside your browser. If you use an upload service anyway, know the terms as of September 2026: FreeConvert deletes uploads after 8 hours; CloudConvert within 24 hours, with free files capped at 1 GB; Convertio's free tier stops at 100 MB per file; Zamzar's stops at 50 MB, which a Dual Pixel RAW file from a 5D Mark IV already exceeds, and it keeps the result for 24 hours. A 40 MB RAW of someone's wedding on a server for a day is a choice, not a necessity.

FAQ

How do I convert CR2 to JPEG on a Mac for free?

Open the file in Preview, choose File > Export, pick JPEG and set the quality slider. For a whole folder, run sips -s format jpeg -s formatOptions 90 *.CR2 --out jpeg/ in Terminal. Both ship with macOS. Canon's free Digital Photo Professional also converts, with your Picture Style rendered.

Does converting CR2 to JPEG lose quality?

Yes, by design. A CR2 holds 12 to 14 bits per channel and a JPEG holds 8, so the editing headroom goes first, and JPEG compression discards fine detail on top. In our tests quality 90 produced files a fifth to a third the size of quality 100, on every body. Keep the CR2 and you lose nothing permanently.

Can I batch convert hundreds of CR2 files at once?

Yes. One sips command handles a whole folder: sips -s format jpeg -s formatOptions 90 *.CR2 --out jpeg/. On an Apple-silicon Mac running macOS 27 it averaged about 0.4 seconds per file across six files from five bodies, so a 400-shot card takes under three minutes. Photos and Canon's DPP also batch-export.

Does the JPEG keep the EXIF data?

Mostly. In our test the sips JPEG kept camera, lens, exposure, date and serial number but dropped Canon's maker data, including the Picture Style. A JPEG pulled straight out of the CR2 with exiftool or our free converter carries no EXIF at all. Location data was untested; check a file in our EXIF viewer.

Why does the converted JPEG look different from the camera's JPEG?

Preview, Photos and sips all use Apple's RAW rendering, which applies Apple's defaults rather than your Picture Style. The camera's own rendering is the JPEG embedded in the CR2; extract that, or use Canon's DPP, if you want the photo to match the back of the camera.

Why did my CR2 convert to a black image?

Check whether it was shot as an in-camera multiple exposure. In our test a 5D Mark IV multiple-exposure CR2 rendered black or corrupted in sips while Quick Look and the embedded preview displayed it correctly. Extract the embedded JPEG or convert that frame in Canon's DPP.

Should I convert CR2 to JPEG, TIFF or PNG?

JPEG for anything you will share or upload. TIFF (16-bit) if a print lab or a retoucher asked for it and you want to keep the headroom; the files are huge. PNG gains you nothing for photographs. Whatever you choose, keep the CR2 as the negative.

Related reading: Convert RAW to JPEG on a Mac, any camera · How to open CR2 files on a Mac · What is a CR2 file? · Canon CR2 RAW editor for macOS · Canon RAW editing on a Mac · Free RAW to JPEG converter