JPG to AVIF Converter: Free, Private, No Upload

Convert JPG files to AVIF in your browser. Smaller output file, batch up to 20 files at once, no upload, no account, no watermark. Your files never leave your device.

JPG to AVIF
Batch up to 20 files
No upload, no account
Metadata stripped

1Add up to 20 images
2Pick from 18 formats
3Download or copy the code

Processed on your device. Your images are never uploaded, and metadata is stripped. How we keep it private

How do I convert JPG to AVIF for free?

Drop your JPG files into the tool above, choose AVIF as output, and download the result. Everything runs in your browser, so nothing is uploaded and there is no limit or watermark. It works on Windows, Mac, Linux, ChromeOS, iOS and Android — anywhere you have a modern browser.

Price: Free, no credits and no daily cap
Account required: No
File uploaded to server: No, processed locally in your browser
Batch limit: Up to 20 files at once
Input format: JPG
Output format: AVIF
Best for: AVIF workflows, smaller files, faster sharing
Works on: Chrome, Edge, Firefox, Safari, iOS and Android browsers
Privacy: No upload, no tracking, metadata stripped
Output quality: Adjustable 1-100, defaults to 90

How to convert JPG to AVIF

1
Drop your JPG files
Drag up to 20 JPG files onto the page or click to choose them. Everything runs in your browser.
2
AVIF is preselected
Output is already set to AVIF. Adjust quality, resize or batch if you want.
3
Download
Save each AVIF, or download all of them together as a ZIP.

JPG to AVIF: what changes and when it makes sense

JPG is a Joint Photographic Experts Group format. It is best known for small files for photographs and near-universal compatibility. The main drawbacks are no transparency, visible blocking at low quality, and quality that drops every re-save.

AVIF is an AV1 Image File Format. It is best known for the smallest files of any common web format at a given quality. The main drawbacks are slow encoding, patchy support outside browsers, and smoothing in fine textures at aggressive settings.

JPG vs AVIF at a glance

Property	JPG	AVIF
Type	Raster image	Raster image
Compression	Lossy (DCT based, with chroma subsampling)	Lossy or lossless, based on the AV1 video codec
Transparency	None	Full alpha channel with soft edges
Animation	No	Yes
Colour depth	8 bits per channel (24-bit colour)	8, 10 or 12 bits per channel, with HDR and wide-gamut support
Support	Opens in every browser, operating system, camera, editor and print service	Supported by current Chrome, Edge, Firefox and Safari, but many editors, social platforms and OS viewers cannot open it
History	Created in 1992 by the Joint Photographic Experts Group and standardised as ISO/IEC 10918. It became the default image format of the early web because it offered photographic compression when storage was expensive. Still the most widely used photo format 30+ years later.	Finalised in 2019 by the Alliance for Open Media (Google, Mozilla, Apple, Microsoft, Netflix, Amazon, Intel and others). Based on AV1 video codec, successor to VP9 and HEVC. First major browser support: Chrome 85 (2020).

What actually changes in this conversion

Both JPG and AVIF use lossy compression, so this adds a second round of loss. Use a high quality setting (90 or above).
JPG has no alpha channel, so every pixel is already opaque.
Expect the AVIF file to be somewhat smaller than the JPG source.
EXIF, GPS and camera data are stripped on every conversion. That is good for privacy, but you lose capture dates.

About JPG: history and technical details

Created in 1992 by the Joint Photographic Experts Group and standardised as ISO/IEC 10918. It became the default image format of the early web because it offered photographic compression when storage was expensive. Still the most widely used photo format 30+ years later.

Technical: 8x8 block Discrete Cosine Transform with 4:2:0 chroma subsampling by default. Baseline supports 8-bit per channel. Progressive loads in waves. Maximum dimensions 65,535 by 65,535 pixels. Maximum 16.7 million colours.

Real-world size: A 12-megapixel photo at quality 85 is typically 2-4 MB. The same photo as PNG is 18-25 MB, as BMP is 36 MB. JPG is 60-80% smaller than PNG for photographs.

Popular tools: Adobe Photoshop, GIMP, Affinity Photo, Lightroom, macOS Preview, Windows Photos, ImageMagick, FFmpeg.

Alternatives: WebP (25-35% smaller), AVIF (30-50% smaller), HEIC (50% smaller, Apple only), PNG (lossless, 5-10x larger).

About AVIF: what you get

Finalised in 2019 by the Alliance for Open Media (Google, Mozilla, Apple, Microsoft, Netflix, Amazon, Intel and others). Based on AV1 video codec, successor to VP9 and HEVC. First major browser support: Chrome 85 (2020).

Technical: AV1 intra-frame coding with variable block sizes from 4x4 to 128x128. Supports 8/10/12-bit colour, HDR, wide gamut (BT.2020), monochrome. HEIF-based container. Encoding is 10-100x slower than JPEG.

Real-world size: AVIF at quality 50 produces files 30-50% smaller than JPG at quality 85 with similar visual quality. Netflix reports 50% bandwidth savings after switching. Google reports AVIF is 20-30% smaller than WebP.

Popular tools: Adobe Photoshop 2024+, GIMP 2.10+, Squoosh, avifenc, ImageMagick, AVIF.io, Netflix (production use).

Alternatives: WebP (faster encode, less compression), JPG (universal), HEIC (Apple-only), JPEG XL (future format).

Browser and software compatibility

JPG: Opens in every browser, operating system, camera, editor and print service. AVIF: Supported by current Chrome, Edge, Firefox and Safari, but many editors, social platforms and OS viewers cannot open it.

AVIF is well supported by current browsers but is still rejected by many editors and social platforms.

Why people move away from JPG

JPG cannot store transparency, so logos, cut-outs and interface assets need another format.
Every re-save of a JPG throws away more detail, a problem for images edited repeatedly.
Sharp edges and text show ringing artefacts in JPG, and newer codecs give smaller files at the same visual quality.

Why people choose AVIF

AVIF often produces files 30 to 50 percent smaller than JPG at comparable quality.
It can carry 10-bit and HDR content that JPG and WebP cannot.
It pays off most on hero images and large photo galleries, where bytes matter the most.

Common mistakes with JPG

Re-saving a JPG multiple times compounds quality loss — always keep the original
Using JPG for logos with text causes visible ringing around letters
Setting quality above 95 rarely improves visual quality but enlarges files

Common JPG to AVIF scenarios

Bandwidth-sensitive sites: Photo-heavy pages see some of the largest wins from AVIF.
Serving with a fallback: Use the picture element to offer AVIF first and JPG to browsers that cannot decode it.

Best practices for keeping quality

If you still have the original camera file, convert from that. A JPG already compressed hard has little detail left to preserve.
AVIF quality numbers do not line up with JPG. Start around 60-70 and compare against the original at 100 percent zoom.
Serve AVIF with a WebP or JPG fallback using the picture element so older browsers still get an image.
Resize before converting if the image will be shown small. A 4000 pixel photo displayed at 800 pixels wastes bytes in any format.
Check the result at 100 percent zoom, especially around text, edges and gradients, before you replace any originals.
Keep your original files. Conversions to a lossy format cannot be undone.
When you convert a set of images, use the same quality setting for the whole batch. The converter handles up to 20 files at once.

JPG to AVIF questions

Quick answers about privacy, quality, supported formats, file limits and how AVIF works.

How much smaller is AVIF than JPG?

AVIF at quality 50 is typically 30-50% smaller than JPG at quality 85 with similar visual quality. Netflix reports 50% bandwidth savings after switching.

Do I need a fallback for AVIF?

Yes, for older browsers. Use <picture><source srcset="x.avif" type="image/avif"><img src="x.jpg"></picture> to serve AVIF first and JPG as fallback.

Why convert JPG to AVIF?

AVIF files are typically smaller than JPG, which makes them faster to share, send and load. The trade-off is a small amount of image detail at low quality settings.

Will converting JPG to AVIF lose quality?

At 90% quality, most people cannot tell the difference. Use 85-95% for photos and you are fine.

Does AVIF keep transparency?

Yes. AVIF supports full transparency, so transparent areas in your original are kept.

Are my files uploaded?

Never. Everything runs in your browser. Your files never leave your device. Open DevTools Network tab while processing — you will see no upload request.

Can I convert many files at once?

Yes, up to 20 files at once. Download them individually or all together as a ZIP.

Does the converter strip metadata?

Yes. Browsers do not pass EXIF data through a canvas, so GPS, camera model and dates are removed on every conversion. That is good for privacy.

Is it free?

Yes. No credits, no daily cap, no account, no watermark. The practical limit is your device memory.

Is AVIF smaller than WebP?

Yes, typically 20-30% smaller at similar quality. But AVIF is much slower to encode and has less software support outside browsers.

Does AVIF support HDR?

Yes. AVIF supports 10-bit and 12-bit colour, HDR (Hybrid Log-Gamma and PQ), and wide-gamut BT.2020 colour. JPG and WebP cannot do this.

Can AVIF be animated?

Yes, though animated AVIF support is still limited in browsers. Chrome and Firefox support it, Safari does not as of early 2026.

Your files never leave your device

No upload, no account, no tracking. Everything happens in your browser using the Canvas API and WebAssembly. You can confirm this in your browser's DevTools Network tab while the tool runs — no request carries your file. See why ToolDeck is different.