HEIC vs JPG Converter: When Each Approach Wins (2026)
Last reviewed 2026-04-25. Covers iOS 18 (HEIC with gain map), iCloud Photo Library, macOS 13+ Photos export, and Windows 10/11 HEIF codec status as of April 2026.
What HEIC and JPG actually are
HEIC is the default container modern iPhones use for camera output. It wraps a HEIF-encoded photo (HEVC pixels, 10-bit depth, 4:2:0 chroma) with EXIF metadata, and on recent devices a gain map for HDR tone mapping. The result is roughly half the file size of an equivalent JPG at visually-equivalent quality. JPG (JPEG) is the universal photo format - 8-bit baseline, 4:2:0 by default, no gain map, supported by every operating system and email client released this century. The trade-off is size: a 3 MB HEIC is typically a 4-6 MB JPG at quality 85, or 6-10 MB at quality 95. Format choice is therefore a compatibility-vs-size decision, not a quality decision.
When to convert HEIC to JPG
Convert when the next person or system the photo touches cannot read HEIC. The five reliable triggers:
- Web upload form rejects HEIC. Most CMSes (WordPress, Shopify), HR portals, and photo-print services accept JPG and PNG only. Converting once beats failing per-platform.
- Windows 10 or 11 recipient without the HEIF codec. Windows preview needs the HEIF Image Extensions package (free in Microsoft Store, but most casual recipients have not installed it). Send JPG and the photo opens in the default viewer.
- Email or messaging attachment. Gmail, Outlook, Slack, and iMessage all preview JPG inline. HEIC attachments either show a broken thumbnail or get silently downscaled to a low-res preview.
- Editing in software released before 2020. Photoshop, Illustrator, and most consumer photo editors of that vintage do not open HEIC natively. Convert to JPG (or PNG, for lossless) before importing.
- Printing through any non-Apple service. Most online print labs reject HEIC at upload. Convert and pre-flight before ordering.
Run the conversion through HEIC to JPG in the browser. EXIF metadata is preserved by default; uncheck the EXIF option in Settings if you are sharing publicly and want to strip GPS or camera-ID data.
When to keep the HEIC original
Conversion drops information that the HEIC carries and the JPG cannot. Keep HEIC whenever any of the following applies:
- iCloud Photo Library sync. iCloud stores HEIC at roughly half the JPG size. Converting locally first doubles your iCloud storage bill for no compatibility benefit inside Apple's own apps.
- Live Photo, Portrait Mode, or HDR gain map. The motion clip, depth map, and gain map all live alongside the HEIC and are dropped on JPG export. Export-to-JPG is a one-way door.
- Round-tripping in Apple Photos or Affinity Photo. Both edit HEIC natively and preserve gain map data on save. JPG re-encoding adds artifacts on every save cycle.
- iPhone-only audience. AirDrop, Messages between iPhone users, and shared albums all handle HEIC end-to-end. Converting first burns disk space and edits-history for no recipient benefit.
- Source preservation. If the photo is one you might re-edit in five years, the HEIC is the closer-to-source asset. JPG conversion is acceptable for shipping a copy; the original stays.
Decision table - HEIC vs JPG by use case
| Use case | Format | Reasoning |
|---|---|---|
| Send to a Windows recipient with no codec | JPG | Universal preview, no install |
| Upload to a web form that rejects HEIC | JPG | Forms validate by extension and MIME type |
| Email a photo album to a mixed audience | JPG | Inline preview survives all major mail clients |
| iCloud Photo Library sync | HEIC | Half the storage bill at equivalent quality |
| AirDrop iPhone to iPhone | HEIC | Both ends decode natively; faster transfer |
| Live Photo or Portrait Mode preserved | HEIC | Motion clip and depth map live in HEIC only |
| Photo print order through a non-Apple service | JPG (or TIFF for premium) | Most labs reject HEIC at upload |
| Edit in Photoshop CC 2019 or older | JPG (or PNG) | HEIC support added in CC 2020+ |
| Edit in Photos / Affinity / Capture One | HEIC | Native edit; gain map preserved |
| Print master with the highest fidelity | TIFF or DNG (export from Photos) | Both HEIC and JPG drop bit depth and edit headroom |
Three approaches besides "browser converter"
The browser converter is the right answer for most one-off conversions. For specific cases, these alternatives produce a better result with less effort:
- Native macOS Photos export. Open Photos on Mac → Select photos → File → Export → Export Unmodified Original (keeps HEIC) or Export ... → Photo Kind: JPEG (converts on export). Photos handles batch exports of thousands of HEICs at OS-level speed and preserves the gain map when exporting to HEIF format. Best for a full library export.
- Native iOS export setting. Settings → Camera → Formats → "Most Compatible" makes the iPhone Camera capture in JPG and H.264 instead of HEIC and HEVC going forward. Use this if your iPhone is mostly producing photos for a non-Apple workflow and you want to avoid the conversion step entirely.
- Photos automatic conversion on transfer. Settings → Photos → Transfer to Mac or PC → "Automatic" converts HEIC to JPG when transferring to non-Apple targets via Lightning cable or Files app. The HEIC original stays on the iPhone; the destination receives JPG. Good for ad-hoc transfers where the source library should remain HEIC.
The browser converter wins when: you need 1-50 photos converted, the source files are already off the iPhone (in Files, Drive, Dropbox), and you do not want to touch iPhone or Mac settings. For 100+ photos, see how to convert 100 HEIC photos to JPG.
When neither HEIC nor JPG is the right answer
Both HEIC and JPG are display-grade formats. They are wrong for two specific cases:
- Print master at A3 or larger. JPG quantizes to 8-bit and applies chroma subsampling; HEIC keeps 10-bit but applies HEVC entropy coding that prints can amplify. For premium print sizes, export TIFF (16-bit per channel, no subsampling) from Photos: File → Export → ... → Photo Kind: TIFF.
- Long-term archival of camera-original data. If the photo will be re-processed in 10 years against future tone-mapping algorithms, neither format preserves enough information. Shoot or export as DNG (Adobe's open RAW container) instead. Most modern cameras and recent iPhones (15 Pro+ in ProRAW mode) support this.
The shorthand: HEIC vs JPG is a question for everyday photos. Print masters and decade-scale archival need a different conversation.
Compatibility status as of April 2026
HEIC compatibility has improved in the five years since Apple introduced it, but is still uneven:
- iOS / iPadOS / macOS: native, no install. AirDrop, Messages, Photos, Mail all preview HEIC inline.
- Windows 10: requires HEIF Image Extensions and HEVC Video Extensions from Microsoft Store. Free, ~30 seconds to install per machine.
- Windows 11: same as Windows 10 (Microsoft did not bundle HEIF in 11 either).
- Android: Android 10+ has native HEIC view. Android 9 and below need a third-party gallery.
- Web browsers (preview an attachment without download): Safari and macOS preview yes; Chrome, Firefox, Edge no inline HEIC preview as of April 2026.
- Email clients: Apple Mail and iCloud preview HEIC; Gmail, Outlook, Yahoo show a generic file icon.
- CMS upload widgets: WordPress core supports HEIC uploads since 6.4 (October 2023) but rendering depends on the theme. Most other CMSes (Shopify, Wix, Squarespace) still require JPG or PNG.
If your audience is uniformly on iOS or macOS, ship HEIC. If it is mixed or unknown, JPG is the safe default.
Frequently Asked Questions
Will the JPG copy look worse than the HEIC original?
At quality 95, the JPG is visually indistinguishable from the HEIC for most photos on a calibrated display. At quality 85, you may see faint banding on smooth gradients (sky, skin tones) because JPG quantizes to 8-bit and HEIC stores 10-bit. If the HEIC carries a gain map for HDR, the JPG export drops it; an HDR-capable display will render the JPG without HDR highlights. For everyday sharing, quality 85 is the right balance; for print-quality output, use 95.
Does converting HEIC to JPG strip GPS or camera metadata?
Not by default in HEIC to JPG - EXIF (timestamp, GPS, camera model, ISO, shutter speed) is preserved on the JPG by default. Uncheck the "Include EXIF" option in Settings to strip metadata before download. Stripping is recommended when sharing publicly (forums, online listings) and not when archiving (the metadata is part of the photo's history).
If I keep HEIC, what do I tell a Windows recipient who cannot open it?
Two options: (1) ask them to install the free HEIF Image Extensions from Microsoft Store - one-time, ~30 seconds, then HEIC opens in Photos and Explorer like any image; (2) just send the JPG copy this once via HEIC to JPG and avoid the codec install conversation. Option 2 wins for one-off recipients; option 1 wins if you regularly send HEIC to that person and the install pays back over months.
Summary
HEIC vs JPG is a compatibility decision, not a quality one. Convert to JPG when the photo leaves Apple hardware to a recipient or system that cannot read HEIC. Keep HEIC when the photo stays inside Apple, you want iCloud storage savings, or you might re-edit and need the gain map intact. For premium print or decade-scale archival, neither format wins - export TIFF or DNG from Photos. The five-second answer is in the decision table; the deeper sections explain the trade-offs so the choice does not feel arbitrary.
Ready to convert? Start with HEIC to JPG for browser-based conversion with EXIF preservation. For the format trade-offs across HEIC, JPG, and WebP, see HEIC vs JPG vs WebP. For batch conversions over 100 photos, see how to convert 100 HEIC photos to JPG.
Why trust these tools
- Ten-plus years of web tooling. The freetoolonline editorial team has shipped browser-based utilities since 2015. The goal has never changed: get you to a working output fast, without an install.
- Truly in-browser - no upload. Every file-processing tool on this site runs in your browser through modern Web APIs (File, FileReader, Canvas, Web Audio, WebGL, Web Workers). Your photo, PDF, audio, or text never leaves your device.
- No tracking during tool use. Analytics ends at the page view. The actual input you paste, drop, or capture is never sent to any server and never written to any log.
- Open-source core components. The processing engines underneath (libheif, libde265, pdf-lib, terser, clean-css, ffmpeg.wasm, and others) are public and audit-able. We link to each one in its tool page's footer.
- Free, with or without ads. All tools are fully functional without sign-up. The Disable Ads button in the header is always available if you need a distraction-free run.