Convert iPhone photos (HEIC) to JPG, WebP, or PNG. Selected file contents are processed locally in your browser.
Local-first HEIC conversion
iPhone photos made compatible.
Drag in your .heic or .heif files. Your browser converts them to universally supported formats without ever uploading to a server.
Drop HEIC images here
HEIC or HEIF · processed on your device
Images are converted in your browser. File contents are not intentionally uploaded by this tool.
Short answer
Convert HEIC to JPG when you need to share an iPhone photo with someone on Windows, upload to a platform that rejects HEIC, edit in older desktop software, or embed in a web page. Keep the original HEIC when the photo lives only on Apple devices — storage is roughly half the size and quality is slightly better at the same file size.
HEIC stands for High Efficiency Image Container — a file inside a HEIF (High Efficiency Image File Format) container, with the image data encoded using HEVC, the same codec used for H.265 video. The standard is ISO/IEC 23008-12, maintained by MPEG, and Apple adopted it as the default photo format in iOS 11 in late 2017.
Under the hood, HEIC stores a still image as a single HEVC keyframe. That borrows the prediction and transform tooling from a video codec, which is why a 12-megapixel iPhone photo lands at roughly 1.5 MB as HEIC versus around 3 MB as JPEG at equivalent perceived quality. The container also supports things JPEG cannot: 10-bit colour depth, wider colour gamuts, multiple images in one file (Live Photos, burst sequences, Portrait-mode depth maps), and small auxiliary metadata for things like image stacks.
Why iPhones save in HEIC by default
Three reasons. First, storage — Apple ships 128 GB as the entry-level capacity and people take a lot of photos. Halving photo size matters. Second, dynamic range — modern iPhone sensors capture more dynamic range than 8-bit JPEG can carry, and 10-bit HEIC preserves it. Third, ecosystem — Photos.app, AirDrop, iCloud Photo Library, and most modern Mac apps work with HEIC natively, so within Apple's world there is no compatibility cost.
If you would rather not deal with HEIC at all, iOS lets you switch: Settings → Camera → Formats → Most Compatible. Your iPhone will then shoot JPEG. You give up the storage and quality benefits, but every file is portable from the moment it's captured.
When converting to JPG is the right move
Sharing with Windows users. Windows 10 and 11 can open HEIC, but only after the recipient installs the HEVC Video Extensions package from the Microsoft Store. Most people will not bother. Converting to JPG removes the friction entirely.
Uploading to platforms that reject HEIC. A surprising number of services still do: many WordPress installs without recent updates, several online photo printers, certain stock-photo libraries, older CMSes, and some corporate document-management systems.
Editing in older desktop software. Photoshop has supported HEIC since CC 2019, but older versions and many alternative editors (GIMP up to 2.10.2, some RAW workflow tools) still cannot open it.
Embedding on the web. Browsers do not natively render HEIC inline. If you are putting an iPhone photo on a web page, you need JPG, PNG, or WebP.
Email attachments. Modern Gmail and Apple Mail handle HEIC inline; older clients and corporate Outlook installations sometimes do not.
When you should keep HEIC
Inside the Apple ecosystem, the JPEG conversion is mostly waste. AirDrop preserves HEIC end-to-end; iCloud Photos stores and serves it; the Photos app on macOS and iOS reads it without thinking. If you convert everything to JPEG out of habit, you double the storage footprint and lose a small amount of quality every time you re-encode.
The rule of thumb: convert at the boundary — when a HEIC photo is about to leave Apple's ecosystem — not at capture time and not in bulk on the device.
What this converter does, technically
The page loads heic2any, a JavaScript HEIC decoder built on the libde265 + libheif WebAssembly toolchain. When you drop a HEIC file, the decoder runs in your browser, produces an uncompressed image in memory, and re-encodes it as JPEG (or PNG / WebP, if you prefer) using the browser's Canvas toBlob. Selected file contents are processed locally in your browser; ConvertUnlimited has no server-side upload endpoint for this flow. You can verify this in DevTools → Network: open the panel before dropping a file, and watch for any outbound requests during processing.
Expect output JPEGs to be roughly twice the size of the original HEIC at quality 0.9. That is the cost of switching to an older, less efficient codec. Quality is typically indistinguishable to the eye.
Batch conversion and large galleries
The dropzone above takes one file or many. We suggest 30–50 photos at a time as a comfortable batch on a desktop machine; mobile devices have less RAM and will slow down on larger batches. When the batch finishes you can download files individually or as a single ZIP archive.
If you are sitting on hundreds of HEIC files and want a one-off bulk conversion, a desktop tool like imagemagick with libheif, or the macOS Preview app's File → Export, will be faster than any in-browser converter — but the privacy posture changes too.
Frequently asked questions
Will I lose quality converting HEIC to JPG?
Slightly, in theory — you are going from a more efficient lossy codec to an older lossy codec. At the default quality 0.9 this is below most people's visual threshold. If quality matters for a specific photo, export at 0.95 or higher.
Does this tool work for HEIF too?
Yes. HEIC and HEIF are the same container; HEIC is just the most common filename extension Apple uses. Files with .heif or .heics extensions decode through the same path.
Does converting strip EXIF, GPS, and capture-date metadata?
This converter preserves EXIF metadata by default. If you want to remove metadata for privacy reasons (location, device model, software version, etc.), run the output through the metadata remover after conversion.
Can I batch-convert hundreds of files in the browser?
Technically yes, but at some point browser memory becomes the bottleneck. 30–50 photos at typical iPhone resolutions is comfortable on desktop. For galleries in the hundreds, a desktop or command-line tool will be faster and more reliable.
What about Live Photos and Portrait depth maps?
This tool extracts and converts the primary still image. The motion data from a Live Photo and the depth map from a Portrait shot are stored in the HEIC container but are dropped in the JPEG output, because JPEG has no equivalent representation for either.
Privacy and terms
For supported workflows, selected file contents are processed locally in your browser. See the Privacy Policy for what the public site does and does not collect, and the Terms of Use for the boundary on what this tool is and is not. For a more detailed walkthrough of the local-processing model, see how local browser processing works.
Files are processed locally where supported. Review the Trust Center for the processing model and the Privacy Policy for public-site privacy boundaries.