CRW to JFIF Converter

CRW to JFIF: What to Check Before You Batch a Whole Card

Converting a Canon CRW raw file to .jfif gives you a plain JPEG that everything can open. That part is easy. What catches people out is what the conversion drops on the way, and both of the losses are silent — no warning, no error, just a file that is subtly wrong if you were not expecting it. This page leads with those two, then gives the measured numbers for the quality settings, then the format background.

Two Things the Conversion Drops

Portrait shots come out sideways. A CRW records the camera's rotation in its own CIFF metadata rather than in a standard EXIF orientation tag, and the raw decoder here does not act on it. We converted a real Canon EOS 300D file whose metadata reads Rotation: 270 — a portrait frame — and the output was 3088 × 2056 landscape with its orientation tag set to "Horizontal (normal)". The picture is intact; it is simply lying on its side. Rotating it afterwards with Rotate JPG, which accepts .jfif as well as .jpg, is a lossless-enough fix and takes one click.

Every camera setting is gone. The source file carried Make: Canon, Camera Model Name: Canon EOS 300D DIGITAL, ISO: 100, exposure time, aperture and the original capture date. The .jfif output carried none of them. What survives is a minimal EXIF block — orientation, resolution unit and the pixel dimensions — and nothing else. If the shot date or the exposure data matters to you, read it out of the CRW before you convert, or keep the CRW.

How to Convert CRW to JFIF

1. Upload Your CRW File: Drag the .crw file onto the page or click "+ Add Files"; a whole shoot can be queued and every file gets the same settings. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.
2. Pick a Quality Preset: Seven rungs from Highest to Lowest, opening on "Very High (Recommended)". The measured cost of each is in the table below, and the step from High to Medium is the one that changes the picture most.
3. Or Set a Specific File Size: Switch Image Compression to "Specific file size", type a byte target and choose B, KB or MB. The Auto Scale toggle lets the encoder shrink the pixel dimensions too if the quality alone cannot reach your target.
4. Set the Image Resolution and Convert: "Keep original" is preselected and gives you the decoder's full output. Resolution Percentage, height presets and explicit Width, Height or Width × Height are there for downscaling. Click Convert to download.

What Each Quality Preset Costs

Measured on a real Canon EOS 300D .crw (8,389,842 bytes, decoding to 3088 × 2056), converted at every rung:

The chroma column explains the cliff. At quality 90 and above the encoder keeps colour at full resolution; at 80 and below it halves the colour resolution in both directions, which is where half the file size disappears between High and Medium. On a landscape or portrait photograph that is usually invisible. On saturated edges — red fabric against sky, coloured text, fine foliage — it is the first artefact you will notice. Stay at High or above if the file is going to be edited again.

CRW at a Glance

One quirk shows up as soon as you convert. Our test file's own EXIF reports 3072 × 2048 — the size of the JPEG the camera would have produced — but the raw decoder outputs 3088 × 2056, sixteen columns and eight rows more. Those extra pixels are the sensor's border area that in-camera processing crops away. They are real image data, usually slightly darker at the very edge, and you can trim them with the Width × Height inputs if you want to match the camera's framing exactly.

Frequently Asked Questions

Is a .jfif file different from a .jpg file?

No. JFIF is the packaging convention that JPEG itself never specified — colour space, aspect ratio, where the file starts — and .jpg is simply the extension that won. Both carry the same baseline JPEG data and the same image/jpeg MIME type, so renaming between them changes nothing inside the file. If nothing has specifically asked you for .jfif, CRW to JPG gives you the same picture with an extension that upload forms argue about less.

Does the output actually contain a JFIF header?

Not literally, and it is worth knowing if you are feeding a system that inspects file structure. The file we produced starts FF D8 FF E1 … Exif — a baseline JPEG whose first marker segment is an EXIF APP1 block, not the classic JFIF APP0 segment, and the string JFIF does not appear in the header at all. Every JPEG decoder reads it identically. Only a validator that insists on seeing the literal JFIF identifier would object, and re-saving through an editor that writes one fixes that.

Why does my converted photo look flatter than the camera's own JPEG?

Because you are seeing the raw data with a neutral rendering rather than Canon's picture style. A CRW holds one brightness value per photosite with no tone curve, no saturation boost and no sharpening applied; the camera's own JPEG engine adds all three. A default conversion demosaics and white-balances but does not try to imitate Canon's look, so the result is lower contrast by design. That flatness is headroom — it is easier to add contrast afterwards than to recover a clipped highlight.

Can I fix the sideways orientation before converting?

Not reliably on this page. The per-file rotate control operates on the uploaded file, and there is no way to write a rotated .crw back out, so the rotation cannot be applied to a raw source. Convert first, then rotate the JPEG — Rotate JPG takes .jfif files directly and a 90° or 270° turn on a JPEG is a cheap, near-lossless operation. If you are batching a mixed shoot, sort the portrait frames into their own run so you can rotate them together.

Which cameras produced CRW files?

Canon's first digital SLR generation and the higher-end compacts of the same era: the EOS D30, D60, 10D and 300D / Digital Rebel, plus the PowerShot G1 through G6 and the S30–S70 series. Canon retired the format in 2004 in favour of CR2, which is built on TIFF rather than CIFF. If your file is from a later body it is almost certainly a .cr2 or .cr3 and belongs on the tool for that format instead.

Will the file be smaller than the CRW?

At most settings, yes. Our 8.4 MB source came out at 3.2 MB at Very High, 2.2 MB at High and 1.1 MB at Medium. The exception is Highest, which produced a 7.6 MB JPEG — quality 100 spends bits on detail that a 6-megapixel sensor never resolved, and gets you within striking distance of the raw file's size while still being lossy. There is very little reason to choose it.

What happened to the white balance the camera recorded?

It is applied, not preserved. The decoder reads the shot's white-balance information while demosaicing and bakes the resulting colour into the JPEG, after which the file is an ordinary sRGB image with no adjustable interpretation left. That is the fundamental trade of converting raw to JPEG: you gain a file everything opens and lose the ability to change your mind about exposure and colour later. Keep the CRW if there is any chance you will want to.

Can I convert an entire memory card's worth of CRW files at once?

Yes — queue them together and each produces its own .jfif at the same Quality Preset and resolution. Two things to plan for. A card of 6-megapixel raws is several hundred megabytes, so upload time rather than processing is the limit. And because portrait frames come out sideways, it is worth doing a single test file first to see how many of yours are affected before committing the whole batch.