Screen Shield: try recording it yourself

Screen Shield is an animated, low-opacity pattern the DynTube player draws over video during playback. Its purpose is to make captured copies show visible artefacts that are less prominent during normal viewing. Record the sample below with the tools and devices relevant to your audience so you can judge that trade-off directly.

The result varies with footage, viewer devices, display settings and capture software. A representative test helps you decide where Screen Shield adds useful deterrence while preserving the experience of paying or authorised viewers.

The sample

This video is playing with Screen Shield on. Screen record this video with the recorder you use for testing, then compare the saved recording with what you are watching now.

How to run the test so it means something

1. Watch the sample first at your normal size and brightness, and note whether the overlay bothers you as a viewer. That cost is real and it is the other half of the decision.
2. Record it with the capture path you are actually worried about — the built-in OS recorder, a meeting tool's screen share, or the third-party app your audience is likely to reach for.
3. Record at the frame rate and resolution that tool defaults to, then try a second frame rate. Capture settings can change what you get back, so hold them steady when you compare runs.
4. Repeat on a second device class. A laptop, a phone and a TV app are three different rendering and capture stories.
5. Play the recording back at full size, not in a thumbnail. Artefacts that dominate at 1080p can disappear in a preview pane.

How to read the result

Compare the quality of the saved capture with the live playback and answer four practical questions:

• Is the recording noticeably worse than the live playback on this device and this tool?
• Would that degradation actually discourage someone from passing the copy on, given what your content is?
• Does the overlay cost your paying viewers anything they would complain about?
• On which content and device combinations is the capture difference strong enough to justify enabling the overlay?

Build a layered protection setup

Use Screen Shield for capture deterrence alongside controls for delivery, access and attribution:

• Encrypted HLS delivery removes the stable single file a download manager looks for. That is a different problem from screen capture, and a different setting.
• Login protection and subscription plans tie playback to a viewer you authorised. Allowed domains add a further check when a domain allowlist is configured and no account-level encryption-key exemption applies.
• Dynamic and IP watermarking can support attribution — but only when the feature is enabled and entitled and configured on the video. Dynamic watermarking needs viewer identity or user text to render; IP watermarking needs the client IP address.
• Extra Security is a separate entitled option for videos using HLS encryption. It routes the player's encrypted-HLS key requests through a DynTube player-specific validation path.
• Studio multi-DRM supports Widevine, PlayReady and FairPlay through a separately arranged protection path.

Availability

Screen Shield is a plan feature included in current Pro and Enterprise defaults, while account configuration can vary. The player uses the effective resolved settings for the video and the account entitlement, so confirm the overlay on a rendered representative video before applying it across a library.

Run the test above, record the device and capture conditions, and use that evidence to choose where Screen Shield belongs in your protection policy.