HEIC conversion troubleshooting
What to check when HEIC to JPG conversion fails
A failed conversion can come from one damaged file, an unsupported HEIC variant, the 50 MB per-file limit, or a browser that ran out of memory. Preserve the original, isolate the cause, and retry only after you know which part failed.
Read the failure pattern
The failure pattern points to what needs fixing
“Conversion failed” is a result, not a diagnosis. Test whether the error follows one file, every file, one browser, or only a large batch before changing the photo or installing software.
Only one HEIC file fails
When other HEIC photos convert in the same tab, the failing file may be incomplete, damaged, mislabeled, or encoded with features the browser decoder does not handle. Keep that file untouched while you test another copy from the source device or iCloud.
Every HEIC file fails immediately
A browser extension, private-window restriction, stale page asset, unsupported browser, or disabled browser feature may be blocking local decoding. The files are less likely to be the common cause when several unrelated photos all fail the same way.
The conversion stalls on a large photo or batch
HEIC decoding expands compressed data into a much larger pixel buffer. A file can be under the 50 MB input limit and still exhaust memory on a phone or a busy browser, especially when many high-resolution photos are processed together.
A file named .heic is rejected before decoding
The filename may not match the contents. Downloads, messaging apps, and manual renaming can produce files with a .heic extension that contain another format or incomplete data. An extension alone does not prove that the file is a valid HEIC image.
File, decoder, or memory
Local conversion depends on valid image data and available browser resources
The converter reads the selected file inside the browser, decodes its HEIF container, renders the visible pixels, and writes a new JPEG. No upload queue can repair missing bytes or an unsupported image item; the browser must be able to read the source completely.
File size and decoded size are different. The site accepts files up to 50 MB each, but a compressed 20 MB HEIC can require far more working memory after decoding. Low-memory mobile devices, very large dimensions, and parallel batch work can therefore fail below the stated file-size ceiling.
Use a two-by-two check: try a known-good HEIC in the current browser, then try the failing HEIC in another current browser or export it again from the source. The result tells you whether to repair the environment or replace the file copy.
A controlled diagnostic path
Isolate the file, browser, and memory variables in order
- 1
Protect the original before troubleshooting
Leave the source HEIC in Photos, iCloud, or its original folder. Work with a duplicate. If the file is incomplete or damaged, editing and re-saving the only copy can remove your best chance of recovering it from the source device or backup.
- 2
Confirm the filename, size, and download state
Check that the file ends in .heic or .heif, is no larger than 50 MB, and has finished downloading from iCloud or another sync service. A cloud placeholder or zero-byte partial file cannot be decoded even though its name appears normal.
- 3
Test one known-good HEIC
Select a different recent iPhone photo and convert it by itself. If it succeeds, the converter and browser are working, so focus on the original file. If it fails too, refresh the page and continue with browser checks instead of modifying either photo.
- 4
Reduce memory pressure and retry one file
Close memory-heavy tabs and apps, remove other files from the conversion queue, and retry the single HEIC. On a phone, keep the tab in the foreground. Do not add a large batch until one representative file completes successfully.
- 5
Try a current browser without interfering extensions
Use an up-to-date Safari, Chrome, or Edge session. If privacy or script-blocking extensions alter page code, test a clean browser profile where local file processing is allowed. The photo should still remain on the device during supported browser-local conversion.
- 6
Re-export or recover the failing source
If only one file still fails, download it again from iCloud, AirDrop it again, or export a new copy from Apple Photos. If the source will not open on the original device either, restore it from a backup or use photo-recovery help; another online converter cannot reconstruct absent image data.
Ready for a controlled retry?
Test one verified HEIC in a current browser.
Conversion failure questions
HEIC conversion failure FAQ
Why does one HEIC fail when the others convert?
The failing file may be incomplete, damaged, mislabeled, or encoded differently. Download or export a fresh copy from the source device before assuming every converter is broken. Keep the original untouched while testing.
Can a file under 50 MB still run out of memory?
Yes. The 50 MB limit measures the compressed input file, not the much larger decoded pixel buffer. A high-resolution image or several parallel conversions can exceed the memory available to a mobile browser.
Does the converter upload a failed HEIC for processing?
No. Supported conversions are processed locally in the browser. That improves privacy, but it also means browser compatibility, available memory, and valid source data determine whether decoding succeeds.
Will trying another converter repair a corrupt HEIC?
A different decoder may support a variant that the first one does not, but no converter can restore bytes that are missing from an incomplete or damaged file. Re-exporting from Photos, iCloud, or a backup is safer than repeated re-encoding.
What changes if the conversion succeeds?
The result is a new lossy JPEG compatibility copy. This browser converter re-encodes visible pixels and does not preserve EXIF metadata, so keep the HEIC original for metadata, future edits, and archival quality.