Google Moves AI Video Developers Beyond Veo 3.1 Preview
Google has closed the Veo 3.1 preview models in its Gemini API and directed developers towards Gemini Omni Flash.
Google has changed the options available to developers building AI video tools, shutting down several Veo 3.1 Preview models through its Gemini API on 22 October 2026. The change matters for creative teams that connect directly to Google's systems to generate scenes, test concepts or build filmmaking applications.
It does not mean that all Veo-related products or consumer video features have disappeared. Google's published documentation identifies specific preview API model versions that reached their retirement date.
Which video models were retired?
Google's deprecation schedule lists three affected versions: Veo 3.1 Generate Preview, Veo 3.1 Fast Generate Preview and Veo 3.1 Lite Generate Preview. Developers still using those model identifiers need to update their workflows to avoid interruption.
The company recommends Gemini Omni Flash, with the model identifier gemini-omni-1.1-flash, or generally available video models offered through the Gemini Enterprise Agent Platform. The migration advice is included in Google's video-generation guide and its separate model deprecation schedule.
What changes for AI filmmakers?
Google describes Gemini Omni Flash as a multimodal system that can work with text, images, audio and video. It supports conversational editing, allowing people to describe changes across multiple interactions instead of starting over with an entirely new prompt for every adjustment.
Those capabilities are relevant to filmmakers who struggle with consistent characters, matching shots and changes to a scene after its first version. However, Google's descriptions are product claims, and results can still vary depending on the material and workflow.
Should creators change anything?
Someone using a consumer-facing video app may not be directly affected. The immediate issue concerns applications connected to the retired API model identifiers, so developers should check their own integrations and migration instructions.
The change illustrates a practical challenge for independent AI series: production software can evolve while an ongoing story is still being made. Alongside writing and directing, creators increasingly need to manage the technical tools on which their projects depend.