ChronoVerify

ChronoVerify is a C2PA Conformant Validator, listed on the C2PA Conforming Products List

Photo provenance check

When was this photo taken?

Check capture time and provenance for any photo, signed or not: read EXIF and XMP, validate C2PA Content Credentials against the official trust list, and get one clear verdict with a signed, timestamped audit record. Free to try, or one API call for stock and trust-and-safety teams, insurance, newsrooms, and OSINT investigators.

EXIF 2026-03-14 09:21 C2PA validated 1 0 1 1 0 0 1 0 1 1 0 1 0 1 verdict: consistent
Drop a photo, click to choose, or paste an image
Or try a sample:

Your photo is processed for this check and is not retained. JPEG, PNG, WebP, AVIF, HEIC, TIFF, GIF, or BMP, up to 25 MB.

How a check works

Every image runs the same deterministic pipeline. Nothing is kept after the check.

Your photo

Uploaded or pasted. Downscaled for analysis, never stored.

Integrity

A SHA-256 and SHA-512 fingerprint locks the exact file.

Provenance

Reads EXIF and XMP, and validates C2PA Content Credentials against the official trust list.

Forensics

Localized error-level and noise analysis flag possible edits.

Verdict

One plain-language result with the evidence behind it.

What you get back

A plain-language verdict, the signals behind it, and a file fingerprint you can re-check yourself.

Multiple signals are consistent with possible editing

manipulation indicated

At least two distinct corroborating signals are jointly consistent with editing. This is a triage flag for human review, not a determination of manipulation, guilt, or forgery.

How strongly the evidence supports this verdict: 60/100
This rates the evidence for the verdict, not the photo. Photos without Content Credentials score at most 70 in this check.
ela_localized_anomaly [pixel]
A local region has re-save error far above the rest of the frame (localization ratio 1000.0). Weak signal; unreliable alone.
noise_dispersion_high [pixel]
Local noise energy is inconsistent across the frame (dispersion 0.473). Weak signal; unreliable alone.
Capture time
2026-03-14 09:21 (EXIF)
Device
Canon EOS R6 (EXIF)
Location
near Sedona, Arizona (34.8697, -111.761)
Content Credentials
none found
Format
JPEG 1200 x 800
SHA-256 1313339afab5c9ed466605db093ea60cc721e1021c3b274213d6f49dc8fa7c67

Sample output. Other images return consistent, inconclusive, or metadata anomaly.

What this can and cannot tell you

A clean result confirms that provenance is intact, not that the scene in the photo is true. Pixel-forensic signals are probabilistic and degrade on recompressed or stripped images. Use the verdict for triage and review, not as proof and not as a sole reason to reject anything. Read the method and limits. See the benchmark and calibration report for how false positives are measured and kept in check.

For developers and teams

Wire the same verdict into your own product with one API call. Teams triage photos at scale for insurance, marketplaces, fintech and KYC, gig platforms, trust and safety, newsrooms, and OSINT investigations. Flat per-image pricing, no operation multipliers.

curl -X POST https://chronoverify.com/v1/verify \
  -F "url=https://chronoverify.com/samples/sample_camera.jpg"

No signup or key needed to try. The public endpoint is free and rate limited. Read the API docs or see pricing.

Building for EU AI Act Article 50 transparency? See compliance and Article 50.

New to provenance? Start with the glossary or browse use cases by vertical.

EU AI Act Article 50

Transparency duties for AI-generated and AI-altered media apply from August 2, 2026. The AI Omnibus package adopted in June 2026 gives generative systems already on the market until December 2, 2026 for machine-readable marking, and the Commission's guidelines were adopted on July 20, 2026 as guidance rather than binding law. ChronoVerify is the verification and audit layer your team uses to read and cryptographically validate C2PA Content Credentials against the official trust list, and to keep a signed record of each check. Provenance validation, not AI detection, and not legal advice. See compliance and Article 50, or check an image for marking now.

Member of the Content Authenticity Initiative

ChronoVerify is a member of the Content Authenticity Initiative. The CAI is the Adobe-founded community advancing C2PA Content Credentials and open content provenance. It is not a certification or an endorsement of any verification result. See how we validate Content Credentials.

Common questions

What is ChronoVerify?

ChronoVerify checks when a photo was taken and whether it shows signs of editing. It reads capture time and provenance from EXIF, XMP, and C2PA Content Credentials, runs pixel forensics, and returns one plain-language verdict with a confidence score. It works on any image, signed or not, through a free web tool and a developer API.

Does ChronoVerify detect deepfakes?

No. ChronoVerify is provenance-first, not a deepfake classifier. It verifies capture-time and provenance integrity and flags possible editing for human review.

Can ChronoVerify help with EU AI Act Article 50?

Yes, ChronoVerify is the verification and audit layer you use to read and cryptographically validate C2PA Content Credentials against the official trust list, with a signed record of each check. It supports your transparency workflow; it does not by itself make you compliant. Article 50 applies from August 2, 2026, with a grace period to December 2, 2026 for the marking duty on pre-existing generative systems. See compliance and Article 50.

How much does ChronoVerify cost?

The public web verifier is free and unlimited. The API has a free tier of 100 verifications per month, pay as you go at $0.003 per image, and one flat monthly plan: Scale at $299 for 200,000 verifications, with signed timestamped reports included in the quota. Signed PDF audit reports are $2.00 each on a funded API key, and a one-time signed report for a single photo is $49, bought at the verdict screen of the free verifier with no account.

Can I use ChronoVerify through an API?

Yes. A single call to the verify endpoint returns the same verdict you see in the browser, including capture time, device, C2PA status, metadata checks, pixel forensics, and a file fingerprint. See the API docs.

How reliable is the verdict?

The integrity layer of file hash and signature is cryptographic and reproducible. The verdict layer is probabilistic and labeled as triage. ChronoVerify was built by a veteran intelligence analyst.