Conversion Limits and Specs
Every input, output, setting and limit of HEIC to PIC in one place, plus the known gaps and how to work around them.
Last updated
Specifications at a glance
This table describes the converter as it works today. Where a limit comes from your device or browser rather than from HEIC to PIC, the table says so.
| Item | Specification |
|---|---|
| Input files | .heic and .heif, added with the file picker, by drag and drop, or by dragging a folder (subfolders included) |
| Output formats | JPG, JPEG, PNG, WebP, PDF, GIF, BMP, ICO, TIFF, AVIF |
| File count and file size | No cap set by HEIC to PIC. Your device's memory is the practical limit |
| Quality | 40 to 100, default 90 (60 on the compressor). Applies to JPG, JPEG, WebP and AVIF |
| Resize presets | Original, 2048, 1920, 1280 or 800 px on the longest edge |
| Filename template | Tokens {name}, {index} (counting from 1) and {ext}; duplicate names made unique automatically |
| Downloads | One file at a time, or every file in a single ZIP |
| Metadata | Not carried over. Output has no EXIF date, camera details or GPS location |
| Color depth | 8 bits per channel. HDR and 10-bit depth are not preserved |
| Multi-image HEIC | Every image exported as its own file. GIF makes one animation; PDF puts each image on its own A4 page |
| One PDF per HEIC by default, or Combine into one PDF for the whole batch in the order the files were added | |
| ICO | 256 by 256 pixels, photo fitted inside a transparent square |
| BMP and TIFF | 24-bit uncompressed BMP and uncompressed RGBA TIFF. Both make large files |
| AVIF | WebAssembly encoder downloaded on first use; noticeably slower than the other formats |
| WebP | Uses the browser's own encoder. Works in Chrome, Edge and Firefox; Safari may not support it |
| Live Photos | The still frame converts. The motion is a separate .MOV video and is not converted |
| Depth maps | Not converted, so Portrait mode depth data is not included in the output |
| Browsers | Current Chrome, Edge, Firefox and Safari |
| Operating systems | Windows, macOS, Linux, Android, iOS and iPadOS |
| Internet connection | Needed to load the page; the conversion itself runs locally |
Device, browser and file problems
These limits come from the hardware, the browser or the file itself, so the fix is usually a smaller batch, a different browser or a fresh copy of the file.
Very large batches stall or the tab reloads
Every photo is decoded into raw pixels in memory, and browsers limit how much memory one tab may use. Phones and laptops with little RAM reach that ceiling first, sometimes by reloading the page without warning. Convert in smaller groups, close other tabs, and download each group before starting the next. A desktop computer copes with much larger batches than a phone.
WebP fails in Safari
If your version of Safari cannot encode WebP, the converter shows an error suggesting JPG instead. Either choose JPG, or open the HEIC to WebP converter in Chrome, Edge or Firefox.
AVIF takes a long time
AVIF compresses well but needs far more computation to encode. Expect it to run noticeably longer than other formats, especially for large photos on a phone. A resize preset speeds it up, and converting a few files first gives you a sense of the time a full batch will take. The HEIC to AVIF converter covers the format in more depth.
A file will not decode
Check that the file finished downloading from cloud storage and really is a HEIC or HEIF image. A .heif file that uses a codec other than HEVC may not decode. If one file in a batch fails while the rest work, that file is probably damaged; ask for a fresh copy or export it again from the device that took it.
What the output leaves out
These gaps are part of how conversion works today. Each one has a workaround, and most come down to keeping the original file.
You need the date taken or location in the converted copy
Converted files do not include EXIF data. Keep the original HEIC files alongside the copies, since the originals still hold the capture date, camera details and location. The HEIC metadata viewer can read those details back whenever you need them.
Photos look flatter than they did on the iPhone
On an HDR-capable screen, the iPhone shows bright highlights using extra HDR data that 8-bit output cannot carry. The converted file shows the standard-range version of the photo. It is the same shot without the extra brightness range, and it looks consistent on ordinary screens and in print.
The Live Photo motion is missing
Only the HEIC still converts. The motion part is a separate .MOV file that the converter does not touch. Converting a Live Photo to JPG explains how to export the parts you need.
Portrait blur cannot be adjusted afterward
Depth maps that let the iPhone change background blur after the fact are not converted, so the effect stays as it appeared when converted. Adjust the blur in the iPhone Photos app first, then export the edited photo for converting.
BMP and TIFF files are huge
Both are written uncompressed, so a single photo can grow to tens of megabytes. That is expected behavior, not a fault. Use them only when a specific program or workflow demands them; PNG is widely accepted and far smaller.
Frequently asked questions
What is the largest HEIC file the converter can handle?
HEIC to PIC sets no size limit of its own. The ceiling is your device's memory, so very large photos or batches work best on a computer with plenty of RAM.
Why do my converted photos look less bright than on my iPhone?
Your iPhone may be showing HDR highlights using extra data that 8-bit output cannot keep. The converted file is the standard-range version of the same photo.
Can I convert the video part of a Live Photo?
No. The converter handles the HEIC still image; the motion is stored in a separate .MOV video file.
Which browsers can make WebP and AVIF files here?
WebP works in Chrome, Edge and Firefox, while Safari may not support it. AVIF uses its own WebAssembly encoder rather than the browser's, so it does not rely on built-in AVIF support, though it is slower.