Skip to content

SYSTEM Cited by 1 source

Netflix Footage Ingest

Footage Ingest is the drive-plug-in gateway application of Netflix's Media Production Suite. It is the on-ramp to the centralised cloud media library that every other MPS tool reads from.

When a physical drive arrives at a Netflix ingest centre, an operator plugs it into a workstation and opens the Footage Ingest application. From Netflix TechBlog 2025-04-01:

"Once a drive has been plugged in and our Netflix Footage Ingest application is opened, a validation is run, ensuring all expected media from set is on the drive. After media has been uploaded and checksums are run validating media integrity, all media is inspected, metadata is extracted, and assets are created for viewing/sharing/downloading with playable proxies. All media is then automatically backed up to a second tier of cloud-based storage for the final archive."

Pipeline stages

Drive plugged in at ingest centre
        │
        ▼
(1) Manifest validation        — all expected media from set present?
        │
        ▼
(2) Upload                     — OCF + OSF to Netflix cloud
        │                         over Open Connect backhaul → AWS
        ▼
(3) Checksum validation        — verifies media integrity end-to-end
        │                         ASC MHL is the standard Netflix leans on
        ▼
(4) Inspection + metadata      — technical inspection; metadata extraction
        │                         into the asset record
        ▼
(5) Proxy generation           — playable proxies for Media Library
        │                         viewing / sharing / downloading
        ▼
(6) Tier-2 archive             — automatic backup to second-tier
                                  cloud storage (final archive)

Every subsequent MPS tool — Dailies, Remote Workstations, VFX Pulls, Conform Pulls, Media Downloader — reads from the library populated by this pipeline. That's why the whole suite is structured around "opt in to Footage Ingest first" — it's the only path to the shared asset namespace.

Observability

Content Hub exposes a Footage Ingest dashboard over the activity stream produced by the pipeline, so any stakeholder (post supervisor, VFX editor, DI facility) can see drive-arrival → validation → upload → archive status without needing to call a vendor. This dashboard is the concrete form of the centralised library pattern's secondary benefit: the library is also the operational log.

Standards dependency

File-management + verification leans on the ASC MHL (Media Hash List) standard — see concepts/open-media-standards. This is what makes checksum validation (stage 3) interoperable with everything upstream (on-set capture tooling, camera cards) and downstream (vendors pulling assets back out).

Ingest centres

Netflix is "rolling out" global ingest centres — physical sites with high-speed internet connectivity where production drives can be dropped off. Per the 2025-04-01 post: "within a matter of hours, all original camera files are uploaded into the Netflix ecosystem." The ingest-centre footprint, bandwidth tier, and exact locations are not publicly enumerated.

Stub caveats

The 2025-04-01 post does not publish:

  • Concurrency / throughput of the ingest pipeline.
  • Failure-mode handling (partial-upload recovery, checksum mismatch, missing-manifest resolution).
  • Ingest-centre count or per-centre bandwidth.
  • Whether tier-2 archive is S3 Glacier, S3 Deep Archive, or a Netflix-proprietary tier.
  • Proxy-generation details (codec, resolution ladders, compute tier).

Expand this page if Netflix publishes a deep-dive on Footage Ingest internals.

Seen in

Last updated · 319 distilled / 1,201 read