85% to 90% is the safest default for most HEIC photos
85% to 90% JPG quality is the range that solves most HEIC upload problems without creating bloated files. A typical 12 MP iPhone photo from an iPhone 15 or iPhone 16 can jump from a 2.5 MB HEIC to a 4 MB to 7 MB JPG at high settings, so exporting at 95% just to be safe usually wastes space. If the goal is quick compatibility, start with the main HEIC to JPG converter, keep the first JPG around 88%, and only make it smaller if the site still rejects the file.
Apple has kept HEIC as the default camera format since iOS 11 in 2017 because it saves roughly 30% to 50% of storage at similar visual quality, and that trade still makes sense on iOS 17 and newer devices. Apple explains the format shift in its HEIF and HEVC support guide, while Microsoft's support note on HEIF and HEVC file handling shows why Windows workflows still hit codec friction. The practical result is simple: keep HEIC originals, export JPG only for delivery, and use the homepage / when a form, CMS, or Windows 11 upload field refuses .heic.
Which JPG quality fits the job
The best setting depends on the destination, not on the file extension alone.
Use 80% to 85% for strict upload caps
A job portal with a 2 MB or 5 MB limit does not care that the original HEIC looked efficient on your phone. Start around 82% to 85%, then send the file through image compression if the first export still lands too high. If the site also wants a maximum width such as 1600 px or 2000 px, resize once with image resizing instead of repeatedly re-exporting the same JPG.
Use 88% to 92% for normal sharing
88% to 92% is the best range for email, listings, support tickets, and family photo sharing. At that level, the visible difference from a 95% export is usually tiny, but the file can be 15% to 30% smaller. This is also the cleanest setting for browser-local batches from the batch converter, especially when you are moving 20 to 100 iPhone shots to a Windows 11 23H2 PC.
How local HEIC to JPG conversion preserves quality
A browser-local converter reads the HEIC file through the browser file APIs, decodes the HEIF container and HEVC image data, turns the result into raw pixels, and then encodes those pixels as JPG. In modern tools, that usually means a WebAssembly-powered codec such as libheif plus the browser's Canvas export pipeline, which is the same class of web technology described by the W3C WebAssembly standard. Quality changes happen at the JPG export step, not because the file stayed local. That is why one careful export at 88% usually beats three rushed exports at 95%, 90%, and 80%.
A practical workflow that avoids oversized JPGs
One clean pass is better than trial and error. Convert once, inspect once, then add the next tool only if a real limit appears.
For one-off forms and marketplaces
Start with the main converter. If the first JPG is under 5 MB or 10 MB, stop there. If the destination is public, strip hidden metadata with EXIF removal before uploading. If you are deciding between local conversion and an upload-based service, free alternative to CloudConvert covers the privacy trade more directly.
For repeat Windows or office workflows
If the same office process rejects HEIC every week, read Open HEIC Files on Windows 11 and standardize on one export range for the whole team. An 88% JPG preset is usually enough for portals, help desks, and internal docs. If screenshots or UI captures look soft as JPG, switch that file to HEIC to PNG instead of forcing every image through JPEG.
FAQ
What JPG quality should I try first after converting HEIC?
Start at 88%. It is a better default than 100% or 95% because it usually preserves visual detail while keeping the file noticeably smaller for 5 MB and 10 MB upload limits.
Why is my converted JPG bigger than the original HEIC?
HEIC is more storage-efficient than JPG, so a 3 MB HEIC becoming a 5 MB JPG is normal. If the new file is too large, lower quality toward 82% to 85% or reduce dimensions once instead of re-exporting multiple times.
Should I use the same JPG quality for every photo?
No. A document photo for a form can handle 82% more easily than a detailed outdoor shot with foliage or hair. Batch jobs still work best when you start with one preset, usually 88%, and only adjust when a destination has a hard cap.
Does converting HEIC to JPG remove metadata automatically?
Not always. Format conversion and metadata cleanup are separate steps, so public uploads should still go through EXIF removal if location, device, or timestamp data matters.