Convert to JPG

Drop in whatever you have — PNG, WebP, AVIF, HEIC from a phone, GIF, BMP, even SVG — and get JPG files back. You do not have to work out what each file is first; a mixed batch is handled in one pass, and none of it is uploaded.

Why JPG is still the answer

JPG is thirty years old and every newer format beats it on compression. It nevertheless remains the correct target whenever the destination is out of your control, because it is the one raster format that essentially all software can read: print shops, government e-filing portals, job application systems, older content management systems, digital photo frames, in-car displays, cheap label printers.

That is the real reason people search for this conversion. It is almost never about quality or size — it is about a form that rejected the file, or a program that would not open it. Compatibility, not compression, is what you are buying.

Where each source format comes from

HEIC arrives from iPhones and iPads, which have shot it by default since iOS 11 in 2017. WebP arrives from websites: right-click, save image, and you get a .webp because that is what the site served your browser. AVIF is the newer version of the same story and is even less widely supported outside browsers.

PNG usually arrives from screenshots and design exports. BMP tends to come from Windows utilities, medical and industrial equipment, and old scanner drivers — it is essentially uncompressed, so BMP files are enormous relative to their content. GIF arrives from the web and from messaging apps.

They all hit the same wall for different reasons, which is why a single destination page makes more sense than sending you to five separate ones.

What each conversion actually costs you

From PNG, BMP or a lossless source: this is your first lossy step, so the quality setting is the only thing that matters. At 82 the difference is very hard to see; below about 60 you will notice blocking in smooth areas like sky and skin.

From HEIC, WebP or AVIF: the image was already lossy, so this is a second generation of loss. Keep the quality at 85 or above for anything you might edit or print, because the encoder is now also spending bits preserving the first encoder's artefacts.

From GIF: a GIF has at most 256 colours, so JPG cannot make the palette worse — but JPEG handles the hard edges of GIF line art badly. Animated GIFs give you their first frame only, because JPG holds a single image.

From SVG: this is not really a conversion, it is rasterisation. A vector has no inherent pixel size, so it has to be rendered at some resolution and from then on it no longer scales cleanly. If the SVG is a logo you will need at several sizes, keep the SVG.

And in every case: transparency cannot survive. JPG has no alpha channel, so transparent areas become solid colour. If your PNG or WebP has a transparent background, convert to PNG instead — this is the single most common unpleasant surprise in image conversion.

Two formats this page will not pretend to handle

TIFF is not supported, and we tested this rather than assuming. Browsers do not decode TIFF, and our initial test appeared to pass only because the canvas fallback silently produced a PNG instead — a false pass that would have shipped a broken tool. Rather than ship a converter that fails on the multi-page and unusual-compression TIFFs that people actually have, we leave it out and say so.

RAW camera files (CR2, NEF, ARW and the rest) are also out. Each is a manufacturer-specific container that needs a demosaic pipeline, not a decoder. Use your camera maker's software or a photo editor for those.

How the conversion runs

Decoding uses your browser's own image decoders for everything except HEIC, which needs a WebAssembly build of libheif. Encoding uses MozJPEG compiled to WebAssembly, which produces smaller files at the same visual quality than the browser's built-in JPEG encoder.

All of it happens in this tab. No upload means no file size cap, no tasks-per-hour quota, no watermark and no account. Open the Network tab in developer tools and convert something — no request carries your image, and the Content-Security-Policy this site sends restricts connections to our own origin regardless.