Does quality drop if I shoot directly in JPG?

Shooting directly in JPG is more advantageous quality-wise than shooting HEIC and converting to JPG later, because only a single round of compression occurs. On the conversion path there are two rounds: HEIC compression at capture, then JPG compression at conversion. However, JPG has a permanent ceiling: the wider color information and HDR data HEIC can carry are never written to JPG at all. So shooting JPG saves you from generation loss but lowers the format ceiling from the outset.

How much space does shooting HEIC actually save?

It would be wrong to give a concrete ratio, because the result varies with the photo's content, the resolution and the device's compression settings. What can be said generally is that HEIC takes up markedly less space than JPG when targeting the same visual quality; the reason is that it uses a more advanced algorithm derived from video compression. If your device storage is at a level where it is constantly filling up, this difference becomes noticeable in practice.

If I am into photography professionally, which is right?

Neither is the full answer. In a professional workflow, the real issue is switching to a capture mode that stores the device's raw sensor data and doing your edits from that data; both HEIC and JPG are processed, compressed outputs. That is a separate discussion, but if you are stuck between the two compressed options, HEIC carries more color and dynamic range information and therefore leaves more room for editing.

Shoot JPG on Your Phone, or Shoot HEIC and Convert?

Q: Can I follow a mixed approach?

Yes, and for most users this is the most sensible option. You leave the device on HEIC and keep your archive efficient, converting only the photos you hand outward to JPG. The advantage of this approach is that you pay the conversion cost only on the files you actually need. The disadvantage is that every share requires an intermediate step; if you go through that step often, changing the device setting may be more practical.

The decision sits between storage and compatibility

Your iPhone shoots HEIC by default. You can change that in the camera settings and have it produce JPG directly. Which is right for you?

This decision is not a contest of technical superiority but a matter of looking at your own workflow. Do your photos mostly stay on the phone, or do they get transferred to a computer constantly? Is your storage tight or plentiful? How many people do you share files with?

In this article we compare the two approaches across storage, quality, compatibility and practical workflow.

Storage: HEIC's clear advantage

HEIC adapts the HEVC technology used in video compression to still images. That technology was developed long after the compression approach JPG rests on, and it achieves the same visual quality with markedly less data.

The practical upshot is this: you can store far more photos in the same amount of storage on your device. If your storage is at a level where it is constantly filling up, or if you take a great many photos, this difference becomes noticeable.

When you switch to JPG, every photo takes up more space. That directly affects device storage, backup space and transfer times.

Quality: two different kinds of loss

A careful distinction is needed here, because the two paths have different loss profiles.

Shooting directly in JPG: A single round of compression occurs. Sensor data is processed and saved directly as JPG. There is no generation loss. But JPG's structural limits come into play from the outset: the wider color range and HDR information HEIC can carry are never written to JPG. That data never exists at all.

Shooting HEIC and converting later: Two rounds of compression occur. First HEIC compresses lossily at capture, then JPG applies its own lossy algorithm at conversion. On top of that, the wide color and HDR information HEIC carries gets flattened on the way to JPG.

So on both paths, the JPG output does not carry the richness HEIC can. The difference lies here: if you shoot directly in JPG you escape generation loss, but a rich version never exists on the phone. If you shoot HEIC, the rich version sits on your device and you produce the JPG only at the moment of need.

In practice, most of these differences are indistinguishable by eye on an ordinary photograph converted at a high quality setting. Where they become pronounced is in high-contrast scenes and when viewing on HDR-capable displays.

Compatibility: JPG's clear advantage

There is no debate here. JPG has worked everywhere for more than thirty years — on every operating system, on every website, in every image program, at every print service.

HEIC, by contrast, is flawless inside the Apple ecosystem and full of friction outside it. Some Windows versions require an additional component, many sites do not accept uploads, older desktop programs do not recognize it, and most print services do not want it.

Behind this difference sit both HEVC's licensing complexity and the software world's slowness in adopting new formats.

Which one in which scenario

Your photos mostly stay on the phone and get backed up to iCloud occasionally: Stay on HEIC. You save space, suffer no quality loss, and nothing goes wrong between Apple devices.

You transfer to a computer every week and upload to a system: Switch the device setting to JPG. Dealing with a conversion every time means both wasted time and an unnecessary round of loss.

You hand a few photos outward each month: Stay on HEIC and convert when needed. You can handle it in a few seconds with the HEIC to JPG converter, and your archive stays efficient.

Your storage is constantly filling up: HEIC. This is precisely the problem the format exists to solve.

You constantly share photos with others for work: JPG. You never have to think about whether the other side can open the file with every share.

You edit and publish your photos: HEIC carries more color and dynamic range information and therefore leaves more room for editing. Do the editing in a lossless working format and produce the published version separately.

The mixed approach: the most balanced for most users

The most sensible solution in practice is usually this: leave the device on HEIC so your archive stays efficient. Convert the photos you hand outward, upload to a site or send to someone else to JPG at that moment.

The logic of this approach is that you pay the conversion cost only on the files you need. Converting all of thousands of photos to JPG unnecessarily — spending storage and adding a round of loss to each one — makes no sense.

If you go through this intermediate step several times a week, then the time saved by changing the device setting becomes more valuable than the storage lost.

In summary

HEIC wins on efficiency, JPG wins on compatibility, and the choice between them depends entirely on your workflow. Shooting directly in JPG eliminates generation loss but means giving up the wide color and HDR information HEIC can carry from the outset. Shooting HEIC and converting when needed keeps the archive efficient but adds a second round of loss with every conversion. For most users the right answer is the mixed approach: shoot HEIC, convert as needed. If you are constantly handing files outward, switching the device setting to JPG saves you from a repetitive chore.