Watermarking

Every copy carries a mark. Every leak traces back.

An invisible marker embedded in a broadcast feed or a distributed file — so when a leak turns up, it can be traced back to the exact source it came from. Available whether you're an individual creator or an enterprise rights holder, and runs on two tracks under the hood: one built for a signal that's live right now, one built for a file that hasn't released yet.

Two tracks, one engine

Different problem, same forensic mark underneath.

A leaking live signal and a leaking pre-release file get stolen differently, so they're watermarked differently too — but both come out of the same engine, and both trace a leak back the same reliable way.

Live

Built for the moment it's airing.

For content most likely to be leaked in real time — a live sports event, a breaking broadcast. A forensic watermark is embedded into every frame, imperceptible to the viewer, while the signal is still going out.

Format support today
  • Codec: H.264
  • Container: MPEG-TS
  • Transport: SRT, UDP, or HLS (with CMAF support)

Best for: Live sports, breaking broadcasts, any single-source feed

VOD

Built for what hasn't released yet.

For pre-release and catalog assets — an unreleased season, a screener list, a review copy. Same underlying technology, delivered as a file instead of a live signal, so it fits into a distribution workflow instead of a broadcast one.

Format support today
  • Codec: H.264
  • Container: MPEG-TS
  • Delivery: Your S3 bucket, or your own cloud storage, over HTTP

Best for: Pre-release screeners, back catalog, review copies

Live, two ways

Delivered at the edge,
or built into the encoder.

Which one fits depends on what you're optimizing for — reaching every individual viewer, or preserving every bit of encode quality on a feed shared to a handful of receivers.

At the CDN edge

Session-level watermarking

We produce two versions of your stream — mechanically distinct, visually identical. Supported CDN partners serve each viewer their own unique mix of the two at the network edge, so every individual viewer's copy is traceable back to them, with no extra hardware on your end.
In the encoder

Embedded, hardware-level watermarking

For broadcasts where encode quality matters most, the mark is embedded directly in the encoder itself instead of a separate transcode pass — the way to go when the same source feed goes out to several receivers (affiliates, distribution partners) that need to stay distinguishable from one another.
When a leak turns up

Recovered, not just recorded.

A leaked clip — live or VOD — gets run back through the same engine to decode the mark. What comes back is a confidence level and the recovered watermark id, not just a yes-or-no on whether a mark exists. A longer clip gives the decoder more of the mark to work with, so it's the most reliable way to get a clean, fully-recovered id back.

Availability

Add-on for creators, included for enterprise.

For creators, watermarking is a self-serve add-on billed per video — see Creator pricing for the current rate. For enterprise engagements, it's scoped in as part of the coverage — see Enterprise pricing.

Trace the next leak back to its source.

Tell us what you're distributing and how — a broadcast feed, a screener list, a back catalog — and we'll scope the coverage that fits.