Content Hub: Upload Instructions

Netflix Content Hub:

Support Questions? Please SUBMIT A REQUEST 

Logging In

If you already have a Backlot account, you will be able to access the Content Hub at the URL above. If you do not yet have a Backlot account, ask your Netflix contact to help you in setting one up.

Once you have a Backlot login, accessing the Content Hub should bring you to the main view, which lists the projects you have access to. If you do not see any links to Netflix projects at this page, work with your Netflix contact to get set up with access to your projects.

Browsing My Projects

When clicking on a project, you should be taken to a screen like this, which shows a list of 'Buckets' and the assets that are contained in the Bucket:


A project is made up of Buckets, which are groupings of assets based on the production or post-production department creating assets. For example, the Footage bucket will contain all Dailies from a project, including web-playable proxies as well as Camera RAW, Sound Rolls, and LUTs.

List of Buckets 

  • Footage (API only)
  • Dailies Bins
  • Editorial
  • Sound Materials
  • VFX
  • Music
  • Final Sound (Request-based Fulfillment)
  • Picture Deliverables (DI assets) (Request-based Fulfillment)
  • Non-Distribution Masters (Request-based Fulfillment)

Browsing Assets

Selecting an individual bucket will take you to the Asset browse page, which you can use to find assets and filter by certain bucket-specific criteria.

Fulfill Requests (DI, Sound, and Non-Distribution Masters)

For a video tutorial of request fulfillment, click here

1. When in a project, you can use the Bucket filter to filter on specific buckets.

2. Click the Final Sound header to open the request view.

3. You can use the filter bar to narrow down to the just requests you want to deliver.

4. Select the requests to deliver by clicking the checkbox on the left side of the table, then press the Upload Assets button on the right-hand side of the page.

5. This will direct to the Source Delivery UI, which you can drag and drop files to upload.

6. Drag and drop the files to upload onto the drop-zone at the top of the page.

7. Associate the uploaded files to a specific request by selecting it in the Files to deliver dropdown.

8. For some request types, you may need to fill out additional metadata. In this case (a feature film), select the Reel that each file is associated with.

9. By selecting the requests to deliver, then clicking the DELIVER button, the Aspera transfer will be initiated.

10. On a successful upload, you will be redirected back to the Content Hub.

Bulk Upload Assets

Files can be archived with the Bulk Upload tool, which allows anyone to upload assets into the Content Hub from their desktop, via Aspera.

1. Drag and Drop files onto a bucket. In this case, dragging and dropping onto the Music bucket.

2. Tag files with the correct metadata and upload. NOTE: it is possible to edit the metadata for files in bulk by selecting multiple files and selecting Edit under the BULK ACTIONS menu. 

Asset States

Assets can be in the following states.

  • Failed Delivery
  • In Progress
  • Validating
  • Invalid
  • Delivered
  • Valid - the file was successfully uploaded

If an Asset is the
Valid state, then the asset has been uploaded into the Content Hub successfully:



Browser Compatibility

Content Hub is currently supported on the Google Chrome browser only.

Proxy Spec Compatibility

For best results, please upload H.264 video. The fast start flag must be set in order to provide playback in the Content Hub player. Your encoding software or NLE should be able to add the Fast Start flag. See below for an example `ffmpeg` command to add the fast start flag from the command line:

`ffmpeg -i <proxy file> -movflags faststart <output file>`

Debugging Aspera Transfers

Please follow the following steps if you get an error message while uploading:

1. Take a look at the transfer window to make sure that uploaded file names show up in transfer queue. If they are not present, it means that the Aspera transfer was not successful. Restart the browser and try the upload again.

2. If the Aspera transfer view shows failures, go to this help page to troubleshoot the Aspera Connect issue.

3. If you are not able to troubleshoot using steps 1 and 2, please email the support team with a screenshot of the error in Content Hub and all the Aspera connect logs.

How to see the Transfer view and Aspera connect logs:
Use this help page and follow the steps. To get the show view, go to Window -> Transfers in menu item of Aspera Connect app.

Frame Sequence ZIP Spec

Frame sequences (DPX stacks, camera rolls for file-per-frame clips) should be placed into the ZIP archive with a checksum.txt file that lists out all of the md5 checksum of the archive’s contents. The ZIP file should be a flat listing of files, and not include sub directories.


Brief install and run demonstration, runtime of 30 seconds:


If you have Python, please ensure it is 2.7+, otherwise download and install from

1. To install Netflix Packager (this step needs to be ran only once), open Command Prompt Shell (Windows, Mac OS) and type in:

pip install npack

Expected Output:

Collecting npack
Downloading npack-0.3.1-py2.py3-none-any.whl
Installing collected packages: npack
Successfully installed npack-0.3.1

Note: In some instances for Python3 pip is called pip3

2. To create the zip in Command Prompt Shell type in:

npack zip -s sourceFolder -t targetFolder -f

Expected Output (for sample command: npack zip -s testF -t . -f
_  _ ___ _____ ___ _    _____  __    
   | \| | __|_   _| __| |  |_ _\ \/ /    
   | .` | _|  | | | _|| |__ | | >  <     
   |_|\_|___| |_| |_| |____|___/_/\_\ version 0.3.1
                                         designed for ContentHub uploads only
                                         for questions please SUBMIT A REQUEST for Content Hub

2017-07-24 21:50:21.607398 | Identified 98783 files to checksum in testF
2017-07-24 21:50:28.879793 | Calculated 98783 checksums
2017-07-24 21:50:28.960537 | Completed writing to checksum.txt
2017-07-24 21:50:29.012010 | Initializing zip file ./
2017-07-24 21:50:57.356130 | Finished zip file ./
2017-07-24 21:50:57.377109 | Execution completed, took 38.04170322418213 seconds

3. Deliver the created sequence zip to Content Hub.

Was this article helpful?
9 out of 10 found this helpful