Image converter — runs entirely in your browser

Two ideas explain most of the difference. Lossy formats (JPEG, WebP, AVIF, JPEG XL) shrink a file by throwing away fine detail your eye is unlikely to notice — the Quality slider decides how much. Lossless formats (PNG) keep every pixel exactly, which is safer for sharp edges and text but makes bigger files for photos. Only some formats can store a transparent background.

JPEG — share it anywhere. The universal choice for photographs. Files are small and open on practically every device and app. No transparency, and re-saving repeatedly slowly softens quality. When in doubt, this is the safe pick.

PNG — graphics, text, and transparency. Lossless, so screenshots, logos, icons, and line art stay crisp with no fuzzy edges, and it is the format to reach for when you need a see-through background. The trade-off is much larger files for full photographs.

WebP — the modern all-rounder. Noticeably smaller than JPEG and PNG at the same quality, supports transparency, and works in every current browser. A great default for images you put on a website.

AVIF — the smallest files. The most efficient compression here, with transparency. Ideal when small size matters most, such as a fast-loading web page. It is newer, so very old software may not open it yet, and encoding takes a little longer.

JPEG XL — future-proof, where supported. Excellent quality for the size, and it keeps transparency. Support is still growing, so pick it only when you know the place you are sending it can open it.

A quick rule of thumb. Sending a photo to someone — JPEG. A screenshot, logo, or anything that needs transparency — PNG. Putting images on your own website — WebP, or AVIF when you want the smallest possible file.

Everything is local. Your images are read, decoded, resized, and re-encoded entirely in your browser using a background worker. Nothing is uploaded — the converter has no upload endpoint at all — so closing the tab destroys every file you added.

One pipeline, any format. Each file is decoded to raw pixels, optionally resized, then encoded to your chosen format. PNG, JPEG, WebP, GIF, BMP, and AVIF are decoded by the browser itself; HEIC/HEIF and TIFF are decoded by engines loaded on demand only when you upload one; SVG is rasterized on the main thread by the browser's own renderer. PNG, JPEG, and WebP are encoded by the browser; AVIF and JPEG XL use compact WebAssembly encoders, also loaded on demand. Every conversion passes through standard 8-bit sRGB pixels, so the output never carries higher bit depths or wide-gamut color profiles from the original. Animated images are not supported — only the first frame of a GIF is converted.

SVG is vector, so it is flattened to pixels. An SVG describes shapes rather than a grid of pixels, so there is no SVG output — converting one rasterizes it with the browser's own renderer. The shapes are drawn directly at the output size you pick, so an image enlarged with the Resize option stays sharp — no small bitmap is being stretched. An SVG's declared size can be tiny, so use Resize to set the dimensions you actually want. Any script inside the SVG is ignored and nothing it references is fetched.

No HEIC output by design. HEIC encoding is patent-encumbered and impractical in the browser, so we offer AVIF instead — the same compression family, royalty-free, and widely supported.

Orientation. Photo rotation is read from the original and baked into the pixels, so portrait photos stay upright. When the original EXIF is preserved (JPEG, PNG, and WebP output), the orientation tag is reset so the image is never rotated twice.

Metadata. By default the app copies the original EXIF into the output whenever the target can carry it — JPEG, PNG, and WebP. AVIF and JPEG XL are re-encoded without it, because their in-browser encoders cannot embed metadata. Tick “Remove all image metadata (EXIF)” to guarantee a clean file. Either way, the app never writes metadata of its own.