Compare

See what changes after a clean export.

Image diff guidance helps explain why the visible picture should look the same while the container and fingerprint change.

Comparison points

01

Visible pixels

The picture remains visually consistent after normal JPEG export.

02

File container

The cleaned file uses a new JPEG container without the original metadata blocks.

03

Fingerprint

Sparse RGB nudges create a fresh technical signature while staying visually subtle.

How to compare an original with its cleaned export

An image diff can answer several different questions, so begin by deciding what matters. A visual comparison asks whether the subject, color, crop, and useful detail still look right. A technical comparison asks whether bytes, hashes, metadata blocks, dimensions, or compression changed. A privacy comparison asks whether sensitive fields remain. The original and cleaned files should not be byte-identical, because the purpose of the cleaner is to create a new container and refreshed technical signature.

Start with ordinary viewing

Open both images at a comfortable size and compare the whole composition. Look at faces, text, smooth gradients, fine lines, shadows, and saturated colors. The cleaned JPEG should preserve the practical appearance of the source, although a new lossy encode can create very small differences. If the image is intended for print, scientific review, legal evidence, or another color-critical use, use a professional comparison workflow and keep the original untouched.

Zoom in for compression artifacts

At high magnification, JPEG may show subtle changes near sharp edges or fine texture. That does not necessarily indicate a cleaning error. The exporter begins at a high quality and lowers it only when needed to meet its output-size target. Compare at the final display size as well as zoomed in. A technically measurable difference can remain invisible to a normal viewer, while an obvious color shift or missing area deserves investigation.

Compare metadata and hashes separately

A file hash should change because the output bytes are new. The cleaner also nudges sparse RGB values, so a decoded pixel hash should change as well. Metadata tools should no longer find the source container’s common EXIF, GPS, XMP, IPTC, C2PA, or generator areas. Remember that different inspection applications report fields in different ways, and a valid new JPEG still contains structural markers required for decoding.

“Looks the same” and “is the same file” are not contradictions. The cleaner aims for visual continuity while intentionally changing the container, metadata, compression, and fingerprint. Save comparisons alongside the private source only when they are useful; the ordinary recipient usually needs the clean export, not a package containing both versions and their technical differences.

Use the result as a quality-control step

For important deliveries, record the original dimensions and file size, clean a copy, open the result, and inspect representative details. Confirm that transparency was not required, because the current output is JPEG with a solid background. Then verify the filename and destination before sharing. This short review catches accidental source selection, extreme compression, or visible private information that metadata removal alone cannot address.