Master Files
High-resolution masters (ProRes, DNxHR, or camera originals) with clear filenames and checksum notes so archivists and post houses can verify authenticity and generate derivatives without quality loss.
A Media Video Package reduces disputes, speeds publishing, preserves licensing intent, and documents technical requirements for downstream platforms. It clarifies who may use the material, in which territories and media, and creates an auditable handoff record suitable for contract enforcement and long-term archival needs.
Typical organizations and roles that prepare or receive Media Video Packages include production companies, post houses, in-house marketing teams, and distribution partners.
Assigning and documenting responsibilities in the package helps each party meet technical, legal, and commercial obligations without back-and-forth clarification.
A commissioning organization that receives the package, confirms technical acceptance, and enforces permitted uses. The client should verify file integrity, review license scope and territorial limits, and confirm signed releases to avoid future copyright or personal-rights disputes.
The production company or creator responsible for delivering master and derivative files, metadata, and signed releases. The producer documents the license grant, delivery formats, and any retained rights or revenue-sharing obligations to protect against later claims.
High-resolution masters (ProRes, DNxHR, or camera originals) with clear filenames and checksum notes so archivists and post houses can verify authenticity and generate derivatives without quality loss.
Platform-ready versions (H.264, H.265, broadcast MXF) conforming to specified bitrates and resolutions, labeled for intended channels, reducing transcoding issues and ensuring consistent playback across destinations.
A delivery spec sheet describing codecs, frame rates, audio configuration, color profile, closed-caption format, and file naming conventions to prevent ingestion errors and speed platform acceptance.
Signed license agreement, usage schedule, territory and term clauses, and payment terms that define permitted exploitation modes and limit ambiguity about monetization and sublicensing.
Talent, location, and third-party release forms confirming consent for the agreed uses; missing releases pose the highest legal risk to distribution and monetization.
Timecode logs, captions/subtitles, thumbnail images, and descriptive metadata for searchability, accessibility compliance, and faster publishing workflows.
| Field | Configuration |
|---|---|
| File Integrity | Enable checksum verification on upload |
| Access Control | Limit downloads by role and IP range |
| Signature Flow | Set signer order and require attribution |
| Delivery Method | Select secure link or SFTP transfer |
Use common formats and integrate with secure platforms to avoid playback or ingestion issues and to preserve auditability.
Date for providing the complete package to client
Commonly 5–14 business days for technical and legal review
Time allowed for producer to fix accepted issues
Client signs acceptance; triggers final payment
Schedule transfer to DAM or cold storage after acceptance
Sign-off by director or client representative
Producer compiles files and documents
Recipient inspects technical and legal items
Client signs acceptance and assets archived
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies | Varies | Varies |
A mid-size services firm standardized electronic handoffs to reduce confusion between teams.
A small firm moved approvals and releases online to accelerate turnaround.