Image converter · AVIF to JPG AVIF to JPG converter: open AVIF images anywhere
Many sites now serve AVIF, but older photo viewers, editors and upload forms cannot open it. Add the AVIF files and download JPGs at the same size. Your browser decodes the AVIF; nothing is uploaded.
- Stays on your device
- Works with any app
- Batch and ZIP download
Convert AVIF to JPG
Output is set to JPEG at quality 90 and the original size. Transparent areas become the background colour.
90 keeps the converted image close to the original; lower it for smaller files.
Lowers quality step by step until the file fits. Works for WebP, JPEG and AVIF.
JPEG has no transparency, so transparent areas are filled with this colour.
Only when format and dimensions stay the same.
No images yet. Choose, drop or paste images, or try the sample photo.
Before
—
After
—
Saved
—
Before and after
Drag across the image or use the slider. Left of the line is the original, right is the compressed version. Zoom in on edges, text and skies, where compression shows first.
What resizing does to a 12-megapixel phone photo
A 4032 × 3024 photo shrunk to fit a square limit. Pixel count drives file size and decoding memory, so resizing usually saves more than any quality setting.
| Max width and height | Output size (px) | Pixels removed | Memory once decoded |
|---|---|---|---|
| Original | 4,032 × 3,024 | — | 46.51 MB |
| 2,560 px | 2,560 × 1,920 | −60% | 18.75 MB |
| 1,920 px | 1,920 × 1,440 | −77% | 10.55 MB |
| 1,200 px | 1,200 × 900 | −91% | 4.12 MB |
| 800 px | 800 × 600 | −96% | 1.83 MB |
Decoded memory = width × height × 4 bytes (one byte each for red, green, blue and alpha), whatever the file size. File sizes depend on the picture, so the tool measures them instead of guessing.
Version v1.0Updated Update history
What to expect from AVIF to JPG
AVIF is one of the most efficient image formats, so the JPG is almost always larger. That is the price of compatibility.
Your browser must open AVIF
Decoding uses the browser's own AVIF support: current Chrome, Edge, Firefox and Safari 16 or later. If it cannot, the page says so above the drop area.
The file gets bigger
AVIF needs fewer bytes than JPEG for the same picture. A larger JPG is expected, not a fault.
Quality 90 by default
Re-encoding adds a second round of compression. At 90 it is hard to see; go lower only if size matters.
Transparency and HDR
Transparent areas become the background colour. HDR and wide-colour AVIF are converted to ordinary sRGB, so very bright highlights may look flatter.
If the app you are using accepts PNG, convert to PNG instead to avoid the second lossy step.
Convert AVIF to JPG in three steps
The page opens with JPEG output, quality 90 and no size limit.
-
1
Add the AVIF files
Click to choose or drop them on the box. Up to 60 at once.
-
2
Check the settings
Keep quality 90 for a faithful copy, and pick a background colour if the images have transparency.
-
3
Download
Download each JPG or all of them as a ZIP, named like the originals with .jpg.
Why smaller images make the largest paint faster
Largest Contentful Paint (LCP) is the time until the biggest image or text block in the viewport is drawn. web.dev splits it into four parts: time to first byte, resource load delay, resource load duration and element render delay. When the largest element is an image, its file size sets the load duration.
- Good LCP: 2.5 seconds or less for at least 75% of page visits (web.dev)
- File size depends on pixel count × bytes per pixel; resizing cuts the first, quality and format the second
- This tool draws each image onto a canvas, scales it in steps of at most half for sharper results, then calls
canvas.toBlob(type, quality) - Compression does not fix a slow server or a late-discovered image: set
widthandheight, do not lazy-load the LCP image and considerfetchpriority="high"
| Format | Type | Transparency | Best for |
|---|---|---|---|
| WebP | Lossy or lossless | Yes | Website photos and graphics; supported by current browsers |
| AVIF | Lossy | Yes | Smallest files for photos; shown only if your browser can encode it |
| JPEG | Lossy | No | Email, upload forms and anything that refuses WebP |
| PNG | Lossless | Yes | Screenshots and UI that must stay pixel-exact; rarely gets smaller |
One phone photo, three decisions
A 4032 × 3024 photo for a blog post whose content column is 800 CSS pixels wide.
| Step | Decision | Result |
|---|---|---|
| 1. Dimensions | 800 px column × 2 for sharp screens → max width 1600, or 1920 for a full-width hero | At 1920: 1920 × 1440, 77% fewer pixels |
| 2. Format | WebP at quality 80 for the page; keep a JPEG copy only if a platform rejects WebP | Typically a large saving on photos; the tool shows the exact size |
| 3. Check | Compare at real size; look at sky gradients and fine text | Lower the quality until artefacts appear, then step back |
| Memory | Decoded size of the original vs a 1200-pixel version | 46.51 MB vs 4.12 MB: what a phone must hold in memory to paint it |
Pixel counts and memory are exact arithmetic; compressed file sizes depend on the picture, so measure them with the tool rather than trusting a rule of thumb.
Where image compression goes wrong
Most oversized images on websites are not under-compressed; they are simply too big.
Uploading the camera original
A 4000-pixel photo shown 800 pixels wide makes every visitor download and decode five times the pixels in each direction. Resize before you compress.
Re-compressing a JPEG again and again
Every lossy save adds artefacts. Keep the original and compress from it, not from the last exported copy.
Saving photos as PNG
PNG is lossless, so photos stay huge. Use PNG for flat screenshots; for photos use WebP, AVIF or JPEG.
Lazy-loading the main image
loading="lazy" on the largest image above the fold delays LCP. Lazy-load images further down the page instead.
See whether your images slow real visitors down
Compressing images is the fix; real-user data tells you which pages need it. TapCub's script measures the same Largest Contentful Paint this page explains, on your visitors' devices.
Core Web Vitals at p75
LCP, INP and CLS for each page at the 75th percentile, the same threshold web.dev uses, collected from the first page load of each visit.
Learn moreSlowest pages first
Pages and templates sorted by LCP, so you compress the images that cost the most visitors first.
Learn morePages and sources together
Compare speed with traffic and conversions on the same pages to decide where an image fix matters.
Learn moreImage compression questions
Still have a question?
Chat with the team behind TapCub — we usually reply within a few hours on business days.
How do I convert AVIF to JPG?
Add the AVIF images here. Output is already JPEG at quality 90 and full size; each file converts as soon as it loads, and you can download the batch as a ZIP.
Why does it say my browser cannot open AVIF?
This tool relies on the browser to decode AVIF. Older browsers, such as Safari before version 16, cannot. Update the browser or open the page in current Chrome, Edge or Firefox.
Why is the JPG bigger than the AVIF?
AVIF compresses photos far better than JPEG. To make the JPG smaller, lower the quality or set a max width.
How do I open an AVIF file on Windows or a Mac?
Recent versions of Windows Photos and macOS Preview open AVIF directly. If yours does not, convert the file to JPG here and open the JPG.
Update history
New features, fixes and data refreshes for this tool, newest first.
-
· v1.0
LaunchedFirst release.
Missing something or found an error? Tell us — requests that come up often go into the next update. All tool updates
Measure the speed your visitors actually get
Add TapCub's script and see LCP, INP and CLS for every page from real visits, next to traffic and conversions.