Initializing... drag & drop files here
Supports: CRW
CRW is Canon's original digital RAW format — the unprocessed sensor file its earliest cameras wrote in the early 2000s, stored in Canon's own CIFF container rather than the TIFF-based CR2 that replaced it. AVIF is a modern still-image format built on the AV1 video codec, designed for small files at high quality. This converter bridges a 20-year gap: it reads an obsolete Canon RAW that fewer and fewer programs still open, renders it, and writes a compact AVIF you can view in almost any current browser. It is the practical way to rescue an early-digital-camera archive into a format that will still open years from now.
| Property | Value |
|---|---|
| Format | Canon RAW (CRW), Canon's first-generation RAW |
| Container | CIFF (Camera Image File Format) |
| Compression | Lossless Huffman on raw sensor data |
| Sensor / bit depth | ~10–12-bit linear sensor data (early-digital, typically 3–6 MP class) |
| First camera | Canon EOS D30 (announced May 2000, 3.1 MP) |
| Cameras using it | DSLRs up to the 10D and Digital Rebel/300D, plus PowerShot G1–G5 |
| Companion file | .thm JPEG thumbnail often written alongside |
| Native browser support | None — needs a CIFF/RAW decoder |
| Superseded by | TIFF-based CR2 (2004), then QuickTime-based CR3 (2018) |
| Property | Value |
|---|---|
| Format | AV1 Image File Format (AVIF) |
| Codec / payload | AV1 still frame in an ISOBMFF (HEIF) container |
| Standard body | Alliance for Open Media (AOMedia) |
| Released | 2019 |
| Bit depth | 8, 10, or 12-bit; this converter outputs 8-bit |
| Compression | Lossy (default here) or lossless; HDR and wide-gamut capable |
| Browser support | ~93% globally — Chrome 85+ (2020), Firefox 93+ (2021), Safari 16.4+ (2023), Edge 121+ (2024) |
| Best for | Web delivery and storage where small, high-quality stills matter |
| Trade-off | Not editable RAW — white balance and exposure are baked in |
.crw files onto the page or click "+ Add Files" to browse. Any companion .thm thumbnails are harmless if included, and you can queue a whole folder from an EOS D30, D60, 10D, 300D, or PowerShot G-series at once.No — CRW is effectively frozen, and support is thinning. Canon retired it after 2004 in favor of the TIFF-based CR2 (and later the CR3), and CRW was never updated again. Because the format predates most modern RAW pipelines and was reverse-engineered rather than publicly documented, newer photo apps increasingly drop CRW from their importers. That is the main reason to convert: getting an early-2000s Canon archive into AVIF means it stays openable even as the last CRW-aware tools disappear. Keep the original .crw files too, since they are your only full-quality source.
Yes, and it is worth understanding why. A CRW stores roughly 10–12-bit linear sensor data — the unprocessed signal that lets you recover blown highlights or re-set white balance long after the shot. Producing any standard image, AVIF included, requires the converter to demosaic that sensor data into ordinary RGB pixels and bake in white balance, exposure, and tone. The AVIF that results is a faithful render of the photo, but it is no longer editable RAW. Treat this conversion as making a viewable copy, and keep the .crw as your editable master for Canon's Digital Photo Professional or Lightroom.
For viewing, AVIF is excellent — at the "Very High" preset the difference from a full-quality render is hard to see, and AVIF holds detail far better than JPEG at the same file size because it inherits AV1's compression. The honest framing is about source, not codec: CRW files from this era came off 3–6 MP sensors (the EOS D30 was 3.1 MP), so the AVIF will be sharp and clean but limited to the resolution that small early-digital sensor captured. AVIF will not invent detail the CRW never recorded; it preserves what is there in a compact, modern file.
AVIF support is now broad: roughly 93% of browsers globally per caniuse, including Chrome 85+ (2020), Firefox 93+ (2021), Safari 16.4+ (2023), and Edge 121+ (2024). In practice any browser updated within the last few years will display it. If you need a file that opens literally everywhere — older phones, legacy image viewers, print shops — a JPEG is the safer universal target; see CRW to JPG. AVIF is the better pick when small file size and modern-quality delivery matter more than reaching the oldest software.
Choose by goal. AVIF gives you the smallest high-quality file and is ideal for web use and space-efficient storage on modern systems. If you want a viewable, shareable picture that opens on absolutely everything — which is what most people rescuing old .crw files actually need — use CRW to JPG. If your priority is an archival, lossless master that no longer depends on a CIFF decoder, CRW to TIFF preserves the rendered image without generational compression loss. Whichever you pick, keep the original .crw as your master.
Treat the AVIF as a viewable render rather than a metadata archive. The conversion's job is to demosaic and re-encode the picture; EXIF fields such as capture date, ISO, and exposure may not all carry across to the AVIF, and CRW stores some of this in CIFF-specific structures that do not map cleanly onto modern containers. If preserving the full original metadata matters to you, the reliable place for it is the .crw file itself — another reason to keep the originals after converting.
In our testing, a 3 MP CRW from an early Canon DSLR rendered at the "Very High" preset produced a compact AVIF, since AV1's still-frame compression is efficient even on detailed photos. Your file is uploaded over an encrypted connection, rendered and re-encoded to AVIF 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, since RAW files can run several megabytes each, not your device.