Drop a folder, or click to choose images
JPEG · PNG · WebP · AVIF · HEIC · SVG · GIF · JXL · TIFF
Files never uploaded · 100% client-side · I cannot see your photos · Privacy policy
Pipeline ready: JPG → AVIF (any input still accepted)
Asset Melt Studio is a JPG to AVIF converter that runs entirely on your device. AVIF is the strongest size win for photo heroes when your audience is on modern browsers. Keep WebP or JPEG as a fallback.
Drop one JPG or a whole folder — the pipeline is already set to AVIF using libavif / AV1 stills. That is the JPG to AVIF workflow people search for: convert JPG to AVIF without an upload, then resize, crop, or hit a size budget (when the codec allows) before you download.
Input is not locked to JPG: you can still open JPEG, PNG, WebP, AVIF, HEIC, GIF, and more in the same session. The JPG to AVIF URL simply pre-selects AVIF so jpg to avif jobs start in one click.
A landscape hero for a landing page.
~95% smaller
Before · JPEG3.6 MB — Photo export
After · AVIF170 KB — Web hero, mid quality
Step 1
You are already on the JPG to AVIF converter. Output is pre-selected as AVIF. You can still drop mixed formats — the JPG to AVIF URL is a starting point, not a file-type lock.
Step 2
Drag JPG images onto the studio, click to choose, or paste. Folder drops queue nested images. Then process — JPG to AVIF encoding runs in Web Workers on this device.
Step 3
Use the before/after scrubber until the JPG to AVIF result looks right. Adjust quality, crop, or resize, then download one AVIF or a ZIP of the batch.
| Topic | JPG | AVIF |
|---|---|---|
| Photo compression | Mature, universal JPEG | Usually smallest modern still |
| Encode time | Fast (MozJPEG) | Slower (AV1) |
| Size budget | Supported | Supported |
| Transparency | No | No (JPEG source) |
| Fallback plan | Not needed | Keep WebP or JPEG |
JPG to AVIF (JPEG to AVIF) is the usual “we already have photos, we need Core Web Vitals” conversion. AVIF often beats both JPEG and WebP on noisy camera images.
Use JPG to AVIF for above-the-fold heroes and gallery thumbs if your CDN or build step can emit a fallback. Do not send AVIF-only to a random email list.
libavif runs locally. Size budget is the practical control when a CMS says 200 KB.
| Source | Before | After | Note |
|---|---|---|---|
| Phone hero | 3.8 MB JPEG | ~180 KB AVIF | Strongest typical saving |
| Studio JPEG | 8 MB JPEG | ~320 KB AVIF | Resize first for web |
| Already 120 KB JPEG | 120 KB JPEG | ~70 KB AVIF | Diminishing returns |
Drop JPEGs. The pipeline is AVIF. Optional resize to the displayed width × 2, then encode.
There is no alpha to preserve from JPEG. JPG to AVIF is a photo path, not a cutout path.
Also export WebP if you want a two-format kit from one queue.
Marketing sites with a modern browser baseline.
When JPG to WebP still leaves heroes too heavy.
Skip JPG to AVIF for print PDFs, some social uploaders, and tools that only sniff JPEG magic bytes.
Mid-range AVIF quality plus a size budget beats guessing. If skin tones band, raise quality or disable extra sharpen.
Strip GPS on people photos before you publish.
Use Lanczos or Magic Kernel resize — do not upscale.
AVIF lossless exists but will not beat a well-tuned lossy still for web photos.
Image processing is 100% client-side in your browser with WebAssembly. Your photos are not uploaded, I cannot see or recover them, and sampled session replay is UI-only and does not include image pixels (media is blocked). The site still sends usage analytics and crash reports — details are on the privacy page. That includes every JPG to AVIF job — the converter never needs your files on a server.
Upload compressors send your bitmap to someone else’s API. Asset Melt keeps jpg to avif on this device. Session replay, if sampled, is UI-only and does not include image pixels.
Related conversions