Image converter

Convert between HEIC, JPG, PNG, WebP, AVIF, GIF, BMP, SVG and ICO. Files are read by your browser and never sent anywhere.

Convert toQuality 82Background behind transparencyRender at 2× the SVG's own size

Choose images

Drop images here or paste from the clipboard.

Your files are processed on this device. Nothing is uploaded.

What this can and can’t do

Every conversion happens in your browser, which sets a hard boundary on what is possible. A browser will happily read 8 image formats, but it’ll only write 4 of them. The list of things you can convert to is short for that reason and this site would rather be short than pretend.

Format	Read	Write	What it is
JPG	Yes	Yes	The universal photo format. Lossy, no transparency, opens anywhere.
PNG	Yes	Yes	Lossless with transparency. Large for photographs, ideal for graphics.
WebP	Yes	Yes	Smaller than JPG at the same quality, with transparency. Web only in practice.
AVIF	Yes	No	Smaller again than WebP, newer support. Browsers read it but can’t write it.
GIF	Yes	No	256 colours and animation. Superseded for photos, still everywhere.
BMP	Yes	No	Uncompressed Windows bitmap. Enormous files, no reason to create new ones.
HEIC	Yes, via a decoder we ship	No	What an iPhone saves by default. Half the size of JPG and Windows often won’t open it.
SVG	Yes	No	Vector, so it has no fixed size. Rasterising it is a one way trip.
ICO	No	Yes	A container holding several sizes at once. What a favicon.ico actually is.

Picking a target format

Something needs to open it, anywhere

JPG. It is thirty years old, every device reads it and no support desk has ever asked what a JPG is. The cost is no transparency and a little lost detail.

It has a transparent background

PNG for a logo, icon or screenshot with transparency, WebP if it is a photograph that also needs transparency. Converting either to JPG flattens the transparent area onto a solid colour, which is the white or black box people are surprised by.

It is going on a website

WebP. It is typically 25 to 35% smaller than JPG at a quality most people can’t distinguish and every browser in current use reads it. AVIF is smaller again, but no browser can create one, so you would need a build step rather than this page.

It is a favicon

ICO, which is a container holding several square sizes at once. The converter writes 16, 32 and 48 pixel versions into one file by default, which is what a browser expects from favicon.ico.

Why it is fast after the first file

Decoding is the expensive part, especially for HEIC, which needs a WebAssembly decoder that has to be downloaded once and then run. Each file is decoded once and kept in memory, so moving the quality slider re-encodes but never re-decodes. On a batch of phone photos the first one takes a moment and the rest are close to instant.

Common questions

Is my file uploaded anywhere?

No. The converter is JavaScript running in your tab. Your browser reads the file off your disk, decodes it, re-encodes it and hands you the result. There is no upload step, which you can confirm by opening your browser’s network tab while you convert or by disconnecting from the internet after the page loads and converting anyway.

Why can I convert to JPG, PNG, WebP and ICO but not to AVIF or HEIC?

Because a browser can read those formats but can’t write them. Encoding is a separate piece of code from decoding and browsers only ship the encoders they need. Rather than pull in a multi-megabyte WebAssembly encoder and claim support, this site only offers conversions it can genuinely perform, so there is no page here for "JPG to AVIF".

Why is my converted file bigger than the original?

Usually because you converted from a modern format to an older one. HEIC and AVIF are far more efficient than JPG and PNG, so a 2MB HEIC can easily become a 5MB JPG at good quality. Going the other way or lowering the quality setting, shrinks it again. PNG is the other common case: it is lossless, so a photograph saved as PNG is always large.

Does converting lose quality?

It depends on the pair. Going into a lossy format (JPG or WebP) re-compresses the image and loses a little detail, which is what the quality slider controls. Going into PNG is lossless, but it can’t recover detail the original already lost. Converting the same file back and forth repeatedly does compound the damage, so keep your original.

What happens to EXIF data when I convert?

It is dropped. The converter works on decoded pixels, so camera model, timestamps and GPS coordinates don’t survive the round trip. That is usually what people want. If you specifically need to remove metadata but keep the file otherwise untouched, use the EXIF remover instead, which rewrites the container without re-compressing the image.

Can it handle a folder of files at once?

Drop as many files as you like and they’re processed one after another, then offered as a single .zip. Everything stays in memory in your tab, so the practical limit is how much RAM your device has rather than any upload size cap.