How bulk HEIC conversion works in the browser
The bulk converter is the same engine as the single-file version, just with two extra steps:
- You drop many files. Each one is queued.
- The converter processes them one at a time (sequential, not parallel — this keeps RAM usage predictable).
- As each finishes, the JPG is held in memory.
- When the whole batch is done, you click Download all as zip — the JSZip library packages the lot into a single .zip file and your browser saves it normally.
Just like the single-file converter, none of your photos touch our server. Bulk conversion doesn't change that — the larger the batch, the more obvious the privacy win, because you're not uploading 2 GB of personal photos to some random converter site.
When you'd want to bulk convert HEIC
- Migrating from iPhone to a non-Apple workflow — exporting years of photos for use in Lightroom on Windows, Affinity Photo, GIMP, or any tool that doesn't speak HEIC.
- Sharing albums with relatives on Windows or older Android — HEIC support is still patchy outside Apple's ecosystem.
- Uploading to web platforms that reject HEIC — many old job-application portals, government forms, school systems, real estate sites still only accept JPG.
- Archiving for long-term compatibility — JPG is 32 years old and will still open in 50 years. HEIC is newer and more locked to specific codec implementations.
Browser memory — the only real constraint
Bulk conversion lives or dies on your browser's RAM budget. Some practical numbers:
- Typical iPhone HEIC: 1-3 MB on disk, decodes to ~30-50 MB of raw pixels in memory.
- During conversion: peak memory ≈ largest single file's pixel buffer + JPG output buffer ≈ 80 MB worst case.
- The accumulated zip: all the JPGs together. 200 photos at 2 MB each = 400 MB zip held in memory before download.
On a desktop with 8 GB+ free RAM, you can comfortably batch 200-300 files. On a laptop with 4 GB free, stay under 100 per batch. If you hit a memory error, the converter tells you clearly — just refresh and split the job.
Privacy in bulk
The privacy guarantee scales perfectly with batch size: 1 file or 1,000 files, the same zero bytes leave your machine. Compare that to uploading 1,000 personal photos to a converter SaaS — your entire photo library briefly living on a server somewhere, possibly logged, possibly indexed, possibly retained "for service improvement" depending on the operator's policy. This converter never even has the option to do any of that.