Guide

How do I batch-convert HEIC to JPG?

Trip ends, event wraps, client asks for the set—export the album and you often get dozens or hundreds of HEIC files. Feeding them one by one into an upload converter is slow and annoying. It also ships originals off your device.

The batch goal is simple: multi-select once, convert locally to JPEG everyone can open, then spot-check a few frames. More controllable than “park on an upload site and wait.” Basics for a single file live in convert HEIC to JPG without uploading.

1. A whole album of HEIC—single-file tools aren’t enough

Phones often default to HEIC. Copy to a PC, deliver to a client, or hit a backend that only accepts JPG, and single-file convert becomes wrist pain.

Batch workflow is about rhythm: export → convert → spot-check → optional metadata strip / watermark. Not dragging one file at a time through a convert page.

Event photography, product detail shots, family album backups—same pattern: many files, one target format, prefer not to expose originals to a random host.

Indie builders shipping screenshots from iPhones hit this too. A launch gallery of HEIC screenshots is useless to half your audience until you batch to JPEG.

2. Workflow: export/copy → multi-select → JPEG → download

Export or copy HEIC/HEIF from phone/album to a folder your computer can reach.
Open Heiclocal and multi-select the files.
Export JPEG (use PNG only if you need transparency).
Download results into a named project folder.

No dedicated client required—browser is enough. Name folders by date or project before you start so the cleaned set is ready for Metastrip later. Support: [email protected].

A practical habit: keep heic-source/ and jpg-export/ side by side. Never overwrite the source folder with exports. If a client asks for HEIC later (rare, but it happens), you still have originals.

3. vs upload batch sites (privacy + waiting)

Upload batch sites: originals leave the device. You wait in a queue. Large sets time out or fail midway.

Local approach: per product design, processing stays in the browser—not uploaded to our servers. Privacy boundary is clearer. You also skip the “upload then download again” tax.

Large batches still depend on your machine’s memory and browser. That is normal. It is not a hidden server quota. If the tab slows down, split the work.

4. Spot-check results; split batches if the browser struggles

Do not assume every file succeeded at perfect quality. Pull a few results: faces, bright skies, text on signs. Look at them.

Quality follows export settings. This page invents neither compression ratios nor a magic “max files per run” number. Limits are whatever your device and browser can handle that day. Fans spinning hard? Shrink the batch. Do not assume the files are corrupt.

Spot-check tip: sort by size after export. Oddly tiny outputs sometimes mean a failed or truncated convert—open those first.

If one file fails while others succeed, isolate it. Retry alone. If it still fails, check extension, transfer integrity, and whether the “HEIC” is actually something else renamed.

5. Next: Metastrip · Stampdrop · HL-1 · HL-3

Before public share, strip GPS and common EXIF with Metastrip—see batch-strip image metadata.
Watermark against casual reuse: Stampdrop.
Single-file basics: HEIC to JPG, no upload.
Windows cannot preview HEIC at all: open HEIC on Windows.

Common order: Heiclocal batch convert → Metastrip → optional Stampdrop. Format conversion does not remove location. Before a public drive or client package, spot-check that stripping actually ran—avoid “converted format, forgot GPS.”

Ogmake is for link preview cards, not this photo path. Keep marketing cards and real-photo exports in different folders so you do not mix pipelines.

FAQ

How many files at once?
Device and browser limits. No invented cap. If it stutters, split.

Does it upload?
Local processing. Not uploaded to our servers per product design.

Windows still can’t open a single HEIC?
Convert with Heiclocal (HL-1); OS decoder options in HL-3.

HEIF supported?
Yes—aligned with product: HEIC/HEIF.

Should every batch go through Metastrip?
For anything leaving your control (clients, public albums, open links), yes—prefer strip. Private backups on your own disk are your call.

Disclaimer

Heiclocal is not an Apple official tool. Judge batch results by the files you export. Support: [email protected].