Skip to content

CR2 to AVIF Converter

Convert CR2 to AVIF in your browser. The large JPEG preview in the first directory is what gets converted; it carries the Picture Style that was active when you shot. No raw development happens here. You get an AVIF encoded with libavif (AV1) compiled to WebAssembly, at the quality you choose. Nothing is uploaded.

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

Drop images here

or choose files · paste with Ctrl/⌘ V

RAW expected · other image formats also work

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

How to use CR2 to AVIF

  1. 1

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

  2. 2

    Set the quality. AVIF quality numbers run lower than JPEG: around 55 to 65 already looks excellent. Encoding is slow on phones.

  3. 3

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

  4. 4

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

Why use Aback Images for cr2 to avif

Where the AVIF goes next

AVIF opens in Chrome, Edge, Firefox, Safari 16 and later, Windows 11 Photos, macOS Preview and recent editors.

AVIF next to CR2

The AVIF is made from the camera's 8-bit preview, so it is a small fraction of a 20 to 50 MB raw file.

A second JPEG generation

The pixels come from the JPEG preview the camera embedded in the CR2, so they have been compressed once already; keep the quality at or above the default.

Processed on your device

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

CR2 vs AVIF

What changes from CR2 to AVIF

Encoding: the CR2 uses lossless JPEG-compressed sensor data, cut into vertical slices; AVIF uses lossy or lossless AV1 intra-frame coding, and the download is an AVIF encoded with libavif (AV1) compiled to WebAssembly, at the quality you choose.

Bit depth: 12 or 14 bits per channel in the CR2; AVIF allows 8, 10 or 12 bits per channel, and the AVIF written here has 8 bits per channel. The sensor's 14 bits are not used: the 8-bit camera preview is converted.

Colour: camera RGB from a Bayer mosaic, with the Picture Style recorded in the maker notes in the CR2; AVIF supports YUV 4:4:4 or 4:2:0 with BT.709, Display P3 or BT.2020 primaries, HDR curves possible, written here as 8-bit sRGB.

Metadata: the CR2 can carry EXIF, Canon maker notes (Picture Style, lens, focus points) and the embedded previews; AVIF can carry EXIF, XMP and ICC stored as HEIF items, but nothing is copied across.

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 usually come from Canon EOS DSLRs made from 2004 to 2018, such as the 5D Mark II and III, 6D, 7D and the Rebel series.

About AVIF

AVIF uses the AV1 video codec for still images. It is the most efficient widely supported format, often half the size of JPEG, with HDR, wide colour and transparency, but encoding is slow.

An AVIF is a HEIF file, the same ISO base media boxes as MP4, with the brand 'avif'. The picture is an AV1 key frame stored as an image item, and its size, colour and pixel layout are item properties.

When converting CR2 to AVIF makes sense

AVIF is the better choice for maximum compression on modern websites, while CR2 suits editing Canon photos in a raw developer.

AVIF strengths: Often 50% smaller than JPEG; Excellent at low quality settings; Transparency, HDR and 10/12-bit colour. Drawbacks to weigh: Slow to encode, especially on phones; Not supported by some older software; Can smooth away fine texture at low quality.

Limitations

  • The 14-bit sensor data, with its highlight and shadow latitude, is not developed here; use a raw editor when you need to recover detail.
  • AVIF encoding is CPU-heavy, so large images and big batches take noticeably longer than JPG or WebP, especially on phones.
  • Some older apps and operating systems cannot open AVIF yet; keep a JPG copy if you share the file widely.

Frequently asked questions

Does converting CR2 to AVIF lose quality?

AVIF is lossy, so detail the eye barely notices is discarded to save space. The CR2's preview is a camera JPEG already, so keep the quality high to avoid stacking artefacts. The sensor's 14 bits are not used: the 8-bit camera preview is converted.

What quality should I choose for AVIF?

AVIF quality numbers run lower than JPEG: around 55 to 65 already looks excellent. Lower values give much smaller files with gentle softening. Encoding is CPU-heavy, so large batches take a while on phones.

Which apps open AVIF files?

Chrome, Edge, Firefox, Safari 16 and later, Windows 11 Photos, macOS Preview and recent editors. It opens in Chrome 85+, Edge, Firefox 93+ and Safari 16+.

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.