CIVITAI / Workflows

LTX-2 I2V Distilled 60-Frame 1080p Consistency Workflow

This ComfyUI workflow is designed for LTX-2 image-to-video generation with a distilled acceleration route, stronger frame-to-frame consistency, and 1080p-class high-resolution output. The main goal of this workflow is to turn one input image into a stable short video while preserving the original subject identity, scene layout, lighting direction, camera framing, and overall visual style across the generated frames. Compared with a heavier non-distilled LTX-2 route, this workflow focuses on a more efficient distilled generation setup. It still uses the LTX-2 Dev model backbone, but adds a distilled LoRA route to improve speed and sampling efficiency. This makes the workflow more suitable for repeated testing, online generation, RunningHub deployment, prompt iteration, and short video production where users need both visual quality and faster turnaround. The workflow is built around LTX-2 19B Dev FP8, using ltx-2-19b-dev-fp8.safetensors as the main checkpoint and gemma_3_12B_it.safetensors as the text encoder. It also uses LTX-2 spatial latent upscaling through ltx-2-spatial-upscaler-x2-1.0.safetensors. The distilled behavior is introduced through the LTX-2 distilled LoRA route, allowing the workflow to run with a more compact sampling structure while still keeping the LTX-2 visual generation pipeline. The core logic is image-to-video consistency. A source image is loaded, resized, preprocessed, injected into the video latent, sampled through LTX-2, spatially upscaled in latent space, refined again, and finally decoded into video frames. This makes the workflow more advanced than a simple one-pass image-to-video graph. It is built as a multi-stage LTX-2 I2V pipeline for creators who want more stable short clips instead of unstable single-pass motion. The input stage starts from a still image. The image is prepared through ImageResizeKJv2 and ResizeImagesByLongerEdge. The workflow is designed around high-resolution output logic, with a 1080p-class route such as 1920 x 1088 available for stronger GPUs. The workflow note also explains that width and height should follow LTX-2 valid size rules, and the frame count should follow the “divisible by 8 plus 1” rule. If invalid values are used, the workflow may silently choose the closest valid parameters, so correct resolution and frame-count planning is important. The frame calculation stage uses a calculator-st