Loop Interpolate:
LoopInterpolate smooths looping animations by generating additional frames between existing frames, including the transition from the end of the clip back to its beginning. Unlike interpolation that only processes a sequence from start to finish, it also treats the last and first frames as neighbors, helping avoid an abrupt jump when playback repeats. It uses either FILM or RIFE 4.9 through the ComfyUI-Frame-Interpolation extension to estimate intermediate images. Internally, it temporarily repeats the first frame at the end of the sequence, interpolates the extended clip, and removes the final duplicate so the animation can repeat without an unnecessary extra copy of its opening frame. It also calculates the corresponding playback frame rate so that smoother motion can retain the original animation’s duration. This is useful for animated artwork, repeating motion studies, and short looping clips, although the quality of the closing transition still depends on how naturally the original ending connects to the beginning.
Loop Interpolate Input Parameters:
images
The required IMAGE batch containing your animation’s frames in playback order. The node treats the entire batch as one looping sequence, including the transition from its last frame back to its first. These should therefore be consecutive frames of the same animation rather than unrelated pictures or separate clips. The node adds intermediate frames throughout this sequence to make motion appear smoother; it does not generate a new animation from a text description or work on latent representations. Use a nonempty batch of consistently sized images, preferably with a visually plausible connection between the ending and beginning. No default value or numerical minimum or maximum is specified for this input.
method
The required selection of the interpolation engine, with the options FILM and RIFE 4.9. FILM calls the external FILM VFI node using the checkpoint film_net_fp32.pt. RIFE 4.9 calls the external RIFE VFI node using rife49.pth and explicitly enables both fast_mode and ensemble. These additional RIFE settings are fixed by LoopInterpolate rather than exposed as separate controls. Your choice determines which model estimates the new frames and can affect the appearance of moving objects, fine details, and transitions. The selected engine must be registered by ComfyUI-Frame-Interpolation, and its checkpoint must be available to that extension. No explicit default is declared in the source; FILM is listed first in the available options. There is no numerical minimum or maximum.
multiplier
The required integer controlling how much the frame count and playback frame rate increase, with a default of 2, a minimum of 2, and a maximum of 8. A value of 2 requests doubled frame density, normally inserting one intermediate frame into each interval, including the interval from the last frame back to the first. A value of 4 normally inserts three intermediate frames per interval. For a batch of N frames, the expected result under the supported engines’ standard interpolation behavior is N multiplied by this value. Higher settings can make motion appear smoother, but they require more generated frames and generally increase processing time and memory requirements. They also provide more opportunities for visible interpolation artifacts when the source motion is ambiguous. This setting increases temporal smoothness, not image resolution.
fps
The required floating-point value representing the original clip’s playback rate in frames per second. Its default is 24.0, its minimum is 1.0, its maximum is 240.0, and its interface step is 1.0. The node multiplies this value by multiplier to calculate the returned playback rate. For example, 24.0 with a multiplier of 2 returns 48.0. This calculation lets you play the larger frame sequence over the same duration as the original, provided your video-saving node uses the returned rate. The value is not passed to the interpolation engine, so changing it does not change which intermediate images are generated; it changes only the returned playback-rate value. Set it to your source animation’s intended frame rate rather than your desired final frame rate.
Loop Interpolate Output Parameters:
IMAGE
An IMAGE batch containing the interpolated looping sequence, with additional frames between successive original frames and across the transition from the last frame back to the first. The temporary duplicate of the opening frame is removed from the end, while the generated frames leading back toward that opening image remain. This avoids adding an extra repeated endpoint when you play the sequence on a loop. Under the supported engines’ standard interpolation behavior, the output contains the original frame count multiplied by multiplier; for example, a 24-frame batch processed with a multiplier of 2 produces 48 frames. This output is a sequence of images rather than an encoded video file, so connect it to an appropriate preview or video-saving node. A smooth-looking loop is not guaranteed if the source ending and beginning are substantially different.
fps
A FLOAT containing the calculated playback frame rate, equal to the input fps multiplied by multiplier. For example, an input rate of 24.0 and a multiplier of 4 produce 96.0. Use this value as the playback rate when assembling the returned image batch into a video if you want to preserve the original animation’s duration. If you instead save the expanded sequence at the original frame rate, playback will be slower and the clip will be longer. The output is a numerical value only; LoopInterpolate does not encode the video or automatically configure another node’s frame-rate setting. Its calculated value can exceed 240.0 because the 240.0 limit applies to the input, not to this multiplication result.
Loop Interpolate Usage Tips:
- Install ComfyUI-Frame-Interpolation and restart ComfyUI before using this node. LoopInterpolate specifically looks for its FILM VFI or RIFE VFI registration; the presence of another interpolation node, including a built-in one, does not satisfy that check.
- Start with
multiplierset to 2. This provides a practical first test of smoother motion without immediately producing the much larger frame batches associated with settings such as 6 or 8. - Set
fpsto the source clip’s playback rate and use the returnedfpswhen saving the result. For example, 24 source frames at 24 fps become an expected 48 frames at 48 fps with a multiplier of 2, preserving a one-second loop. - Preview the closing transition over several repeats. Interpolation can bridge the ending and beginning, but substantially different poses, camera positions, lighting, or compositions may still produce warping or an obvious transition.
- Compare FILM and RIFE 4.9 on a short representative sequence before processing a large batch. Choose based on the result for your artwork rather than assuming either method will always handle every kind of motion better.
- If processing is too demanding, lower
multiplieror reduce the source image resolution. Test with a shorter loop when evaluating settings, while remembering that changing the clip’s endpoints also changes its closing transition. - Keep separate animations in separate batches. The node interprets every adjacent pair as part of one continuous sequence and will also interpolate from the final image of the entire batch back to its first image.
- Do not append an extra copy of the first frame solely to close the loop before this node. LoopInterpolate performs that step internally; an already duplicated endpoint can introduce an unwanted repeated-frame pause.
Loop Interpolate Common Errors and Solutions:
Loop Interpolate needs ComfyUI-Frame-Interpolation installed
- Explanation: This is the exact RuntimeError raised when the selected external node, FILM VFI or RIFE VFI, is missing from ComfyUI’s node registry. The extension may be absent, may have failed to load, or may not provide the selected engine.
- Solution: Install or repair ComfyUI-Frame-Interpolation, follow its dependency instructions, and restart ComfyUI. If it is already installed, check the startup console for import failures and confirm that the selected FILM VFI or RIFE VFI node is available.
Checkpoint missing or unable to load — dependency error text varies
- Explanation: The selected engine needs
film_net_fp32.ptfor FILM orrife49.pthfor RIFE 4.9. If that checkpoint is unavailable or cannot be read, the external interpolation node may report a missing-file, download, or model-loading error. LoopInterpolate itself does not define the checkpoint download or storage procedure. - Solution: Follow ComfyUI-Frame-Interpolation’s instructions for obtaining and installing the selected checkpoint. If its download process fails, check connectivity and write permissions; if loading fails after download, check whether the file is incomplete or damaged.
CUDA out of memory or another device-memory allocation error
- Explanation: Interpolating high-resolution frames or using a large multiplier can exceed the memory available to the selected engine. The exact message depends on your hardware and the external interpolation implementation.
- Solution: Reduce
multipliertoward 2, lower image resolution, and release other memory-heavy workloads. Use a smaller test sequence to verify the workflow before processing the full animation. LoopInterpolate does not expose a batch-size or memory-management control.
Invalid method selection — possible KeyError
- Explanation: The implementation directly looks up
methodin a dictionary that contains only FILM and RIFE 4.9. An unsupported value supplied through an API or altered workflow can therefore produce a KeyError, although the normal dropdown restricts you to valid choices. - Solution: Select FILM or RIFE 4.9 using the node’s dropdown. For API requests or manually edited workflows, match the option’s spelling and spacing exactly.
Invalid or empty image batch — error text varies
- Explanation: The node expects a valid, nonempty ComfyUI IMAGE batch. Empty data, an incompatible data type, or incorrectly prepared image dimensions can fail during preparation or inside the external interpolation engine. LoopInterpolate does not include a dedicated input-validation message for these cases.
- Solution: Connect an IMAGE output that contains actual animation frames, confirm that the batch is not empty, and ensure its frames have consistent dimensions. Do not connect latent data, video filenames, or other non-IMAGE values in place of decoded frames.
Playback is too slow or the clip duration changes — no exception message
- Explanation: This usually happens when the expanded image sequence is saved at the original frame rate instead of the multiplied frame rate returned by the node. More frames at the same playback rate create a longer clip.
- Solution: Connect the returned
fpsto your video-saving node’s frame-rate input where supported, or manually enter the same calculated value. Confirm that the inputfpsdescribes the original animation’s intended playback rate.
The loop still jumps, warps, or pauses at the boundary — no exception message
- Explanation: Processing the last-to-first transition does not guarantee that two very different endpoint images will connect naturally. Interpolation can produce distorted intermediate images when motion is unclear, and an opening frame already duplicated at the end of the source can create a repeated-frame pause.
- Solution: Inspect the source endpoints, remove an unnecessary duplicate closing frame, and choose a loop segment whose ending naturally leads into its beginning. Compare FILM and RIFE 4.9, and test at a multiplier of 2 before increasing the setting; generating more intermediate frames does not repair an inherently mismatched transition.
