Free Tool Desk

Image Integrity Checker

Check a JPG, PNG, GIF, WebP, or BMP file for truncation or corruption before you rely on it — free and instant.

Free to use No sign-up required Files deleted after processing

Verify a JPG, PNG, GIF, WebP, or BMP file is structurally complete before you rely on it — useful after a bulk upload, an FTP/S3 transfer, or a batch export, when a corrupted or truncated file can otherwise sit unnoticed until something downstream (a print job, a build pipeline, a storefront) fails on it.

Accepts JPG/PNG/WEBP/GIF/BMP · up to 20 MB each

Choose a file before converting.

Processing your file…

This usually only takes a moment.

Detected format
File extension

Your file is processed on our server and deleted automatically afterward — see the privacy note below.

Overview

About Image Integrity Checker

Upload an image and this tool checks whether the file is structurally complete, rather than just whether it opens. A file can look fine in a thumbnail and still be damaged — a JPEG missing its end-of-image marker, a PNG missing its final chunk, a WebP or BMP file whose own header declares more data than the file actually contains — all common signs of an interrupted upload, download, or file transfer. This tool checks the file's real byte signature against its extension, walks each format's container structure (including verifying every PNG chunk's checksum), and cross-checks the result against two independent decoders (GD and ImageMagick) — then reports every finding, not just a pass/fail.

Compatibility

Supported Formats

Accepts JPG, JPEG, PNG, GIF, WebP, or BMP input up to 20 MB. Reports a structural pass/fail — no output file is produced.

Guide

How to Use Image Integrity Checker

  1. Choose or drag in a JPG, PNG, GIF, WebP, or BMP file.
  2. Click "Check File Integrity".
  3. Review the findings — a clean file gets a clear pass; a damaged one lists exactly what is wrong.

Highlights

Features

  • Real structural checks, not a preview Verifies each format's end markers, chunk checksums (PNG), and declared-vs-actual file size (WebP/BMP) — not just whether the file happens to render.
  • Two independent decoders Cross-checks the result against both GD and ImageMagick, so a single decoder's leniency can't hide a real problem.
  • Extension-mismatch detection Flags a file whose real content doesn't match its file extension, a separate and common source of downstream errors.
  • No files retained This is a report-only tool — no output file is created, and your uploaded image is deleted automatically after the check runs.

Applications

Use Cases

  • Verify a batch of product photos survived an upload to a store or CMS without silent truncation
  • Check a file a client or contributor sent you before you build it into a design or a print job
  • Diagnose why one specific image in an otherwise-working batch fails to load or print

Good to Know

Limitations

This checks container structure and decoder agreement, not visual content — a structurally valid file can still show the wrong picture, and this tool wouldn't catch that. It flags corruption; it doesn't repair a damaged file.

Files are processed on our servers and are not shared with third parties. Files are deleted as soon as processing or download finishes. Any leftover temporary file is removed automatically by our cleanup process within the configured retention period (60 minutes). See our Privacy Policy for full details.

Support

Frequently Asked Questions

How is this different from just opening the file?

Many viewers and browsers silently tolerate minor corruption (a missing end marker, a truncated final chunk) and render whatever data is present without any warning — so "it opened fine" is not proof the file is intact. This tool checks each format's actual container structure (end markers, chunk checksums, declared-vs-actual size) rather than just attempting to display the file.

What causes an image to become truncated or corrupted like this?

The most common cause is an interrupted transfer — an upload or download that was cut off partway, a failed FTP/S3 sync, or a build process that ran out of disk space mid-write. The file's header (which usually determines its declared format and dimensions) is often written first and survives, while the rest of the data is missing or incomplete.

What formats are supported?

JPG/JPEG, PNG, GIF, WebP, and BMP — PNG checks include walking every chunk and verifying its CRC-32 checksum; WebP and BMP checks compare each format's own declared file size against the file's actual size.

Will it flag a file with the wrong extension?

Yes — if a file's real content (checked by its byte signature, not its name) doesn't match its file extension, that is reported as a separate finding, since a mismatched extension can cause some software to misread or refuse the file even when the underlying data is otherwise fine.

Is my image kept on your server?

No. This is a report-only tool — no output file is created, and your uploaded image is deleted automatically shortly after the check runs.

Keep Going

Related Tools