HEIC to PNG: The Editing-First Conversion
When someone converts HEIC to JPG, they're fixing a compatibility problem: the file won't open anywhere. When someone converts HEIC to PNG, they're making a deliberate quality decision: they want a lossless working file they can edit, composite, or archive without introducing any new compression artifacts. These are different problems with different right answers. If you just need your iPhone photos to open on Windows or get accepted by a print lab, use the HEIC to JPG converter. If you're retouching portraits, removing backgrounds for product photos, building design compositions, or creating a quality-preserved archive, PNG is the correct output.
The main thing to know going in: PNG files from iPhone HEIC sources are large. A 2MB HEIC becomes 8–12MB as PNG. This isn't a bug; it's what lossless compression looks like for high-resolution photographs. If storage or bandwidth is a concern, use JPG. If editing quality is the priority, accept the size and use PNG as your working format, then export to JPG or WebP when you're done editing.
What HEIC Stores and What Gets Lost When You Edit It
HEIC uses HEVC (H.265) lossy compression, which means some image data is permanently discarded when the iPhone saves the photo. This discarded data is genuinely imperceptible in normal viewing, but it matters for editing. When you open a HEIC in an editor, make adjustments, and re-save, the encoder runs again on an already-compressed image. Each save cycle adds another round of lossy compression. Do this five or ten times and quality degradation can become visible, particularly in smooth gradients, skin tones, and fine detail.
Converting to PNG before editing stops this cycle. The PNG captures the image as-is from the HEIC, and from that point every edit and re-save is lossless. You never add more compression artifacts on top of existing ones.
HEIC Technical Specs:
- Compression: Lossy HEVC (H.265), roughly 50% smaller than JPG at equivalent quality
- Color depth: 16-bit, significantly richer than PNG's standard 24-bit (8-bit per channel)
- Special content: Can store Portrait mode depth maps, Live Photo motion, HDR data
- Re-save behavior: Lossy, quality degrades with each additional encode cycle
- Editing software support: Photoshop CC 2018+ on macOS, Lightroom 9+; inconsistent on Windows
- Best used for: iPhone storage; not ideal as an editing working format
Why PNG Is the Professional Editing Format
PNG (Portable Network Graphics) uses DEFLATE lossless compression, created in 1996 as an open-standard replacement for GIF. Lossless means exactly what it says: the compressed file contains all original pixel data and decompresses back to an exact copy of the source image. Every single time, with no degradation, regardless of how many times you compress and decompress.
For editing workflows, this property is fundamental. Photoshop's native PSD format is lossless. TIFF is lossless. Professional photographers working in Lightroom or Capture One export to TIFF or PNG before sending to retouchers for exactly this reason: the retoucher needs a format that doesn't compound quality loss with every save. PNG gives you that, in a universally supported format that doesn't require Photoshop to open.
PNG Technical Specs:
- Compression: Lossless DEFLATE, zero quality loss on compression or re-save
- Transparency: Full alpha channel with 256 opacity levels
- Color depth: Up to 48-bit color (16 bits per channel with alpha)
- Re-save behavior: Pixel-identical every time, no generational loss
- Software support: Universal across all editing tools, all versions, all platforms
- Best used for: Editing master files, background removal, design compositing, quality archiving
Specific Situations Where HEIC to PNG Is the Right Choice
Choose PNG over JPG when the destination is editing software, not a final output. Here are the workflows where PNG is clearly the correct choice:
- You're retouching portraits or editing photos across multiple sessions: Every JPG re-save adds a new compression pass. If you're going to work on an image in Photoshop, save, come back tomorrow, adjust, and save again, PNG prevents quality accumulation over multiple sessions.
- You need to remove the background from an iPhone product photo: Background removal tools (Remove.bg, Canva, Photoshop's Object Selection, Luminar) output transparent PNGs. Starting with a PNG source gives you the cleanest possible input and the most accurate cutout output.
- You're using the photo in a Figma, Canva, or Adobe XD design composition: Design tools accept PNG natively and handle alpha channel transparency correctly. If you're placing an iPhone photo into a design layout, PNG is the cleaner import format.
- You're sending iPhone photos to a professional photo retoucher: Retouchers prefer lossless source files. Sending a PNG means they receive full pixel data to work with, not a pre-compressed JPG or an HEIC that may not open correctly in their software.
- You're creating a long-term quality archive of important photos: PNG is an ISO-standardized open format that any image-handling software will be able to open indefinitely. HEIC's long-term accessibility depends on continued HEVC codec support outside Apple. For photos you genuinely want to preserve at full quality for decades, PNG is the safer archival choice.
- You're creating overlays, cutouts, or layered graphics: Any workflow that involves placing a photo over another image, animating it, or using it as a layer in motion graphics needs transparency support, which only PNG and WebP provide among common formats.
When JPG is the better choice: If you just need your iPhone photos to open on Windows, be accepted by a print lab, be sent as email attachments, or be shared on social media, use HEIC to JPG instead. The file will be 3–5x smaller than PNG and perfectly adequate for those purposes. PNG's size penalty is only worth paying when editing quality or transparency is a genuine requirement.
How the Conversion Works
HEIC to PNG is one of the more demanding conversions because it combines the complexity of HEVC decoding with the large output sizes of lossless PNG. The process uses the heic2any JavaScript library and the HTML5 Canvas API:
- File selection: Your HEIC files load into browser memory only. No network activity.
- HEVC decoding via heic2any: The library reads the HEIC container and decodes the HEVC-compressed pixel data into raw image values. This step is computationally intensive, particularly for 48MP photos from newer iPhones.
- Canvas rendering: The decoded pixels are drawn onto an HTML5 Canvas element.
- PNG encoding: The Canvas exports the pixel data as PNG using lossless DEFLATE compression. Because no data is discarded in this step, the output file is significantly larger than the HEIC source.
- Download: Your PNG is available as a download. The HEIC file is unchanged on your device.
Processing time is longer than HEIC to JPG conversion because PNG files are larger and lossless encoding is more computationally intensive than lossy JPEG encoding. Expect 3–8 seconds per photo on a modern device, longer for 48MP files from iPhone 15 Pro models.
File Sizes: What to Expect
The size increase from HEIC to PNG is substantial. This is normal and expected given the difference between lossy HEVC and lossless DEFLATE compression:
- iPhone 12 standard photo (4000×3000): 1.5MB HEIC converts to approximately 8–10MB PNG
- iPhone 13 or 14 standard photo (3024×4032): 1.8–2MB HEIC converts to approximately 9–12MB PNG
- iPhone 15 Pro 48MP main photo: 4–8MB HEIC converts to approximately 20–35MB PNG
- iPhone screenshot (1170×2532): 300–800KB HEIC converts to approximately 2–5MB PNG
- Portrait mode photo: Similar to standard shot; depth map data is not carried over to PNG
If you're batch converting many photos, check that your destination drive has sufficient space before starting. 100 standard iPhone photos converted to PNG can easily consume 1–1.5GB. For most editing workflows, this is fine and expected. If you only need the photos for compatibility (opening on Windows, printing, sharing), convert to JPG instead for a fraction of the file size.
What "Lossless" Actually Means for Your Editing Workflow
Lossless means the PNG output contains exactly the pixel values that were decoded from the HEIC. No further compression artifacts are introduced during the PNG encoding step. However, it's worth being precise about one point: the quality is locked at whatever the HEIC contained. HEIC is itself lossy, so some quality was already discarded when your iPhone captured the image. Converting to PNG doesn't recover that; it simply stops any further degradation.
In practical terms for editing: open your PNG in Photoshop, adjust exposure, retouch skin, and sharpen. Save as PNG. Open the saved PNG again tomorrow, adjust color grading, and save again. The quality after the second save is identical to the quality after the first save, which is identical to the original conversion output. This is what makes PNG the right intermediate format for multi-step editing workflows.
Common Questions and Problems with HEIC to PNG Conversion
I expected a transparent background but the PNG has a white background
Standard iPhone photos have solid backgrounds, not transparent ones. HEIC does support transparency technically, but iPhone camera photos are always captured on solid backgrounds. Converting to PNG gives you a format that supports transparency, but doesn't automatically create transparency where there wasn't any. To get a transparent background, you need to remove the background using a tool like Remove.bg, Canva's background remover, or Photoshop after converting to PNG.
The conversion is very slow or the browser freezes on large files
HEIC to PNG is the most memory-intensive conversion on this site. HEVC decoding and lossless PNG encoding of a 48MP photo can require 1–2GB of working memory. If your browser slows down or the tab becomes unresponsive, close all other browser tabs and apps, then try converting 3–5 files at a time rather than all at once. On older devices with less RAM, stick to smaller batches.
My PNG file won't open in Photoshop even though PNG is supposed to be universal
This is almost always a file size issue with Photoshop's scratch disk, not a format problem. Very large PNGs (30MB+) from 48MP iPhone photos can fail to open if Photoshop doesn't have enough scratch disk space allocated. Check Edit then Preferences then Scratch Disks in Photoshop and ensure you have a drive with several GB free assigned as scratch space. The PNG itself is valid; Photoshop just needs the resources to decode a very large image into its working format.
Should I convert to PNG or keep HEIC if I'm editing in Lightroom?
Lightroom Classic version 9.0 and later can import HEIC files directly. If you're on a recent version of Lightroom, you don't necessarily need to pre-convert to PNG; Lightroom works non-destructively and its edits don't re-compress the source file. Convert to PNG when you need to export to a third-party tool, when you're sending files to a retoucher who doesn't use Lightroom, or when you need transparency support for design work.
Batch Converting HEIC Files to PNG
Select multiple HEIC files at once using Shift+click for a range or Ctrl/Cmd+click for individual files. The converter processes them in sequence and shows progress for each one. Download individually or as a ZIP archive.
A practical note on batch size for PNG specifically: because PNG files are 4–6x larger than their HEIC sources, batch converting 50+ photos can result in several gigabytes of output and can strain RAM on older devices. Process in groups of 10–20 if you're working with a large library, particularly if the photos are from a newer iPhone with a high-resolution sensor. Save each batch to disk before starting the next one.
Your Photos Stay on Your Device
iPhone photos are among the most personal files people have. They contain GPS coordinates, timestamps, and images of people and places that are genuinely private. People converting HEIC to PNG are often doing so for professional editing work, which may include client photos, unreleased product images, or personal portraits. None of that should leave your device to reach a third-party server.
This converter has no server component. The heic2any library decodes your HEIC files inside your browser, the Canvas API encodes them as PNG inside your browser, and the output file is provided as a local download. Nothing is transmitted at any point. Disconnect from the internet after loading the page and the converter still works, because it requires no connection once loaded.
- No uploads: Your HEIC files never leave your device
- No GPS data transmitted: Location metadata in your iPhone photos stays on your device throughout
- No storage: We have no server receiving your files, so there's nothing to store
- No accounts: No email, no sign-up, no personal information required
- Works offline: Disconnect after page load and conversion still works
- No watermarks: Output PNGs are clean files with nothing added
Why No-Upload Conversion Is Different: What Actually Happens in Your Browser
HEIC to PNG is the most technically layered conversion this tool performs. It combines a JavaScript HEVC decoder with a browser-native lossless PNG encoder, running entirely in browser memory with no server component. Understanding the pipeline makes it clear why local processing is particularly meaningful for this specific format pair and this specific use case.
What the browser does with your HEIC file, step by step
When you select a HEIC file, the browser gives JavaScript a sandboxed File object with no filesystem path, no directory visibility, and no persistence after the page closes. The converter passes this to the heic2any library, which reads the file's bytes into an ArrayBuffer in browser memory and begins parsing the ISOBMFF container structure. HEIC files are structured as a sequence of typed boxes: the ftyp box declares the file type as HEIC, the meta box contains the item location data that maps to the compressed image payload, and the mdat box holds the actual HEVC-encoded bitstream. The heic2any library implements an HEVC decoder in JavaScript that reads the bitstream, processes the slice headers and macroblock data, and reconstructs the raw pixel values. This is computationally intensive purely because HEVC is a complex codec designed for efficient storage, not for easy software decoding. The decoded pixel data lands on an HTMLCanvasElement. From there, the Canvas calls toBlob('image/png'), which passes the pixel array to the browser's built-in PNG encoder. That encoder applies DEFLATE lossless compression and produces a valid PNG file. For a 12MP standard iPhone photo, the decoded pixel grid in memory is roughly 36MB of raw RGBA data before PNG compression. The final PNG on disk is smaller due to DEFLATE, but during processing that full buffer lives in browser RAM. URL.createObjectURL() wraps the PNG Blob in a temporary reference for download. When the tab closes, the OS reclaims all of it.
What an HEIC file actually contains beyond the primary image
The ISOBMFF container that HEIC uses was designed to hold multiple items in a single file, and iPhones use that capability fully. A typical iPhone HEIC file can contain the primary HEVC-compressed still image, EXIF metadata in its own item (GPS coordinates, timestamp, device model, lens and exposure data), an XMP metadata block, a thumbnail image used for quick preview, an HDR gain map stored as a secondary image item (on iPhone 12 and later), a depth map from Portrait mode stored as an auxiliary image, and a reference to the Live Photo video track stored in a companion MOV file. When you upload an HEIC file to a server-side converter, the receiving server gets all of this. The full ISOBMFF container, including the GPS-tagged EXIF block and any auxiliary image data, arrives at their endpoint. The converter library on the server side decides what to do with each item. Many simply extract the primary image and discard the rest, but the entire container was transmitted regardless.
The heic2any library running locally extracts only the primary image item from the container, passes its HEVC bitstream through the JavaScript decoder, and puts raw pixels on the Canvas. The EXIF item, the XMP block, the thumbnail, the HDR gain map, and the depth map auxiliary image are all left in the ArrayBuffer in memory, unused. The PNG encoder receives only pixels. The output PNG contains no EXIF GPS data, no device model, no timestamp, no color profile beyond what the Canvas compositing step uses, and none of the auxiliary image data from the HEIC container. This is not a deliberate scrubbing step; it is the natural consequence of a pixel-only pipeline through the Canvas API.
Why upload risk is highest for archiving and editing workflows
People converting HEIC to PNG are usually doing so for one of two reasons: editing, where they need a lossless working file for retouching or compositing, or archiving, where they want a quality-preserved, universally readable copy of important photos. Both of these use cases involve files that are more personal and more sensitive than photos being converted for casual sharing. An editing workflow might involve a client's product photography, a wedding photographer's pre-edited RAW-to-HEIC exports, or portraits sent by someone under a confidentiality agreement. An archiving workflow involves the photos people most want to protect: family events, children, medical visits, private locations. These are the files where GPS coordinates in the EXIF carry the most real-world weight. The GPS data in a HEIC photo of your home, your child's school, or a medical facility is not abstract metadata. Uploading those files to convert them adds an unnecessary step where that data leaves the device the person controls.
What server-side HEIC to PNG tools actually do
Server-side HEIC to PNG conversion typically uses libheif with a libpng backend, or FFmpeg with the hevc decoder and PNG muxer, or ImageMagick built with HEIC delegate support. These tools run on the server's CPU, which handles HEVC decoding faster than a JavaScript implementation in the browser can. Speed and color management are their genuine advantages: a server-side tool using libheif can preserve ICC color profiles and handle HEVC bitstreams that push against the edges of the spec more robustly than heic2any. The cost is the upload: your HEIC file, with its full ISOBMFF container including GPS-tagged EXIF, HDR gain maps, and any auxiliary image data, is transmitted to their infrastructure, written to temporary storage, decoded, encoded as PNG, and staged for download. Their system logs the request. Their data retention policy determines how long the original file persists. None of that is necessary for a conversion that a modern browser can perform locally without any of it.
The verification step is the same as with any browser-based tool. Open developer tools, go to the Network tab, and convert a file while watching the request log. Filter by XHR and Fetch, or watch all requests. You will see the page's static assets from the initial load and nothing carrying your image data during or after conversion. The heic2any library, the Canvas encoder, and the resulting PNG Blob all exist inside the browser process. Nothing leaves it.
Frequently Asked Questions
Does converting HEIC to PNG improve quality over converting to JPG?
For a single one-time conversion, the visible quality difference between PNG and JPG at 90% is minimal for most viewers. The real advantage of PNG shows over time: every subsequent edit and re-save of a PNG is lossless, preserving quality across multiple editing sessions. JPG re-compresses with each save, accumulating artifacts. If you'll edit the image once and never touch it again, JPG at 90% is simpler and much smaller. If you'll work on it repeatedly or pass it to someone else for retouching, PNG protects your investment in the original quality.
Why is my PNG 5–6x larger than the HEIC file?
HEIC uses lossy HEVC compression to store a photograph in 2MB by discarding imperceptible image data. PNG uses lossless compression that stores every pixel's exact value, which for a high-resolution photograph requires far more space. The 5–6x size increase is the expected and correct result of converting from a highly efficient lossy format to a lossless one. There's nothing wrong with the conversion; this is what lossless looks like.
Will Portrait mode depth data and Live Photo motion survive the conversion to PNG?
No. PNG is a still image format that stores one flat image with no support for depth maps, motion clips, or multi-frame data. The conversion extracts the primary still image from the HEIC container at full resolution. The Portrait mode depth map and Live Photo motion component are not carried over. If you need those elements, keep the original HEIC on your iPhone. The PNG is the photographic still only.
Can I use the PNG files in Canva for background removal?
Yes. Upload the converted PNG to Canva, open it in the editor, and use the Background Remover tool in the image settings panel. Canva will remove the background and output a transparent PNG you can place over any design element. Canva's background remover also works with JPG uploads, but PNG input can give cleaner edge detection because lossless source data has no JPEG compression artifacts along the subject edges.
Is there a limit to how many files I can convert?
No limit from the tool. The constraint is your device's RAM and the disk space for your output files. HEIC to PNG is memory-intensive because of HEVC decoding and the large PNG output size. For large batches, process 10–20 files at a time and save each batch before starting the next to avoid memory pressure building across a long session.
Can I use these PNG files commercially?
The conversion doesn't affect the copyright or usage rights of your images. If you own the rights to the iPhone photos, you own the rights to the converted PNGs. We add no watermarks, claim no rights, and impose no restrictions on the output. The converted files are standard PNGs that belong entirely to you under the same terms as the originals.
Related HEIC and PNG Converters
Visit our complete converter directory for all 25+ image format combinations.