Initializing... drag & drop files here
Supports: CR3
CR3 is Canon Raw v3 — the unprocessed sensor capture written by EOS R, EOS M and recent EOS DSLR bodies. Canon introduced it in 2018, and it stores the capture in an ISO base-media container using a proprietary crx codec, which is exactly why almost nothing outside Canon's own software and a handful of raw editors will open one. Converting to WebP develops that raw into a finished picture that every current browser displays, at a fraction of the size. The trade-off is fixed and worth knowing before you start: developing bakes in white balance, exposure and tone, so keep the CR3 as your master and treat the WebP as a delivery copy.
.cr3 files onto the page or click "Add Files". Queue as many as you like — every file in the batch converts with the same settings..webp. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours. No sign-up, no watermark.| Property | CR3 (input) | WebP (output) |
|---|---|---|
| What it is | Canon Raw v3 — undeveloped sensor data | Finished delivery image for the web |
| Container / codec | ISO base media file format with a proprietary crx codec |
RIFF container, VP8 intra-frame coding |
| Introduced | 2018, by Canon | Announced by Google on 30 September 2010 |
| Specification | Proprietary; publicly reverse-engineered | Open, published by Google |
| Colour depth | Full sensor capture, adjustable after the fact | 8-bit — lossy uses YCbCr 4:2:0, lossless uses RGBA |
| Maximum dimensions | Whatever the sensor shot | 16,383 px per side |
| Transparency | None — it is a photographic capture | Alpha supported in both lossy and lossless |
| Editing latitude | Full: white balance, exposure and tone still open | Baked in at conversion |
| Opens without extra software | No | Chrome 32+, Firefox 65+, Edge 18+, Safari 16+ — about 96% of browsers in use |
Need the widest possible compatibility instead? CR3 to JPG opens literally anywhere. Need a lossless editable master? CR3 to TIFF. Shooting an older Canon body that writes CR2? The same develop-and-encode applies to CR2 to WebP.
The Lossless? switch does more than change file size — it changes how colour is stored. Lossy WebP encodes 8-bit YCbCr with 4:2:0 chroma subsampling, so three quarters of the colour resolution is discarded (luma detail is kept in full). That is invisible in skin, sky and foliage but it softens hard saturated edges — red text on blue, a crisp brand colour, a fine coloured line. Lossless WebP keeps full 8-bit RGBA with no chroma subsampling.
| Lossy WebP (Lossless? = No) | Lossless WebP (Lossless? = Yes) | |
|---|---|---|
| Colour storage | 8-bit YCbCr, 4:2:0 chroma subsampling | 8-bit RGBA, no subsampling |
| Size, per Google's own figures | 25–34% smaller than a JPEG at equal SSIM | 26% smaller than the equivalent PNG |
| Hard saturated edges | Slightly softened | Preserved exactly |
| Photographic subjects | Ideal — the intended use | Wasteful; several times larger for no visible gain |
| Screenshots, flat art, charts | Visible fringing | The correct choice |
| Best default for a CR3 | Yes — leave it on No | Only for a pixel-exact proof |
You lose editing latitude first, and visible quality only if you push the presets down. A CR3 holds the undeveloped sensor capture, so white balance, exposure and tone are still open decisions; developing to WebP commits all three and lands the result at 8 bits per channel. At the default Very High preset a photograph is visually very close to the developed raw. What is gone for good is the ability to re-pull a blown highlight or re-neutralise a colour cast — so keep the original CR3.
Because CR3 is proprietary. Canon built it on the ISO base media file format but wrapped the pixel data in its own crx codec, and the format has never been published — the tools that read it today do so from reverse-engineered documentation. General viewers, older editors and every browser therefore treat a .cr3 as an unknown file. Converting is the practical fix: WebP is an open format with a published specification.
Lossy, in almost every case — that is the No (Recommended) default. Google measures lossy WebP at 25–34% smaller than a JPEG at the same SSIM score, which is what you want for a gallery, a listing photo, or anything you are emailing. Choose lossless only when a pixel-exact copy matters: a proof someone will pixel-peep, or artwork with hard saturated edges that 4:2:0 chroma subsampling would fringe. Lossless WebP still runs about 26% smaller than the equivalent PNG, but several times larger than the lossy version of the same photo.
Partly at best. The WebP format can carry EXIF and colour-profile chunks, but a raw-to-WebP conversion produces a brand-new image rather than a repackaged one, so treat the shot data as expendable: the Canon maker-notes, the crx raw payload, and the developing latitude do not survive in any form. If the capture metadata matters to your archive, keep the CR3 next to the WebP rather than relying on the export.
Not one you will hit. WebP caps each side at 16,383 pixels, and no Canon body comes close: a 45-megapixel EOS R5 frame is 8192 x 5464. In practice the limit that bites is bandwidth, not the format — a full-resolution WebP of a 45-megapixel capture is still a large file to serve. Image resolution starts on "Keep original", so pick a Preset Resolution or set a Width if the picture is destined for a web page rather than an archive.
Yes. Instead of the Quality Preset, choose the Specific file size mode under Image Compression, type a target and pick Bytes, Kilobytes or Megabytes. Auto Scale sits alongside it: leave it off and the converter reaches your target by lowering encoder quality alone; turn it on and it is also allowed to reduce the pixel dimensions, which is what you want when the target is aggressive — say a 45-megapixel capture squeezed under 200 KB.
WebP is the smallest of the three at a given visual quality, and it is the right pick when the destination is a web page. Choose CR3 to JPG when maximum compatibility matters — print labs, older software and every device on earth read JPEG. Choose CR3 to PNG when you want a lossless render to keep editing, though lossless WebP does the same job about 26% smaller. For an archival master with the widest editor support, CR3 to TIFF is the conventional choice.
It is 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. The only practical limit on a big batch is upload size and time: CR3 files run tens of megabytes each, so a folder of them takes noticeably longer to send than it does to convert.