The Amount Netflix Offered to Cover Was $800

$800 and $105 Million

Producer Simon Afram and his company Op Fortitude sued Netflix on July 30 in the U.S. District Court for the Central District of California. The film is Fortitude, a World War II thriller starring Nicolas Cage. According to the complaint, the production hand delivered the film’s master copy on a hard drive to Netflix on June 15, for an internal screening and a distribution evaluation.

The drive vanished from a desk at Netflix’s Los Angeles office. The complaint quotes a Netflix employee saying someone took a good amount of drives from their desks. The producers say it took nine days to be told, and that Netflix offered to cover roughly $800, the cost of replacing the drive. That drive held the only master of a film with $45 million of production money in it. The suit asks for $105 million and pleads breach of contract and negligence.

All of that is the plaintiffs’ account. No court has ruled, Netflix has not filed its answer publicly, and the terms attached to the handoff have not been disclosed.

The Master Moved Unencrypted

The line founders should read as their own problem is not the damages figure. It sits just above it. The copy was reportedly delivered unencrypted. A finished, unreleased film travelled on physical media, with no lock on it, into someone else’s building.

Notice what the producers claim the harm is. Not a confirmed leak, but the possibility of one. Their argument is that distributors will not buy a film that could surface online at any moment. Value drops without anyone proving the file ever moved, and that property is not unique to entertainment. Unpublished model weights, a source snapshot handed to an enterprise customer, a raw dataset shared during diligence all lose value the same way, on the mere fact that they could be circulating.

What the Contract Priced

Look at where the $800 came from. It prices the medium, not the content. It is the market rate for one drive.

That the receiving party could reach for that number at all suggests the paperwork between the two companies may not have described the deposit in units of the asset. Absent that, compensation for a loss starts at the price of the object, and anything above it has to be proven by the party claiming harm. That is precisely why $105 million now exists in the form of a lawsuit. Written into the contract beforehand, it would have been an invoice instead.

Startups walk into this structure more often than they expect: handing training data to a large company for a proof of concept, uploading an entire codebase to a data room during acquisition diligence, shipping source assets to an outside studio. The bigger the counterparty, the more likely you sign their standard paper, and that paper usually caps the recipient’s liability low.

Three Things to Settle Before You Hand It Over

Write down what is being transferred in units of the asset. Not “one hard drive” but “one complete unreleased master, production cost X.” In a dispute, that single line moves the starting point of the argument.

Put encryption and custody into the transfer terms: whether it is encrypted, who may open it, when it must be returned or destroyed, and how fast you must be told if something goes wrong. Nine days became a talking point most likely because no notification window existed.

Stop treating physical media as the default. Deliver through a path that logs access and lets you revoke it, and when something disappears you at least keep a record of who opened it and when. A drive on a desk carries no such record.

The question the court actually has to answer narrows to one thing: how do you price an unreleased work when no leak has been confirmed? By the $45 million spent making it, by the distribution revenue it expected, or by the cost of the drive, as Netflix reportedly proposed. Wherever that math lands, it becomes the reference for every contract that hands the same kind of object to somebody else.