---
title: "Video Watermarking — Static vs Dynamic | Kinescope"
description: "Watermarking does not prevent copying — it identifies who leaked a copy. How static and dynamic per-viewer watermarks work, and why they pair with DRM."
url: https://kinescope.com/glossary/watermarking
---

# *Watermarking*

A marker burned into the video itself. Unlike encryption it prevents nothing — its job is to make a leaked copy point back at the account it came from, which turns an anonymous act into an attributable one.

**Updated:** July 2026 **5 min read** **Security**

In short

Watermarking stamps an identifying mark into the video frames themselves — a fixed logo, or a per-viewer ID — so it prevents no copying but makes a leaked recording traceable to the account it came from.

## What is video watermarking?

Watermarking embeds an identifying mark into the picture. It survives screen recording, [re-encoding](https://kinescope.com/glossary/transcoding) TranscodingRe-encoding a source video into multiple resolutions and bitrates so a player can switch between quality levels on the fly.[Open definition →](https://kinescope.com/glossary/transcoding) and re-uploading, because it is part of the frames rather than metadata around them — which is exactly the point. Every other protection layer fails at the camera; this one keeps working.

It is worth being blunt about what that means: a watermark does not stop anybody. It changes the arithmetic for the person considering a leak, because the copy they hand over carries their own name.

Kinescope renders both kinds: a static logo or text overlay, and a dynamic mark with the viewer's name, email or ID.

## Static and dynamic watermarks

| Type | What it shows | What it is for |
| --- | --- | --- |
| Static | Your logo or fixed text, identical for every viewer | Branding, and a mild deterrent against casual reposting |
| Dynamic (forensic) | The individual viewer's name, email or account ID | Attribution — tracing a specific leaked copy back to one account |

The distinction matters more than it sounds. A static mark tells the world whose content it is; a dynamic one tells you whose copy it is. Only the second changes anyone's behaviour, because only the second makes the leaker identifiable.

Dynamic marks are usually rendered by the player over the video, often drifting position so they cannot be reliably cropped out, independently of the [resolution](https://kinescope.com/glossary/resolution) ResolutionThe pixel dimensions of a video frame — 480p, 720p, 1080p, 2160p (4K). Determines how sharp the picture looks on a given screen.[Open definition →](https://kinescope.com/glossary/resolution) being served. Truly forensic schemes go further and encode the identifier into the pixel data itself, invisible to the eye and recoverable from a re-encoded copy.

## How a per-viewer watermark works

**Identity arrives with the session**

When playback is authorised, your backend supplies whatever identifies the viewer — name, email, account ID, seat number.

**The mark is composed**

That string becomes an overlay: position, opacity and movement pattern configured so it is readable in a recording but not intrusive to a paying viewer.

**It rides on the frames**

Because it is drawn over the video during playback, it appears in any screen capture, phone recording or re-upload made from that session.

**A leak becomes evidence**

When a copy surfaces, the mark names the account. That is usually enough to close the hole rather than guess at it.

## What watermarking does and does not do

| Threat | Does watermarking help? | Why |
| --- | --- | --- |
| Screen recording | Yes — the main case | The mark is in the frames, so it survives into the recording |
| A phone pointed at the monitor | Yes | The one attack no encryption touches; the mark still reads |
| Re-upload to another platform | Yes | Re-encoding does not remove a burned-in overlay |
| Downloading the original file | No | Nothing is prevented — that is what [DRM](https://kinescope.com/glossary/drm) DRMEncryption of the video file plus a licence server that issues a per-session key — so a downloaded copy stays unplayable.[Open definition →](https://kinescope.com/glossary/drm) is for |
| Sharing the playback link | No | Link control belongs to [signed URLs](https://kinescope.com/glossary/signed-url) Signed URLA playback link carrying an expiry and a cryptographic token — it stops working once the window closes, and a tampered link never works.[Open definition →](https://kinescope.com/glossary/signed-url) and domain rules |

Read the table as a division of labour rather than a scorecard. DRM stops the file being taken, signed links stop the URL being passed around, and watermarking covers the gap neither can reach — the moment a camera or a capture tool is pointed at a legitimate session.

## Making it work in practice

A watermark only deters if viewers notice it. A mark hidden in a corner at five percent opacity satisfies a compliance checkbox and changes nobody's behaviour.

**Make it legible, not obnoxious**

The viewer should be able to read their own email if they look for it. That is the whole deterrent.

**Move it**

A mark that drifts between positions cannot be cropped or masked out of a recording with a fixed rectangle.

**Say that it is there**

Deterrence works before the leak. A line in the course terms noting that sessions are marked does more than any amount of opacity tuning.

How Kinescope handles this

### Kinescope burns per-viewer marks into every frame

Kinescope renders both kinds: a static logo or text overlay, and dynamic marks carrying the viewer's name, email or ID, composed from the identity your backend supplies at playback. They sit alongside [DRM](https://kinescope.com/glossary/drm) DRMEncryption of the video file plus a licence server that issues a per-session key — so a downloaded copy stays unplayable.[Open definition →](https://kinescope.com/glossary/drm) and [signed links](https://kinescope.com/glossary/signed-url) Signed URLA playback link carrying an expiry and a cryptographic token — it stops working once the window closes, and a tampered link never works.[Open definition →](https://kinescope.com/glossary/signed-url) rather than replacing them — see [anti-piracy for video](https://kinescope.com/solutions/anti-piracy-video) for the full stack, all of it part of [Kinescope's video hosting](https://kinescope.com/products/video-hosting).

[See video DRM](https://kinescope.com/solutions/video-hosting-drm)

## Further reading

-   [Digital watermarking — Wikipedia](https://en.wikipedia.org/wiki/Digital_watermarking) — a vendor-neutral overview.
-   [DRM](https://kinescope.com/glossary/drm) — the layer that protects the file rather than attributing the leak.
-   [How to stop video piracy](https://kinescope.com/blog/how-to-stop-video-piracy) — a practical guide for creators.
-   [Anti-piracy for video](https://kinescope.com/solutions/anti-piracy-video) — how the layers combine.

[![Denis Konnov](https://kinescope.com/blog-assets/authors/denis-konnov.jpeg)](https://kinescope.com/authors/denis-konnov)

Written by

[Denis Konnov](https://kinescope.com/authors/denis-konnov) Verified

CMO at Kinescope

Denis leads marketing and content at Kinescope, working closely with the platform's engineers. This glossary is reviewed and kept up to date by the team building Kinescope's streaming, encoding and CDN delivery infrastructure.

## FAQ

Can’t find the answer you need? Check out our [Help Center](https://docs.kinescope.com/).

Embedding an identifying mark into the picture itself — either a fixed logo or a per-viewer identifier. It does not prevent copying; it makes a leaked copy traceable to the session it came from.

A static watermark is the same for everyone — typically your logo — and serves branding. A dynamic watermark carries the individual viewer's name, email or account ID, so a leak can be traced to one account. Only the dynamic kind is a real deterrent.

It stops nothing directly. It changes the incentive: someone sharing a recording that carries their own email on every frame is handing over evidence along with the video. In practice that deters the casual sharing which accounts for most leaks.

A fixed overlay in a corner can be cropped. That is why dynamic marks move around the frame, and why forensic schemes encode the identifier into the pixel data where cropping and re-encoding do not reach it.

## Know whose copy it was.

Dynamic watermarks carry each viewer's identity into every frame, alongside DRM and signed links.

[Start free](https://app.kinescope.io/user/create?lang=en)[Read the docs](https://docs.kinescope.com/)
