Welcome to the Netflix Partner Help Center. Have a question or need help with an issue? Send us a ticket and we'll help you to a resolution.

Production Assets: Data Management

Back-up / Data Verification

  • Two or more back-up copies of all original camera footage and audio with MD5 checksums must be generated and verified.
  • Archival of camera RAW footage, audio, and color information should maintain original directory structure, filenames, and metadata that were created by the cameras, audio recording devices, and dailies software to one or more of the following:
    • LTO-5, LTO-6 or LTO-7 tape in LTFS format
    • Netflix’s Content Hub (cloud-based)
    • High-speed RAID-protected external hard-drive
  • Footage must be QC’d for possible issues, referencing camera reports with scene/take information.
    • When Editorial proxies created from the original camera footage are available, the Editorial Team should provide sign off that all scene/takes have been transferred and accounted for.
  • Original camera card/media reformatting should only take place when the following steps are complete:
    • Multiple backups are complete and verified at another location
    • QC check of all picture and sound media 

Folder and File Naming 

Legal characters: [ a-z ], [ A-Z ], [ 0-9 ], [ . ], [ _ ], [ - ]

(ILLEGAL: spaces or any other symbols/characters)

Folder Structure

The following section applies to productions that are NOT using a Netflix API-integrated dailies solution. Production assets should be prepared by a DMT / DIT according to the following specification.

  • Root directory: PROJECT TITLE
  • Second-level directory: ASSET TYPE
    • OCF - Original Camera Files
    • WAV - Production Sound
    • LOOKS - Any on-set looks (.cdl, .ccc, .edl with CDLs)
    • LUT - Any LUTs used (.cube, .3dl)
    • ALE - Any ALEs generated, with all fields available, including CDL columns if applicable
    • PROXIES - Any proxies recorded or generated, whether at camera or through dailies processing (for editorial and/or review)
    • REPORTS - Any data or dailies reports generated
  • Third-level directory: SHOOT DAY & DATE
    • Example: Day_001_20161016
  • Fourth-level directory: CAMERA / SOUND ROLL

 OCF Example:

CHEFS_TABLE/

   OCF/

       Day_001_20161016/

           A001CGAL/

           A002DJEU/

Below this folder level, original folder structure and filenames must be maintained from camera or sound cards.

MD5 checksum manifest must accompany all original camera files, stored in the folder of files upon which the checksums are being run, at one of the following directory levels:

  • camera card
  • shoot day
  • root level

Production Assets Example: 

 orig_cam_ftg_folder_structure_20180321.png

Was this article helpful?
11 out of 11 found this helpful