How to Convert AVIF to JPG: Step-by-Step Tutorial

By Bill Crawford  ·  March 2026  ·  6 min read  ·  Last updated March 7, 2026

Connect on LinkedIn →

What This Tutorial Covers

This tutorial walks you through converting AVIF images to JPG format using the browser-based tool on this site. No software installation required. You will learn how to add files, choose the right quality setting, use batch mode with ZIP download, and prepare your converted JPG images for deployment.

For background on why you might convert from AVIF to JPG and when each format is the better choice, see the companion AVIF to JPG Complete Guide.

What You Need

• One or more .avif files
• A modern browser with AVIF decoding support: Chrome 85+, Edge 85+, Firefox 93+, or Safari 16.4+
• No account, no software, no subscription

Step 1: Open the Converter

Navigate to dataconversioncenter.com/image-tools/avif-to-jpg/. The page loads JSZip from CDN for ZIP generation — no installation needed. AVIF decoding uses the browser's native image rendering pipeline, and JPG encoding uses the HTML5 Canvas API's toBlob() method. All processing runs in your browser tab.

Step 2: Add Your AVIF Files

You have two ways to add files:

• Drag and drop: Open your file manager and drag one or more .avif files directly onto the drop zone. The zone highlights in blue when you hover over it.
• Browse: Click anywhere on the drop zone (or the "Browse Files" link) to open your file picker. Select multiple files using Ctrl+click (Windows) or Cmd+click (Mac).

After adding files, thumbnails generate immediately using the browser's native AVIF decoder. You will see input cards for each file showing the filename, file size, and a "Ready" status badge. If a file cannot be decoded (for example, if your browser does not support AVIF or the file is corrupt), the thumbnail will not appear and an error will show during conversion.

Step 3: Set the JPG Quality

The quality slider controls the JPEG compression level for all output files:

• Quality 90 (default): Recommended for most use cases. Excellent visual quality with meaningful compression.
• Quality 92–96: Best for photography or product images where sharpness is critical. Files will be larger.
• Quality 80–89: Good for web thumbnails and preview images where file size matters more than maximum detail.
• Quality 60–79: Only for very small preview or thumbnail images. Compression artifacts will be visible at normal viewing sizes.

The quality setting applies to all files in the batch. If you need different quality levels for different images, process them in separate batches.

Step 4: Choose Your Download Preference

Before converting, decide how you want to receive your output files:

• Individual downloads (default): Leave the "Download as ZIP" checkbox unchecked. After conversion, each output card shows an individual download button. Files are downloaded one by one.
• ZIP archive: Check "Download as ZIP". After conversion, clicking "Download ZIP" bundles all converted JPGs into a single dataconversioncenter_avif_to_jpg_YYYYMMDDHHMM.zip file.

ZIP mode is strongly recommended for batches of 5 or more files, as it downloads everything in one click and avoids triggering browser download limits.

Step 5: Click Convert to JPG

Click the Convert to JPG button. The tool processes files in parallel batches of two at a time for performance. For each file:

1. The browser's native AVIF decoder renders the image into a Canvas element.
2. The Canvas API's toBlob('image/jpeg', quality) method encodes the pixel data as a JPEG blob at your chosen quality level.
3. The output file is stored in memory — no network request is made.

The progress bar updates after each pair of files completes. Status badges on input cards change from "Ready" → "Converting…" → "Converted" or "Error".

Conversion speed depends on image resolution and your device. A batch of 10 standard photos typically completes in a few seconds on a modern desktop. Very large images (e.g., 20+ megapixel) may take longer.

Step 6: Download Your JPGs

After conversion completes, a summary banner confirms how many files succeeded. You then have several options:

• Per-file download: Each output card has a "⬇ Download JPG" button. Click it to download that individual file.
• Download All JPGs: If ZIP mode is off, this button triggers sequential downloads of all converted files.
• Download ZIP: If ZIP mode is on, this button generates and downloads the ZIP archive.

After downloading, the tool resets automatically. To convert another batch, simply drop new files onto the drop zone.

Tips for Best Results

• Start from the best source. If you have access to the original uncompressed image (RAW, TIFF, PNG), convert from that rather than from AVIF to minimize generation loss.
• Use quality 90+ for photography. Second-generation lossy compression (AVIF → JPG) can degrade fine detail and introduce blocky artifacts at lower quality settings.
• Check for transparency. If your AVIF images have transparent areas, they will appear white in the JPG output. If transparency must be preserved, use AVIF to WebP instead.
• Test in your target platform. After conversion, verify JPGs display correctly in the email client, CMS, or application where they will be used.
• Process large batches in ZIP mode. For 10+ files, ZIP mode is faster and more reliable than downloading files individually.

Troubleshooting

"Could not decode AVIF file" — Your browser may not support AVIF decoding. Upgrade to Chrome 85+, Edge 85+, Firefox 93+, or Safari 16.4+ and try again.

White boxes instead of thumbnails — The browser may be loading the thumbnail. Wait a moment; thumbnails generate asynchronously. If they never appear, the AVIF file may be malformed.

Output files are larger than expected — High quality settings (92+) produce larger JPG files. Lower the quality slider slightly if file size is important. Also note that AVIF typically achieves much smaller sizes than JPG, so JPG output at equivalent visual quality will naturally be larger.

Conversion stalls on a specific file — Very large images (50+ megapixels) can require significant memory. Try processing that file individually in a fresh browser tab.