You spent a whole summer recording a term of chemistry lessons. Then a parent sends you a screenshot of a Telegram channel selling your videos for a tenth of your price.
It is the fear we hear most from teachers in Egypt and the Gulf. When your income depends on one cohort a year, a leak hits the whole season.
The good news: most leaks come from weak setups, not clever pirates. The honest news: no platform can make leaks impossible. This guide shows which protection layers work, what each one stops, and where the limits are.
Where course video leaks actually come from
Before you pick tools, look at the routes a video takes out of your hands. From easiest to hardest for the person leaking it:
- The file is reachable. A Google Drive link, an unlisted YouTube video or a direct
.mp4address. Anyone with the link can watch it and pass it on. - Account sharing. One student pays, and five friends log in with the same email and password.
- Download tools. Browser extensions and download managers that grab the video as it plays.
- Screen recording. Built-in recorders on laptops and phones.
- A phone camera pointed at the screen.
Each layer below closes one or more of these routes. None closes the last one.
Keeping the file out of reach
Private streaming instead of file links
Your video should never live at a public address. It sits on private storage, and the player only receives it after your server checks two things: is this student logged in, and has this student paid for this lesson?
This alone ends the most common leak, a link forwarded in a WhatsApp group. It is also why an unlisted YouTube video is not protection. Unlisted means "not shown in search", not "private". We compare the two approaches in own platform vs YouTube and WhatsApp groups.
Signed links that expire
Even a private video needs an address for the player to load. A signed URL makes that address useless outside the session that asked for it: it carries a cryptographic signature and an expiry time, issued for one student, one lesson and a short window. If it gets copied and posted somewhere, it stops working within minutes or hours, depending on the setting.
One caution: some systems also lock the link to the student's IP address. On mobile data in Egypt and the Gulf, IP addresses can change mid-lesson, so strict IP locking tends to punish honest students. Short expiry is usually the better lever.
HLS streaming with encryption
HLS splits a video into segments of a few seconds each, plus a playlist telling the player what comes next. The player can also switch quality as the connection changes, which helps students on weak mobile data.
With AES-128 encryption on top, each segment is encrypted and your server hands the key only to logged-in, authorised sessions. A basic download manager that grabs "the video" gets fragments it can't play.
Be realistic, though. The browser must decrypt the video to show it, so a skilled person can still capture the key during playback. HLS encryption raises the bar a lot. It is not a wall.
DRM for high-value courses
DRM is what large streaming services use. The three main systems are Widevine (Chrome, Android, Firefox, Edge), FairPlay (Safari and Apple devices) and PlayReady (Edge and Windows). The decryption key is handled inside a protected module in the browser or device, sometimes at hardware level, rather than by ordinary page code.
Most download tools stop working, and on many devices a screen recording shows a black rectangle instead of the video. Not on all of them, though: behaviour varies by platform, security level and phone model. Treat "blocks screen recording" as likely, not guaranteed.
DRM usually comes through a premium video hosting or player service that charges by usage. It pays off for expensive courses and large audiences, but may cost a new teacher with a few hundred students more than it saves. Test it on your students' real devices first.
Watermarks and device limits: the human layers
A moving watermark with the student's details
This is the layer teachers underestimate. The player shows the student's name and phone number over the video, semi-transparent, moving every few seconds so it can't be cropped out.
It blocks nothing technically. It changes behaviour: few students will share a recording with their own phone number across it, and if a clip appears on Telegram, you know which account it came from.
An honest detail: a watermark drawn by the player sits on top of the video, not inside the raw stream. That is fine. Encryption and DRM guard the raw stream, while the watermark covers what they can't: screen recording and phone cameras. Some premium services also offer forensic watermarking, embedding a unique mark in the video itself for each viewer, at a higher cost.
Device and session limits
Account sharing is quieter than downloading, and it can cost you more. The fixes are simple:
- Allow a set number of devices per account, often two: a phone and a laptop.
- Allow one active session at a time. A new login ends the old one.
- Let the admin reset devices when a student genuinely changes phones.
- Log every view. If one account watches from Cairo and Riyadh within the same hour, flag it.
Just don't lock out honest students. Two siblings sharing a family laptop is normal.
What each layer stops, side by side
| Layer | What it stops | What it doesn't stop | Effort and cost |
|---|---|---|---|
| Private streaming with login | Forwarded links, public access | Account sharing, recording | Basic, should be standard |
| Signed, expiring URLs | Copied links working later | Recording by a logged-in student | Low |
| HLS with AES-128 | Ordinary download managers | Skilled key capture, recording | Low to medium |
| DRM | Most download tools, screen recording on many devices | Phone camera | Medium to high, usage fees |
| Dynamic watermark | Nothing directly, but deters and traces leaks | A leaker with nothing to lose | Low |
| Device and session limits | Account sharing | One student recording alone | Low |
Common mistakes that make leaks easy
- Treating a hidden download button as protection. Disabling right-click stops nobody who knows browser developer tools or download extensions.
- Relying on "unlisted" links. Private means checked at the server, every time.
- Posting videos inside WhatsApp or Telegram groups. Once a file is on a phone, you have lost control of it.
- One shared password for a whole class. It will be in a group chat by the second week.
- Releasing the whole term on day one. Weekly releases limit what one leak can take and keep students engaged.
- Promising students the videos "can't be recorded". Tell them about the watermark instead. That message works.
A sensible setup for your size
If you are a teacher starting out, the baseline is private streaming, signed URLs, HLS encryption, a dynamic watermark and a device limit. That covers the leak routes you will actually meet, at a reasonable cost.
If you run an academy with thousands of students or charge premium prices, add DRM, viewing analytics and possibly forensic watermarking. Don't skip the non-technical side either: clear terms students accept at sign-up, parents who know the rules, and content refreshed each year so an old leak loses value. For the wider picture, see the complete guide to a teacher's e-learning platform.
Questions people ask
Can you make my videos impossible to record?
No. Nobody can stop a phone camera pointed at a screen. DRM can block screen recording on many devices, and a watermark makes any recording traceable. That combination is the honest maximum.
Will DRM work on all my students' devices?
It works on modern browsers and most phones, but older devices and some in-app browsers can have trouble. Test on the phones and laptops your students really use before switching it on for everyone.
Does protection make videos slower to load?
Not when done properly. HLS actually helps on weak connections, because the player drops to a lower quality instead of stopping to buffer.
Won't a watermark annoy students?
Keep it small, semi-transparent and slow-moving. Most students stop noticing it within minutes.
What should I do when I find a leak?
Identify the account from the watermark, suspend it, and contact the student or parent. Then report the content to the platform hosting it. Telegram, YouTube and Facebook all have copyright reporting processes.
Where to start
Ask your current setup one question: if a student copies the link to your lesson right now, what happens? If the answer is "it works for anyone", fix that first. Everything else builds on it. Video protection is also one part of a wider picture: see website security basics.
Content protection is part of every education platform Unilira builds, sized to your audience and budget. To see which layers make sense for your courses, book a short meeting and bring a list of where your videos live today.
