An infinite zoom is a sequence of images where each new picture lives inside the centre of the previous one. Play them back with a smooth scale and the camera seems to fall forward forever. It looks like magic, but it is really just a bit of geometry plus some careful prompt planning. Here is how I think about it.
1. Every frame is the previous frame, scaled down
Pick a zoom factor k, for example 2. Frame n+1 is pasted into the centre of frame n at 1/k of its width. During playback you scale the whole stack continuously from 1x to kx, and the moment you reach kx the inner frame fills the screen. That is the cut point, and if the inner frame really matches what the outer frame showed there, nobody notices it, because the picture on screen hasn't changed.
def frame_scale(t, k=2.0, frames=8):
"""t in [0, 1) over the whole video -> (frame index, scale of that frame)."""
pos = t * frames # which hand-off we are in
i = int(pos)
local = pos - i # 0..1 inside this hand-off
return i % frames, k ** local # geometric growth: constant zoom speed in log terms
The growth curve is worth a thought. Scale doesn't have to grow as k ** local, but it is a good default. Geometric (exponential) interpolation corresponds to a constant logarithmic zoom speed, and in practice it usually makes the perceived zoom speed more even. A linear ramp from 1 to k tends to feel like it speeds up and then slows down within each hand-off, so you may notice a little "bump" at every seam.
The growth curve is only one ingredient, though. Whether a seam actually looks smooth also depends on how well the frames are registered (aligned), on focus and sharpness across the boundary, and on how you blend or cut between the two frames.
2. The centre of each frame is reserved
Because the next scene is pasted into the middle 1/k of the frame, that area is effectively a window. When you describe a scene, plan what sits there:
- a doorway, a window, a picture frame, a pupil, a coin, a screen
- something with a clear edge, so the inner image has a natural border
- not text, and not a busy texture, which will show the seam
3. One connecting detail per hand-off
Write the whole path as one line before generating anything. Here is a chain that tells a small personal story:
travel group photo -> street in the photo -> café window on that street -> anniversary dinner table -> the same travel photo on the table
Each arrow is a hand-off, and each one needs a single object that exists in both scenes. For example: the yellow tram in the photo becomes the real tram on the street; the café's striped awning is visible in both the street and the window scene; the candle in the window is the candle on the dinner table; and the framed photo leaning on the vase is the photo you started with. Describe each shared object with the same words (colour, material, shape) in both prompts. That repetition is what makes two separately generated images read as one continuous shot.
4. Keep light and palette locked
Choose one light direction and three or four colours for the whole chain. Geometry can line up perfectly and the loop will still feel broken if frame 4 is warm sunset and frame 5 is cold noon.
5. Close the loop
For a true loop, the last scene's centre should contain the first scene. In the chain above, the last hand-off ends on the same travel photo we started with, standing on the dinner table, so it is a good idea to describe that photo in the first prompt too.
Be careful with i % frames in the function above: it only wraps the index back to frame 0. It doesn't make the loop visually seamless. For that, the inner window of the last frame has to match the first frame in:
- position (it sits where the first frame will be scaled from),
- scale (the same
1/kwindow), - orientation (no rotation or mirroring surprises), and
- content (the same photo, the same objects, the same light).
Also check focus and texture at the boundary. If the last frame's window is soft and the first frame is crisp, or one has film grain and the other doesn't, you will see the jump every time the loop restarts.
6. Test as thumbnails
Before final renders, lay all frames out as small thumbnails in a row. At that size you only see shapes and colours, which is exactly what the eye tracks during a fast zoom. Any frame whose central shape jumps is the one to regenerate.
Tooling
You can do all of this by hand: generate each frame with your favourite image model, then composite and animate with a short script (Pillow plus ffmpeg is enough). Whatever tools you use, the planning steps above are what decide whether the result feels seamless.
Want to turn a personal story into an explorable zoom artwork? Infinite Zoom Art lets you share the people, places, memories, and optional reference photos behind the story. The finished artwork opens through a shareable browser link, where viewers can explore its connected scenes or watch the zoom play automatically. The geometry above is a general way to reason about seamless transitions, not a description of the product's internal implementation.
For a concrete example, Love, in the Little Things is a fictional anniversary story told in twenty connected scenes; you can scroll or drag to zoom, or press play.
Summary
- Pick a zoom factor. Exponential (geometric) interpolation of scale usually makes perceived zoom speed more even than a linear ramp, but it isn't the only thing that matters.
- Reserve the centre of every frame for the next scene.
- One shared, identically described detail per hand-off.
- Fixed light direction and palette.
- Last frame contains the first, and the wrap-around matches in position, scale, orientation and content;
i % framesalone only wraps the index. - Check focus and texture at the seams, and check the chain as thumbnails.
If you try this, I'd love to see the path you wrote down.

Top comments (1)
Planning the geometric constraints before animating is what makes an infinite zoom feel intentional rather than like a transition hiding seams. A useful validation step is checking the final frame against the initial frame at the exact loop boundary, including scale, focal point, and any texture phase—not only the nested layout.