Los Angeles, and a warning from the vendor

At SIGGRAPH in Los Angeles on 20 July 2026, Nvidia announced the Synthetic Video Detector, a microservice in its AI for Media platform that analyses footage frame by frame and estimates whether it was generated. Rev Lebaredian, the company's vice president of physical AI simulation, framed the stakes plainly, saying that if we cannot tell the difference between a synthetic video and a real one, it can erode public trust.

The more useful sentence came further down the announcement, and it came from Nvidia rather than from a critic. Rather than replacing established verification practices, the company wrote, the microservice provides another signal for time-sensitive decisions. That is a vendor telling you in advance not to treat its output as proof. It is worth taking literally.

Three numbers, and the lowest one is yours

Nvidia published accuracy at three levels of compression. In its own testing the model reached up to 92 percent on uncompressed video, 87 percent at 15 percent compression and 82 percent at 50 percent compression. The company also reported an area under the curve of 0.9614 and accuracy of 0.9453 on an internal test set. Performance is quick enough for live use, at 1080p in as little as 22 milliseconds on RTX systems and roughly 30 milliseconds on L40 accelerators.

Now consider which of those three numbers describes your situation. Video that arrives at a European business has been through delivery encoding, and usually through a platform that re-encoded it again. A clip forwarded through a messaging app, pulled from a social feed or captured off a video call is not uncompressed footage. The 92 percent belongs to a laboratory condition. The number that describes an ordinary working day is the 82.

The product does not accept the format its headline uses

Nvidia's technical documentation states that the service takes H.264 encoded MP4 video, decoded on the GPU into frames. H.264 is a compressed format. So the input the product actually accepts is compressed by definition, while the accuracy figure leading the announcement was measured on uncompressed video. Those two facts sit on two different Nvidia pages and neither contradicts the other, but read together they tell you that the headline number describes an input the service does not take.

The same documentation describes the model's signals as resilient to common video transformations including compression and re-encoding. Resilient is an adjective. The announcement supplies the arithmetic behind it, which is a fall of ten percentage points between uncompressed footage and material at 50 percent compression. When a vendor gives you both a reassuring word and its own measurements, use the measurements.

It answers generation, not truth

The detector estimates whether pixels were synthesised. It does not assess whether the events on screen occurred. A real camera pointed at a staged scene, a genuine recording with a false caption, or authentic footage from the wrong year all pass as real, because in the only sense the model measures, they are. The architecture is an ensemble of DINOv2 and DINOv3 vision transformers, and it returns a single probability between zero and one for the whole video, with optional scores per frame.

That gap matters most in the cases businesses actually face. The invoice redirected after a convincing video call, the insurance claim supported by footage, the identity check during remote onboarding: in each, the question is whether the thing depicted is real, not merely whether a model drew the pixels. A high confidence score of genuine is compatible with a completely fraudulent transaction.

What to establish before it sits in front of your ingest

Wowza is embedding the service through its Video Intelligence Framework, which reaches more than 35 000 deployments across over 170 countries, so this will arrive inside infrastructure many companies already run rather than as a separate purchase. Before it does, settle three things. Ask for measured accuracy at the compression level your own footage carries. Ask what probability threshold triggers an action, since Nvidia publishes no guidance on false positives. Then ask who reviews the flags, because at scale a rate near one in five on compressed material generates work rather than answers.

Keep the mechanisms separate in your own planning too. Marking content at the point of creation and classifying it after the fact are different things: provenance travels with the file if nothing strips it, while a classifier is guessing from the pixels every time. A detector is a reasonable second signal. It is not a control you can put your name against, and Nvidia has said as much.