My LTX-2.3 I2V workflow inspired by nomadoor. I've tweaked a few things that work for me and it may not work in some cases.
The workflow generates two videos: a ~0.25 megapixels low resolution video ("small_XXX") after the first stage and a 2x upscaled ~1.0 megapixels final video ("big_XXX") after the second (upscale) stage. After the first stage you could play the "small" video and if you don't like it you could cancel the second stage and restart the generation. Also a low-quality preview is generated on the fly (via LTX2.3 Tiny VAE), so you could cancel even before the first stage is complete. Note that the 1.5x or 2x upscale stage for LTX-2.3 is by desigh and is not optional (unlike Wan for example), although tests show that you can do one-stage generation with high resolution and skip the upscale if your vid is relatively static.
Tips:
The default sampler in the workflow is "lcm", but "res_2s" is better, especially for vids with lots of action and smaller faces, if you don't mind waiting twice as long (res_2s is slow).
If you have enough VRAM + RAM (always set your virtual RAM to at least 150GB, even 250GB if you have enough disk space), you could set length to 241 for 25 fps (or 513 for 50 fps) or even more (at some point you'll get OOM error).
The workflow defaults to random seeds (seed -1), but itβs better to use fixed seeds (click 'new fixed random' for both stages before each run). This allows you to change only the second-stage seed and when you click 'Run' again, only the second stage will regenerate with slight variations in video and audio. If you encounter an OOM error while using fixed seeds, simply click 'Run' again β the second attempt sometimes succeeds.
Model:
ltx-2.3-22b-dev_transformer_only_fp8_scaled.safetensors (Kijai)
SHA256: f0b8f92f8a33daf7e7f508878db6d6f25f9c8bc7b90fcb5650fb402a9d9e9f13
or
ltx-2.3-22b-dev_transformer_only_bf16.safetensors (Kijai; heavy, but recommended - works even on 12GB VRAM if you set your virtual RAM to 100GB or more)
SHA256: 0c83957f8c79d49c52ff5e3c0980a759d4dd532563d62cab35fda2b247606bd2
Video vae:
LTX23_video_vae_bf16.safetensors (Kijai)
SHA256: 01ea62d09bc139f95c5dee7b5c062ad6a3e6cd8be910a1983ac02e7eb5b8ee3b
Audio vae:
LTX23_audio_vae_bf16.safetensors (Kijai)
SHA256: 5bc10fa4adecf99dda132d916e23048cbd56797702c5fa50eb5d2079048a38c3
Lora:
ltx-2.3-22b-distilled-lora-384-1.1.safetensors
SHA256: f5d4953f3386197a4b4f5abdb17616ff256171e8075c111d6e7d2dfa6e823b3a
Text encoders:
gemma-3-12b-it-IQ4_XS.gguf (unsloth, more)
SHA256: e209a303d9d0841c1ab29a728b930ef630ba27766aa0067258f9e400f7ae8c65
ltx-2.3_text_projection_bf16.safetensors
SHA256: 911d59bb4cb7708179c9a0045ea0fe41212ecfb77aed3a02702b7c0a8274911f
Latent_upscale_model:
ltx-2.3-spatial-upscaler-x2-1.1.safetensors
SHA256: 5f416311fa8172b65af67530758964708d29a317b830d689a51143b7f91913ed
or
ltx-2.3-spatial-upscaler-x1.5-1.0.safetensors
SHA256: b2b3193e68cb04b4701e1d59bec4ed5d5e3e84506d9a42d5a129d37d39823df7
LTX2.3 Tiny VAE
taeltx2_3.safetensors (madebyollin)
SHA256: f0773b4e3e57318e6aa4dd4a35e1d16213a5f160fbc0376163f06888bbcbe246
Model Storage Location:
πComfyUI/
βββ πmodels/
βββ πdiffusion_models/
β βββ ltx-2.3-22b-dev_transformer_only_fp8_scaled.safetensors
β OR
β βββ ltx-2.3-22b-dev_transformer_only_bf16.safetensors
βββ πlatent_upscale_models/
β βββ ltx-2.3-spatial-upscaler-x2-1.1.safetensors
β OR
β βββ ltx-2.3-spatial-upscaler-x1.5-1.0.safetensors
βββ πloras/
β βββ ltx-2.3-22b-distilled-lora-384-1.1.safetensors
βββ πtext_encoders/
β βββ gemma-3-12b-it-IQ4_XS.gguf
β βββ ltx-2.3_text_projection_bf16.safetensors
βββ πvae/
β βββ LTX23_video_vae_bf16.safetensors
β βββ LTX23_audio_vae_bf16.safetensors
βββ πvae_approx
βββ taeltx2_3.safetensorsDescription
FAQ
Comments (15)
How are things going with NSFW?
Looks like the Loras for regular LTXV2 are doing their job.
Will there be GGUFs of the Kijai's files? Thank you π
amazing wf. this is more of a general question but i did experience "slow motion" when i set fps to 30 and length to 361 but only for upscaled. any ideas why...noticed this in the comfyui ltx 2.3 template wf for both t2v and i2v
Excellent workflow. This makes LTX2.3 actually usable. Great job.
Thanks. LTX has potential, but 2.3 is still a disaster - out of 100 generations you'll probalby get 5 usable, the rest is slop with multiple issues and It's nothing any workflow can fix (i've already tried about 20). Hope they'll fix it in the next versions, especially the "dead eyes syndrome" - it just can't generate human eyes.
@bnzarev821Β Yeah, this workflow was the best I've tried so far with i2v, but after a lot of testing, I would agree, i2v is still messed up. It's so close to being totally great, but the character consistency, weird audio buzz, and lack of prompt adherence is so bad. It works out sometimes in limited ways, and they definitely improved the visual quality from 2.0, but it still has a ways to go.
Great workflow. I would love the ability to have a save last frame to start a new segment from the last frame.
Not once, not ever can i use any workflow ever shared by anyone! There's always a node or something missing, and confyui can never install. The constant updates breaking everything are the biggest mess i ever had to deal with
If you have problems with comfyui, try to install and use it via https://pinokio.co
I know what you mean, always errors...
does this workflow work with ltx-2.3-22b-dev.safetensors
Hi,
First of all, thank you so much for sharing this excellent LTX-2 I2V workflow! Iβm a beginner from Taiwan and I really like your workflow β itβs one of the best Iβve tried so far.
I have one question I hope you can help with:
When I set the video to 5 seconds (121 frames at 24 fps), the motion speed feels normal. However, when I increase it to 10 seconds (242 frames) or longer while keeping the same fps, the transformation becomes obvious slow-motion (like the 5-second version is just being slowed down).
Is there any recommended setting or prompt trick to make longer videos (10β20 seconds) have natural, steady motion speed instead of feeling like slow motion?
Any advice would be greatly appreciated!
Thank you again for your great work!
Best regards,
A Taiwanese newbie user
I tried the fp8 workflow. with no changes at all. in i2v it only blurs the picture away. any ideas?
same here