Ask an instructor where their pirated course came from and the answer is almost never a hacker — it is a student, a phone, and the screen-record button that ships with every operating system. Web-based players cannot stop this; the browser is a hostile environment where anything rendered can be captured. Native apps change the physics: on iOS and Android, a player can register for screen-capture notifications and blank the video the instant recording begins; on Windows and macOS, OS-level protection flags the content so capture tools record a black rectangle where your lesson used to be. When screenshots are blocked at the system level — not with a polite "please don't" overlay — the casual recorder gets nothing, and casual recording is 95% of the leak.
What each platform actually blocks #
- iOS: screenshot and screen-recording detection blanks the video; the recording shows the player chrome and black content.
- Android: system-level capture protection plus emulator and root detection — rooted devices are refused playback entirely.
- Windows and macOS: OS content-protection flags defeat common capture software and hardware capture in supported configurations.
- Everywhere: per-student watermarks on each frame, so any leak that does happen traces to its source account.
Why watermarks still matter when blocking works #
Blocking and watermarking solve different halves of the problem, and the second half is the one people forget. OS-level blocking stops the phone pointed at the screen by software; it does not stop a camera pointed at the screen by hand. That is what per-student watermarks are for: when every rendered frame carries an invisible-but-forensic identifier tied to the watching account, a camera recording of a screen still incriminates its source. The deterrence math works at the population level — the rational student who knows frames are watermarked does not record, because the copy points back at them by construction. Watermarks convert piracy from an anonymous free-for-all into a signed confession waiting to be read.
The instructor-side takeaway is a procurement question, not a technical one. When you evaluate a platform, do the airplane test: open a lesson, start a native screen recording, and watch the result. If the video appears in the recording, your content is a screen-recording button away from a piracy forum, regardless of what the marketing page says about DRM. Protection that exists in the demo and not in the recording is decoration.
Piracy prevention is layered or it is fictional: encryption in transit, blocking in the OS, watermarks on the frame, expiry on the download.