Turn on Layer's invisible watermark
Last updated: November 19, 2026
Add an invisible watermark to every image, video and audio file your workspace generates, so each still reads as AI-generated after its metadata is stripped.
Before you start
The watermark is a workspace setting, on every plan. Projects, groups and members do not set it.
To change it yourself through the API, you need Manage workspace settings, which the Admin role has.
It adds to the Content Credentials every generated file already carries. See Content credentials and watermarks for what each one does.
Turn it on
The watermark is not in Settings. Turn it on in either of two ways.
Ask us
Contact support from an admin account and ask for the invisible watermark on your workspace. Name the workspace, and say whether child workspaces should be able to turn it off.
Use the API
Set the
invisible_watermark_enabledcontrol on the workspace's AI policy totrue, with a patch to/v2/workspaces/{workspace_id}/ai-policy. The developer docs have the request.Lock it to stop child workspaces from turning it off.
Check that it works
Generate an image in the workspace and download it.
Upload it to Content Credentials Verify. Its actions list Watermarked after Created (or Edited).
Result
Every generation in the workspace, and in its child workspaces unless they turn it off, is watermarked before it reaches your board, the library or the API. Images and video carry an ID tied to the file; audio carries a mark that says only that Layer made it. Files you generated before turning it on are not marked.
Production tips
Turn it on before a campaign ships. Ads, trailers and store assets travel through platforms that strip metadata; the watermark is what still marks them as AI-generated there.
Export in a format that holds it. PNG, JPEG, WebP, MP4, MOV, WebM and the common audio formats carry the watermark. GIF, TIFF, AVIF, SVG, PSD and 3D models do not.
Expect it to wear under heavy compression. Images keep it through JPEG compression, resizing to half and light cropping; audio through MP3 at 128 kbps. A video re-encoded at a low bit rate can lose it, so deliver video at high quality.
Lock it when a publisher requires AI labeling. A lock keeps every child workspace marking its output.
If something goes wrong
A file has no Watermarked action. The watermark is best effort: a format it does not support, a WebM with a transparent background, or a run that ran out of time is delivered without it, and the generation still completes. Generate it again, or in a supported format.
Content Credentials Verify finds nothing. The file was edited or re-saved outside Layer, which drops its Content Credentials. The watermark may still be in it; your developers can check with the detectors in the developer docs.
Saving the policy through the API turned it off. Replacing the whole policy (
PUT) without the control turns it off. Use a patch, which leaves other controls as they are.