Initializing... drag & drop files here
Supports: JPG, JPEG, JFIF
.jpg, .jpeg, or .jfif files, or click "+ Add Files" to browse. Batch upload is supported, and files stay on your device — nothing is sent until you click Convert.image/avif) in your browser session and download individually or as a ZIP. No watermark, no sign-up, no per-day cap.AVIF (AV1 Image File Format) is a still-image container built on the AV1 video codec, standardized by the Alliance for Open Media (Google, Apple, Microsoft, Netflix, Mozilla, Amazon, Meta) in 2019. Per MDN, lossy AVIF averages ~50% smaller than JPEG at visually identical quality and beats WebP by roughly 20 percentage points. JPEG, by contrast, is a 1992 standard that lacks transparency, HDR, and wide color gamut.
<picture> fallback — Use <source type="image/avif"> first, JPEG as the <img> fallback. Chrome 85+ (Aug 2020), Firefox 93+ (Oct 2021), Safari 16.1+ (Oct 2022), and Edge 121+ (Jan 2024) all decode AVIF natively per caniuse, covering ~94% of global traffic.| Property | JPEG | AVIF |
|---|---|---|
| Released | 1992 (ISO/IEC 10918) | 2019 (AOMedia AV1 Image File Format) |
| Underlying codec | DCT-based (JPEG) | AV1 intra-frame |
| MIME type | image/jpeg |
image/avif |
| Typical compression | Baseline | ~50% smaller at equal quality (MDN) |
| Bit depth | 8-bit per channel | 8 / 10 / 12-bit per channel |
| Transparency (alpha) | No | Yes |
| HDR / wide color gamut | No | Yes (BT.2020, PQ, HLG) |
| Animation | No | Yes (multi-image sequences) |
| Lossless mode | No (lossy only in practice) | Yes |
| Progressive rendering | Yes | No (must fully download) |
| Browser support | Universal | Chrome 85+, FF 93+, Safari 16.1+, Edge 121+ |
| Royalty / patent status | Free | Royalty-free (AOMedia) |
| Preset | Approx. quality factor | Best for | Trade-off |
|---|---|---|---|
| Highest (lossless) | q=100, lossless flag on | Archival masters, screenshots with text | Files can exceed source JPEG |
| Very High (default) | ~q=85-90 | Hero images, photography portfolios | ~50-70% of source JPEG size |
| High | ~q=75-80 | Blog images, product grids | ~30-50% of source JPEG size |
| Medium | ~q=60-70 | Thumbnails, social previews | Visible softening at 100% crop |
| Low / Lowest | ~q=40-55 | Lazy-loaded below-the-fold | Blocky on flat colors |
For predictable file budgets, use the Specific file size target instead — set 100 KB, 250 KB, or 1 MB and the encoder picks the highest quality that fits.
No. JPEG is already a lossy format, so its artifacts are baked into the pixels. Converting JPEG to AVIF re-encodes those existing artifacts in a smaller container — you save bytes, not detail. For best visual results, start from a lossless source (PNG, TIFF, or RAW) when you have one. Use PNG to AVIF for that path.
It happens with already-aggressively-compressed JPEGs (quality 60 or below) or images with heavy fine-grain noise. AVIF's encoder spends bits trying to preserve the noise faithfully. Two fixes: drop the Quality Preset one notch (Very High → High), or use Specific file size to cap the output below the JPEG size.
Roughly 94% of global traffic supports AVIF as of May 2026: Chrome 85+ (Aug 2020), Firefox 93+ (Oct 2021), Safari 16.1+ (Oct 2022 on macOS Ventura / iOS 16.1), and Edge 121+ (Jan 2024). For older browsers, serve a JPEG fallback via the <picture> element with <source type="image/avif"> listed first.
The AVIF spec supports embedded EXIF, XMP, and ICC profiles in meta boxes. xconvert preserves the EXIF block from the source JPEG by default — camera make/model, exposure, and capture date carry over. Strip metadata in your own export pipeline if privacy is a concern (xconvert does not re-write GPS data).
Photoshop has shipped native AVIF read/write since version 23.2 (March 2022) via File → Save a Copy → AVIF. Lightroom Classic added AVIF export in version 13.0 (October 2023). If your workflow targets Photoshop AVIF, match its default quality (~85) by using xconvert's Very High preset.
AVIF compresses ~20% better than WebP at the same perceived quality (MDN data) and supports 10/12-bit HDR that WebP does not. WebP is older and has slightly broader fallback support, but every browser that supports WebP also supports AVIF as of 2024. The modern recommendation is AVIF first, WebP as a secondary <source>, JPEG as the universal fallback. See JPG to WebP if you need the WebP path.
You can pick AVIF's lossless mode (set Quality Preset to Highest), but the input JPEG is already lossy, so "lossless" here means no further loss beyond what the JPEG already lost. Lossless AVIF of a JPEG source typically ends up larger than the JPEG itself. For genuinely lossless workflows, start from PNG or TIFF.
The AV1 bitstream format wasn't designed for progressive decode — the file must be fully downloaded before any pixels can be shown. MDN notes this is rarely visible in practice because AVIF files are 30-50% smaller than the JPEGs they replace, so the total time-to-first-pixel still drops. If progressive matters (e.g., very large images on slow networks), keep JPEG.
Files are processed in your browser session via WebAssembly. They aren't stored after your session ends and you can clear them anytime by closing the tab. There's no account requirement, watermark, or per-file size cap aside from your device's available memory.