On this page

Add Video Watermark

Kind: VideoWatermark
Configuration object: videoWatermark

Use Add Video Watermark to embed an experimental, recoverable copy identifier in a completed MP4. The runtime verifies the exported identifier by decoding the output pixels before publishing the artifact.

Inputs

videoSource selects one public HTTPS MP4 URL or a current run's media reference. Source bytes must be nonempty and fit 128 MiB. Remote downloads use no provider credential.

The marker occupies a 32-by-20 luma region at the top-left of each frame. The processing backend must support the input MP4 and the lossless H.264 output path.

Configuration

Property	Default	Usage
`videoSource`	Input expression	Expression selecting one source string.
`identifier`	`"benchius-review-copy"`	Static nonblank identifier, at most 64 UTF-8 bytes, without control characters.

Choose a non-sensitive copy label. Identifiers are recoverable from the pixels and should be treated as readable data.

Outputs

Returns:

Field	Meaning
`watermark_scheme`	`"benchius-luma-lsb-v1"`.
`identifier`	Identifier recovered from the exported pixels.
`verified_from_pixels`	`true` after successful verification.
`limitation`	Explicit warning describing durability and authenticity limits.
`_workflow_media`	One MP4 artifact named `watermarked-video.mp4`.

The processor uses lossless H.264 to preserve the marker and copies the supported audio track. Duration and audio presence are validated. The output remains bounded to 128 MiB. Verification failure returns no published video.

Example

{
  "id": "mark-video",
  "name": "Mark the review video",
  "kind": "VideoWatermark",
  "videoWatermark": {
    "videoSource": {
      "function": "input",
      "value": "input._workflow_media[0].reference"
    },
    "identifier": "campaign-review-copy-01"
  }
}

Connect a completed video Model or Stitch Video result to this step. Change the source path to "input" when the entire input is a URL.

Operational notes

The host needs its configured server or browser FFmpeg watermark implementation. Lossless H.264 can produce substantially larger files, so a valid input can still exceed the output budget.

Cropping, resizing, lossy recompression, and deliberate editing can destroy the marker. The identifier is readable and forgeable and provides no cryptographic proof of ownership. Use this experimental scheme for demonstrations and copy tracking, with separately reviewed provenance controls where required.