Cookies for analytics and advertising
We use cookies for analytics and advertising, both sent to Google. Refusing changes nothing you can see.Read the privacy page
Image converter
Drop any image and the format is worked out from its bytes rather than its name, so a photo your phone called .jpg that is really HEIC is still identified correctly. Every image conversion here runs inside your browser: the file never leaves your device, there is no queue and no size cap, and the result downloads straight back to you.
Up to 100 files at once. Mixed formats are fine.
They convert one after another and download together as a ZIP.
Most used image conversions
Every image format we handle
18 formats in this category, 201 working conversions — 201 of them without your file leaving the device.
- JPGJPG
The universal photo format. Small files, no transparency, quality drops each time it is saved.
- PNGPNG
Lossless raster format with transparency. The safe choice for screenshots, logos and line art.
- WebPWebP
Google format for the web. Roughly 30% smaller than JPG at the same quality, with transparency.
- TIFFTIFF
The print and archiving standard. Lossless, multi-page capable, understood by every scanner.
- GIFGIF
Limited to 256 colours, but the only image format everything animates. Large files for video-like content.
- AVIFAVIF
The most efficient web image format today. Smaller than WebP, slower to encode.
- JXLJXL
The JPEG successor. Can repack existing JPGs 20% smaller without touching image quality.
- BMPBMP
Uncompressed Windows bitmap. Huge files, still produced by scanners and older software.
- ICOICO
Icon container holding several sizes in one file. Still what browsers expect as a favicon.
- HEICHEIC
What an iPhone saves photos as. Half the size of JPG, and awkward everywhere outside Apple.
- HEIFHEIF
The container standard behind HEIC. Same efficiency, same compatibility problems.
- CR2CR2
Canon sensor data from older DSLR bodies. Holds far more tonal range than a JPG.
- CR3CR3
The newer Canon raw container used by mirrorless bodies.
- NEFNEF
Nikon raw capture. TIFF based, which is why generic tools half-open it and get the colours wrong.
- ARWARW
Sony raw capture from Alpha bodies.
- DNGDNG
Adobe's open raw format. The one raw container that is not tied to a single camera maker.
- ORFORF
Olympus and OM System raw capture.
- RAFRAF
Fujifilm raw capture, with the X-Trans sensor layout most converters handle badly.
Tools for image files
Somebody whose photo is too big in the wrong sense — not too many kilobytes but too many pixels, for an avatar, a forum, a website or a form that wants a specific size.
Somebody who wants to know what a file is carrying before deciding anything — where a photo was taken, which camera, who wrote a document — without changing it and without handing it to a website.
Which format you actually want
For a photograph, JPEG remains the format everything can open, and WebP or AVIF will hold the same picture in noticeably fewer bytes if you control where it is going. AVIF is supported by every current browser and is the sensible default for anything destined for a web page.
For a logo, a screenshot, a diagram or anything with sharp edges and flat colour, PNG is the right answer and JPEG is the wrong one — JPEG was designed for photographs and puts visible fringing around lettering and hard lines. If the artwork exists as a vector, keep it as SVG for as long as you can: it stays sharp at any size, and rasterising is a door that only opens one way.
HEIC is the odd one out. iPhones write it, most of the rest of the world cannot read it, and converting to JPEG is usually why people arrive here. We read HEIC and deliberately do not write it — producing it needs an encoder we cannot license for this, and offering a broken button would be worse than saying so.
What a conversion costs the picture
Moving between two lossless formats — PNG to WebP lossless, PNG to TIFF — changes nothing at all; the pixels that come out are the pixels that went in. Moving into a lossy format discards detail deliberately, and how much is yours to choose on each page.
Moving *out* of a lossy format cannot undo what the first encoder threw away. Converting a heavily compressed JPEG to PNG produces a large file that faithfully preserves the compression artefacts, which is rarely what anybody wanted. Each pair here says which of these it is rather than promising "no quality loss" everywhere.
Image converter: common questions
Are my images uploaded to a server?
No. Every image conversion on this site runs in your browser, so the file never leaves your device. You can watch the network tab in your developer tools while you convert, or disconnect from the internet and convert anyway.
Can I convert HEIC to JPG?
Yes, and it is the most common reason people arrive here. We read HEIC and HEIF and write JPG, PNG, WebP and the rest. What we do not do is write HEIC, because the encoder that would need is licensed in a way we cannot ship.
Will converting reduce the quality?
It depends on the pair, and each page says so plainly. Lossless to lossless changes nothing. Into a lossy format discards detail by design, at a quality you set. Out of a lossy format cannot recover what was already gone.
Is there a limit on size or number of files?
None that we impose, and no account or watermark. Drop a hundred at once if you like. Because nothing is uploaded there is no server capacity to ration — the practical ceiling is your own memory.