Gemini stopped sampling video at a fixed frame rate and cut token use by up to 88%

Gemini 3.7 Flash, 3.6 Flash and 3.5 Flash-Lite now sample video adaptively rather than at a fixed frame rate. Google reports token use down as much as 88% against fixed-rate sampling, cost down as much as 66%, and accuracy up as much as 7%.

A fixed frame rate spends the same tokens on a static shot as on a cut.

The mechanism is a tool call, not a sampler. Google describes an agentic loop in which the model invokes an internal tool to load the relevant part of the video file, deciding what to watch, at what speed, and through which modality: frames, audio or transcript. The model seeks into the file the way a person scrubs a timeline, instead of being handed a fixed strip of stills.

Google does not publish what triggers a new sample point, so the decision logic is unauditable from outside, and these are its own figures on its own benchmark. That is a reason to measure your own workload rather than a reason to disbelieve the direction, because the billing change is already in effect whether or not the mechanism is disclosed.

Take the saving and re-measure. Google says the change needs no code edit and carries no separate fee, and the company puts 3.7 Flash ahead of the other two on overall quality.