Skip to content

JXL to CR2 Converter

Convert JXL to CR2 in your browser. You download a Linear DNG (.dng), not a .cr2: only a Canon camera can create a genuine CR2, and every editor that opens CR2 also opens DNG. Nothing is uploaded.

  • Processed locally
  • No upload, no wait
  • No sign-up
  • No watermark

Drop images here

or choose files · paste with Ctrl/⌘ V

JXL expected · other image formats also work

Files are processed on this device. Nothing is uploaded.0 B uploaded

How to use JXL to CR2

  1. 1

    Add your JXL files: drop them here, choose them, or paste from the clipboard.

  2. 2

    Pick the colour that replaces transparent areas, since DNG has none.

  3. 3

    Click Convert. Each file is decoded and encoded in a background thread on this device.

  4. 4

    Download the .dng files one at a time or together as a ZIP.

Why use Aback Images for jxl to cr2

Where a CR2 would go

CR2 files are opened by Canon Digital Photo Professional, Lightroom, Photoshop Camera Raw, Capture One and darktable, and every one of them opens the DNG too.

DNG next to JXL

The DNG is written uncompressed, so expect it to be several times larger than the JXL, which stores lossy VarDCT or lossless modular coding; existing JPEGs can be repacked without loss.

No new artefacts

JXL is already lossy, since it stores lossy VarDCT or lossless modular coding; existing JPEGs can be repacked without loss; the DNG keeps the decoded pixels uncompressed, so this step adds no compression damage of its own.

Processed on your device

Your images are decoded, edited and encoded inside this browser tab by Web Workers. Nothing is uploaded to a server.

JXL vs CR2

What changes from JXL to CR2

Encoding: the JXL uses lossy VarDCT or lossless modular coding; existing JPEGs can be repacked without loss; CR2 uses lossless JPEG-compressed sensor data, cut into vertical slices, and the download is a Linear DNG: demosaiced 8-bit RGB with the colour matrices raw editors need.

Bit depth: 8 to 16 bits per channel, or floating point in the JXL; CR2 allows 12 or 14 bits per channel, and the DNG written here has 8 bits per channel, linearised. High-bit-depth JPEG XL files are reduced to 8 bits per channel.

Colour: sRGB, Display P3, linear and other spaces described in the codestream in the JXL; CR2 supports camera RGB from a Bayer mosaic, with the Picture Style recorded in the maker notes, written here as 8-bit sRGB.

Transparency: the JXL stores it as an extra channel in the codestream; the DNG has none, so transparent areas are filled with the colour you choose.

Animation: frames inside a single codestream; the DNG holds one image, so only the first frame is converted.

Metadata: the JXL can carry EXIF and XMP boxes in the container form, often stripped by encoders; CR2 can carry EXIF, Canon maker notes (Picture Style, lens, focus points) and the embedded previews, but nothing is copied across.

About JXL

JPEG XL is a next-generation format designed to replace JPEG. It compresses better than JPEG and WebP, supports lossless, HDR and progressive decoding, and can losslessly repack existing JPEGs.

A JPEG XL file is either a bare codestream starting with FF 0A or an ISO base media container whose 'jxlc' box holds the codestream. A recompressed JPEG keeps a 'jbrd' box that lets the original JPEG bytes be rebuilt exactly.

JXL files usually come from image editors, archival pipelines and lossless JPEG recompression.

About CR2

CR2 is the raw format of Canon EOS cameras from 2004 until CR3 replaced it in 2018. It holds the sensor's 12 or 14-bit readings, losslessly compressed, plus a large JPEG preview rendered with the camera's Picture Style.

CR2 is TIFF-based: the TIFF header is followed by the letters 'CR' and version 2.0, then four image directories: a large JPEG preview with the EXIF block, a 160×120 thumbnail, a small uncompressed RGB image, and the sensor data as lossless JPEG cut into vertical slices.

CR2 files come from Canon EOS DSLRs made from 2004 to 2018, such as the 5D Mark II and III, 6D, 7D and the Rebel series.

When converting JXL to CR2 makes sense

Forms and workflows that ask for CR2 usually feed a raw editor, and each of those opens DNG as well, so the DNG can take the CR2's place. Keep the JXL if you only need to view or share the picture.

What CR2 offers when it comes straight from the camera: Large embedded JPEG rendered with the camera's Picture Style; Lossless 12 or 14-bit sensor data; Widely supported after fourteen years of Canon DSLRs. Its drawbacks: Replaced by CR3 in 2018, so current Canon bodies no longer write it; 20 to 50 MB per photo; Sliced lossless JPEG data that only raw decoders can read.

Limitations

  • The DNG holds the decoded 8-bit pixels, so it adds no dynamic range or detail beyond the JXL.

Frequently asked questions

Why do I get a .dng file instead of a .cr2?

A real CR2 is written by Canon cameras and holds the sensor's own readings (12 or 14 bits per channel, stored as lossless JPEG-compressed sensor data, cut into vertical slices) along with EXIF, Canon maker notes (Picture Style, lens, focus points) and the embedded previews. A JXL holds no sensor data, so no software outside the camera can create a genuine CR2. The Linear DNG you get instead is Adobe's open raw format, and every editor that opens CR2 files opens it with the same raw controls. It holds decoded pixels, so it adds no quality or dynamic range.

Does converting JXL to CR2 lose quality?

DNG is written uncompressed, so the pixels are stored exactly as decoded. Artefacts already in the JXL stay, but nothing new is lost. High-bit-depth JPEG XL files are reduced to 8 bits per channel.

What happens to transparency when converting JXL to CR2?

JXL stores transparency as an extra channel in the codestream. DNG has no alpha channel, so transparent pixels are composited onto a solid colour, white unless you pick another. To keep transparency, convert to PNG, WebP or AVIF instead.

Will my animated JXL stay animated?

No. DNG holds a single image, so only the first frame is kept. Convert to animated WebP, APNG or GIF to keep the motion, or export every frame with the GIF Frame Extractor.

Are my images uploaded anywhere?

No. Processing happens inside your browser with WebAssembly and Web Workers. The site only downloads the app code and codecs; your files never leave your device. You can confirm this with the live upload counter on the tool, or in your browser's network panel.

Can I process many files at once?

Yes. Drop a whole selection or folder. Files are processed in parallel on several worker threads, each result can be downloaded on its own, and everything can be saved as one ZIP.

Is it free? Is there a file limit or watermark?

It is free with no account, no watermark and no daily limit. The only limit is your device's memory: very large images (over roughly 100 megapixels) may be refused to keep the tab from crashing.