Why the Same iPhone Photo Looks Worse Every Time You Touch It

Why the Same iPhone Photo Looks Worse Every Time You Touch It

A woman selling vintage jackets on Depop noticed it first in her thumbnails. She'd photographed the jacket on her iPhone, which — like most iPhones set up in the past several years — saved the shot as HEIC by default. To list it, she exported a JPEG copy for the app to accept. That JPEG looked crisp in June. By August, after being cropped once to fix the framing and adjusted again for brightness before a re-listing, it had gone soft around the edges — not blurry exactly, just less defined, like it had been photocopied one too many times. She assumed her camera was at fault, or maybe the app's upload compression. Neither was the real cause. The HEIC original sitting untouched in her camera roll was fine. What had degraded was the JPEG copy, and it had degraded a little more with every save.

This exact pattern plays out constantly, and almost nobody traces it back to where it actually starts.

Three Formats, Doing Three Different Jobs

The confusion usually comes from treating HEIC, JPEG, and PNG as interchangeable — different flavors of the same thing. They're not; each one is built around a different priority.

HEIC is what the iPhone camera captures by default. It's efficient — roughly half the file size of an equivalent JPEG — which matters when you're shooting hundreds of photos on limited storage. But it isn't really built to be opened, edited, and re-saved repeatedly outside Apple's own apps. Most other software converts it to something else the moment it's touched, usually without asking.

JPEG is where it typically lands next: the default export target for almost every editor, messaging app, and marketplace, because it's small and universally recognized. The trade-off is that JPEG is lossy. Every time it's saved, the format throws away some visual information to keep the file size down, and it has no memory of what it already discarded the last time.

PNG works differently from both. It's lossless — nothing gets discarded on save, ever — and it stores transparency with real precision rather than a simple on-or-off toggle. The file is larger as a result, but nothing is lost no matter how many times it's opened again.

Format<br>Compression<br>Re-saving<br>Transparency<br>Best use

HEIC<br>Efficient, lossy<br>Not built for repeated edits<br>No<br>Original camera captures

JPEG<br>Lossy<br>Degrades with each save<br>No<br>Quick sharing, casual web use

PNG<br>Lossless<br>Safe for unlimited saves<br>Yes (256 levels)<br>Editing, text, graphics, transparency

Where the Damage Actually Starts

A photo that starts as HEIC doesn't usually stay that way for long. The moment it's shared with someone on Android, uploaded to a marketplace or CMS that won't accept HEIC, or opened in an editor that converts on import, it typically becomes a JPEG — often without anyone choosing that step deliberately. That conversion itself isn't the problem. The problem starts afterward, once that JPEG gets opened and saved again. And again.

Crop it in the Photos app: saved. Add a caption in Canva: exported, saved. Adjust the exposure a month later in a listing tool: saved once more. Each of those saves is a fresh round of lossy compression, discarding a bit more data than the last, with no memory of what was already lost. Individually, none of these edits look aggressive. But by the fifth or sixth round, fine edges have softened, smooth gradients show visible banding, and small text develops a faint halo it didn't have originally. This is generally known as generation loss, and it's cumulative — a side effect of the JPEG stage, not something inherent to HEIC itself.

What Actually Changes With PNG

Converting that working file to PNG at some point doesn't fix things through a filter or a setting. It changes the underlying math. PNG compresses the way a ZIP file does — by finding patterns and repetition — without ever touching the pixel values themselves. Whatever goes in comes back out exactly the same, whether it's opened once or fifty times.

The transparency handling works on the same principle. PNG stores 256 levels of opacity per pixel, not just transparent-or-not. That's what allows a soft, feathered edge around a subject cut out of its background — something JPEG can't do at all, since it has no transparency channel to begin with. A JPEG is always, structurally, a rectangle.

Where That Precision Actually Shows Up

These aren't abstract technical points. They surface in specific, ordinary situations.

A reseller cutting a product out of its background for a marketplace listing needs that gradual, feathered edge — a hard cutout with jagged pixels around the collar of a jacket reads as amateurish next to a listing where the product simply sits on white. That softness only exists because PNG can store partial transparency; there's no equivalent workaround in a format that can't store transparency at all.

A real estate listing photo often passes...