HEIC stands for High Efficiency Image Container. Apple switched iPhones to this format by default in iOS 11 in 2017, replacing JPEG as the camera's default output. The reason was storage: HEIC files are roughly half the size of equivalent JPEGs at the same visual quality, which matters when a phone shoots 12 to 48 megapixel photos and users expect to keep thousands of them. HEIC uses the HEIF container format with H.265 (HEVC) video compression applied to still images. That's the same codec used for high-efficiency video streaming, adapted to compress individual frames. It's genuinely better compression than JPEG's aging DCT algorithm, which dates to 1992.
The compatibility problem is straightforward: H.265 requires licensing fees and more complex decoding than JPEG, so it wasn't built into every operating system and application from day one. Windows didn't support HEIC natively until a paid codec extension was made available through the Microsoft Store. Most web browsers added HEIC decoding only recently, and many still don't support it. Design tools, online platforms, and document editors largely assume JPEG or PNG as input. So every HEIC file sitting in your iPhone's camera roll is one compatibility problem waiting to happen the moment you try to use it anywhere beyond Apple's own ecosystem.
What "lossless conversion" means when the source is already lossy
The phrase "lossless conversion to PNG" needs some clarification. HEIC itself is a lossy format. When your iPhone shot that photo, it compressed the raw sensor data using H.265, discarding some information to achieve the smaller file size. That information is gone. Converting the HEIC to PNG doesn't recover it — what it does is decode the HEIC pixel data exactly as it stands and store those decoded pixels in PNG without any further quality reduction. The PNG output is lossless relative to the HEIC source, not relative to the original camera capture. You're getting a pixel-perfect copy of what the HEIC file contained, with no additional degradation introduced by the conversion itself.
This distinction matters for editing workflows. If you convert a HEIC to PNG and then edit it in Photoshop, you can save the PNG as many times as you like without accumulating any additional compression damage. Each save writes exactly the pixels you have. If you converted to JPEG instead and edited it repeatedly, every save cycle would introduce new JPEG compression on top of the existing HEIC compression, gradually degrading the image. For any workflow where the photo will go through multiple editing steps, PNG is the right intermediate format for this reason.
The file size reality and when it tips you toward JPEG instead
A 3MB HEIC from your iPhone camera will typically become a 12 to 18MB PNG after conversion. PNG's lossless compression is good at compressing solid colors, gradients, and text, but photographs with complex detail and natural noise compress poorly in PNG compared to JPEG or HEIC. If you're converting HEIC photos for sharing, web use, or submission to a portal, that size jump is a real problem. A portal that accepts images up to 100KB isn't going to accept an 18MB PNG any more than it would accept the original HEIC.
For those cases, converting to JPEG using the HEIC to JPG converter gets you a much smaller file that's compatible everywhere. If you do convert to PNG and then need to bring the file size down for a specific platform, the compress under 100KB tool handles that in a second step, though at that point you're accepting lossy compression anyway and JPEG would have been the more direct path.