File Integrity Verification
Check in seconds whether a screenshot, document or video captured with JUS. has been altered. Drop the file below; its SHA-256 fingerprint is computed in your browser.
Your file is never uploaded — everything runs locally, in your browser.
How does it work?
A file's SHA-256 digest is unique to it; changing even a single pixel produces a completely different hash.
The hash computed at capture time is written into the report. If the hash here matches it exactly, the file is unaltered.
The computation happens in your browser; the file is never uploaded to JUS. servers.
It proves the file's content has not changed since capture (integrity).
On its own it does not prove “when” the file was captured. A qualified timestamp (TSA) is a separate step.
FAQ
Is my file sent to JUS.?
No. SHA-256 is computed in your browser (WebCrypto); the file never leaves your device.
Which files can I verify?
Screenshots, full-page captures, PDFs, videos — any file. What matters is that the hash in the report was produced from the same file.
Why doesn't the hash match?
The file may have been re-saved, compressed, cropped or otherwise modified. Even the smallest change alters the hash completely. Upload the exact file referenced in the report.