Somebody will point a phone at a screen. That is the end of the argument about whether video can be made uncopyable in a browser, and any vendor who tells you otherwise is either uninformed or hoping you are.
So the useful question is not “how do I make this impossible?” It is “how do I make this expensive, and how do I make it traceable?” Those two have real answers.
Effort is a real defence
Most leaks are not sophisticated. They are a student who right-clicked, chose "save video as", and shared the file. Or one who opened the network tab, copied the media URL, and pasted it into a downloader.
Blocking the context menu, hiding the media URL behind blob playback, and blurring the video when the window loses focus do not stop an attacker with a capture card. They stop the ninety percent who were only ever going to try the easy thing. That is not a small win — it is most of the problem.
Attribution changes the calculation
A watermark carrying the viewer’s own email is the single most effective anti-piracy feature in an LMS, and it has nothing to do with prevention.
A student deciding whether to drop a lesson into a group chat is doing a quick risk calculation. If the file is anonymous, the risk is zero. If their own email address is drifting across every frame, the risk is that the academy knows exactly who leaked it within minutes of finding the file.
Make it moving, not static — a fixed overlay in a corner gets cropped in about four seconds.
The leak nobody counts
While everyone worries about video downloads, the bigger revenue loss is usually simpler: one account, twelve viewers. No file ever leaves the platform, and the academy sells one seat instead of twelve.
Device limits fix this and almost nobody turns them on. Cap concurrent sessions per account, evict the oldest instead of blocking the newest — so a legitimate student who upgraded their phone never opens a support ticket — and the shared-password economy stops working overnight.
What we would actually do
If you run a paid academy, in this order:
Turn on the moving watermark. It costs your students nothing and changes the leak calculation completely.
Set a device cap with eviction on. Three devices is a sensible starting point.
Hide media URLs. Invisible to honest students, blocks the lazy download path.
Add capture deterrence last. It is the one students notice, so introduce it once the rest is bedded in.
And then stop thinking about it. Past this point you are buying diminishing returns with real usability cost, and your time is better spent on the course.