Skip to content
FireConvert
10 min read

Convert HEIC to PNG — the Windows-friendly, lossless way

Someone AirDropped you a .heic file, you double-clicked it on Windows, and Photos told you to go buy an extension from the Microsoft Store. Converting to PNG is the lossless escape hatch: one format every Windows app, every editor, and every browser has opened natively since roughly forever. Here's the honest version — including why the PNG you get back is often several times larger than the HEIC you started with.

The short version

  1. Drop your .heic files on the converter. Batches work — select the whole iPhone share in one go.
  2. Leave the target on PNG. It's lossless, so there's no quality slider to fiddle with.
  3. Leave sRGB as the colour profile unless you're in a specific wide-gamut workflow (most people aren't).
  4. Click Download. Single file → single PNG. Batch → ZIP.
  5. Open the result in literally any Windows app. Paint, Photos, Photoshop, Figma, Preview, Chrome, the clipboard. No extension required.

If you're one-and-done, stop here. The rest of this post is for when the PNG is eight times the size of the HEIC, when you're wondering why PNG instead of JPG, and when you're setting up a Windows workflow for a whole holiday's worth of iPhone photos.

The Windows HEIC problem, plainly

HEIC is Apple's default iPhone photo format since iOS 11 (2017). It's a still-image wrapper around HEVC (H.265) — the same video codec used by Apple TV+, Netflix 4K, and most modern streaming. That's the problem.

HEVC is patent-encumbered. MPEG-LA and the HEVC Advance pool collectively own hundreds of essential patents, and Microsoft has to pay per-device royalties to include a decoder in Windows. That's why, when you try to open an .heic on Windows 11, Photos opens the Microsoft Store and shows you:

  • HEIF Image Extensions — free, adds the container parser.
  • HEVC Video Extensions from Device Manufacturerused to be free, now a paid $0.99 purchase. You need this one too, or the HEIF extension has nothing to hand the actual pixels to.

A buck isn't much. The problem is that (a) a lot of people rightly don't want to hand Microsoft their card for a codec, (b) the extensions only unlock Photos and a narrow set of first-party apps — Paint 3D, old Paint, Outlook attachments, Word image-insert, and every third-party tool still can't touch the file, and (c) on Windows 10 the experience is worse: the extensions are harder to find, and plenty of corporate Windows fleets block Microsoft Store installs entirely.

Converting to PNG sidesteps all of it. PNG has been native to every Windows release since Windows 2000, every browser since Internet Explorer 4, and every image tool worth mentioning since the late 1990s. There is no extension, no royalty, no store.

Why PNG instead of JPG?

This is the first real decision and the SERP almost never explains it. HEIC has two live targets, and the right answer depends on what you're going to do with the file next.

PNG — when you pick it

  • You're going to edit the photo. Photoshop, GIMP, Figma, Affinity, Krita — none of them open HEIC natively without plug-ins, and they all eat PNG without thinking. Editing a JPG adds a second round of lossy compression on top of HEIC's first round; PNG is lossless, so the bits that come out of the HEIC decoder are the bits that land in your editor.
  • You want an archival intermediate. PNG is the neutral, uncompressed-ish format that you can always down-convert later. JPG is a terminal format — once you've re-encoded, you can't get the precision back.
  • There's transparency. Rare on iPhone camera-roll HEICs, but if someone handed you a HEIC exported from Procreate or a design tool, alpha might be there. JPG has no alpha channel. PNG preserves it exactly.
  • It's a screenshot or UI capture. iOS Screenshot can be saved as HEIC on some configurations. PNG is the correct target for sharp edges and flat colours; JPG will introduce ringing around text.
  • You're printing or prepping for print. Labs and print shops prefer PNG or TIFF over JPG for masters. PNG travels cleanly through prepress software; JPG accumulates generational loss with every re-save.

JPG — when you pick it instead

  • You're uploading to a CMS, social platform, or email. JPG is a tenth the size. For web delivery there's no real case for PNG on a photograph. Use our HEIC to JPG converter instead.
  • The destination has a file-size cap. PNGs of full-resolution iPhone photos routinely come out at 20–40 MB. Gmail's attachment limit is 25 MB; Discord's free cap is 25 MB; WhatsApp compresses aggressively either way.
  • You're sharing the final photo with family. Nobody needs the lossless version to look at on a phone.

Shortest rule of thumb: PNG if the file is going into an editor or an archive; JPG if it's going into a browser, inbox, or DM.

Why your PNG is 3-8× larger than the HEIC

This is the #1 "something's broken" support ticket on any HEIC-to-PNG tool, and it's never broken. It's arithmetic.

HEIC is lossy 10-bit HEVC compression. A typical iPhone 14 Pro photo is 12 MP (4032 × 3024) and comes out around 2.2–3.5 MB. PNG is lossless 8-bit RGB (or RGBA) compressed with DEFLATE. The same 12 MP image, fully uncompressed, is 4032 × 3024 × 3 bytes = ~36 MB. DEFLATE then claws back some of that — typically ending at 12–25 MB for a real photograph.

So a 3 MB HEIC legitimately becomes a 15 MB PNG. Nothing is wrong. HEIC is smaller because it's throwing away visual information your eye can't resolve; PNG is bigger because it's preserving every pixel exactly as the decoder produced them. You cannot have both.

If the size bothers you, the honest options are: (a) convert to JPG at quality 90+, which gets you within visual-parity of the HEIC at roughly the same file size, or (b) run the PNG through our image compressor for a lossless 10–30% reduction via better DEFLATE tuning — not the order-of-magnitude cut JPG gives, but real.

Colour profiles — the bit that silently breaks things

iPhone HEICs ship with a colour profile attached. Usually Display P3 on newer iPhones (wide gamut, more saturated reds and greens than your average monitor can show), or sRGB on older ones. If the conversion drops that profile, your PNG will look fine on an iPhone and slightly washed-out or over-saturated on a Windows laptop.

Most HEIC-to-PNG converters — especially the command-line ones stitched together with libheif and ImageMagick — strip the ICC profile on export. The PNG is left with no profile, and every viewer has to guess. Chrome assumes sRGB. Windows Photos assumes sRGB. Photoshop flags it as untagged and asks you what to do.

As of this week (commit 717f5ba), our HEIC pipeline embeds a proper sRGB ICC profile on every PNG export. Colours look identical on the iPhone and on a Windows monitor. If you're in a colour-managed wide-gamut workflow — photography masters for a P3-capable print lab, video-adjacent stills for HDR grading — we surface a toggle in advanced settings to preserve the source P3 profile instead; for everyone else, the sRGB default is the right answer. Incidentally that same pipeline change made the converter roughly 14-16× faster, so batches that used to take a minute now take four seconds.

Transparency — when HEIC actually has it

iPhone camera-roll HEICs don't have alpha channels; iPhone cameras can't shoot transparent photos. But HEIC is a general format, not an iPhone-only format, and three sources legitimately produce transparent HEICs:

  • Procreate exports with transparent backgrounds — the default for isolated illustrations.
  • iOS Shortcuts and Apple's CIImage pipeline, when explicitly asked for RGBA output.
  • Some third-party iOS camera apps that do matting or background-removal on capture.

PNG preserves the alpha channel exactly — one of the real reasons to prefer it over JPG here. Our tool auto-detects alpha and warns you if you've picked a target that would flatten it (JPG would; PNG doesn't). If you're not sure whether your HEIC has transparency, just convert to PNG — PNG with no alpha is the same size as PNG with opaque alpha, so there's no penalty.

Batch workflow — a whole camera roll at once

The realistic Windows-user scenario: you just came back from a trip, your partner has an iPhone, they AirDropped you 60 HEICs, and you need them as PNGs to drop into Lightroom or paste into a report. One at a time is not happening.

On iPhone, grab them as HEICs cleanly

In Photos, select the range → Share → Save to Files → pick a folder in iCloud Drive or On My iPhone. That gives you real .heic files. Do not use Mail or Messages, which silently re-encode to JPG at lower quality. Do not use "AirDrop as Photo" to a Windows machine — it goes through SMB and may convert. AirDrop specifically is Mac-to-Mac.

Get them to Windows

Three honest options, in order of reliability:

  • iCloud for Windows — installs a sync client; the Files folder you saved to shows up as a real Windows folder.
  • USB cable to your PC — iPhone appears in File Explorer under "This PC". Navigate to DCIM. Warning: Windows lies about file sizes on this connection and sometimes shows 0-byte files; copy them to a local folder before converting.
  • A cross-platform share — Google Drive, Dropbox, or a one-click service like Send Anywhere. Upload from iPhone, download on Windows. The most reliable, but requires a detour through someone else's server.

Batch convert

Drag the folder of HEICs onto our converter. Set PNG as the target, leave sRGB as the profile, hit Convert. We process sequentially in a web worker so your browser stays responsive, and hand back a ZIP with all the PNGs. On a typical laptop, 60 full-res iPhone HEICs take 60–90 seconds with the new pipeline (down from 14–22 minutes before the speed fix). Browser memory is the practical ceiling; if a batch of 300+ exceeds it, split in two.

Editing workflow — HEIC → PNG → Photoshop / GIMP / Figma

Almost no image editor reads HEIC natively in 2026. The exceptions are Apple Preview, macOS Finder Quick Look, recent Affinity versions with the optional extension, and Photoshop on Windows only if you've installed the Microsoft HEIF extensions and Photoshop 2023.5+. Every other path requires a PNG (or JPG) intermediate:

  • Photoshop — drag a PNG in. Layers preserved if you export back out.
  • GIMP — native PNG. No HEIC without a third-party plugin.
  • Figma — paste a PNG directly into a frame. HEIC upload is rejected.
  • Krita, Affinity Photo, Pixelmator Pro (Windows? no), Corel PaintShop — PNG yes, HEIC maybe.
  • Canva — accepts PNG. Accepts HEIC on Pro; strips the profile.
  • Adobe Lightroom — actually opens HEIC, but its catalog metadata handling on Windows is quirky. Many pros pre-convert to PNG (or TIFF) and manage colour there.

The PNG intermediate is lossless, so this is a free round-trip — no generational quality loss from the HEIC-to-PNG hop. The loss happens earlier, when the iPhone compressed the original capture into HEIC; after that, PNG preserves exactly what the decoder produces.

When NOT to convert HEIC to PNG

The section every other blog post skips because it undercuts the CTA. We'll say it anyway:

  • Everyone viewing the file is on Apple hardware. iPhone, iPad, recent Mac, Apple TV all handle HEIC natively and a PNG is four times larger for zero gain. Keep the HEIC.
  • You're uploading to a website or social platform. The destination is going to re-encode anyway, usually to JPG or WebP, and it wants the input as small as possible. JPG at Q90 or HEIC to PDF for document-style sharing beats PNG on every axis for file-size delivery.
  • You're sending it over email or chat to a non-technical recipient. 20 MB PNG vs 2 MB JPG — the JPG will arrive; the PNG will get silently downscaled by whatever pipeline it crosses.
  • You need the EXIF metadata downstream. PNG's metadata support is weaker than JPG's. If GPS, camera model, and shooting-time metadata is load-bearing for your workflow, HEIC to JPG preserves it more cleanly.

How our tool compares (honestly)

HEIC-to-PNG is a crowded space. What differs is whether the tool uploads your files, whether it embeds a colour profile, how it handles batches, and whether it's telling you the truth about what's happening. Honest scoresheet:

ToolCostWhere it winsWhere it loses
FireConvertAppFreeRuns in-browser (no upload), correct sRGB ICC profile embedded by default, wide-gamut P3 preserved on toggle, alpha-channel preserved, batch via drag-folder, ~14–16× faster than typical server-side HEIC decoders, no Windows extensions requiredPer-file cap on free tier; browser memory caps hard batches around ~300 files; EXIF metadata preservation is opt-in rather than default
Windows Photos + HEIF extensions$0.99 (HEVC extension) + free HEIF extensionZero-install once paid; integrates with Photos and File Explorer previews; works offlineNot free; doesn't actually convert — you still need "Save a Copy" per file, no batch; no ICC profile control; locked to Microsoft Store (blocked on many corporate fleets)
Apple Preview (Mac only)Free (Mac only)Native HEIC everything; Export As… dialog; preserves P3 profile; solid encoderMac only (the whole reason this post exists is that you're not on a Mac); no batch UI — one file at a time; no explicit ICC profile picker
Photoshop$22.99/mo (Photography plan)Full colour-managed pipeline; P3 and sRGB explicit; layered edits; scriptable batch via Image ProcessorExpensive for a format conversion; requires Creative Cloud install + sign-in; HEIC on Windows still needs the Microsoft extensions; overkill for a batch of iPhone photos
online-convert.comFree w/ caps, $9+/moCovers a wide format matrix; paid tier unlocks decent batchUploads every file to their servers; daily cap on free; strips ICC profile silently (PNGs come out washed out on wide-gamut monitors); inserts a watermark on some free tiers
XnConvertFree (personal)Desktop batch, scriptable, fast on huge libraries, handles dozens of formatsWindows install required; HEIC support depends on bundled libheif; ICC profile handling varies by version; UI is powerful but not friendly; no iOS-share workflow

Honest summary: if you already live in Photoshop with a colour-managed workflow, use it. If you're a Windows power user doing this monthly, XnConvert is worth the install. For everyone else — occasional iPhone share, a Windows 10 or 11 laptop, no Microsoft Store extensions, no paid subscription, wants the colour to match what they saw on the iPhone — our HEIC to PNG tool is the shortest path.

Works well / doesn't work

Works well

  • iPhone camera-roll HEICs heading to Windows for editing, archiving, or printing
  • HEICs from Procreate, iOS Shortcuts, or third-party camera apps where alpha matters
  • Batches up to ~300 photos per session on a modern laptop
  • Screenshots saved as HEIC that need sharp-edge preservation in PNG
  • Privacy-sensitive files (the conversion runs entirely in your browser tab; files never upload)
  • Colour-accurate exports for Windows monitors (sRGB profile embedded correctly)

Doesn't work (well) yet

  • Live Photos — we extract the still frame and drop the motion. If motion matters, use iOS's own "Save as Video" then MOV to MP4.
  • Burst-mode HEIC stacks — we unpack the primary image; alternate frames are discarded.
  • 16-bit precision — HEIC stores 10-bit HEVC; PNG can carry 16-bit, but we export 8-bit by default. A 16-bit toggle is on the roadmap for HDR-adjacent workflows.
  • EXIF/XMP transfer — stripped by default (privacy-safe); a preserve-metadata toggle is available but not on by default.

Tips for the best result

  • Save HEICs from the Photos app via "Save to Files", not Mail or Messages. The latter re-encode to lower-quality JPG behind your back.
  • Leave sRGB as the profile unless you know you need P3. Windows monitors overwhelmingly display sRGB; a P3-profiled PNG on an sRGB monitor without colour management looks over-saturated.
  • If the PNG looks big, it's supposed to. 15 MB from a 3 MB HEIC is arithmetic, not a bug. Run it through our image compressor for another 10-30% off losslessly.
  • Convert once, archive the PNGs. Don't re-convert the HEIC every time you edit — each HEIC decode goes through the same lossy HEVC pipeline; the PNG is the stable master.
  • If the destination is the web, don't pick PNG. HEIC to JPG is a tenth the size and visually identical.
  • On Windows 10 with no Store access, bookmark the tool. It's the only route that doesn't require extensions, Creative Cloud, or a desktop install.

Common questions

Why is my PNG so much bigger than the HEIC?

Because PNG is lossless and HEIC is lossy. The HEIC threw away high-frequency detail your eye doesn't resolve; PNG preserves everything the decoder produces, pixel-for-pixel, compressed only with DEFLATE. A 3 MB HEIC legitimately becomes a 12–25 MB PNG on a typical iPhone photo. If size matters more than lossless preservation, convert to JPG instead — same quality, ~10% the size.

I'm on Windows 10 — do I need to install anything?

No. Our tool runs entirely in your browser (Chrome, Edge, or Firefox on Windows 10 all work). No Microsoft Store extension, no desktop app, no admin rights needed. This is specifically designed for the case where Windows Photos cannot open your HEIC natively.

Can I batch-convert an entire iPhone camera roll?

Yes. Select the range in iOS Photos → Share → Save to Files → pick a destination → copy that folder to Windows → drag the folder onto our tool. We process in a web worker and hand back a ZIP of PNGs. ~300 files per session is comfortable on a modern laptop; larger libraries should be split in two.

Will conversion lose quality?

No. PNG is lossless — the bits that come out of the HEIC decoder are the bits that land in the PNG. The only lossy step happened earlier, on the iPhone, when the HEVC encoder compressed the original sensor data. After that, PNG preserves exactly what's there. Converting the same HEIC to PNG twice gives you identical files.

How fast is it on a big batch?

Our HEIC pipeline landed a significant speed fix this week — the decoder is now 14-16× faster than it was three days ago, with correct sRGB profile embedding. On a current laptop (2023-era Intel or Apple Silicon), 60 full-resolution iPhone HEICs convert in roughly 60-90 seconds. Older batches that used to push past 15 minutes now finish under 2. Server-side competitors tend to be slower because the file has to upload first.

Are my files private?

Yes. The HEIC decoder runs in your browser tab via WebAssembly — the file never leaves your machine, there's no upload, no server-side processing, no analytics on file contents. This is specifically important for personal photo libraries you don't want touching someone else's server.

Can I convert PNG back to HEIC later?

Yes, though for most use cases you shouldn't. HEIC's file-size advantage comes from lossy compression; encoding a lossless PNG back into HEIC means another lossy step on top of data that's already been through one. If you absolutely need HEIC for iOS delivery, do it; otherwise the PNG is a better archival format.

Ready?

HEIC to PNG →. Drop the files, leave the defaults, download the PNGs. Free, in your browser, no upload, no Microsoft Store extension, no sign-up, no watermark. Now 14-16× faster with proper sRGB colour embedding. If the PNGs end up bigger than the HEICs, that's arithmetic — chain them through our image compressor or pick HEIC to JPG instead if size is the constraint.