Faqs

Video Download and Screen Recording Protection

DynTube uses layered controls to make unauthorized access and reuse harder while keeping playback practical for approved viewers. The right combination depends on how viewers authenticate, where the video is embedded, and which protection features your plan and project support.

Build protection in layers

  • Use AES-128 encryption or DRM as the project's delivery-protection mode. These modes are configured as alternatives for a project rather than stacked together.
  • Restrict playback to approved website origins and keep the account-level encryption-key origin exemption off when origin enforcement is required.
  • Use signed, expiring playback links so copied URLs have a limited useful lifetime.
  • Add visible or dynamic watermarking to associate playback with a viewer or session when the feature is available.
  • Use Screen Shield where supported to add deterrence and controls for sensitive viewing workflows.

What does encrypted delivery protect?

Encryption keeps media segments from being useful without the required key or license. Signed links limit which playback requests are accepted and for how long. Origin controls limit approved website contexts. Together, these controls reduce casual link sharing, direct file access, and common downloader workflows.

Configuration matters. An empty origin list or an account setting that permits encryption keys on every origin can weaken the domain boundary you intended. Test a protected project from an approved domain and an unapproved domain before publishing broadly.

How does screen recording differ?

A viewer's device must display decoded frames for authorized playback. Software, another device, or a camera may capture what an authorized viewer can see, so online delivery cannot guarantee prevention of every screen recording. The practical response is deterrence, traceability, restricted access, and fast response—not a percentage promise.

Dynamic watermarking can place session or viewer information into the visible experience, while Screen Shield can strengthen supported viewing scenarios. Access control should also limit who receives a playable session in the first place. These measures complement encryption and DRM; they do not replace authentication or authorization in your application.

  1. Authenticate and authorize the viewer in your own site or application.
  2. Issue a short-lived signed playback URL after access is approved.
  3. Configure one project protection mode—AES-128 or DRM—based on the required device and plan support.
  4. Add a non-empty allowed-origin list and keep the key-origin exemption disabled for that boundary.
  5. Enable watermarking or Screen Shield when the content risk justifies it.
  6. Test approved and denied scenarios on the browsers and devices your audience uses.

How should I investigate a suspected leak?

Preserve the copied URL, page, time, account, and watermark evidence without publishing secrets. Rotate exposed signing credentials if appropriate, shorten future link expiry, review origin configuration, and remove access for the affected viewer or integration. Contact support with identifiers rather than raw credentials.

  • Video Playback Issues
  • Video Options
  • Video Player

Something missing or wrong here? Tell us and we will correct it. New to DynTube? Start with uploading and embedding.