Compare bytes, not just thumbnails
Compare Photo Files with SHA-256: What It Proves
A local SHA-256 comparison helps check whether a prepared photo and another accessible copy have matching file contents. Different hashes mean the bytes differ, not that privacy failed. Matching hashes do not prove the image was private, authentic, or delivered to the intended person. Inspect the prepared copy before using it as your reference.
By Qingxin Studio, the developer of HushPic · Updated
Choose a reference you have actually reviewed
Identify the final prepared photo and keep it distinct from the untouched original. Record which file you intend to compare, not merely its gallery title. A hash faithfully identifying the wrong original would not help your sharing decision.
Obtain the second file only through an authorized local save or download. A thumbnail inside a message is not a separate file you can hash, and an unavailable recipient attachment leaves the comparison unverified. Do not claim to know the delivered bytes from the sender’s preview alone.
Compute both hashes locally in PowerShell
Microsoft documents Get-FileHash and the explicit SHA256 algorithm. A read-only example is Get-FileHash -LiteralPath 'C:\PhotoReview\prepared.jpg' -Algorithm SHA256. Run it again for the other accessible file, replacing the example path with that exact file’s local path.
Use LiteralPath rather than a broad wildcard to avoid including unintended files. Read the complete Hash values and confirm both results say SHA256. Keep output private: even a local command’s Path column can contain personal folder names. Do not upload the photos to a web hash calculator for this task.
Interpret matching and different results narrowly
Matching SHA-256 values are strong practical evidence of matching file contents, not a visual-similarity score or privacy certification. A filename change alone is a different question from a content change. Compare the values, not the spelling of the paths.
A different value can reflect export settings, recompression, metadata changes, or other byte changes. The hash does not identify which change occurred. Reinspect the second file’s visible content and supported metadata before deciding whether it is suitable; do not call every mismatch corruption or disclosure.
Restart the reference after editing
If you generate another sharing copy, review it and calculate a new reference hash. Do not compare today’s attachment against a superseded result and assume yesterday’s check still applies. Preserve originals and avoid deleting duplicates during a diagnostic comparison.
The browser checker reads supported local metadata categories, not hashes, pixels, or recipient delivery; it cannot clean or generate verified output. HushPic prepares separate supported photos on-device and performs bounded post-write checks. Review suggestions and regenerate after changes. Neither tool authenticates recipients or makes a hash match proof of anonymity.
Sources
This guide is published by Qingxin Studio, the developer of HushPic. Product claims describe our supported workflow, not independent certification. Our review checklists are practical first-party guidance; linked platform sources support only the mechanisms they describe. Automatic checks may miss details. Read our content and corrections policy.