Content credentials and watermarks

Last updated: November 19, 2026

Every image, video and audio file you generate in Layer carries signed Content Credentials that say it was made with AI, by which model, on Layer. A workspace can also add an invisible watermark that stays in the file after its metadata is stripped. Together they are how Layer marks its output as AI-generated under rules such as Article 50 of the EU AI Act, and anyone can check them with free, public tools.

How it works

Layer marks generated files in two ways, one in the file's metadata and one in its content.

Content Credentials

Content Credentials are the open C2PA standard for a file's origin. Layer signs a manifest into every generated file whose format can hold one, before the file reaches your board, the library or the API. It is always on, and there is nothing to set up.

The manifest records:

  • that the file was created with AI, or, when you edited an existing file, that it was opened and then edited with AI;

  • the model that made it, and when;

  • the files the run was built on (the file you edited, your reference images, a first frame), including their own Content Credentials when they had them;

  • your workspace, the run, the seed and the styles applied.

It never holds your name, your email address or your prompt.

When the model's provider signs its own Content Credentials into its output, Layer keeps them inside Layer's, so a checker shows both.

Invisible watermark

Metadata is easy to lose: many apps, chat tools and social platforms strip it, and re-saving or re-encoding a file breaks the signature. The invisible watermark is woven into the pixels or the sound itself, so the file still reads as AI-generated after that. You cannot see or hear it.

It is off until an admin turns it on for the workspace. See Turn on Layer's invisible watermark.

Which files are marked

Images

PNG, JPEG and WebP carry Content Credentials and, when it is on, the watermark. GIF, TIFF, AVIF and SVG carry Content Credentials only.

Video

MP4 and MOV carry Content Credentials and, when it is on, the watermark. WebM has no place for Content Credentials, so it carries only the watermark, and a WebM with a transparent background carries neither.

Audio

WAV, FLAC, MP3, M4A and AAC carry Content Credentials and, when it is on, the watermark. AAC files are delivered as M4A, with the sound unchanged.

Everything else

PSD files, 3D models, playable ads and ZIP archives carry neither.

Check a file

Upload a file to Content Credentials Verify to see its manifest: the AI tool, the actions, and the files it was made from. Layer's credentials read as valid, with a note that the signer is not on the C2PA trust list. Layer is not on that list yet.

The watermarks are made with open-source models, and the same models detect them: TrustMark for images, Video Seal for video and AudioSeal for audio. Your developers can find the details in our developer docs.

What it means for you

  • Download and share as you normally do. A file downloaded from Layer, and an export from Layer, keep their Content Credentials.

  • Editing a file in another app usually drops its Content Credentials or makes them read as changed. That is the standard working as intended; the watermark, when it is on, survives most edits, though heavy compression can wear it away.

  • Both marks are best effort. If one cannot be added to a file, the file is still delivered, without it.

  • The credentials name your workspace, so anyone who inspects a file can see it came from your Layer workspace, though not which person made it.

Related