Research · verified against primary sources 07/24/2026

Fighting screenshots, without watermarks.

The bottom line: no browser can block or even detect an OS screenshot. Not ours, not Netflix's, not anyone's. The one guarantee is Apple-DRM video in Safari, which turns screenshots black. Chrome often shows black too, but only as a GPU side effect that one settings toggle defeats — Netflix caps Chrome at 720p because they know it. Both apply to one-way encrypted streams, not live two-way calls. On the web you deter and trace. In native apps you can genuinely block (Android) and detect in real time (iOS). Nothing anywhere stops a second phone filming the screen.

What each technique really does

Technique	Web Safari	Web Chrome	iOS app	Android app
Our WebRTC video today	Nothing	Nothing	n/a	n/a
JS "screenshot detection" scripts	Snake oil	Snake oil	n/a	n/a
DRM playback (FairPlay / Widevine)	BLOCKS — hardware DRM, guaranteed black	Often black by GPU side effect — defeated by turning off hardware acceleration; Netflix caps Chrome at 720p for exactly this reason	n/a	n/a
DRM piped into live WebRTC (castLabs)	Blocks · one-way only, heavy build	Nothing	n/a	n/a
Android FLAG_SECURE	n/a	n/a	n/a	TRULY BLOCKS shots, recording, casting
iOS capture detection	n/a	n/a	DETECTS — blank video live, log screenshots, notify, ban	n/a
iOS secure-layer trick (Confide-style black shots)	n/a	n/a	Works today · Apple says unsupported, may break	n/a
Invisible forensic marking (in the pixels)	TRACES	TRACES	TRACES	TRACES
ToS + DMCA takedown machine	DETERS + REMOVES — what the whole creator economy actually runs on

What the comparables actually do

OnlyFans: no screenshot blocking on web at all. Disabled right-click, DRM on files, and an industrial DMCA takedown pipeline (Rulta, BranditScan). That's the whole defense.
Cameo Live: "recording blocked" — via their native app, not the web. The one comp claim we couldn't fully verify technically.
Snapchat: blocks nothing; detects and tells the other person. Social punishment, native apps only. Snapchat WEB has no detection at all.
Zoom: admits it cannot block screenshots; its answer is visible watermarks (rejected here).
Netflix: black screenshots only where hardware DRM exists (Safari, native apps). On desktop Chrome they accept capture and just cap quality at 720p. If Netflix can't block Chrome, nobody can.
Signal / Telegram / banks: FLAG_SECURE on Android (true block), detection or secure-layer on iOS. All native.

Snake oil to refuse

Any vendor claiming "blocks screen capture on web": true only in Safari via Apple DRM. Their own fine print admits 0% on Chrome/Mac.
JS screenshot-detection packages: there is no browser event for OS screenshots. Period.
HDCP: protects HDMI cables, not screenshots.
CSS/DOM "invisible watermarks": not in the actual pixels, stripped trivially. Forensic marking only counts if baked into frames at the sender.

The plan (ranked, no visible watermarks)

1 · Legal spine (days): anti-capture + right-of-publicity terms, a pre-call line — "capturing this call is prohibited and traceable" — and a DMCA agent + takedown workflow. Right of publicity is unusually strong for celebrity faces: stronger than copyright alone.
2 · Screenshot-hostile UX (days): blank the star's video when the fan's window loses focus or switches apps, disable picture-in-picture and casting. Stops the casual, not the determined.
3 · Invisible forensic marking (1–2 weeks): imperceptible per-session pixel signature baked into the star's outgoing video at their device — survives screenshots, re-encoding, even a phone filming the screen (to a degree). A leak identifies the leaker's account. Nothing visible on screen.
4 · Native apps (later): Android = FLAG_SECURE, real blocking, one line of code. iOS = real-time capture detection (blank the video the instant recording starts, log screenshots, notify the star, ban repeat offenders) + the Confide-style black-screenshot layer as best-effort.
5 · Only if leaks become a real business problem: the Safari DRM route for fan-side video — the sole true web blocking that exists. Heavy build, Safari-only, judged not worth it until proven necessary.

What we can honestly tell talent

"Capturing calls is prohibited and traceable. Our apps block screenshots outright; on the web every call is invisibly marked to the viewer's account, and captured content gets taken down under DMCA." Never promise screenshots are impossible on the web — desktop Chrome disproves it in one keypress, and the talent deserves the straight version.