Certified.Photos
for newsrooms today

Authenticated submissions, end to end.

We’re building for newsrooms. Cryptographic provenance at capture, with a public certificate page verifiable by you and even your readers.

A generic newsroom, end to end.

capture → desk → published → reader

This walkthrough covers a typical newsroom workflow: staff photographer or stringer captures in the field, photo arrives at the desk already verified, editor publishes, and the reader can check the photo’s certificate page independently.

01

Editorial setup (one time).

The desk publishes a signing policy: which contributors can submit, which device tiers are accepted (software-attested vs. hardware-attested), and whether geofence or time-window rules apply for specific assignments.

Newsroom logo and contributor onboarding flow are generated. A per-organization signing identity is provisioned, chained to the desk's verified credential.
02

Contributor onboarding.

Staff photographers, stringers, and freelance contributors download the Certified.Photos app and are linked to the newsroom. Their captures carry the contributor’s identity attached to the cryptographic record.

03

At the scene — signed at the shutter.

Contributor opens the app and taps the shutter. The photo is cryptographically signed at the moment of capture, before the file is written to the device. C2PA manifest, invisible watermark, and witness-anchored timestamp are all bound to that exact frame.

If the device has no network signal, signing still happens locally; the witness anchor is added when the device reconnects. The capture time itself is not editable after the fact.
04

Arrival at the desk.

The photo lands in the newsroom submission portal already verified. The desk sees: who took it, when (precise to the millisecond), where (if not redacted for source protection), on what device, and which attestation tier signed it. Editor decides whether to run it — the verification work is done.

Failed verifications are flagged before they reach a human. Reused, AI-generated, or tampered submissions never enter the queue.
05

Permanent proof. Deletable PII.

The cryptographic record of capture lives forever. The personally identifying data — photographer ID, GPS coordinates, EXIF — lives in deletable storage. Right-to-erasure works. Source protection in war zones works.

The proof of authenticity does not depend on the data that has to be deletable. Redaction or erasure of PII does not break verification.
06

Publish with a verification link.

Every certified photo has a public certificate page at cert.photos/v/<id> — a public, account-free page that shows the capture record. Today, newsrooms surface that link manually (caption, credit line, or a hand-placed badge image) next to the published photo.

Native CMS integration — automatic badge embedding through a plugin or module — is on the roadmap. See below.
07

Reader-side verification.

Anyone, anywhere, can click the badge or paste the image URL into the certificate page. They see the same cryptographic record the desk saw. Trust no longer depends on the newsroom’s reputation alone — it’s verifiable independently.

Verification survives recropping, recompression, and screen-recapture, thanks to the invisible watermark imprinted at capture. The photo can be shared on social, screenshotted, embedded elsewhere — the certificate still resolves.
08

Archive & long-tail trust.

The photo’s certificate page remains live indefinitely. Years from now, a researcher, an editor revisiting an old story, or a court reviewing historical record can pull up the verification record. The provenance outlives the news cycle.

The cryptographic record is replicated across an independent witness network — designed to outlive any single operator.

CMS integration — coming soon.

Newsroom CMS integration is on the roadmap and not yet available. If you publish on WordPress, Drupal, Brightspot, Arc XP, a custom stack, or a static-site / Jamstack pipeline and you want to scope an integration with us, email [email protected].

Talk to us.

Newsroom? Let’s book a 45-minute working session: your team and ours, scoped to your specific workflow. Other industry? Email us and we’ll get back with an honest read on timing.