Building a Reliable Browser-Local HEIC-to-JPG Batch Workflow

Converting one HEIC photo in a browser is mostly a decoding problem. Converting a batch is a workflow problem.

A useful batch converter has to keep files isolated, avoid exhausting memory, preserve successful results when one source is damaged, and make the output limitations clear. Here is the architecture I use for that workflow.

Keep the processing boundary explicit

The selected HEIC or HEIF files should stay inside the browser. The decoder can run as a self-hosted WebAssembly runtime, while the page itself still performs ordinary network requests for HTML, scripts, and optional analytics.

Those two facts are compatible:

• Page delivery can use the network.
• Source files, full file names, decoded pixels, generated JPG files, and ZIP archives do not need to be uploaded for processing.

For Image Convert, both HEIC tools use a pinned, self-hosted libheif 1.23.1 runtime. There is no server fallback if local decoding fails.

Treat every file as its own state machine

A batch should not be represented by one global success flag. Each file needs an independent state such as:

1. queued
2. decoding
3. encoding
4. ready
5. failed
6. removed

That separation matters when one file is unsupported or damaged. A failure should not erase the JPG files already produced from other inputs.

The user should be able to see which file failed, why it failed, and which files are still downloadable. If a ZIP option is offered, it should contain successful results only.

Prefer conservative processing over maximum concurrency

HEIC decoding can hold a compressed source, decoded pixels, a canvas or image buffer, and an encoded JPG at the same time. Starting many large photos in parallel can multiply that memory cost quickly.

Sequential processing is slower on paper, but it is easier to reason about and usually more reliable across laptops, phones, and memory-constrained browser tabs. A small, documented concurrency limit can also work, but it should be chosen deliberately rather than by mapping every file to a Promise at once.

After each item finishes, release temporary buffers and canvases that are no longer required. Revoke object URLs when an item is removed or after its download URL is no longer retained.

Start the default flow after validation

For a straightforward HEIC-to-JPG task, file selection can start the validated default conversion automatically. The important word is validated.

Before decoding, check the accepted extension and MIME information available from the browser, apply file and dimension safeguards, and map known failures to clear messages. Do not silently send an unfamiliar file to another service.

Automatic start works well here because the default output is unambiguous. A tool that creates one ordered PDF or opens a crop editor needs a different loaded-state workflow.

Make output limits visible

JPG is a lossy format. A converted photo may also lose metadata, and a Live Photo is not preserved as an interactive photo-and-video pair. Color and gamma behavior can vary across browser decoding and encoding paths.

The interface should explain those limits before users mistake “converted successfully” for “identical to the source.”

A practical completion checklist is:

• Open representative JPG results before deleting the originals.
• Keep the HEIC sources until the destination accepts the JPG files.
• Expect metadata to be reduced or absent.
• Treat Live Photos as still-image conversion unless motion handling is explicitly implemented.
• Split very large batches when browser memory becomes a constraint.

Design the batch around recovery

The best batch experience is not the one that assumes every file succeeds. It is the one that makes partial success easy to understand and recover.

A damaged source should produce a useful per-file error. Other successful files should remain available. Clearing the queue should release retained resources. Downloading a ZIP should never include failed or incomplete items.

I wrote a more detailed, task-focused walkthrough in How to Batch Convert HEIC to JPG in Your Browser, including practical uses, local-processing boundaries, and output limitations.