A direct camera session
The web app offers an in-browser camera. Its capture source is reported by the client; the browser alone cannot prove camera hardware or the scene in front of it.
OPEN CAPTURE SYSTEM / VERSION 01
A picture
with a paper trail.
Make a photo or short video in RealCam. Get a signed record of its exact bytes and when the service received it. Give anyone a way to check it.
No account. Your original stays on your device.
ILLUSTRATION / THE MOMENT & ITS RECORD
+
● REC
01 / REALCAM STUDIO
Make a record.
Read the evidence.
The camera and the checker live side by side. A receipt is evidence of a particular file, with its limits stated plainly.
Connecting to proof service
REALCAM / LIVE VIEWCAMERA OFF
Your camera,
ready when you are.Nothing starts until you choose to open it.
● 00:00
ready when you are.Nothing starts until you choose to open it.
STANDBYORIGINAL FILE STAYS HERE
CAPTURE CONTROL
Make the moment count.
Open the camera, then take a photo or record up to 30 seconds of video. RealCam signs a file hash after capture.
◈
Camera access is temporary. We send the file’s SHA-256 hash and minimal receipt details, never the original image or video.
✓
SIGNED RECORD CREATED
Your capture has a receipt.
Keep the original bytes. Editing or recompressing them changes the exact hash.
CHECK A CAPTURE
Look beneath
the pixels.
Choose a photo or video. Your browser computes its hash locally and asks RealCam whether that exact file has a signed receipt.
Your original never leaves this browser. Only its hash is sent for lookup.
◉
The file is the question.
AWAITING FILE
The file is the question.
The receipt is the answer.
Exact integrity, receipt time, and declared capture source appear here when a matching record exists.
02 / HOW THE PROOF WORKS
One moment.
Three checks.
Exact-file fingerprint
We hash the original bytes with SHA-256. Any change to those bytes—including a normal export—changes the exact match.
Time-stamped receipt
The service signs a record with the hash and its server receipt time. Anyone can verify that signature against RealCam’s public key.
✳
“Verified” should mean what the evidence actually verifies.
A valid RealCam receipt proves a record was signed for a particular file. It does not prove the scene was unstaged, that AI was absent before capture, or that a client device was uncompromised.
03 / TAKE IT WITH YOU
Proof in
your pocket.
Use the web studio on a phone or computer, or try the native Android beta. iPhone testing is available by invitation.
Open web studio
INVITE ONLY
iPhonePrivate TestFlight beta
▣
DOWNLOAD APK ↗
Android64-bit beta · APK · 17.7 MiB
↗
OPEN ↗
Mobile browserOpen now · add to your home screen
On iPhone, open RealCam in Safari and choose Share → Add to Home Screen. The Android beta installs directly from an APK; it is not on Google Play and physical-device testing is still pending.
THE ROAD AHEAD
More evidence,
more carefully earned.
NOW Browser and native photo and short-video capture, SHA-256 lookup, signed portable receipts.
NEXT Device attestation and verified sensor evidence where hardware supports it.
LATER Standards-based Content Credentials, edits and derivatives, and stronger video provenance.
QUESTIONS / ANSWERS
Trust needs
fine print.
Does a RealCam receipt mean a photo is real? +
It proves that RealCam signed a record for matching file bytes at a server time. Browser capture does not prove the physical scene, exclude a screen in view, or independently attest the device.
What if my file does not match? +
There is no exact receipt for those bytes. The file may be edited, recompressed, exported by another app, made outside RealCam, or simply not in the registry. A missing match is not evidence that a file is fake.
Do you store my pictures or location? +
No original photo or video is uploaded by the web studio. The service stores the hash and limited receipt details. It does not request location.
Can I verify the receipt elsewhere? +
Yes. Download the JSON proof file. It contains the exact signed statement and signature; the public verification key is published at our key endpoint.