Identity and integrity
Computes SHA-256, identifies JPEG or PNG from header bytes, and reports dimensions independently of the filename.
Inspect a photo’s hash, true container, dimensions, metadata and editing markers, C2PA/JUMBF signals, entropy, and appended data—then download a branded evidence report.
Evidence warning: No software can prove a photo is “real” from one file. Metadata can be forged, editing can be legitimate, and absence of a provenance credential is not evidence of fakery.
Maximum 10 MB. The API processes the file in memory and does not retain file content. Use only images you are authorized to analyze.
Computes SHA-256, identifies JPEG or PNG from header bytes, and reports dimensions independently of the filename.
Surfaces EXIF/XMP, camera, software, timestamp, Photoshop/Adobe, ICC, and sparse-metadata signals where readable.
Detects C2PA/JUMBF-style markers while clearly separating marker presence from cryptographic trust validation.
Finds data after a JPEG end marker, secondary file signatures, and whole-file entropy for deeper review.
Preserve the original and record its SHA-256 hash before editing or converting it.
Review every note, warning, and error alongside the complete technical facts.
Corroborate findings with provenance validation, source files, witnesses, and specialist examination when stakes are high.
No. It reports structural and metadata evidence. AI detectors and missing camera metadata are probabilistic signals, not proof.
No. It shows that an Adobe-related marker exists; ordinary cropping, color correction, and exporting can create the same trace.
The beta detects C2PA/JUMBF-style markers but does not yet validate the cryptographic signature, certificate chain, or issuer trust.
The PDF records devFlokers branding, file identity and hash, verdict, typed findings, evidence, recommendations, technical facts, and limitations.
We use cookies to enhance your experience. By continuing, you agree to our Privacy Policy.