Workflows
How to Convert iPhone HEIC to JPG
Converting iPhone HEIC to JPG is usually about compatibility, not image quality hype.
What you are really solving
How to Convert iPhone HEIC to JPG sounds simple, but the real task is making phone photos behave correctly in older apps, portals, websites, and everyday sharing systems — so the first move is to identify the destination (blog post, online form, CMS, email, ad platform, or messaging app) before touching any settings.
Step by step
Keep the guesses low: inspect the file, decide what the destination actually needs, then resize or compress in small, deliberate steps instead of re-exporting at random until it finally fits.
- Choose the HEIC file that needs a more compatible export.
- Convert to JPG when the destination does not reliably support HEIC.
- Resize or compress the JPG if the final upload path still has size limits.
- Keep the original HEIC file if you may need the source again later.
Settings that usually work
Use JPG for broad compatibility and then adjust size separately only if the final destination still needs a smaller file.
Example scenarios
A government form or job portal that rejects HEIC uploads. An office document workflow where colleagues cannot preview the original file correctly. A website or CMS that still expects JPG or another legacy-friendly format.
How it affects SEO and page speed
The conversion itself is not an SEO tactic, but it helps when phone photos are being published into systems that expect a more compatible web-friendly format.
Developer and workflow notes
Teams that accept user uploads should document whether HEIC is supported and when a conversion fallback is needed.
Common mistakes to avoid
- Assuming every platform handles HEIC the same way.
- Discarding the original HEIC source immediately.
- Using PNG for ordinary phone photos when JPG would be more practical.
- Ignoring later size optimization once the file is compatible.
What changes in file size and pixels when you convert
Converting does not shrink the photo on its own. A 12-megapixel iPhone HEIC and the JPG you export from it hold the same pixel grid, but HEIC stores it with HEVC compression at roughly half the bytes. Expect the JPG to land near double the source size at matching visual quality: a 2 to 3 MB HEIC typically becomes a 4 to 6 MB JPG. The conversion is a compatibility step, not a compression step, which is why a separate size pass is so often needed after it.
Pixel dimensions follow the capture mode, not the format, so the JPG inherits whatever resolution the original was shot at. Default iPhone capture is 12 MP; 24 MP and 48 MP only apply if Resolution Control or ProRAW was enabled. A 48 MP source is the one to watch, since a full-resolution JPG export from it can exceed 25 MB and stall slower upload forms.
For quality, JPG at 80 to 85 percent keeps phone photos clean while cutting bytes hard; below about 70 percent, JPEG drops to 4:2:0 chroma subsampling and red text or saturated edges start to smear. Stay at 90 percent or above only when the photo will be cropped, printed, or re-edited, because every JPG re-save compounds artifacts that HEIC and PNG would not.
- 12 MP default: 4032 x 3024 px, 4:3 aspect ratio, source HEIC about 2 to 3 MB
- 24 MP (Resolution Control on): 5712 x 4284 px, 4:3
- 48 MP (Pro main camera / ProRAW): 8064 x 6048 px, 4:3, source 25 to 100 MB+
- 16:9 video-style still: 4032 x 2268 px at 12 MP
- Square capture: 3024 x 3024 px at 12 MP
Fixing sideways photos and stripped depth data
The most common conversion failure is a portrait photo that lands rotated 90 degrees. iPhone HEIC stores portrait shots on a landscape pixel grid and records the turn in an orientation flag, and HEIC carries two of them: a QuickTime rotation value and an EXIF Orientation tag. A weak converter physically rotates the pixels and then copies the original EXIF tag unchanged, so the viewer rotates a second time and the image ends up sideways. A correct export bakes the rotation into the pixels and resets EXIF Orientation to 1, leaving the JPG upright everywhere.
Conversion also drops everything HEIC can hold that JPG cannot. A single HEIC container can store the depth map, a Portrait-mode segmentation matte, the Live Photo motion clip, and burst frames; JPG is one flat 8-bit image with no alpha and no depth, so all of that is discarded silently. If you need the depth blur or the moving frame later, that is the reason to keep the original HEIC rather than the JPG. Wide-gamut color is the other quiet loss: iPhone HEIC is tagged Display P3, and a JPG saved without an embedded ICC profile gets read as sRGB, which visibly flattens bright greens and reds.
GPS coordinates, the capture timestamp, and the camera model survive conversion as standard EXIF, which matters for two opposite reasons: a photo library or print service needs them to sort and orient correctly, but anything posted publicly leaks the exact location and time the shot was taken.
Sizing the JPG for where it lands
Once the JPG is upright and compatible, match its dimensions and weight to the destination instead of uploading the full 4032 x 3024 frame everywhere. Government and job portals are the strictest: many cap uploads at 1 MB or even 200 KB and reject anything wider than 2000 px, so resize the long edge to 1600 px and hold quality at 80 percent to clear both limits. Web and CMS use rarely needs more than 1920 px on the long edge; at 1920 x 1440 and 80 percent quality a photo lands near 300 to 500 KB, which is the right weight for an article image. Email attachments behave best under 5 MB total, so a 2048 px long edge keeps several photos in one message without bouncing.
Resolution stated in DPI is a red herring for any screen target, because browsers and forms read pixels, not DPI; the 72-versus-300 number only matters when a print service or document template explicitly asks for it. When a strict KB ceiling is the constraint, set the pixel dimensions first and let quality fine-tune the last few kilobytes, since halving the long edge cuts the pixel count to a quarter and does far more for file size than shaving quality percentage. The HEIC to JPG tool handles the format step, and Resize Image then Compress Image cover the dimension and weight passes when a destination still pushes back.
Related tools
Use the tools below to apply this workflow directly in your browser and finish the job without leaving the page.
