See What Content
Authenticity Looks Like
Sign files to embed cryptographic provenance. Verify files to inspect their origin chain. Understand why provenance matters — and where it breaks.
Unsigned vs Signed — Side by Side
Same image, different levels of trust. The signed version carries an embedded OP manifest with signer identity, timestamp, and tamper-evident hash.
vehicle-damage-claim.jpg
signed_vehicle-damage-claim.jpg
Try It Yourself
Upload any image or video to sign or verify it. Take a photo with your camera to sign it instantly. All processing happens server-side — files are not stored.
What Happens When You Re-Save?
Provenance is embedded in the file structure. Any modification — even saving with different compression — breaks the chain. This is by design.
Why This Matters
OP provenance is embedded in the file structure. When you modify the file in any way, the cryptographic hash changes and the provenance chain breaks. This is by design — it proves the file hasn't been tampered with. But it also means provenance is fragile.
Test Bench — Explore Trust Tiers
Click each asset to inspect its verification result. Verified, signed, unsigned — each tells a different story about the file's origin. You can also sign any file directly.
Help Us Build the Right Tools
10 quick questions about your industry, needs, and priorities. Your answers directly shape what we build next.
Ready to Build With This?
Get free API access to sign and verify media programmatically.
Get Free API AccessProvenance shows origin and chain of custody. It does not prove the content is true or unaltered in meaning. Powered by open standards for content authenticity.