Media verification

Limits

• Does not establish that the depicted or recorded content is true.
• Binds the exact bytes only. A re-encode, a resize, or a platform re-upload changes the hash.
• No credentials is not evidence that the content is fake, and a pass is not evidence that it is real.
• A confirmed stamp proves these exact bytes existed by a Bitcoin block. It does not prove the content is true.
• A re-encode changes the hash, so it does not match a stamp of the original bytes.

Check a file on your device

Your file stays on your device. This control hashes it in the browser and sends only the SHA-256.

File on your device Check a file on your device

Full check (uploads the file, up to 2 GB): verifies signatures and edits.

Up to 2 GB. Files over the upload limit: to check whether a copy matches a REGISTERED file, send its SHA-256 instead (computed on your own device: Mac `shasum -a 256 <file>`, Windows `certutil -hashfile <file> SHA256`, Linux `sha256sum <file>`; POST /verify-media with {"sha256": ...}) -- a match means byte-for-byte the registered file; an unregistered hash gets no claim either way, because a hash says nothing about what is inside. To verify or register a larger file we need the file itself: email contact@invinoveritas.dev for large-file pricing. Do NOT compress or re-encode to fit: that changes the bytes, so the file no longer matches its registration or its signature.