HEIC Files Corrupted or Won't Open: Recovery Guide

Your HEIC file produces an error, shows a broken image icon, or opens as a garbled mess. Other HEIC files on the same device open without problems. The file itself is damaged, not your device or software. This guide walks through how to confirm corruption, attempt recovery, and prevent it from happening again.

Step 1: Confirm the File Is Corrupted, Not Just Unsupported

Many HEIC "corruption" reports are actually compatibility problems. Before attempting recovery, rule out a simple codec issue.

The definitive test

Open the file on an iPhone or Mac. Apple devices have native HEIC decoding built into the operating system. If the file opens normally on an Apple device, it is not corrupted. Your other device simply lacks HEIC support. In that case, see Why Can't I Open HEIC Files? for platform-specific fixes.

If you do not have access to an Apple device, try these 3 checks:

1. Check the file size. A 0-byte file or a file under 1 KB is almost certainly corrupted or incomplete. A typical HEIC photo from an iPhone is 1-4 MB.
2. Check the file header. Open the file in a hex editor or run file photo.heic on Linux/Mac. A valid HEIC file starts with ftyp at byte offset 4. If the first bytes are zeros, random data, or HTML content, the file is corrupted or was replaced during transfer.
3. Try multiple HEIC-capable apps. If the file fails in every app that normally handles HEIC, corruption is the likely cause.

Quick diagnostic table

| Symptom | Likely Cause | | --- | --- | | Opens on iPhone/Mac, fails on Windows/Android | Codec issue, not corruption | | Fails on every device including iPhone/Mac | File corruption | | File size is 0 bytes | Incomplete transfer or write failure | | File size is abnormally small (under 1 KB) | Truncated during transfer | | File opens but image is partially garbled | Partial data corruption | | Error: "not a valid image" or "unsupported format" | Header corruption or wrong file extension |

Common Causes of HEIC Corruption

HEIC files become corrupted for the same reasons any file does. Understanding the cause helps determine whether recovery is possible.

1. Incomplete file transfer

This is the most frequent cause. A USB cable disconnects during transfer. A download over Wi-Fi drops mid-stream. A Bluetooth transfer times out. The result is a truncated file that contains only part of the original data. The file header may be intact, but the image data is cut short.

2. Storage media errors

Failing SSDs, aging SD cards, and damaged USB drives produce bit-level corruption. Individual sectors become unreadable. The file system reports the file exists, but the stored bytes no longer match what was originally written. SD cards in phones are especially vulnerable because of constant write cycles.

3. Incomplete iCloud sync

iCloud Photos uses an "optimized storage" mode that keeps low-resolution placeholders on the device. The full-resolution file downloads on demand. If a sync interrupts during download, the resulting local file may be incomplete. This appears as a valid HEIC file that opens as a blurry thumbnail or produces a decode error.

4. Software bugs during capture

Rare but documented: a crash or forced close of the Camera app during photo capture can produce a corrupted HEIC file. The HEIF container is written but the HEVC-compressed image data inside is incomplete. This is more common on older iOS versions and third-party camera apps.

5. File system corruption

Power loss during a write operation, improper ejection of external drives, or operating system crashes can damage the file system metadata. The file may appear intact in the directory listing but contain incorrect data. Running a file system check (chkdsk on Windows, fsck on Linux, Disk Utility on Mac) can sometimes expose these issues.

Recovery Methods

Try these methods in order. Each successive method handles more severe corruption but recovers less data.

Method 1: Try a different app or decoder

Different HEIC decoders have different error tolerance levels. A file that crashes one decoder may partially render in another.

Apps to test with:

• Apple Preview (Mac): Apple's decoder is the most tolerant of minor HEIC errors
• Google Photos: Handles some edge cases that other viewers reject
• IrfanView (Windows, with plugins): Known for lenient format parsing
• libheif command line (Linux/Mac): Provides detailed error messages that help diagnose the corruption type

If any app renders the image, even partially, take a screenshot or export to JPG immediately. A partial recovery is better than no recovery.

Method 2: Extract the embedded preview thumbnail

HEIC files contain an embedded EXIF thumbnail, typically 160x120 or 320x240 pixels. This thumbnail is stored separately from the main image data. If the main image data is corrupted but the file header and EXIF metadata are intact, the thumbnail may still be extractable.

Using ExifTool (free, cross-platform):

exiftool -b -ThumbnailImage photo.heic > thumbnail.jpg

Using Python with Pillow:

from PIL import Image
img = Image.open("photo.heic")
# Some corrupted files still yield EXIF data
exif = img.info.get("exif")

The extracted thumbnail is low resolution but may be the only recoverable version of the image. For photos with sentimental value, even a 320x240 thumbnail is better than nothing.

Method 3: Use data recovery software

If the file was deleted or the storage media is failing, data recovery tools can sometimes retrieve an earlier, uncorrupted version of the file.

Recommended tools:

• PhotoRec (free, open-source): Scans storage media at the raw level and recovers files by header signature. Works on Windows, Mac, and Linux. Recovers HEIC files by detecting the ftyp header pattern.
• Disk Drill (free tier available): User-friendly interface for scanning drives and recovering deleted or corrupted image files.
• R-Studio: Professional-grade recovery tool that handles complex file system damage.

Key requirement: stop writing data to the storage device immediately. Every new file written reduces the chance of recovering the corrupted original. If the corrupted HEIC files are on a phone's internal storage, avoid taking new photos until recovery is attempted.

Method 4: Partial decode with libheif

The libheif library (the same library that powers HEIC decoding in Linux and many other tools) can attempt partial decoding of damaged files. It may extract whatever image data remains intact, even if the result is an incomplete image.

heif-convert --quality 90 corrupted.heic output.jpg

If the file has partial data corruption, libheif may produce a JPG where some portions render correctly and damaged sections appear as gray blocks or color artifacts. This is a partial recovery. The HEICify converter uses libheif-js internally and may successfully decode files that other tools reject outright.

Method 5: Restore from backup

This is the most reliable recovery method when it is available.

Check these backup sources:

1. iCloud Photos: If the original was taken on an iPhone with iCloud Photos enabled, the full-resolution original exists in iCloud. Sign in at icloud.com/photos and download the file again.
2. Google Photos: If auto-backup was enabled, Google stores a copy (possibly slightly compressed).
3. Time Machine (Mac): Browse Time Machine backups to find an earlier version of the file.
4. Windows File History: If enabled, previous versions of files in backed-up folders may be retrievable.
5. Cloud storage versions: Google Drive, Dropbox, and OneDrive keep version history for 30-180 days depending on the plan.

iCloud is the single most effective backup source for iPhone photos. If iCloud Photos was enabled when the photo was taken, the original exists in Apple's cloud regardless of what happened to the local copy.

When the File Is Unrecoverable

Some files cannot be saved. Accept that recovery is not possible when:

• The file is 0 bytes. There is no data to recover. The file entry exists but contains nothing.
• The file header is completely overwritten. If the first bytes are not a valid HEIF container signature, no HEIC decoder can interpret the data.
• The storage media is physically damaged beyond recovery. Professional data recovery labs charge $300-$1,500+ and still cannot guarantee results on physically damaged media.
• No backup exists anywhere. Without a second copy, a fully corrupted file is permanently lost.
• The file was overwritten by new data. Once the storage sectors are reused for new files, the original data is gone.

If the file has sentimental value and the storage media is physically damaged, a professional data recovery service is the last resort. Companies like DriveSavers, Ontrack, and Gillware specialize in recovering data from damaged devices. Expect to pay $500-$1,500 for phone or SSD recovery.

Prevention: Stop Corruption Before It Happens

Preventing corruption is far easier than recovering from it. Follow these 6 practices.

1. Never interrupt file transfers

Wait for the transfer progress bar to complete fully. Do not unplug USB cables, close laptop lids, or switch apps during active file transfers. A 3-second interruption can truncate a multi-megabyte photo file.

2. Use reliable transfer methods

AirDrop and iCloud Photos are the most reliable ways to move HEIC files from an iPhone. Direct USB transfer with verified completion is the next best option. Avoid Bluetooth for large batches. Email and messaging apps often compress or re-encode photos, which avoids corruption but reduces quality.

3. Verify transfers immediately

After transferring HEIC files to a new device, open 3-5 random files to confirm they display correctly. Catching a failed transfer immediately allows you to re-transfer from the source before the originals are deleted.

4. Enable iCloud Photos

iCloud Photos creates an automatic, always-current backup of every photo taken on an iPhone. This is the single best protection against HEIC file loss. Even if the phone is lost, stolen, or destroyed, every photo exists in iCloud. The 5 GB free tier fills quickly with photos. The 50 GB plan costs $0.99 per month and provides meaningful headroom.

5. Replace failing storage media

SD cards and USB drives have finite write cycles. If a drive starts producing read errors, corrupted files, or intermittent disconnections, replace it immediately. Do not continue using it and hoping for the best. Copy all data off the drive first, then dispose of it.

6. Keep local backups

Cloud backups can fail, sync can lag, and accounts can be locked. Maintain at least 1 local backup of important photos on a separate physical drive. A $50 external SSD holds tens of thousands of HEIC photos and provides a recovery path independent of any cloud service.

Summary

A HEIC file that will not open is either corrupted or unsupported. Test on an Apple device first to rule out a codec issue. If the file is genuinely corrupted, try alternative decoders, extract the EXIF thumbnail, use data recovery software, attempt a partial decode with libheif, or restore from backup. Prevention is always more effective than recovery: use reliable transfers, verify files after copying, and maintain backups. For files that are not corrupted but simply will not open on your device, convert them to JPG with HEICify and the compatibility problem disappears.