Three approaches, constantly confused, solving completely different problems. Here is what each one is actually for, so you stop paying for the wrong one.
These three are usually presented as competing grades of the same product — bronze, silver, gold. They are not. They address different problems, and buying the most expensive one does not give you the other two.
Knowing which is which is the difference between spending on protection and spending on the feeling of protection.
Your video should not sit at a fixed public address. On a well-built platform it is served through links that are tied to an authorised viewing session and expire quickly, so there is nothing durable to save, forward, or feed to another tool.
This is not a premium feature. It is the minimum standard, it costs nothing extra, and it is invisible to students. A platform that cannot confirm it does this is not protecting your video at all, whatever its security page says.
Treat it as a yes-or-no question when you evaluate a platform.
The student's own identity, shown on screen while they watch.
This is the only control that answers the question every instructor eventually asks: who leaked this? Every copy that escapes carries the identity of the account it came from, which makes an anonymous leak impossible.
Its real value, though, is earlier than that. Most sharing is casual rather than criminal — a file passed to a friend, a link dropped in a group. Seeing your own name on the screen turns a thoughtless act into a deliberate one, and most people stop there. The control works before anything leaks. The watermarking guide covers how to set it up so that effect actually happens.
Cost is low, and it is normally a platform setting rather than a separate licence.
DRM is the encryption-and-licensing system that streaming services use for films and television. It is serious engineering, and it works at what it was designed for: protecting studio catalogues distributed to millions of devices.
For a course business it usually does not add up:
| Secure delivery | Watermarking | DRM | |
|---|---|---|---|
| Bulk copying of your library | Stops | No | Stops |
| Link sharing | Stops | No | Stops |
| Casual re-sharing | No | Deters | No |
| Identifies who leaked it | No | Yes | No |
| Ongoing cost | None | Low | High |
| Setup | Built in | A setting | A project |
| Playback reliability | Unaffected | Unaffected | Can suffer |
The pattern is easy to read. DRM's only strong column is one that secure delivery already covers. Watermarking's column is covered by nothing else at all.
For essentially every course business:
That covers every realistic problem, at a fraction of what a DRM deployment costs.
Not "is my content protected?" The answer is always yes.
Ask three specific ones instead:
Three concrete answers tell you more than any security page. A platform that cannot answer them plainly has already told you what you needed to know — and the wider protection guide puts the whole question in proportion.
Almost certainly not. It was built for film and television catalogues, it carries ongoing licence fees, and it can cause playback problems on older devices. For a course business the money leaks through shared logins and casual re-sharing, and DRM addresses neither of those.
It means your video is not served from a fixed public address. Links are tied to an authorised viewing session and expire quickly, so nothing durable is left to save or forward. It is the minimum standard rather than a premium feature, and it should cost you nothing extra.
Secure delivery as the baseline, per-student watermarking as the layer that deters sharing and identifies any leak, and device limits to close shared logins. That combination covers the problems that actually cost a course business money.
Yes, in narrow cases: licensed content whose owner contractually requires it, a certification body that specifies it, or material where an early leak carries legal exposure. Outside those, the same budget buys more protection elsewhere.
Most advice on protecting courses is either useless or dishonest. Here is what each control genuinely stops, what it does not, and the honest answer about the one attack nobody prevents.
A watermark does not stop copying. It stops anonymous copying — and that turns out to be most of the problem. Here is how to set one up so it actually deters.
The honest answer is no — not completely, not by anyone. But most recording is casual, and casual recording is very stoppable. Here is the line between the two.