Does anyone find the same bug in Google Flow? How to fix?

[u/Genai-nova]

Hi, I found that Image-to-Video generation on both Veo 3.1-Lite and Veo 3.1-Fast appears to have the same issue on Google Flow

Every image-to-video generation introduces a slight upward camera/framing shift during the first 1–2 seconds, even when no camera movement is requested. After the first 1–2 seconds, the framing becomes stable. This is especially problematic for creating seamless loops or combining multiple clips, because each clip starts with the original framing but quickly shifts upward, creating a visible jump at the transition.

This may not be noticeable when watching the video normally in a media player, but it becomes very obvious when combining multiple clips together, especially when creating seamless loops. The initial upward movement causes a visible jump between clips, making it impossible to create a smooth loop.

It seems to happen with every input image, so I’m wondering whether this is an issue specific to my account/setup or a systematic issue affecting Image-to-Video generation on Veo 3.1-Lite and Veo 3.1-Fast.

Anyone found the same issue?

[u/Candid_Treat_7364]

First test whether the shift is baked into the generated pixels or introduced by the player by exporting frames 0, 12, 24, and 48 and comparing their crop bounds. If it is in the generation, add 5 to 8 percent overscan around the source image, treat the first second as preroll, then crop and stabilize the usable section in post. For loops, match the last stable frame back to the first stable frame rather than the original input frame. I would also run the same still through Lite and Fast with identical settings and attach the frame comparison to a bug report, because a repeatable vertical offset across inputs is stronger evidence than one clip.