ANALYSIS FORENSIC ADVANCED

Hex Damage Map

Upload a file and find out exactly what's wrong with it: which PNG chunk's checksum fails, where a JPEG's markers stop making sense, whether a PDF's cross-reference table actually resolves — backed by a byte-level heatmap of the whole file.

File

Common error messages this diagnoses

If you're here because something threw one of these, this tool shows you exactly what's wrong and how much is recoverable:

  • "This file appears to be corrupted" — generic OS/app message — this tool shows exactly which bytes deviate from what's expected.
  • "Unexpected end of file" — the file is shorter than its own structure expects.
  • "Invalid file header" — the first bytes don't match any known format's magic bytes.

What this tool deliberately doesn't check

Structural validation confirms a file's containers, chunks, and checksums are intact — it doesn't decode the actual payload. Specifically: PNG's deflate/zlib-compressed pixel data isn't decompressed or checked for validity, only its chunk boundaries and CRC-32s. JPEG's entropy-coded scan data (after the SOS marker) isn't decoded — only the marker segments before it. ZIP entries aren't decompressed to verify their contents match their declared CRC-32; for that, use the ZIP Inspector, which does check per-entry local headers. A file can pass every check here and still fail to open if the compressed payload itself is corrupted in a way that doesn't touch the container structure.