Short answer: drop a corrupted JPG here and the tool identifies which of three damage classes it has — won't-open (header or marker damage), gray-from-the-bottom (truncation), or wrong colors (bad markers) — so you know what's recoverable. It all happens in your browser: your photo is never uploaded, 0 bytes leave your device, and you can confirm that yourself in the browser's Network tab. The honest limit: missing data — like the gray region of a truncated file — can't be brought back, and full JPEG repair is still in development, so today you get a free local diagnosis and prognosis.
Photo won't open, or half of it is gray? Start here
- Drop the photo
- Local diagnosis — damage class identified
- Honest prognosis, before anything else
Fixing a JPG starts with knowing which of three damage classes hit it, because they decide the outcome. The tool above reads the photo locally in your browser (nothing uploaded) and identifies the class. Where the product stands, plainly: full JPEG repair isin development; today the tool gives you the diagnosis and prognosis free, so you know what's recoverable before the engine lands. It will run the same way, in your browser, no upload.
What corrupted JPGs look like — three damage classes
These blocks are illustrations, not screenshots, but if you've got a broken photo open right now, you'll recognize yours:
Why the classes differ: a JPEG is a short run of structuralmarkers (dimensions, decode tables) followed by the compressed picture, which decodes strictly top-to-bottom. Marker damage leaves the picture intact but unreadable (classes 1 and 3): rebuild the structure and the whole image returns. Damage to the picture data itself (class 2) is a hard boundary: everything above the cut decodes; below it there is nothing in the file to decode.
The errors this covers
Could not complete your request because an unknown or invalid JPEG marker type is found.Photoshop — marker damage, classes 1 and 3. The strictest reader of the bunch.
It looks like we don't support this file format.Windows Photos — misleading wording: the format is supported, the file's structure is damaged enough that Photos can't tell.
The file "IMG_2041.jpg" could not be opened. It may be damaged or use a file format that Preview doesn't recognize.macOS Preview — same family, Apple's phrasing.
Where broken JPGs come from
Two sources dominate. Storage and transfer trouble: failing or counterfeit SD cards, a card pulled during a write, an interrupted import; the file ends up truncated or bit-flipped.Data recovery output: photos carved back after deletion are the single biggest source of broken JPGs, because recovery tools guess file boundaries. Recovery finds bytes; repair makes them a picture again. If your photos came out of a recovery tool, diagnose them here before assuming they're lost.
What this can and can't fix
Repairable
- Header and marker damage (class 1 and 3) — the whole image typically returns, untouched pixels, no re-encoding
- Truncated files (class 2) — the surviving top portion is rebuilt into a clean, viewable photo
- Recovered photos with plausible sizes and partial damage
Not repairable
- The gray region of a truncated photo — JPEG decodes top-down, and that area is data that doesn't exist in the file
- Files that read 0 bytes or contain another file's fragments — a recovery problem, not a repair problem
- Missing pixels are never "restored" by guesswork: no AI hallucination — what comes back is your real photo
The current honest boundary: today this page diagnoses your photo and tells you its class; the full JPEG repair engine is in development and ships in-browser like everything else we make. The diagnosis is free either way; you'll know the prognosis before anyone asks you for a cent.