Convert JPG to AVIF

Drop your JPGs below. The format is already set to AVIF, and each photo gets the lowest quality that still clears a measured target, up to 16 MB a file as a guest or 32 MB with a free account. Free. No account, no watermark.

  • AVIF already selected
  • Quality searched per photo
  • EXIF kept if you ask
Compression Level
None
No compression, only apply settings on image
Lossless
Without any visual change in the image quality
Ultra
Max compression with some quality loss
Smart
Balance between the image quality and compression
Change Format Will allow you to convert images to different extensions
Auto WEBP AVIF PNG JPG Auto tries every format your image can be saved as and gives you the smallest one
Resize Will allow you to change the width, height or scale of images
Keep EXIF Will allow you to preserve meta data in images
Maximum file size is 16 MB per image and supported formats are: PNG, JPG, JPEG, WEBP, GIF, HEIC, HEIF, TIFF, TIF
Guests get 10 images a day, 10 left today. A free account gets 40 a day.
Delete this image?
The image and its optimized copy will be removed from storage. This cannot be undone.

Rename this image
Choose the name the optimized image downloads with. Its format stays the same.

Uploaded as

Rename the selected images
Each image gets this name and a number, counted in the order they were uploaded. Their formats stay the same.

Share this image
Choose the compression level that suits your images
Level What it promises What happens Pick it when
Lossless
Not one pixel changes in a JPEG, PNG or GIF The file is repacked, never re-encoded. JPEGs get an optimised Huffman table and progressive scan, PNGs a tighter deflate pass, GIFs a lossless gifsicle run. A lossy WebP has no repack step, so it is re-encoded at the highest quality the level allows. A sideways phone JPEG is rotated losslessly on the way through and keeps its colour profile. The one exception to the promise is a PNG or WebP tagged with a wide-gamut profile such as Display P3: its colours are converted to sRGB, so the values change but the picture doesn't. Logos, line art, anything you'll edit again, or when the file is evidence.
Smart
No visible change, targets 40 dB PSNR and a perceptual score of 70 A quality search runs per image and stops at the lowest quality that still clears the PSNR target. That answer is then scored on the SSIMULACRA 2 scale, because an average over every pixel lets a mostly flat picture through at a quality its detail doesn't deserve, and when it falls under 70 the search moves back up until it doesn't. Photos and graphics end up at different qualities because they need different ones; an image that cannot reach the targets inside the quality ceiling is encoded at the ceiling. Almost everything on a website. This is the default for a reason.
Ultra
Smallest file, targets 34 dB PSNR and a perceptual score of 50 The same two-stage search with lower targets. Fine texture softens a little; edges and text stay sharp. Thumbnails, backgrounds, email images, anything shown small or blurred anyway.
None
No compression at all Only the resize, conversion or metadata setting you chose is applied. An untouched upload comes back byte for byte. You only wanted to resize or convert, and quality is someone else's decision.

Measured, not estimated

What JPG to AVIF saved on five real photos

These are the JPG photographs from the showcase on our home page, converted to AVIF by the same pipeline your upload goes through. Smart aims for a result you can't tell from the original; Ultra trades a little fine texture for a much smaller file.

Sample Original Smart Ultra
Fjord 1800 by 1200 832 KB JPG 532 KB 36.1% smaller 263 KB 68.4% smaller
Raspberries 1800 by 1200 342 KB JPG 44 KB 87.2% smaller 10 KB 97.2% smaller
Night skyline 1800 by 1200 427 KB JPG 146 KB 65.8% smaller 74 KB 82.7% smaller
Canoe at dusk 1800 by 1200 387 KB JPG 71 KB 81.7% smaller 24 KB 93.7% smaller
Café interior 1800 by 1200 356 KB JPG 45 KB 87.3% smaller 23 KB 93.6% smaller

Sources are 1800 by 1200 camera-style JPGs saved at quality 92. Metadata stripped, no resize. Your photos will land elsewhere: a busy landscape keeps most of its bytes, a soft portrait loses most of them.

Why AVIF

AVIF spends bytes where a photo needs them

A JPG codes a photo in 8 by 8 blocks, and at low qualities you can see them. AVIF comes from the AV1 video codec, which predicts each area from its neighbours and only stores what the prediction got wrong. On photographs that's worth a lot. On our samples it beat both JPG and WebP at the same measured quality on every photo.

The catch with most converters is the quality number. Pick 50 and one photo looks fine while another turns to mush. Iminify doesn't ask you for a number. It encodes your photo at several AVIF qualities, measures each result against your upload, and keeps the smallest one that still clears the level's target. That search runs on images up to 36 megapixels; anything larger is encoded at the level's fixed ceiling.

AVIF is also the slowest format here to encode. A 12 megapixel photo takes noticeably longer than it would as WebP. For a page you ship once and serve a million times, that's a good trade.

What survives

What a JPG keeps on its way to AVIF

  • EXIF, when you switch it on

    Stripped by default. Turn on Keep EXIF and the block is written into the AVIF during the encode, capture date and GPS included. Plenty of tools drop it without saying so.

  • The right way up

    A sideways phone photo is turned upright before its orientation tag goes, so it never comes back on its side.

  • Colours

    A Display P3 or CMYK profile is converted to sRGB instead of being thrown away, so the picture looks the same in every viewer.

  • The JPG's own artefacts stay in

    Your JPG already lost detail when it was saved. AVIF can't put that back; it re-encodes what's there. A heavily compressed web JPG shrinks less than a photo straight off a camera.

When not to

When JPG is still the right file

  • The file has to open in old desktop software, a printer kiosk or an email client. AVIF works in Chrome, Firefox, Edge and Safari 16.4 or newer, and not much else.
  • You'll edit the photo again. Every lossy save costs a little, so keep the original JPG as your master and convert a copy.
  • You need pixel-for-pixel fidelity. Converting a JPG is always a re-encode; choose Lossless on the Compress JPEG page if nothing may change.

How to

JPG to AVIF in three steps

  1. 1

    Drop your JPGs

    One or a whole batch. AVIF is already chosen under Change Format.

  2. 2

    Keep Smart, or pick Ultra

    Smart is the default and aims for no visible change. Ultra goes smaller and softens fine texture a little.

  3. 3

    Compare, then download

    Open Compare on any result to drag a slider across the before and after, then download one file or the whole batch as a zip.

Questions

JPG to AVIF questions

From the blog

What we've measured so far

We run the encoders on real photos and screenshots and publish the numbers: when WebP beats AVIF, what quality 80 means in each encoder, and how many kilobytes an image on a web page should weigh.

All posts
ComfyUI's Flux Dev example render of a fox-eared girl in a maid dress holding a cake, captioned: 1,215,064-byte PNG to 125,684-byte WebP, and the workflow still loads in ComfyUI.

ComfyUI PNG to JPG loses the workflow. WebP and AVIF can keep it

ComfyUI's Flux Dev example image is a PNG of 1,215,064 bytes, and the two text chunks holding its prompt and workflow take 12,240 of them. The rest is 1024x1024 pixels stored without loss. Across the 92 PNGs in ComfyUI's examples repository that carry a workflow, the text was no more than 3.32 percent of any file, with a median of 0.62 percent. Converting to JPG shrinks the file, but ComfyUI's own loader can't read a workflow back out of a JPG. A WebP or AVIF can keep it, at about a tenth of the size. We took the text-to-image examples of ten models from ComfyUI's examples repository, made smaller copies several ways, and dropped the copies back onto ComfyUI 0.37.0's canvas to see which ones still held the workflow.

6 min read
Bar chart of one photograph in bytes: 852,461 as served, against Lighthouse's target of 45,084 at its phone slot and encodes of 47,876 (JPEG), 46,320 (WebP) and 41,735 (AVIF).

Improve image delivery in Lighthouse: what it replaced and how it counts savings

PageSpeed Insights ran Lighthouse 13.5.0 on our home page on 22 September 2026 and flagged "Improve image delivery" in the mobile report: "Est savings of 1,300 KiB". All of it came from one photograph. The fjord shot in our before-and-after comparison is on the page twice, as the 832.5 KiB original and as our own compressed copy at 555.3 KiB. Both files are 1800x1200, and the report says they're displayed at 637x425. Three later runs that day said 1,359 KiB and 364x243. If your old notes say "Serve images in next-gen formats" or "Properly size images", this is where they went: Lighthouse 13 folded four image audits into this one insight. And its savings aren't measured: each figure is arithmetic on bytes and pixels. We reproduced every number in that insight, made the file it asks for, and traced one reason the same page gets two answers.

8 min read
The harbour picture Nano Banana 2 generated at 4K, 5504x3072: 10.51 MB as sent, a quality-100 JPEG, and 1.58 MB re-encoded as a quality-82 JPEG holding 40 dB.

How big is a Nano Banana image? 52 files measured, from 512 px to 4K

We asked Nano Banana 2 for a 4K, 16:9 picture of a fishing harbour through the Gemini API on 23 September 2026. It came back as a 5504x3072 JPEG of 10.51 MB. The same request again gave 11.10 MB. Both files were saved at JPEG quality 100, the top of the scale. So, how big is a Nano Banana image? From Nano Banana 2 or Pro, a detailed picture is roughly 1 MB at 1K, 4 MB at 2K and 10.45 to 12.13 MB at 4K, and a flat illustration less. The original Nano Banana sends a PNG instead, about 2.1 MB for the same prompt at 1024x1024. Here are the 52 images of our test set, from all four Nano Banana models, and what five of them shrink to.

9 min read

Turn your JPGs into AVIF

The format is already set. Drop a photo and look at the before and after yourself.