Why convert HEIC to JPG?
HEIC is what iPhones shoot by default — it stores the same photo in roughly half the space. The problem is what happens next. Microsoft Windows can't open it without a paid codec, most browsers still can't display it, and a huge number of upload forms, government portals and print shops reject it outright. You didn't choose HEIC; your phone did. Converting to JPG is how you make the file usable everywhere.
Universal compatibility
JPG opens on every device, browser, printer and upload form in existence. No codec pack, no "unsupported format".
Files never leave your device
Most converters upload your photos to a server you know nothing about. Here, decoding happens in your browser tab. Nothing is sent anywhere.
Fast & unlimited
No queue, no file-size cap, no 3-per-hour limit. Modern browsers decode HEIC natively; everyone else runs a WebAssembly decoder.
How to convert HEIC to JPG
- Add your files — drag them in, click Choose files, or paste with Ctrl + V. Multiple files at once are fine.
- Adjust if you want — drag the quality slider to trade file size against detail, or cap the resolution for email and web.
- Download — save individual images, or grab everything at once as a ZIP.
What output size should you expect?
This is worth knowing before you start, because HEIC and JPG are not equally efficient. Measured on a 1440×960 iPhone photo of 286.7 KB:
| Output setting | File size | vs original |
|---|
| JPG quality 95 | 771 KB | +169% |
| JPG quality 85 | 482 KB | +68% |
| JPG quality 75 | 366 KB | +28% |
| JPG quality 65 | 302 KB | +5% |
| JPG quality 55 | 260 KB | −9% |
| Match original size (auto) | 283 KB | −1% |
The HEVC codec inside HEIC is simply more efficient than JPEG — that is the entire reason Apple uses it. So a faithful JPG is normally larger, and every converter on the internet behaves this way. Your two levers are the quality slider and Match original size, which searches per file for the setting that lands closest to the file you started with.
FAQ
Why is my JPG bigger than the HEIC I started with?
Because HEIC is simply a more efficient codec. For the same visual quality, the HEVC compression inside HEIC needs roughly half the bytes of JPEG — that is Apple's whole reason for using it. So a faithful JPG of the same photo is normally larger. It is not this tool wasting space, and any converter will show you the same thing. If size matters more than compatibility, pick the WebP option (about 25% smaller than JPG) or press Match original size.
What does "Match original size" do?
It searches for the JPG quality setting that lands closest to your original file's byte size, doing the search separately for every file. You will usually end up around 65–72% quality — still visually identical on a screen, but without the files ballooning.
Is this really free? What's the catch?
Free and unlimited. The page runs entirely inside your browser, so there is no server cost per conversion for us to pass on to you. No account, no email, no watermark.
Are my photos uploaded anywhere?
No. That is the whole design. Your browser downloads a decoder once, then does all the work locally. Open the Network tab in DevTools while converting and you will see no request carrying your image — and the panel on this page counts the outbound bytes for you.
Does it strip metadata like EXIF?
Yes, and we would rather say so than pretend otherwise. Conversion runs through a canvas, so EXIF — including GPS coordinates and the original capture time — is dropped. For most people sharing photos online that is a privacy win, but if you need to preserve EXIF for professional work, use a desktop tool.
Which Apple and Android files are supported?
Any HEIC or HEIF container: single photos, and HEIF files written by some Android phones. HEIC image sequences (bursts) convert their first frame. Live Photos convert as a still JPG.
Why is the first conversion slower?
Your browser downloads the WebAssembly decoder once (about 1.4 MB, then cached). On Safari 17.6+ we skip that entirely because the browser already decodes HEIC natively.
Is there a file size or count limit?
No artificial limit. Everything is processed on your machine, so the only ceiling is your own memory. Very large batches (40+ full-resolution photos) will use a lot of RAM.