How to Tell If a File Is Corrupted in 3 Minutes
Start Here: Confirm the file before you repair it
- Use this page when you are asking one narrow question: is the file itself actually corrupted, or are you looking at the wrong app, wrong format, or wrong device?
- If you already know the file is failing and now need to decide whether the problem sits in the app, the file, or the storage device, use File Corruption Triage: Diagnose the Failure Before You Repair.
- If the error is specifically "invalid image" or "file could not be opened" for a photo, use Invalid Image Error? Fix "File Could Not Be Opened" Fast.
- If you already confirmed corruption and just need the next repair route, use Why Do Files Get Corrupted? Common Causes and Fast Next Steps or compare Free File Repair Tools.
- If the source device is failing, disconnecting, or asking to be formatted, move to recovery or preservation before repeated checks.
This page is not the full triage system. It is the confirmation page that helps you decide whether "corruption" is the right word at all, so you do not waste time on the wrong category of fix.
1) Run the 3-minute confirmation check
Before you try repair tools, do these checks in order:
- Compare the file size with what you expected.
- Open the file in a second app or on a second device.
- Check whether nearby files from the same folder or device still work.
- If possible, inspect the header or compare a checksum.
Those four checks answer most "is this corrupted?" questions faster than a long repair workflow.
2) Signs that point to true file corruption
Treat the file as truly corrupted when you see one or more of these:
- the file fails in multiple apps and on multiple devices
- the size is 0 KB or clearly smaller than expected
- the file opens only partly, then shows missing sections, gray blocks, or gibberish
- checksum or header validation fails
- the file extension says one format but the internal structure does not match
In those cases, the file itself is usually damaged and you should move toward format-specific repair or backup restore.
3) Signs that point to a viewer or compatibility problem instead
The file may be intact when:
- it opens in one app but not another
- only one platform rejects it
- the failure started right after a software update
- the file extension or codec is unsupported on the current device
That is not the same as corruption. It usually means viewer, codec, or compatibility trouble.
For those cases, use File Format Compatibility Guide or the relevant platform-specific guide before trying repair tools.
4) Signs that point to storage trouble instead of one bad file
The problem may be larger than one file when:
- multiple neighboring files fail together
- the same card or drive keeps producing damaged copies
- the storage device disconnects, turns RAW, or asks to be formatted
- recent transfers from the same source are all incomplete
When that happens, stop treating this like a one-file incident. The safer next move is recovery or preservation of the device, not repeated repair attempts on every broken file.
5) The most useful checks, in plain language
| Check | What it tells you | Best use |
|---|---|---|
| File size | Whether save, export, or transfer ended early | Fastest first pass |
| Second app or second device | Whether this is app-specific | Rules out false corruption reports |
| Header check | Whether the file structure begins correctly | Best for obvious format mismatch |
| Checksum | Whether the file changed from a known good copy | Best when you have the original hash |
You do not need all four every time. Usually the first two already tell you whether the file deserves deeper validation.
6) What to do after the answer is clear
- It is true file corruption: move to format-specific repair, restore from backup, or file recovery.
- It is a viewer or compatibility problem: update apps, switch viewers, or convert only after confirming the file is healthy.
- It is a storage problem: stop writes and move to device-level recovery or preservation.
The goal of this page is not to solve every incident. It is to stop you from using the wrong category of fix.
Related Recovery Paths
- File Corruption Triage: Diagnose the Failure Before You Repair
- Invalid Image Error? Fix "File Could Not Be Opened" Fast
- File Format Compatibility Guide
- Can Corrupted Files Be Recovered? Real Outcomes
- Complete File Recovery Guide: What to Do in Order
Try Magic Leopard(TM) Photo Repair
If the file is confirmed damaged and the storage device is healthy, repair the file copy before you experiment with riskier recovery steps.