The HEIC Format and Why It Needs Converting
High Efficiency Image Container (HEIC) is Apple’s default photo format since iOS 11. It wraps a still image encoded with High Efficiency Video Coding (HEVC, also known as H.265) into an HEIF container. The compression is roughly twice as efficient as JPEG for the same subjective quality — a 12‑megapixel iPhone photo that might take 5 MB as JPEG can occupy 2.5 MB as HEIC. That halving of storage matters on devices with fixed capacity.
The catch: HEIC is poorly supported outside the Apple ecosystem. Windows (before certain updates), Android (without add‑on libraries), most web browsers, many photo‑printing kiosks, and nearly all enterprise document management systems cannot open it. Attempting to share an HEIC image with someone who does not own an Apple device often results in a “cannot preview” message or a garbled attachment. The most reliable fix is to convert to JPEG, a format every browser, operating system and print pipeline has supported for decades. This page does exactly that — it reads HEIC and writes JPEG. It does not produce HEIC; if you need a different output format you need another tool.
How the Conversion Works (Client‑Side Processing)
Every conversion happens inside the user’s browser. No file is uploaded to any server. The browser decodes the HEIC container and decompresses the image pixels on the device, then re‑encodes those pixels as a JPEG. The quality parameter passed to the encoder is taken directly from the slider (40–100%, default 92%).
Because the work is done locally, the tool respects privacy and works offline once the page is loaded. The only network request made is to fetch the page itself and its scripts. There is no per‑file size limit; the practical ceiling is what the device can hold in memory, which on modern hardware comfortably covers high‑resolution phone photos.
An important fallback exists: the browser can produce a JPEG only if it supports JPEG encoding. A few browsers (very rare, but technically possible) may not. In that case the tool automatically writes the image as PNG instead, and the result is clearly labeled: “Your browser doesn’t support saving this format — used PNG instead.” The user still gets a usable image, though at a much larger file size than a JPEG would have been.
Input, Output and Quality Controls
Inputs
- One or more HEIC (or HEIF) images — this page accepts no other input format.
- A quality value between 40 and 100 percent, set via a slider (default 92%).
- The target output format is fixed to JPG; there is no output‑format choice on this page.
Outputs
- For each successfully processed image: a download button that saves a
.jpgfile. - A line showing the output filename, dimensions, original file size, converted file size, and a label: either “Saved” (converted size smaller than original) or “Larger” (converted size bigger).
- Below the list of converted images: a summary line reading
Total: ‹total original size› -> ‹total converted size›. - When two or more images have been converted: a “Download all (.zip)” button that bundles every output into a single ZIP archive.
The quality slider is the primary control over the size–fidelity trade‑off. JPEG is a lossy format; every encoding discards information. At 100% quality the encoder uses its least aggressive quantization table, producing a very large file that is visually nearly indistinguishable from the original (though still not lossless). At 40% the file shrinks dramatically but blocking artefacts, colour banding and ringing around edges become visible. There is no preset “optimal” value — the right setting depends on the image content and the acceptable file size.
Understanding the “Saved” vs “Larger” Labels
HEIC’s compression advantage means that most HEIC images converted to JPEG at a sensible quality (say 70–90%) will produce a larger file. The tool compares the original file size in bytes with the converted file size. If the converted size is smaller, it is labelled “Saved”; if larger, “Larger”. Because HEIC already achieves about 50% compression relative to JPEG at the same quality, “Larger” is the expected outcome unless the slider is set very low (40–50%) where the JPEG quantisation outweighs the format inefficiency. The user can use this feedback to adjust quality: if nearly every conversion says “Larger”, one may choose to reduce quality further or accept the file size increase for the sake of universal compatibility.
JPEG also suffers from generation loss — re‑encoding a JPEG (or any lossy image) introduces additional degradation. Because this page accepts only HEIC input, no JPEG is ever re‑encoded here: the loss is a single, one‑time step from the decoded HEIC pixels to the final JPEG.
Error Handling and Edge Cases
The tool checks inputs at several stages and displays precise error messages. Every error message in this list is verbatim from the page:
-
“This file type isn’t supported.”
The file is not a HEIC/HEIF image — this page accepts nothing else. No attempt is made to parse it. -
“Choose up to ‹max› images at a time.”
The batch limit has been exceeded: this page converts up to 20 images at a time. Selecting more than 20 triggers this error before any conversion begins. -
“This file could not be opened as an image. It may be corrupted, empty, or not actually an image.”
The file’s extension or MIME type was acceptable (say,.heic), but the decoder could not extract a valid image frame. Common causes: a truncated download, a zero‑byte file, or a file renamed to.heicthat is actually something else. -
“Conversion failed. Try a different image or format.”
Everything passed the initial checks, but the JPEG encoding step threw an error. This is rare and usually points to a browser glitch. The user is advised to try a different image. -
“‹count› file(s) could not be processed.”
In a multi‑file batch, one or more files failed individually. The successfully converted images are still shown and downloadable; this message appears as a summary warning. -
“Your browser doesn’t support saving this format — used PNG instead.”
As described above. The output file is a PNG, not JPEG, and is clearly labelled as such.
Batch Processing and Download Options
To convert multiple images, the user selects them all in one go (using the Ctrl/Command key or Shift in the file‑picker). Each image is processed one at a time, in selection order, while a status line shows which file is being converted. The results then appear as a list, each with an individual download button. When two or more images have been successfully converted, a “Download all (.zip)” button appears at the top of the results. Clicking it creates a ZIP archive in the browser — named brobrogo-converted.zip — containing all JPEG output files (or PNG fallbacks) and downloads that ZIP. The original filenames are preserved (with the extension changed to .jpg; if two outputs would share a name, the later ones get -1, -2 suffixes). The ZIP file has no root folder — all images are placed at the top level of the archive.
There is no option to selectively exclude individual images from the ZIP; if you need only some, download them individually. The batch limit applies to the input selection, not to the number of successfully converted images shown.
Who Needs This Tool and Why
The primary users are iPhone and iPad owners who need to share photos with people or systems that do not support HEIC. Common scenarios:
- Uploading to a website that only accepts JPEG (many e‑commerce platforms, school portals, government forms).
- Emailing photos to someone on an older computer or Android device that cannot view HEIC.
- Sending images to a photo‑printing service that explicitly states “no HEIC files.”
- Reducing storage on a device while retaining universal readability — though converting to JPEG actually increases file size, the conversion frees the user from HEIC compatibility worries.
- Batch conversion for a photographer who switches between Apple and non‑Apple workflows and needs all images in a single compatible format.
The client‑side nature also appeals to privacy‑conscious users who must not upload sensitive photos to a remote server. Because no data leaves the device, the tool can be used behind a corporate firewall or with personally identifiable images without additional risk.
FAQ
Why is my converted JPG larger than the original HEIC?
HEIC is inherently more efficient. At any quality setting above the low end, a JPEG will be larger than the same image stored as HEIC. The “Larger” label is normal unless you set the quality slider very low (40–50%).
Can I convert other formats to JPG on this page?
No. This page converts HEIC/HEIF files only; anything else is rejected as an unsupported type. Sibling pages cover the other sources — PNG to JPG, WebP to JPG and AVIF to JPG.
What if my browser doesn’t support saving JPG?
The tool falls back to PNG and labels the output clearly. This is extremely rare — all major desktop and mobile browsers support JPEG encoding.
Is there a limit on the number of images I can convert at once?
Yes — up to 20 images per batch. If you select more, you will see the error “Choose up to ‹max› images at a time.”
Does this tool convert images to HEIC?
No. It only reads HEIC and writes JPG. If you need to produce HEIC files, you will need a different tool (usually an Apple device or a specialised encoder).
What quality setting should I use?
For most purposes, 80–85% offers a good balance between file size and visual quality. For archival or high‑quality prints, use 95–100% and accept the larger file. For web uploads where size matters, 60–75% is common. Test with a representative image to see if artefacts are acceptable.