Convert HEIC to JPG without losing quality: a practical guide

Every iPhone since 2017 has defaulted to HEIC for photos. That's a neat trick for saving storage space, but it's also the reason your coworker, your kid's teacher, or the person running your website's CMS can't open the image you just sent. The file sits there, unopenable, while you get a confused email back.

The obvious fix is to convert HEIC to JPG without losing quality, and the good news is you can do it well. The bad news is you can also do it badly. This post is about doing it well, in a browser, without installing anything, and without turning your crisp sunset photo into a blocky mess.

Why JPG is the compatibility choice

HEIC is technically superior in a few ways. Better compression, support for multiple images in one file, richer color metadata. But none of that matters when the recipient double-clicks the file and gets an error dialog. Windows didn't get native HEIC support until a 2018 update, and even now it often requires a paid codec extension. Many Android phones handle it, but plenty don't. Email clients, school assignment portals, content management systems, print labs, government upload forms, these all expect JPG.

JPG is the lowest common denominator that just works. That doesn't mean you have to crush your photos into oblivion to get there.

Where quality loss actually comes from

Converting HEIC to JPG isn't like translating a document where meaning might get lost. It's re-encoding. The HEIC file uses one compression algorithm, the JPG uses another, and during conversion the image gets decompressed and recompressed. That second compression step is where artifacts sneak in if you aren't careful.

But here's the thing that's often misunderstood: the quality slider in a conversion tool isn't a "keep more original data" dial in the way raw photographers think about bit depth. It's a tradeoff between file size and how aggressively the JPG algorithm discards information your eye won't notice. Set it too low, and you'll see blocky edges in blue skies and muddy skin tones. Set it too high (95-100), and you get enormous files with almost no visible improvement over 85-90.

The sweet spot for photos of people, places, and things is about 85-90 on a typical 0-100 quality scale. At that point, compression artifacts are invisible to almost all viewers on almost all screens, while the file size stays practical for email and uploads. I'd only push toward 95+ for images with heavy text, sharp graphics, or if I knew the JPG would be edited again later.

What ruins quality faster than conversion

Here's a tip that'll save you from yourself. Do not, under any circumstances, re-screenshot or screen-capture a HEIC photo and save that as your JPG. I see people do this because it feels quick. They open the photo, take a screenshot, crop it, done.

That process loses quality twice over. First, you're capturing screen pixels, not image pixels, so you're limited to your display resolution. Second, you're adding another layer of re-encoding if the screenshot tool outputs compressed JPG. The result looks obviously worse than a clean format conversion at quality 85, often by a huge margin.

If you care about keeping photos looking good, always convert the source file directly. No screenshots in the middle.

When JPG isn't the right choice

JPG handles continuous-tone photographs beautifully. It does not handle transparency. If your HEIC has transparent areas, or if you're converting something that really needs to stay as a logo or graphic with see-through parts, JPG will flatten that to a solid color, usually white.

In those cases, PNG is your friend. It's the better output format when transparency must survive the conversion. It's larger, yes, but it's lossless for the actual pixel data, and it preserves alpha channels. For the standard batch of iPhone photos of your trip, your product, your project documentation, stick with JPG. For graphics with transparency, head toward PNG instead.

Batch conversion without the headache

The typical scenario: you've got twenty, fifty, two hundred HEIC photos from your phone that need to become JPGs before you can share them, upload them, or hand them off. Downloading software, installing it, learning its quirks, then doing it again on the next computer, that's friction you don't need.

A browser-based conversion handles this cleanly. TinyPixel's HEIC to JPG converter runs locally in your browser. Files don't upload to a server. You drag the photos in, pick your quality setting, get JPGs back. Dozens at a time if you want. No install, no account, no wondering where your photos went.

This matters for privacy too. Family photos, work documents, client materials, sending them to some random conversion service means trusting that service. Local browser processing means the images never leave your machine.

The practical workflow

Here's how I actually do this when I'm helping someone get their iPhone photos into a usable state:

1. AirDrop or cable-copy the HEIC files to my computer. (Or use them straight from wherever they're stored.)
2. Open the converter, drop the files in.
3. Set quality to 85-90. That's my default for photos. I'll only adjust down if I desperately need smaller files, or up if I see problematic content.
4. Convert, download the batch, move on.

For web uploads where I also need smaller dimensions, I'll run the JPGs through a resize tool next, or compress them further if the platform has strict file limits. The compress image tool handles that without another re-encode cycle if I'm careful about settings.

A note about what "without losing quality" actually means

I want to be straight with you. Any conversion from HEIC to JPG involves some loss. It's mathematically unavoidable. The HEVC codec in HEIC and the DCT-based compression in JPG work differently, and some information gets reshaped in the handoff.

But "without losing quality" in practice means "without losing visible quality." Without your recipient, your viewer, your printer noticing anything wrong. At 85-90 quality, with a clean direct conversion, that standard is totally achievable. Your photos look the same. The file works everywhere. That's the win.

If you need other formats too

Sometimes JPG isn't the end of the story. Maybe a web developer wants WebP for modern browsers. Maybe you need a PDF for a document submission. The same batch-friendly, local-browser approach works for those too. The core idea stays the same: convert the source directly, pick the right format for the job, don't let screenshots or excessive quality settings ruin things unnecessarily.

Wrapping up

HEIC is fine until it's not. The moment you need to share broadly, upload to a picky system, or work with someone on Windows without codec packs installed, you're converting. Do it directly, at quality 85-90, and your photos come through looking essentially identical to the originals. Do it with screenshots or at quality 100, and you're either adding needless artifacts or needless file size.

The whole point of taking photos is to be able to use them. Converting HEIC to JPG properly just removes the friction that Apple's efficient format accidentally creates.