Skip to content
← All Guides
🔒 No Upload Required ✅ Free Forever 🌐 Browser-Based
Image Tools

HEIC to PNG Crop: Complete Conversion Guide for Lossless Quality

By Bill Crawford  ·  March 2026  ·  9 min read  ·  Last updated March 12, 2026

Connect on LinkedIn →

🚀 Ready to crop and convert? HEIC to PNG Crop Converter — free, browser-based, no sign-up.

Open Tool →

What Is PNG and Why Use It for HEIC Photos?

PNG (Portable Network Graphics) is a lossless raster image format that uses Deflate compression to reduce file size without discarding any pixel data. Unlike JPEG, which sacrifices image detail at compression boundaries to achieve small file sizes, PNG retains every pixel exactly as it was captured or encoded. The result is a file that is larger than JPEG but pixel-perfect — no compression artifacts, no smearing of fine detail at edges, and no quality degradation regardless of how many times you open, edit, and resave the file.

PNG also supports a full alpha transparency channel. This makes it uniquely suited for graphics that need transparent or semi-transparent areas — UI icons, product photos on white backgrounds that need transparency for compositing, and design assets that will be layered over other content. When you crop a HEIC photo and export to PNG, you get a universally compatible, lossless file that every modern browser, image editor, and design tool can open natively.

What Is HEIC and Where Does It Come From?

HEIC (High Efficiency Image Container) is the default photo format on iPhones and iPads since iOS 11. It uses HEVC (H.265) video compression to store photos at roughly half the file size of an equivalent JPEG while maintaining comparable visual quality. A typical iPhone photo at 12 megapixels occupies 2–4 MB as HEIC, compared to 5–8 MB as JPEG.

The trade-off is compatibility. Apple devices handle HEIC natively, but Windows requires a codec extension from the Microsoft Store, Linux support is sparse, and most web platforms and image editors expect universally supported formats. PNG has been a web standard since 1996 and is supported everywhere. Converting a cropped HEIC region to PNG removes all compatibility barriers — the output file works in every browser, design tool, and image processing pipeline without any codec requirement.

When Should You Crop and Convert HEIC to PNG?

HEIC vs PNG: Format Comparison

PropertyHEICPNG
File typeCompressed raster (HEVC codec)Lossless raster (Deflate compression)
Color depth10-bit HDR support8-bit or 16-bit per channel
CompressionLossy (HEVC) — very compactLossless — no quality loss
TransparencyLimited alpha supportFull alpha channel support
Browser supportChrome 105+, Safari, Edge nativeUniversal in all browsers
Design tool supportLimited outside Apple ecosystemUniversal — Photoshop, Figma, Illustrator
File sizeVery compact — HEVC compressionLarger — lossless means no pixel data discarded
Best foriPhone storage, Apple workflowsLossless exports, web graphics, UI assets

What the PNG Output Contains

The HEIC to PNG Crop Converter produces a standard PNG file at the exact pixel dimensions of the selected crop area. The PNG is generated using the HTML5 Canvas API's canvas.toBlob() method with MIME type image/png. This captures every pixel of the selected region from the decoded HEIC image at full original resolution — the display canvas is only used for the interactive overlay. The output PNG is a 24-bit RGB file. If the source HEIC contained alpha channel data, it will be preserved in the PNG output as a 32-bit RGBA file. No metadata from the HEIC source (EXIF, GPS, or color profile data) is carried through, since the conversion passes through the HTML5 Canvas which strips embedded metadata.

The filename of the downloaded PNG follows the pattern [original-filename]_crop.png. For a source file named IMG_4521.heic, the output is IMG_4521_crop.png. The download triggers immediately in the browser — no server round-trip occurs at any point in the workflow.

How the Crop Workflow Works in the Browser

The HEIC to PNG Crop Converter decodes your HEIC file entirely in the browser using a two-stage approach. First, it attempts native HEIC decoding via createImageBitmap() — available in Chrome 105+, Safari, and Edge. If native support is not available (such as in Firefox), it automatically falls back to the heic2any JavaScript library, which uses a WebAssembly-based HEVC decoder for full cross-browser compatibility. The decoded image is drawn onto an HTML5 Canvas element, and an SVG overlay renders the crop rectangle and handles on top.

When you drag a handle, the tool maps canvas coordinates back to the original image's pixel dimensions using a scale factor (natural width ÷ display width). This ensures the crop is applied at full resolution — the canvas is only a display proxy. When you click Convert & Download PNG, an off-screen canvas draws only the selected region using drawImage with source rectangle parameters. The cropped canvas is converted to a PNG blob via canvas.toBlob() and downloaded directly. No server round-trip is required at any point.

Using the Output PNG in Design Tools

The PNG output is directly importable into every major design tool. In Photoshop, use File → Open or drag the file onto the canvas — it opens as a layer at the exact pixel dimensions of the crop. In Figma, drag the PNG file onto the canvas — it imports as an image fill in a frame at the correct dimensions. In Sketch, use Insert → Image to place it. In Affinity Photo or GIMP, use File → Open or File → Import. The output PNG is a standard 24-bit or 32-bit file compatible with all of these tools without any conversion or import step.

Because the PNG is lossless, it is also suitable as a source asset for further compression. After importing into Photoshop or Figma, you can export to JPEG or WebP at a controlled quality setting, knowing the PNG source is pristine. This is the standard professional workflow for web asset preparation: lossless source, controlled lossy delivery.

✍ Try it yourself — crop and convert a HEIC photo to PNG in seconds.

Open HEIC to PNG Crop Converter →

Frequently Asked Questions

Does PNG preserve lossless quality from the HEIC source?

Yes. PNG uses lossless Deflate compression, meaning every pixel in the cropped region is preserved exactly. The HEIC decode step does introduce the original HEVC compression decisions made by the iPhone camera, but the subsequent Canvas → PNG step adds no further quality loss. The output PNG is a pixel-perfect representation of the HEIC data as decoded by the browser.

Why is the PNG file larger than the source HEIC?

HEIC uses very efficient HEVC (H.265) video compression, which is lossy and achieves dramatic file size reductions by discarding imperceptible image detail. PNG uses lossless Deflate compression and retains every pixel. A 3000×2000 PNG will typically be 5–15 MB depending on image complexity, compared to a 2–4 MB HEIC source. This is expected and normal — lossless preservation comes at the cost of file size.

Does the PNG output support transparency?

PNG fully supports an alpha transparency channel as a 32-bit RGBA file. The Canvas API preserves alpha channel data if it is present in the decoded HEIC source. However, most HEIC photos from iPhone cameras are fully opaque (no transparency), so the output PNG is typically 24-bit RGB. If you need a transparent-background PNG from a photo, you will need to use a background removal tool after converting.

How does the output file size compare to JPEG?

The PNG output will be significantly larger than an equivalent JPEG of the same crop dimensions. A lossless PNG of a 3000×2000 photo region might be 8–15 MB, while a JPEG at 85% quality of the same region would be 1–3 MB. If file size is the primary concern and lossless quality is not required, consider using the HEIC to JPG Crop tool instead. For modern web delivery with good compression, HEIC to WebP Crop or HEIC to AVIF Crop produce smaller files than PNG with near-lossless visual quality.

Is the conversion free with no file size limit?

Yes. Because all processing runs entirely in your browser, there is no server to impose a limit. The only practical constraint is your device's available RAM. There are no usage caps, no watermarks, and no account required.