Initializing... drag & drop files here
Supports: CR2
CR2 is Canon's raw sensor capture: a TIFF-structured container holding undemosaiced data at 12 or 14 bits per channel, which nothing on the open web displays. PNG is the opposite kind of file — a finished RGB raster defined by the W3C PNG Specification, Third Edition (published 24 June 2025, and standardised earlier as ISO/IEC 15948), supported by every browser and image editor made this century. The short answer: pick PNG when you want a compression-artefact-free copy of the rendered photo for screen use, screenshots of detail crops, or an image that will be re-edited a few times. Pick JPG when the file has to be small enough to send, and TIFF when it goes to print or into an archive.
| Property | CR2 (Canon Raw v2) | PNG (output) |
|---|---|---|
| What it holds | Undemosaiced Bayer sensor data plus maker notes | Finished RGB (or RGBA) pixels |
| Container | TIFF/IFD structure, raw payload packed with lossless JPEG | PNG datastream, DEFLATE-compressed |
| Bit depth | 12- or 14-bit per channel depending on the body | 8 or 16 bits per channel for truecolor |
| Standardised by | Nobody publicly — Canon's format, reverse-engineered by tools | W3C Recommendation / ISO/IEC 15948 |
| Editing latitude | Full: white balance, exposure, highlight recovery all still open | None: the render is baked in |
| Transparency | No — a photograph is fully opaque | Yes, an alpha channel is available (unused here) |
| Opens in a browser | No | Yes, in every current browser |
| Typical size, 24 MP frame | 20-40 MB | Tens of megabytes at full resolution |
| Best for | The master you keep and re-edit | Screen delivery, detail crops, artefact-free copies |
| Export target | Compression | Metadata carried | Best use |
|---|---|---|---|
| PNG | Lossless at the Highest preset; palette-quantised below it | eXIf chunk exists in the spec but is rarely read | Screen use, detail crops, re-saving |
| JPG | Always lossy | EXIF and ICC widely supported | Email, web upload, sharing |
| TIFF | LZW / Deflate lossless, or JPEG-in-TIFF lossy | EXIF and ICC widely supported | Print, prepress, archive |
| PPM | None at all — flat bytes | None beyond width, height and max value | Scripts, OpenCV, Netpbm pipelines |
.cr2 files onto the page or click "Add Files". This tool accepts .cr2 only, and you can queue a batch of Canon shots at once.Only at the Highest Quality Preset. PNG's compression is lossless by design, but that describes the container, not the pipeline feeding it: at the default Very High (Recommended) preset the encoder quantises the image to a reduced colour palette first, which shrinks the file substantially and is genuinely lossy before DEFLATE ever runs. If your reason for choosing PNG is "no data thrown away", set the preset to Highest — you will notice the Colors control vanish, which is the visible sign that no quantisation is happening.
JPG for anything that gets sent, uploaded or posted; PNG when the pixels themselves matter. A lossless full-resolution PNG of a detailed frame runs to tens of megabytes because there is simply a lot of unique detail in a 24-megapixel render and lossless compression can only do so much with it. JPG discards the differences a viewer cannot see and lands a few megabytes — which is why Gmail's 25 MB attachment ceiling is a real constraint for PNG and almost never one for JPG.
TIFF, in almost every case. Both can be lossless, but TIFF is what print and prepress software expects, it carries EXIF and ICC colour profiles that studio tools read reliably, and it holds several compression schemes so you can trade size against compatibility. PNG's own metadata story is thinner in practice — the Third Edition spec defines an eXIf chunk for shooting data, but it is an ancillary chunk decoders are free to ignore, and many do. Use CR2 to TIFF for the archive copy and keep the CR2 itself as the real master.
The PNG format allows 16 bits per channel, but this page has no bit-depth control — the settings shown are Quality Preset, Colors, resolution and target file size. If your requirement is specifically two bytes per sample, CR2 to PPM is the target here that exposes a Bit Depth control with a 16-bit (High Precision) option. For a high-fidelity file that other photo software understands, TIFF is the more practical answer.
Because they store different things. The CR2 holds one losslessly packed sensor mosaic — a single value per photosite. The PNG holds a fully demosaiced image with a red, green and blue sample for every pixel, so there is roughly three times as much data to compress before DEFLATE starts. Add that photographic noise and fine texture compress poorly by nature, and a full-resolution PNG routinely ends up larger than the raw that produced it. Dropping the resolution, or setting a Specific file size with Auto Scale enabled, is the fastest way to bring it down.
Do not count on it. PNG does have a standard place to put Exif — the eXIf chunk defined in the PNG Third Edition — but it is ancillary, which means a decoder is explicitly allowed to skip it, and tooling support is far patchier than for JPG or TIFF. If shutter speed, aperture, ISO, lens and GPS need to survive, export to TIFF or JPG, or simply keep the original CR2, which is the only file that also holds Canon's maker notes.
Not by itself. A CR2 is a rectangular, fully opaque photograph, so the PNG comes out opaque too — the alpha channel is there but unused. Its value is later: because PNG can carry transparency, when you mask out a background in an editor the cut-out survives the save. That is the practical reason to choose PNG over JPG for an image you intend to composite, even though the conversion itself adds nothing transparent.
Use the Specific file size control instead of the Quality Preset: name a size in megabytes and switch on Auto Scale, which lets the converter reduce the output resolution to reach your figure. Without Auto Scale the encoder can only squeeze compression settings, and a lossless-leaning format like PNG has very little room to give — so on a big frame the scaling is usually what actually gets you there.
They are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours. There is no sign-up, no watermark, and files are never shared or made public. The one thing worth planning for is upload time rather than processing: a single CR2 commonly runs 20-40 MB, so a large batch takes a while to send even on a fast connection.