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.
Of every protection control available to a course business, per-student watermarking gives the most real security for the least cost and effort. It is also the one most often configured badly — set to barely visible, parked in a corner, and quietly useless.
Here is what a watermark achieves and how to set one up so it does its job. The wider picture is in the protection guide.
Start by discarding the wrong expectation. A watermark does not prevent recording or downloading, and does not make your video harder to copy.
What it does is make every copy attributable. A leaked file with a student's name and code across it is no longer an anonymous file circulating in a group. It is evidence that a specific account leaked it.
That produces two effects, and the second is much larger.
After a leak, you can identify the source. Useful, and the reason most people think they want watermarking.
Before a leak, students see their own name over the lesson and understand that sharing traces back to them personally. Most casual sharing simply never happens. This is where nearly all the value sits — a control that prevents the problem rather than helping you investigate it afterwards.
Watermarking is the only control that stays useful even when everything around it fails. It is not a layer over the video; the student's details are part of the picture. Record the screen and it is in the recording. Point a phone at the monitor and it is in the photo. Re-encode and re-upload it and, as long as the picture is still worth watching, the identifier is still in it.
Every other control protects a step in the delivery chain. This one protects the picture itself, which is why it belongs at the top of the list rather than being treated as a finishing touch.
Make it move. A watermark fixed in one place is far easier to remove than one that cycles slowly between positions with a margin in from the edge. A moving, inset watermark cannot be separated from the video without damaging the video, which is exactly the property you want.
Put the right things in it. The goal is to identify one account and no more:
That last one deserves a moment. Putting a personal phone number on screen works precisely because it feels risky to the student. But it also means that if the video does leak, you have published their number to everyone who received it — a real harm to someone who may simply have lost a laptop. Name plus code gives you almost all the deterrent with none of that exposure, and it is the right default for most academies.
Keep it legible but unobtrusive. Readable rather than dominant, a single line rather than a banner, and never sitting over the part of the frame where your content appears. Consistent across every lesson, so it reads as part of the platform rather than as a glitch.
Tell students why. One line at enrolment — lessons carry your name to prevent redistribution — turns the watermark from something that feels like distrust into something that signals the course is worth protecting. Students who paid a real price usually understand immediately.
Watermarking can be built so that it is practical to use, or built so that it merely appears on a feature list. The difference shows up in one question: can I turn it on for my whole library at once, or does each course have to be processed first?
If enabling it means waiting while your catalogue is rebuilt, or if it only applies to videos uploaded afterwards, the feature will not get used. If it is a switch that applies everywhere immediately, it will. Ask before you commit.
Be clear on the limits so you do not over-rely on it:
No, and that is not its job. A watermark stops copying anonymously. Every leaked file carries the identity of the account it came from, which means you can identify the source and remove them — and, more importantly, students know that before they share anything.
Yes. A watermark fixed in one place is much easier to remove than one that cycles slowly between positions with a margin in from the edges. A moving, inset watermark cannot be separated from the video without damaging the video itself.
Enough to identify one account and no more. A student name plus a short student code is usually ideal. Phone numbers are the strongest deterrent and the biggest privacy consideration — putting a personal number on screen is a decision to make deliberately, not by default.
A badly designed one will. A well-designed one is low opacity, small, moves slowly and never covers the content. Most students accept it immediately once they understand it protects a course they paid for from being resold at a tenth of the price.
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.
Three approaches, constantly confused, solving completely different problems. Here is what each one is actually for, so you stop paying for the wrong one.
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.