Short answer: drop a PSD here and the tool sorts it into one of three cases — won't-open (a damaged header or section-length field around intact artwork), truncated (a crash or interrupted save cut off the end), or opens-but-flat (the layer section is damaged but the merged image survived). It runs in your browser: the file is never uploaded, 0 bytes leave your device, and you can confirm that in the browser's Network tab. It repairs the file right in your browser now, recovering the flattened composite — as a PSD, or exported to PNG or JPEG. The honest limits: what comes back is the flattened composite, not your layers, and a truncated tail can't be brought back.
PSD won't open, or opens without layers? Start here
- Drop the file
- Local read — which of the three cases it is
- Honest prognosis, before anything else
Fixing a PSD starts with knowing which section broke. A PSD is a small header plus four length-prefixed sections, and the one users want most — the flattened composite raster — sits last, behind the big, fragile layer section. That layout decides everything: damage to the header or a length field blocks a reader from a picture that's actually intact, while a truncation eats the composite from the end. Where the product stands, plainly: the PSD enginerepairs the file in your browser now; it recovers the flattened composite (and an embedded thumbnail when that's all that's left), never the layer stack. It runs the same way as everything we make: in your browser, pure, no upload.
What broken PSDs look like — three cases
These blocks are illustrations, not screenshots, but if you've got a problem file open right now, you'll recognize yours:
Why the cases differ: a PSD is a fixed header(8BPS, dimensions, color mode) followed by four length-prefixed sections — color mode, image resources (which hold a small JPEG thumbnail), the layer and mask section, and finally the flattened composite. Header or length damage leaves the composite intact but unreadable (case 1): re-derive the boundaries and it returns. A truncation eats the composite from the end (case 2): a hard boundary, because the missing rows aren't in the file. And when only the layer section is hit (case 3), the composite is fine — but the layers can't be rebuilt, so what you get is the flattened image.
The errors this covers
Could not complete your request because it is not a valid Photoshop document.Header or section-length damage — case 1. The composite is usually intact behind it.
Could not complete your request because the file is not compatible with this version of Photoshop.A desynced parser reading a damaged length field as an impossible value.
Could not complete your request because of a program error.Photoshop's catch-all — often a truncation from a crash or interrupted save (case 2) that leaves the file structurally incomplete.
Where broken PSDs come from
One pattern dominates: a save that didn't finish.Photoshop or the machine crashing mid-write, a full disk, an interrupted Dropbox / Drive / Creative Cloud sync, or a save to a network drive that dropped — all leave the file truncated, and because the composite is written last, the tail is exactly what's lost. The other source isdata-recovery output: PSDs carved back after deletion, where the tool guessed the boundaries and returned a garbage prefix or the wrong length. Recovery finds bytes; repair makes them an openable image again.
What this can and can't fix
Repairable
- Header and signature damage — the
8BPSmagic and geometry rewritten, cross-checked against the decoded composite - Corrupt section-length fields — boundaries re-derived by re-walking the resource blocks instead of trusting the broken length
- Truncated composite — every complete scanline before the cut is emitted, with an honest count of rows recovered vs expected
- A damaged layer section with an intact composite — the flattened image is recovered
- Nothing left but the embedded JPEG thumbnail — extracted as a labeled preview
Not repairable
- Layers, masks, adjustment layers, smart objects and effects — once the layer section is damaged there's no deterministic reconstruction, and we don't guess; no AI fill
- Rows past a truncation in a ZIP-compressed composite — deflate can't resync beyond the break
- Files that read 0 bytes or contain another file's fragments — a recovery problem, not a repair problem
The current honest boundary: today this page tells you which of the three cases your PSD is, and always what you'll get back — the flattened image, not the layers. The composite-recovery engine repairs your file right in your browser now 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.