Most "HEIC vs JPG" articles end with the same lazy verdict: "HEIC is better, but JPG is more compatible." Sure. That doesn't help you decide what to do with the photo of your kid's soccer game that you're about to text to grandma, or the headshot you're about to upload to a job application.
The real question is never "which format is theoretically better." It's "which one is right for this specific photo, going to this specific place, right now." Here's how to actually pick.
Open the HEIC to JPG converterThe 30-second version
If you only read one paragraph: shoot HEIC, share JPG. Keep your iPhone's camera on the default High Efficiency setting so your library doesn't bloat — but the moment a photo leaves the Apple ecosystem (email, web upload, Slack, print service, any non-Apple person), convert to JPG. That's the workflow most pros and most prosumers actually use, even if no one writes it down that way.
Where they actually differ
Both formats store the same kind of thing — a grid of pixels with a bit of metadata. The differences come from how they compress and what software understands them.
| HEIC | JPG | |
|---|---|---|
| File size | ~50% smaller | Baseline |
| Bit depth | 10-bit color | 8-bit color |
| Transparency | Yes | No |
| Live Photo / depth | Stored alongside | Discarded |
| Opens on iPhone/Mac | Yes | Yes |
| Opens on Windows (default) | No | Yes |
| Opens in Slack / Discord / forms | Often no | Yes |
| Patent-encumbered | Yes (HEVC) | No |
HEIC is technically superior on every quality-and-size axis. JPG is technically superior on every "will the recipient be able to actually open this" axis. Both things are true at the same time, which is why the question keeps coming back.
When HEIC actually makes sense
You're keeping the photo on Apple devices
If the photo lives in your iCloud Photo Library and you only ever look at it on your iPhone, iPad, or Mac, HEIC is strictly better. Same quality, half the storage. Apple's Photos app handles HEIC natively and even shares it as JPG automatically when you AirDrop or message it to certain destinations. (The "certain" is doing a lot of work there — see below.)
You're shooting a lot, fast
If you're at a wedding, a kid's birthday, or a hike where you'll come home with 400 photos, HEIC is the difference between filling your phone and not. A 256GB iPhone holds roughly twice as many HEIC photos as JPGs at the same visible quality.
You care about Live Photos or depth data
HEIC files can carry the auxiliary data Apple's camera captures — Live Photo motion, portrait mode depth maps, ProRAW exposure metadata. If you convert to JPG, all of that is gone. For photos you want to preserve as fully editable later, leave them as HEIC.
You're shooting Portrait mode you'll edit later
Portrait mode photos stored as HEIC keep the depth map. Open the same photo in Photos a year later and you can still re-do the background blur. Convert to JPG and that's locked in forever.
When JPG actually makes sense
The photo is going to anyone outside Apple
This is the big one. The instant your photo crosses out of iMessage-to-iPhone or AirDrop-to-Mac, you should assume the recipient cannot open HEIC without effort. Windows users in particular need a paid extension from the Microsoft Store to view HEIC files, and most don't have it installed.
You're uploading to a web form
Job applications, government portals, school enrollment, insurance claims, photo print services — almost none accept HEIC. The file picker either grays it out or accepts it and then fails server-side. Convert to JPG before you upload and you skip the whole drama.
You're emailing photos to non-iPhone family
Mail and iMessage do an OK job of auto-converting HEIC to JPG when they recognize the destination is non-Apple. They don't always recognize it. The safest path: convert first, then send. Use our HEIC to JPG converter on a batch of photos at once — drop a folder, get JPGs back.
You need to compress for size
If you need to email or upload a JPG under a specific file size limit (most email servers cap at 25MB, many forms cap at 5MB), JPG plays nicely with quality sliders and resizing tools. We have a dedicated JPG compressor with a quality slider and a max-dimension picker exactly for this. HEIC compression tools are rarer and more inconsistent.
You're posting to Slack, Discord, or a forum
Most chat platforms accept HEIC uploads but then can't render the thumbnail, so it looks like a broken attachment until someone downloads it. JPG renders inline every time.
The hybrid workflow most people end up at
After enough trial and error, most iPhone users (consciously or not) settle on a hybrid:
- Leave the iPhone camera on the default High Efficiency setting so the library stays HEIC and storage stays manageable.
- When you go to send a photo somewhere that isn't another iPhone, convert to JPG first.
- If you're sending multiple photos in one go, batch convert them in one drop.
The annoying middle step is what made the HEIC-to-JPG converter category exist. The trick is to do it without uploading your photos to a stranger's server — which is what most "free" converters quietly do. (We wrote a separate piece on why free converters upload your files if you want to go down that rabbit hole.)
Convert HEIC to JPG locallyThe "should I just switch the iPhone setting" question
If you genuinely never need HEIC's space savings — you mostly shoot a few photos a week, you have plenty of iCloud storage, and almost every photo eventually goes to a non-Apple person — yes, flip the camera to JPG and forget about it. Settings → Camera → Formats → Most Compatible. Done.
But for most people that's leaving real storage savings on the table. A power user with 30,000 photos in their library and a 256GB phone really does feel the difference between HEIC-mode and JPG-mode, and "convert when needed" is the better long-run setup.
Other formats on the horizon
HEIC isn't the only "modern format" trying to replace JPG. AVIF (royalty-free, AV1-based) and JPEG XL (next-gen JPEG) are both technically excellent and both stuck in the same compatibility purgatory HEIC sits in. Apple now supports AVIF on the web side. Chrome supports AVIF and JPEG XL behind flags. Windows still defaults to "decline." Until one of them wins the OS-default battle, JPG remains the lingua franca for "I just need someone else to open this."
For now, the practical advice doesn't change: shoot in whatever your phone's default is, convert to JPG when the photo crosses out of your ecosystem, and don't pay 99 cents to Microsoft for the privilege.
If you need PNG, PDF, or compression instead
JPG is the right choice most of the time, but not always:
- For lossless export (screenshots, UI work, anything with text or sharp edges), convert to PNG with our HEIC to PNG converter.
- For multiple photos that need to be one document (think: emailing six receipts as one attachment), use HEIC to PDF instead — it rolls them all into a single multi-page PDF.
- If you already have JPG and need to get an iPhone photo under 5MB for an email or upload, the JPG compressor pairs the quality slider with a max-dimension cap so you can hit a target size in one shot.
That's the framework. Shoot HEIC, share JPG, pick the right exit format for the destination. It's not a war between two formats — it's a tool choice you make per-photo, like picking which lens to bring.
Open the HEIC to JPG converter