C2PA is an open technical standard for attaching tamper-evident provenance information, known as Content Credentials, to images, video and audio. AI watermarking, such as Google’s SynthID, embeds an invisible signal in the content itself. Implementing both means choosing tools that sign content, keeping credentials intact through editing and publishing, and training your PR team to verify media before it goes out.
What problem does C2PA solve?
Brands and newsrooms increasingly face two questions about any piece of media: where did this come from, and has it been altered? C2PA answers them with a signed record attached to the file. The record can show which device or software created it, what edits were made and whether generative AI was involved.

The Coalition for Content Provenance and Authenticity, which maintains the standard, was founded by companies including Adobe, Microsoft, Intel and the BBC, and its members now include major camera makers, platforms and AI companies. Content Credentials is the consumer-facing name for the information, often shown with a small “CR” icon.
How is AI watermarking different?
C2PA metadata travels alongside the content and can be removed, for example when a screenshot is taken or a platform strips metadata on upload. Watermarking hides a signal inside the pixels or audio waveform, so it can survive some editing and compression.
Google’s SynthID marks content made by its own models, OpenAI and others add C2PA data to generated images, and some providers combine both. Neither method is perfect. Watermarks can be weakened by heavy edits, and metadata can be stripped. Used together they give a stronger signal than either alone.

Why should a PR or brand team care?
Provenance helps in both directions. When you publish, credentials let journalists, partners and platforms confirm that an image or statement video is really from you. When you receive media, such as a supposed leaked photo or a video of an executive, checking credentials is one of the first steps in deciding whether it is real.
Regulation is moving the same way. The EU AI Act includes transparency obligations for AI-generated and manipulated content, and platforms such as Meta, TikTok, YouTube and LinkedIn read C2PA data to apply AI labels.
Phase one: map your media flow
Before buying or switching on anything, document how images and video move through your organisation.
- Where content is created: in-house cameras, agencies, stock libraries, AI tools.
- Where it is edited: Photoshop, Lightroom, Premiere, Canva, Figma.
- Where it is stored: a DAM, shared drives, the CMS media library.
- Where it is published: website, press room, social channels, newswire services.
- At which steps metadata is likely to be stripped, such as image optimisation plugins or CDN processing.
This map tells you where credentials will survive and where they will break.
Phase two: choose tools that sign
Several mainstream tools can already add Content Credentials. Adobe Photoshop, Lightroom and Firefly support them, and some cameras from Leica, Sony and Nikon can sign images at capture. Adobe’s Content Authenticity web app lets you attach credentials to finished files. Many AI image generators add C2PA records to their output by default.
Decide what your credentials will say. At minimum: your organisation as the publisher, the creation tool and whether AI was used. Be consistent, because a mix of signed and unsigned official images weakens the value of signing.
What usually breaks during publishing?
The most common failure is the website itself. Image compression, resizing plugins, WebP conversion and CDNs often strip metadata to save bytes. Social platforms may also remove or re-sign data on upload.
Test your pipeline by uploading a signed image and inspecting the published version with the Content Credentials verify tool at contentcredentials.org. If credentials disappear, look for settings to preserve metadata, or keep an original signed file available from your press room for download.
Phase three: the implementation checklist
Use this list to move from pilot to standard practice.
- Media flow mapped, with metadata-stripping steps identified.
- Signing enabled in the main creation and editing tools.
- A credential template agreed: publisher name, tool, AI use statement.
- Website and DAM tested to confirm credentials survive upload and optimisation.
- Press room offers original signed files for journalists.
- Internal rule on labelling AI-generated or AI-edited visuals, matching platform policies.
- Verification step added to the crisis protocol for suspicious media.
- Agencies and freelancers briefed to deliver signed files.
- Review date set, because tool support changes quickly.
How do you verify media you receive?
Verification is the other half of the work. When a journalist sends an image for comment, or a suspicious video of an executive appears on social media, the team needs a fast routine. Check for Content Credentials with the verify tool, run a reverse image search, look for watermark detection tools offered by the main AI providers where available and contact the supposed source directly.
Missing credentials do not prove an image is fake, because most media still carries none. Present credentials that show AI generation, or edits you did not make, are strong evidence and should go straight to the crisis lead.
How Alien Road applies C2PA and AI watermarking
In a typical engagement our PR team starts with the media flow map, working with the client’s communications, design and web teams. We identify where credentials are lost, usually in image optimisation or CMS processing, and propose fixes or a separate download route for originals. We then set up signing in the client’s editing tools and write a short credential and labelling policy.
For crisis readiness, we add a verification step to the issues protocol: any suspicious image or video involving the brand is checked for Content Credentials and known watermarks before a response is drafted. Reporting covers the share of published official media carrying valid credentials and any verification cases handled. For example, a client’s press room can offer signed product photos so editors can confirm their source with one click.
Where to start this week
Take three recent official images from your press room or website. Run each through the Content Credentials verify tool and note what, if anything, survives. Then sign one new image in Photoshop or Adobe’s Content Authenticity app, publish it the normal way and check it again. The difference will show exactly which step in your pipeline needs fixing first.
Keep reading: PR Services · Digital PR