Initializing... drag & drop files here
Supports: CRW
CRW is Canon's original digital RAW — 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. TIF (TIFF) is the long-standing archival and print master format. If your goal is a lossless, print-ready copy that opens in every professional imaging tool — and a hedge against the day no software reads CRW anymore — convert to TIF and keep the .crw as your editable master. If you only need a shareable picture, a JPG or AVIF copy is smaller and opens everywhere.
| Property | CRW (Canon RAW) | TIF / TIFF (rendered output) |
|---|---|---|
| What it is | Unprocessed sensor capture (a digital negative) | Rendered raster image |
| Container | CIFF (Camera Image File Format) | TIFF — Aldus 1986, Revision 6.0 in 1992, now maintained by Adobe |
| First written by | Canon EOS D30 (announced May 2000, 3.1 MP) | Desktop publishing / scanning, mid-1980s onward |
| Sensor / source | Early-digital, typically 3–6 MP class | Whatever the render produces (full source resolution) |
| Editing latitude | Full — white balance and exposure recoverable | Limited — adjustments baked in at render |
| Compression | Lossless on raw sensor data | LZW, DEFLATE, PACKBITS (lossless) or JPEG (lossy) |
| Native browser support | None — needs a CIFF/RAW decoder | Safari only; not a web delivery format |
| Best for | Master archive, re-editing | Print, layered editing, long-term archival |
.crw is the full-quality source. Render a copy to TIF and archive the CRW alongside it..crw files onto the page or click "+ Add Files" to browse — straight off an EOS D30, D60, 10D, 300D, or a PowerShot G1–G6 / Pro1 / S30–S70. Any companion .thm thumbnails are harmless if included, and you can queue a whole folder at once..tif or .tiff spelling under "File extension" to match your workflow.Yes, and it is the one trade worth understanding before you archive. A CRW stores the unprocessed linear sensor signal — what lets you recover blown highlights or reset white balance long after the shot. To write any TIF, the converter must demosaic that data into ordinary RGB pixels and bake in white balance, exposure, and tone. With LZW or DEFLATE the resulting pixels are preserved exactly (mathematically lossless), but the latitude is not. Because these files came off cameras Canon stopped making after 2004 and may be your only copy, render a copy to TIF and keep the original .crw as your master. If you want control over the look, develop the CRW in a RAW editor first, then convert the result.
CRW is effectively frozen and support is thinning, which is the main reason to make a TIF copy. Canon retired CRW after 2004 in favor of the TIFF-based CR2 (and later CR3), and the format predates most modern RAW pipelines — it was reverse-engineered rather than publicly documented, so newer apps increasingly drop it from their importers, and some users lost CRW support outright after an OS update. A few desktop tools (Canon DPP, Adobe Camera Raw, RawTherapee, ExifTool) still read it, but those are exactly the programs that may not be around in another decade. Rendering a TIF now, while CRW decoders still exist, is a sensible preservation move. Keep the .crw files too — they are your only full-quality source.
Not if you pick a lossless compression type. The catch is the default: this converter's "Compression Type" dropdown starts on JPEG, which is lossy — leave it there and the TIF discards image data like an ordinary JPEG would. Switch to LZW or DEFLATE and the encode is mathematically lossless: every rendered pixel is preserved, the file just gets smaller without quality loss. PACKBITS is lossless too (slightly larger, maximum compatibility), and NONE writes a fully uncompressed TIF. The only unavoidable change is the RAW-to-RGB render itself, which happens no matter which target you choose.
It depends on the file's job. TIF is the right target when the copy is a preservation or print master: with LZW or DEFLATE it is losslessly compressed and reads in every professional imaging and print tool, which is exactly what a 20-year-old archive wants. The downside is that TIFF is not a web format — only Safari displays it natively, per MDN — so for sharing or the web, render a CRW to JPG copy for universal compatibility or a CRW to AVIF copy for small, current-browser delivery. Many people keep a TIF master plus a JPG or AVIF copy.
Expect it to grow, often several times over. In our testing, a full-resolution CRW from an early Canon DSLR rendered to an LZW TIF came out several times larger than the raw it started from, because the TIF stores fully rendered RGB across three color planes rather than a single sensor mosaic — and the source files themselves are already only a few megabytes from a 3–6 MP sensor. LZW or DEFLATE keeps that size in check while staying lossless; if size matters more than print fidelity, convert to JPG instead or downscale with the "Resolution Percentage" control. For irreplaceable originals, keep the .crw archived alongside the TIF.
No — they are the same TIFF file with a different spelling of the extension. Some print shops, scanners, and older Windows software expect the three-letter .tif; many modern tools accept either. Pick whichever your workflow wants under "File extension." If you specifically need the four-letter form, CRW to TIFF produces an identical file with the .tiff extension.
Your CRW is uploaded over an encrypted connection, rendered and encoded into TIF on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, and your photos are never shared or made public. The main practical limit on a big upload is its size and the time it takes to send, not your device, since RAW files run several megabytes each. For irreplaceable originals, keep the .crw archived alongside the TIF.