What Flow Looper actually does
Flow Looper aims at a very specific pain point: making a still image feel alive without turning it into a full animation project. The core idea centers on drawing a corridor with two splines, then pushing pixels down that corridor and looping the motion with a cross-fade.
That puts it in the same general family as classic flow mapping workflows, but packaged as a Fuse that lives where a lot of Resolve artists already spend their time: the Fusion page. If you ever built a “moving texture down a path” rig in node compositing, you already know the appeal. The win is not that the math exists. The win is that you can hand this to an editor who occasionally opens Fusion, and they might still come back with something usable.
Corridor animation, not a full 2D puppet show
Flow Looper focuses on motion constrained to a defined corridor. You draw the corridor, then the tool handles the continuous movement and looping behavior. The creator describes using several Flow Loopers on a single image to animate different regions. Oh, well.
That corridor constraint matters. It gives you a clear place to cheat motion into a still without needing to invent a full deformation rig. Think steam, fire, drifting energy, or anything that reads as “directional movement” once it repeats cleanly.
The approach also means you can stack multiple instances for layered motion: one corridor for flames, another for smoke, another for embers, each with its own behavior. That layering idea shows up directly in the shared example of a dragon breathing fire, animated by combining multiple instances. At some point, someone will try to animate a face with it. That is fine. That is also how plug-in comment sections become performance art.
Controls: speed shaping, noise, and edges
The feature set goes beyond “make pixels move” and into “make pixels move in a way that does not look like a conveyor belt.” Flow Looper includes start and end flow length controls intended to create acceleration-like behavior, or to keep one end static while the other moves. In practice, that kind of control usually helps sell motion that ramps in, ramps out, or stays anchored so the loop does not scream “tile.”
There is also a turbulence control that varies direction per pixel using noise so the motion does not stay perfectly linear along the corridor.That is the difference between “demo” and “could pass in a shot.” Even small directional variation can break the mechanical look. Edge fading controls aim to blend the flowing region on top of the image more naturally.
The Gumroad listing for Flow Looper shows a price of $12, Which is well worth it, if ou ever had to do something like this, and didn’t have the time for it.
Where this sits in real world Resolve workflows
If you live in editorial and only step into Fusion when the timeline needs “a little something,” Flow Looper looks designed to be that little something, but repeatable and controllable. If you live in Fusion, the tool still has a place, because corridor-constrained motion loops show up constantly in motion graphics and stylized comps. It is also a relatively friendly concept to hand off. “Here is the corridor, here is the direction, here is the loop” is a better brief than “make this still feel alive.”
For artists browsing the Tangenten tag archive, this is the second clear theme: Fuse tools that try to make Fusion friendlier without pretending nodes do not exist. Finally, check performance. Fusion can handle a lot, but it can also punish you for stacking clever tools on top of each other. Multiply a heavy operation by six instances and your interactive session becomes a slideshow. New tools and innovations should be tested before use in production, ideally on a clone of the job, not the only copy of the job.
