How to Batch Convert JPG to AVIF - Complete Bulk Conversion Guide

Converting dozens or hundreds of JPG files to AVIF one by one is tedious and time-consuming. Batch conversion solves this — process an entire folder of images in minutes rather than hours, with consistent quality settings across every file. This guide covers the most effective methods for bulk JPG-to-AVIF conversion, from browser-based tools to command-line approaches.
Why Batch Convert JPG to AVIF?

AVIF (AV1 Image File Format) offers dramatically better compression than JPG, making it one of the most valuable format upgrades available for web images.
| Benefit | Impact |
|---|---|
| 50–60% file size reduction | Significant storage and bandwidth savings |
| Better quality at same file size | Images look sharper and cleaner |
| Saves hours of manual work | Process hundreds of files at once |
| Consistent output | Uniform quality and size across all images |
For a website with 200 product images averaging 400KB each (80MB total), converting to AVIF at 75% quality could reduce that to approximately 30–35MB — without any visible quality difference on screen.
Method 1: Online Batch Converter (Easiest)
The simplest way to batch convert is using our JPG to AVIF Converter directly in your browser — no installation required.
Step 1: Upload Multiple Files
- Open the JPG to AVIF Converter
- Drag and drop multiple JPG files at once
- Or click to browse and Ctrl+click (Cmd+click on Mac) to select multiple files
Step 2: Configure Quality Settings
Choose the quality setting that matches your use case:
| Use Case | Quality | Expected Saving |
|---|---|---|
| Archival | 90% | ~45% smaller |
| Portfolio | 82% | ~55% smaller |
| Web images | 75% | ~60% smaller |
| Thumbnails | 65% | ~70% smaller |
The quality percentages above refer to AVIF's quality scale — 75% AVIF typically produces results that look better than 75% JPG because AVIF's compression algorithm is fundamentally more efficient.
Step 3: Convert and Download
Click Convert and download your AVIF files:
- Download individually — for small batches
- Download all as ZIP — for larger batches; all files in a single download
Method 2: Command Line with ImageMagick
For technical users or anyone processing very large numbers of files, command-line tools offer speed and scriptability.
Basic ImageMagick Batch Conversion
# Convert all JPG files in the current directory to AVIF at quality 80
for file in *.jpg; do
magick "$file" -quality 80 "${file%.jpg}.avif"
done
With Resize (Optimize for Web at the Same Time)
# Convert and resize to max 1200px width, quality 75
for file in *.jpg; do
magick "$file" -resize 1200x1200> -quality 75 "${file%.jpg}.avif"
done
Pros: Very fast for large batches, fully automatable Cons: Requires ImageMagick installation, some technical knowledge needed
Squoosh CLI (Google)
Google's Squoosh CLI is another excellent option:
# Install and run
npx @squoosh/cli --avif auto *.jpg
# With specific quality setting
npx @squoosh/cli --avif '{"quality": 75}' *.jpg
Method 3: Desktop Applications
For users who prefer a GUI and need to process files regularly:
XnConvert (Free, Cross-Platform)
XnConvert is free for personal use and handles batch image conversion with a friendly interface:
- Available for Windows, Mac, and Linux
- Built-in batch processing with queue management
- Supports AVIF output with quality control
- Can also resize and apply other adjustments in the same pass
Workflow:
- Add input files or folder
- Set output format to AVIF and quality
- Choose output folder
- Click Convert
Adobe Photoshop
For Photoshop users:
- Use File → Scripts → Image Processor for batch processing
- Requires AVIF plugin (available through Adobe's plugin marketplace)
- Useful when you need to apply other Photoshop adjustments alongside conversion
Optimal Quality Settings by Use Case
E-Commerce Product Photos
| Setting | Value | Reason |
|---|---|---|
| Quality | 82% | Balances detail and file size |
| Resize | Match display dimensions | Avoid unnecessarily large files |
| Color space | sRGB | Web compatibility |
Product images need to show fine texture details (fabric, material grain, text on packaging), so don't go below 80%.
Photography Portfolio
| Setting | Value | Reason |
|---|---|---|
| Quality | 85–88% | Preserve fine detail |
| Resize | Max 2400px | High-quality viewing |
| Color space | sRGB | Consistent display |
Portfolio images are your showcase — quality matters more than file size here.
Blog and Content Images
| Setting | Value | Reason |
|---|---|---|
| Quality | 75% | Fast loading priority |
| Resize | Max 1200px | Typical content width |
| Color space | sRGB | Standard web |
Blog readers scan quickly and rarely zoom in — 75% AVIF quality is indistinguishable from the original for typical editorial photos.
Social Media Content
| Setting | Value | Reason |
|---|---|---|
| Quality | 78% | Good quality, smaller size |
| Resize | Platform-specific dimensions | Optimal display |
| Color space | sRGB | Universal |
Note: Most social platforms transcode your uploads anyway, so starting with a good-quality AVIF is more important than using the exact right platform dimensions.
Expected File Size Results
Here's what to expect when converting a typical batch of photos:
| Original JPG | AVIF 85% | AVIF 75% | AVIF 65% |
|---|---|---|---|
| 500 KB | ~230 KB | ~180 KB | ~140 KB |
| 1 MB | ~450 KB | ~350 KB | ~270 KB |
| 2 MB | ~900 KB | ~700 KB | ~540 KB |
| 5 MB | ~2.2 MB | ~1.7 MB | ~1.3 MB |
Average reduction: 50–70% depending on quality settings and image content. Images with lots of photographic detail (complex scenes, portraits) tend to compress better than images with large areas of solid color.
Batch Conversion Best Practices
1. Organize Files First
Create a clear folder structure before starting:
📁 images/
📁 jpg_originals/ ← keep originals here
📁 avif_converted/ ← output goes here
Never overwrite your originals — always convert to a separate output folder.
2. Test Before Full Conversion
Before converting 500 images, test with 5–10 representative samples:
- Pick images that represent the range of your content (portraits, landscapes, close-ups)
- Convert at your chosen quality setting
- Visually compare originals and AVIF versions side by side
- Check file sizes are within your acceptable range
- Adjust quality up or down if needed
3. Use Consistent Settings
Apply the same quality to all files in a batch:
- Consistent visual quality across the site
- Predictable file sizes for capacity planning
- Consistent loading times
4. Always Keep Original JPGs
Never delete your original files:
- AVIF encoding doesn't suit all images equally (some highly compressed JPGs don't benefit much)
- You may need to re-convert with different settings later
- Originals are valuable for future format migrations
5. Implement JPG Fallback for Web Use
When deploying AVIF images on a website, provide a JPG fallback for browsers that don't support AVIF yet (~7% globally):
<picture>
<source srcset="photo.avif" type="image/avif">
<source srcset="photo.jpg" type="image/jpeg">
<img src="photo.jpg" alt="Photo description">
</picture>
Handling Large Batches
50–200 Images
Our online converter handles this comfortably. Upload in batches of 50–100 files for best performance.
200–1000 Images
Consider:
- Breaking into multiple browser sessions
- Using XnConvert desktop app for a single-batch workflow
- Command-line tools for automation
1000+ Images
At this scale, automation becomes necessary:
- Write a shell script using ImageMagick or Squoosh CLI
- Set up a watch folder that converts new files automatically
- Consider server-side conversion using a CDN with on-the-fly AVIF conversion (Cloudflare Images, Cloudinary, etc.)
Troubleshooting Common Batch Issues
"Conversion Is Very Slow"
Cause: AVIF encoding is computationally intensive — significantly more so than JPG encoding.
Solutions:
- Process smaller batches at a time
- Use a lower quality setting (faster encoding with smaller files)
- For very large batches, use a desktop app or command-line tool which can use multi-core processing
"Some Images Look Worse Than Others"
Cause: Certain types of content are harder for AVIF to compress cleanly: synthetic gradients, fine text on images, and very high-frequency noise patterns.
Solutions:
- Increase quality for problem images (90%+ for challenging content)
- Keep the original JPG for images where AVIF quality isn't satisfactory
"File Sizes Aren't Decreasing Much"
Cause: Source JPGs were already heavily compressed (low quality originals), or images have content types that AVIF handles less efficiently.
Solutions:
- Start with higher-quality source images
- Try a slightly lower quality setting — sometimes 70% AVIF still looks better than 60% JPG but at a smaller size
- Accept that some images simply don't compress as well as others
"AVIF Files Don't Open on Some Devices"
Cause: ~7% of browsers (primarily older versions and some email clients) don't support AVIF.
Solutions:
- Always implement the
<picture>element with JPG fallback on websites - For email: use JPG exclusively (AVIF has essentially no support in email clients)
- Check Can I Use AVIF for current browser support data
Frequently Asked Questions
How many files can I convert at once?
Our online converter efficiently handles batch uploads. For optimal performance, convert in batches of 50–100 files. For larger batches, desktop tools or command-line solutions scale better.
Will batch conversion maintain consistent quality?
Yes — the same quality setting applies to every file in the batch, ensuring uniform output.
Should I resize images before or during conversion?
For web use, resize to display dimensions during the same conversion pass. This double-optimization (smaller dimensions + better compression) maximizes the performance benefit. Many batch tools (including our online converter) let you apply both simultaneously.
Can I batch convert images with transparency?
JPG doesn't support transparency, so there's no transparency to preserve when converting from JPG to AVIF. If you need transparency, convert from PNG to AVIF instead — our PNG to AVIF converter handles those cases.
What quality should I use for batch web conversion?
General web images: 75–80% Product photography: 80–85% Portfolio / high-detail: 85–90% Archival (maximum quality): 88–92%
How does AVIF compare to WebP for batch conversion?
AVIF provides 30–50% better compression than WebP at equivalent quality, making it the better long-term choice for new content. However, WebP has slightly broader browser support (~97% vs ~93% for AVIF). For a mixed-compatibility strategy, AVIF with WebP fallback and JPG fallback is ideal:
<picture>
<source srcset="photo.avif" type="image/avif">
<source srcset="photo.webp" type="image/webp">
<img src="photo.jpg" alt="Photo description">
</picture>
Conclusion
Batch converting JPG to AVIF is one of the highest-impact image optimizations available for web projects. A few hours of conversion work can reduce your total image bandwidth by half — permanently improving page load times, Core Web Vitals scores, and user experience for every visitor.
Start with a test batch to validate your quality settings, organize your folder structure, and then convert systematically. The online converter handles most use cases, while command-line tools provide the scalability for large-scale projects.
Related tools: JPG to WebP | Image Compressor | Image Resizer