Proofcan compared.
What each provider says about itself on its own site, set next to what Proofcan does. These are starting points for your own evaluation, not rankings.
| Proofcan | A C2PA manifest declaring the image as AI-generated, an invisible TrustMark watermark carrying a lookup ID, and a registry record. | Images only (PNG, JPEG, WebP), up to 50 MB each and 25 per batch. No video, audio or text. | Published: Free (5 marks a month), EUR 29, EUR 99 and EUR 199 a month for 100, 400 and 1,000 marks. |
| Truepic | Authenticates photos and videos at capture and applies AI analysis (current homepage). | An archived Enterprise C2PA page says its Lens SDK captures photos, videos and audio in mobile apps. | Pricing is set with the Truepic team per inspection type; plans named Flex and Standard. |
| IMATAG | Invisible watermark for identifying the source of leaks. | Its pricing page says the Leaks and Authenticity products work on images and videos. | Leaks and Authenticity: pricing on demand; available as SaaS, API or on-premise. |
| Steg.AI | Imperceptible watermarks to trace leaks, protect against deep fakes and signify ownership; visible watermarks are also offered. | Videos, images, documents and audio. | Basic plan is self-serve sign-up; Enterprise is “Contact Us”. |
| ForensicMark | An API that embeds invisible forensic watermarks into images and attaches C2PA content credentials. | Demo upload formats: JPEG, PNG, WebP, HEIC, AVIF, up to 100 MB. | Says there is no self-serve pay-per-use option yet. |
| Adobe Content Credentials | Each asset is cryptographically hashed and signed to capture a tamper-evident record (Content Authenticity Initiative). | Adobe says Content Credentials can be applied to images, audio and video files. | A free web app; the CAI’s tools are free and open source. |
| Google SynthID | Embeds digital watermarks directly into AI-generated images, audio, text or video. | Images, audio, text and video. | SynthID Text is open sourced for developers (ai.google.dev). |
How entries are chosen
- An entry exists only if we found the statement on the vendor’s, platform’s or regulator’s own page and quoted it. Entries we could not confirm that way are left out rather than guessed.
- Every quoted sentence was re-checked against the live page on 6 October 2026 by script. Pages that block scripted fetches were read from an Internet Archive snapshot of the same page, and the entry says so.
- We report what a source says, nothing more. “Not documented” means we did not find it in the pages we read; it is not a statement that something is absent.
- Only facts the provider publishes on its own site are used, with a quote and a link. Where a provider’s pages blocked us or were out of date, the entry says which source we used and its date.
- Each comparison states where Proofcan does not do what the other provider describes.
Sources
Each entry links to its own sources, with the date each was last checked.
Page reviewed . Proofcan is a technical tool, not legal advice, and does not guarantee compliance.