CR2 to WebP Converter
Initializing... drag & drop files here
Supports: CR2
Advanced Options - Our defaults are optimized for the best results. We recommend you keeping the defaults unless you have a specific need.
Reset to defaults
Need help?CR2 to WebP: A Canon Negative Turned Into a Web Image
A .cr2 is a digital negative — ExifTool lists the format as "Canon RAW 2 (TIFF-based)" — holding unprocessed sensor data that no browser will render and that no gallery should ever be asked to load. WebP is the opposite kind of file: a finished picture built for delivery, which Google measures at 26% smaller than an equivalent PNG when lossless, and 25–34% smaller than a comparable JPEG at equivalent SSIM quality when lossy. This page develops the raw into ordinary pixels and re-encodes them as WebP. The trade you are making is deliberate — you gain a file that loads fast and opens everywhere, and you give up the raw's editing latitude, so keep the original .cr2 as your master.
How to Convert CR2 to WebP
- Upload Your CR2 File: Drag your
.cr2files onto the page or click "+ Add Files". A whole shoot can be queued at once and every file is converted with the same settings. - Set the Quality Preset: Image Compression opens on the "Very High (Recommended)" Quality preset, with Highest through Lowest available. Switch to "Specific file size" instead if you need to hit an exact figure in bytes, kilobytes or megabytes, and turn on Auto Scale there to let the resolution drop when the quality alone cannot reach the target.
- Decide Lossless and Resolution: Lossless? is set to "No (Recommended)", so the default output is lossy WebP; switch it to "Yes" for a pixel-exact encode. Image resolution starts on "Keep original" and also accepts a percentage, a preset height such as 1080p, a width or height in pixels, or an explicit Width x Height.
- Convert and Download: Click Convert and save the
.webp. Your file is uploaded over an encrypted connection, converted on our servers and deleted automatically a few hours later — no sign-up, no watermark.
Lossy or Lossless: What the Toggle Really Changes
| Behaviour | Lossless? = No (default) | Lossless? = Yes |
|---|---|---|
| Colour handling | 8-bit Y'CbCr with 4:2:0 chroma subsampling | Full RGBA, no subsampling |
| Pixels preserved | Approximated, guided by the Quality preset | Exactly as rendered |
| Typical size against the usual rival | 25–34% smaller than a comparable JPEG | 26% smaller than the same PNG |
| Fine saturated detail | Slightly softened, most visible on red text and hard colour edges | Held exactly |
| Quality preset still applies | Yes, it drives the encoder | No, there is nothing to trade away |
| Re-encoding later | Compounds the loss each time | Reproduces the same pixels every time |
| Sensible use | Websites, galleries, client proofs, anything shipped to a browser | A working copy that will be edited again, or flat graphic content |
CR2 and WebP Side by Side
| Property | CR2 | WebP |
|---|---|---|
| Kind of file | Raw sensor capture, a digital negative | Finished, compressed delivery image |
| Structure | TIFF-based container, per ExifTool's format list | RIFF-based container from Google, built on On2 technology |
| Bit depth | 12–14 bits per channel is typical for Canon raw | 8 bits per channel |
| Editing latitude | Full — white balance, exposure and highlight recovery are still open | None, the render is baked in |
| Transparency | No, a sensor capture is opaque | Yes, an 8-bit alpha channel |
| Maximum dimensions | Whatever the sensor recorded | 16383 x 16383 pixels |
| Animation | Not applicable, a single capture | Supported by the format; this page writes a single still |
| Opens in a browser | No | Yes — 96.18% of tracked browsers per caniuse |
| Right for | Editing and archiving the shot | Publishing and sharing the shot |
Frequently Asked Questions
Will converting CR2 to WebP lose image quality?
Something is always given up, but not necessarily what people expect. Even with Lossless? set to Yes the WebP is only pixel-exact against the rendered image: WebP stores 8 bits per channel, while a Canon raw typically holds 12 to 14, so the extra tonal headroom that lets you rescue a blown sky or re-judge white balance is gone the moment the raw is developed. Leaving the default lossy setting adds ordinary compression on top of that, which at the "Very High" preset is not visible at normal viewing sizes.
Should I turn Lossless on for photographs?
Usually not. Lossless WebP is designed for flat, hard-edged content and for master copies that will be edited again, and on a photograph it produces a much larger file for a difference nobody sees on screen. Leave Lossless? on "No (Recommended)" for anything going to a website, a gallery or a client, and reach for Yes only when the WebP is standing in as a working file.
Why is the WebP so dramatically smaller than the CR2?
Because they store completely different things. A CR2 keeps one unprocessed value per sensor photosite at 12–14 bits along with the camera's full metadata, all of it kept so the image can be re-developed later. A WebP keeps only the finished picture, at 8 bits per channel, compressed for viewing. Nothing is being thrown away carelessly — the raw's job was to hold options open, and the WebP's job is to be looked at.
Can I hit an exact file size, such as 500 KB?
Yes. Switch Image Compression from the Quality preset to "Specific file size", type the figure and choose Bytes, Kilobytes or Megabytes. If the target is aggressive for the image's dimensions, enable Auto Scale in the same panel so the converter is allowed to reduce resolution as well as quality — without it, a very small target on a full-resolution raw leaves the encoder nothing to give.
Which browsers and apps will open the WebP?
Effectively all current ones. caniuse puts WebP at 96.18% of tracked browsers, with full support in Chrome from version 32, Firefox from 65, Edge from 18, and Safari from 16 — Safari 14 and 15 handle it partially. Desktop editors caught up more slowly than browsers, so if a file is going to somebody using an older version of a photo tool, CR2 to JPG remains the safest hand-off.
Is there a maximum image size WebP can hold?
Yes: Google's WebP FAQ puts the ceiling at 16383 x 16383 pixels. No Canon raw comes close — even a 100-megapixel capture is well under that on either axis — so in practice the limit only matters for stitched panoramas and scanned artwork, which can exceed it. If you are converting a very large stitch rather than a single frame, check the pixel dimensions first.
The colours look different from Canon's Digital Photo Professional. Why?
Because a raw file has no single correct appearance. Every converter applies its own demosaicing, white balance interpretation and tone curve, and Canon's own software applies the picture style recorded by the camera. What you are seeing is a different, equally valid rendering of the same sensor data. If a specific look matters, develop the raw in your editor of choice first, export a rendered image, and convert that instead of the .cr2.
Should I be exporting WebP at all, or something else?
WebP is the right answer when the destination is a browser and you want the smallest file that still looks right. Choose CR2 to JPG when the file has to be openable by absolutely anything, CR2 to PNG when you need a lossless still with an alpha channel, and CR2 to AVIF when you want to push web file sizes further still at the cost of some older-browser reach. Already sitting on finished WebP files that are too heavy? Run them through WebP compression rather than converting again.