How to Batch Convert HEIC to JPG (Unlimited, Free)
If you’ve just airdropped a few hundred photos off your iPhone and you’re staring at a folder full of .heic files, converting them one at a time is not a plan — it’s a punishment. The good news: you can drop the entire selection at once, let your own computer do the work, and get a single ZIP of JPGs back. I’ve run batches of well over a thousand photos this way, and because the whole thing happens in your browser, there’s no per-file limit to bump into.
The fastest way to convert a whole folder
Here’s the workflow I use, start to finish:
- Open the HEIC to JPG converter.
- Select every HEIC file you want —
Ctrl+Ain a folder, or click the first andShift+clickthe last — and drag the whole lot onto the drop zone. You can also click to open the file picker and multi-select there. - Wait while each photo decodes and re-encodes. A progress indicator shows how far along the batch is.
- Click Download all to grab one ZIP containing every converted JPG, with the original filenames preserved.
That’s it. No “upgrade to convert more than 5 files” wall, no email, no waiting in a queue. The conversion runs on your device, so the only thing that limits batch size is your hardware — not someone else’s server budget.
Why there’s no per-file limit (the client-side difference)
Most “free” online converters are actually thin front-ends to a server. You upload your photos, their machine converts them, and you download the result. That model has three built-in problems, and batching makes all of them worse:
- They cap your batch. Server time and bandwidth cost money, so free tiers throttle you — typically 5, 10, or 20 files, then a paywall.
- Everything uploads. Your full-resolution photos travel to a third party and sit on their disk. For a few hundred personal pictures, that’s a lot of private data leaving your control.
- It’s slow over the wire. A 1,000-photo batch might be 4-5 GB. Uploading that, then downloading it back, is often slower than just converting locally.
SnapHEIC works the other way around. The decoder runs in your browser as WebAssembly, so your files are read from disk, converted in memory, and never sent anywhere. That’s also why we can strip EXIF and GPS data on the way out — the metadata never has to leave your machine for us to remove it. If you want the technical proof, I broke it down on the how it works page, and there’s a dedicated guide on whether converting HEIC online is safe.
Browser vs. server batch converters
| What matters for big batches | SnapHEIC (in-browser) | Typical server converter |
|---|---|---|
| Files per batch | Unlimited (hardware-bound) | Often capped (5-20 free) |
| Photos uploaded | None | All of them |
| Download format | One ZIP | ZIP, sometimes paid |
| Speed on big batches | No upload wait | Upload + download time |
| EXIF/GPS handling | Stripped locally | Depends on provider |
| Cost | Free, unlimited | Free tier, then paywall |
Performance tips for big batches
Converting locally means your device is doing the heavy lifting, so a few habits make large batches go smoothly — especially on a phone.
- Convert in chunks of a few hundred on mobile. A laptop will happily chew through 1,000+ files, but phones have less RAM. If a huge batch makes Safari or Chrome sluggish, split it into groups of 200-300 and run them back to back. The result is identical; you’re just being kind to the memory.
- Keep the tab in the foreground. Mobile browsers aggressively throttle or suspend background tabs to save battery. On a long batch, leave the converter on-screen rather than switching apps, or the work pauses.
- Plug in or keep the battery healthy. Sustained conversion uses the CPU. On a phone, a low-power mode can slow things noticeably.
- Use a desktop for very large libraries. If you’re clearing out a multi-year camera roll, doing it on a laptop is genuinely faster and lets you select everything at once from a single folder.
- Don’t worry about quality. Each JPG is encoded fresh from the HEIC source; batching doesn’t compress files any harder than converting one by one would.
Other batch formats, same workflow
JPG is the right default for most people — it’s the most universally accepted format and opens on literally everything. But the drag-a-whole-folder, download-a-ZIP flow works for the other targets too:
- HEIC to PNG when you need lossless quality or transparency.
- HEIC to WebP for the smallest web-friendly files.
- HEIC to PDF to bundle a stack of photos into one document — handy for receipts or scanned pages.
If you only need to see the photos rather than keep them, the HEIC viewer opens them instantly without converting at all.
Should you batch-convert, or stop making HEIC files?
If you find yourself doing this conversion every few weeks, it’s worth treating the cause as well as the symptom. iPhones shoot HEIC by default to save space — I explain the reasoning in why your iPhone photos are HEIC — but you can flip a single setting to make the camera save ordinary JPGs from now on. The steps are in how to stop your iPhone saving as HEIC.
My honest take after years of doing both: leave HEIC on (the space savings are real and the quality is genuinely better), and batch-convert the photos you actually need to share or upload. You get the best of both — a smaller camera roll and JPGs on demand, no per-file limit, nothing uploaded.