Why does the workflow process every frame if I only need the transition?

To maintain temporal consistency. Running inference across the full frame range helps keep the look stable and reduces popping before and after the handoff. If you need faster runs, trim your inputs to just the necessary ranges, reduce resolution/FPS, or shorten the clips.

How can I reduce artifacts like flicker or warping at the transition?

Try increasing the transition duration, lowering the LoRA influence/strength, and locking the seed for repeatable results. Place the cut around frames with similar composition (camera angle, subject size), and ensure both inputs share the same resolution and FPS.

What GPU/VRAM do I need?

Requirements scale with resolution, clip length, and transition duration. Start with short clips at a modest resolution to gauge performance. Longer sequences or HD+ resolutions benefit from GPUs with more VRAM; if you hit limits, downscale or shorten the frame ranges.

Does the output include audio?

The SaveVideo node outputs a silent video. If you need audio, export the video and reattach audio from one of the source clips (or a music track) in your video editor.

Seamless Video Transitions - LTX 2.3 FLW LoRA

This ComfyUI workflow creates a seamless, learned transition between two input clips using an LTX 2.3 FLW LoRA. You feed one video into each LoadVideo node, and a dedicated transition node (UUID: 63482e7d-23c9-4396-a7a2-cd4ca2316eac) synthesizes a smooth handoff from the end of the first shot to the start of the second. The SaveVideo node then assembles the processed frames into a single output clip. A built-in MarkdownNote provides an at-a-glance guide to recommended settings and practical tips.

Technically, the workflow performs diffusion-based video-to-video generation guided by the LTX 2.3 FLW LoRA to harmonize color, texture, and motion across the cut. For temporal consistency, inference runs over the full frame range (not just the transition window). That design keeps the look stable across the entire sequence but also means longer clips and higher resolutions will increase runtime and VRAM use. You’ll typically set the in/out ranges for each source clip, define a transition length, and adjust the LoRA influence/strength and seed in the transition node. SaveVideo controls the output frame rate and file name for export.

API

Use this workflow from code

Every Comfy workflow is a JSON graph. The payload below is this workflow, exactly as ComfyUI runs it — fetch it from the URL, keep it in version control, or load it in ComfyUI and run it node by node.

GET https://comfy.org/workflows/download/5b94a8f404fa.json

Fetching workflow JSON…

Run it from Python or TypeScript with the Comfy SDK. The same code targets Comfy Cloud or a ComfyUI you host yourself — only the base URL changes.

# Install (beta)
pip install comfy-sdk        # Python
npm i @comfyorg/sdk          # TypeScript

# Run this workflow (Python)
from comfy_sdk import Comfy

client = Comfy(api_key="comfyui-...")
wf = client.workflows.from_file("workflow_api.json")
job = client.run(wf)
for output in job.get_outputs("<output-node-id>"):
    output.to_file(output.name)

The SDK takes a workflow in API format: open this workflow in ComfyUI and use File → Export Workflow (API). API access requires a Comfy Cloud plan with an API key. SDK docs · Get an API key

FAQ

Frequently Asked Questions

View all workflows