Create protected video packages on Windows, control who can open them, bind playback to an authorized PC or USB drive, add viewer watermarks, and revoke leaked access after delivery.
Keep these four values distinct. Two stay with the publisher, one identifies a viewer's computer when PC binding is used, and only the Playback Password is sent to the viewer.
Keep this publisher key with the project record. It is used when creating playback passwords later.
Send this credential to the authorized viewer so the protected video can be opened.
Use the viewer's machine code when playback must be bound to one authorized Windows PC.
Use a recognizable label so the correct project and Encryption Key can be found later.
Add training videos, course recordings, premium media, product demonstrations, or supporting files that belong in the same protected delivery.
Choose how viewers will be authorized and keep the project information needed for future password creation.
Configure controlled playback settings that discourage copying, screen capture, virtual-machine misuse, and unapproved viewing environments.
Create the delivery file only after the encryption key, binding mode, watermark, access limits, and anti-copy rules are ready.
Use one password when approved viewers may open the package on more than one computer and device-specific control is unnecessary.
Simple shared accessCreate a playback password from one viewer's machine code so that password works with the authorized computer.
One computer, one passwordKeep playback associated with the selected USB delivery device when protected content should not be copied away and used normally elsewhere.
Controlled removable-media deliveryAssociate playback with the delivered optical media when training or licensed content is distributed on CD or DVD.
Controlled disc deliveryGenerate access for a viewer, customer, course group, or delivery batch after the protected package has been created.
The online blacklist lets the publisher disable a playback password without rebuilding every protected package already delivered.
Use the toolbox for player preparation, password tasks, project utilities, and other supporting work around protected delivery.
No. The publisher keeps the Encryption Key and uses it to create Playback Passwords for authorized viewers.
It is required when PC Binding is used to create a password for one authorized computer.
Yes. Add it to the configured online password blacklist so future verification rejects it.
Yes. USB Disk Binding and CD Binding are available for controlled physical-media delivery.
Yes. Watermark text can be included when creating access so protected playback carries visible viewer or project information.
The DRM project is created on Windows. Protected playback can be delivered through supported GiliSoft players for compatible desktop and mobile platforms, depending on the output and player selected.
It helps identify the right project and Encryption Key when new passwords or access changes are needed later.
Use Video DRM when access must remain controllable after delivery through device binding, watermarks, expiration, or password revocation. Use ordinary encryption when a fixed password is enough.
Prepare protected downloads for courses, clients, subscribers, and offline delivery.
Choose how viewers prove access and where the protected video may play.
Add traceability and discourage unauthorized recording or redistribution.
Apply DRM controls to paid lessons, internal training, and learner downloads.
Understand when DRM, encryption, or copy protection better matches the delivery model.
Use simpler password encryption when ongoing licensing and revocation are unnecessary.
Package content with playback passwords, binding rules, watermarking, blacklist control, and authorized viewing.
View Video DRM Protection
Enter your email address to get our latest newsletter