LTX2.3 FP4 Models
Because no one uploads FP4 here. and they should (fp4 works on 3xxx and above for vram savings.)
LTX2.3 Distilled FP4ME - Distilled FP4 Mixed Extreme - 14.1GB**
LTX2.3 Full Dev FP4ME - Full Dev FP4 Mixed Extreme - 14.1GB**
LTX2.3 Official NVFP4 - From Lightricks - Updated 3/17/2026 - 21GB
LTX2.3 Dev NVFP4 - from Hippotes / LTX-2.3-various-formats - 18.15GB
LTX2.3 Dev FP4 STFO - from Kijai's Transformers only Scaled FP8 - 16.63GB**
LTX2.3 Distilled FP4 - My first FP4 - Transformers Only - 18.15GB**
** Are transformers only, or I broke vae/text projection :) needs seperate Vae and Text projection downloads.
I have a fix for lora issue on FP4ME models. Comfy Bathroom, custom lora loader with presets as well as custom config. https://huggingface.co/MrReclusive/LTX-2.3-FP4
Diffusion model loader/unet loader seems to get confused with these, use the checkpoint loader even though it has no clip/vae
Description
Vae's For TFO model
FAQ
Comments (44)
so what is everyone's thoughts on 2.3 so far?
and how are your outputs coming out?
I've been fighting what seems to be a decode issue with the "cloudy" outputs.
First impression, much better voices realism and expressiveness, sound overall is better, but ltxv2.0 loras seems to work somewhat badly on it, and anatomy realism seems worst than 2.0 base as I remember, the model seems unable to make coherent body unless fully clothed outside of the face and maybe the neck (and even the neck sometimes it's... so so. Also 2.0 Loras seems to kinda work but not really (I mean they affect the output, somewhat, but it's a bit garbage here and there)
@BlastFromThePresent yeah, sound is amazing, but haven't figured out good workflow for using ltx2 lora's, my cloudy issue does stem from the ltx 2 detailer, but, they didn't release a detailer for 2.3 so not much choice.
and i think that's the disconnect between ltx2 loras and ltx2.3 working , its not really the generation, it's what it does to the latent making the ltx2.3 vae struggle.
the cloudyness is definitely a vae issue, but that's being introduced by the ltx2 lora's, maybe i should try stripping some blocks from a lora, see if it helps.
update: Yes, removing blocks 0-10 from the detailer lora fixed the "smokey" issue on decode.
@BlastFromThePresent lora strength 0.6 -0.5 seem to work
Which gemma TE are you using?I tried the fp8/fp4 gemma in comfyuiorg repo but i always get this error"untimeError: mat1 and mat2 shapes cannot be multiplied (6820x4096 and 2048x4096)". i even turned off the prompt enhancer. Im using the runexx workflow
yes.. that is a issue with comfy atm, they broke a shit load of stuff with the recent update.
you can try this on comfy start and see if it helps --disable-dynamic-vram
i had to recode a bunch of crap in the multigpu loaders to fix this.
and its nothing to do with the models, its the loaders because comfy added a bunch of crap that loaders arn't expecting so.. funny errors.
i use dual clip loader, not gemma loader, i know the most rencent multigpu loaders do work if you --disable-dynamic-vram on comfy start, but will crash if you don't have --disable-dynamic-vram set.
we are in for a rough week while everything gets fixed.
at first i though it was issues with ltx2.3, then found even my ltx2 workflows were bricked.
also, my workflow is in all my videos if you wanted to check those, it is multigpu setup, but no reason you can't just set it all to use same gpu.
I had this and had to both update comfy itself, and remove one of the custom nodes. SMz nodes or something like that. Google your error and there is a recent huggingface or github thread on it (last week or so)
@Gericho222 yeah, i fixed my errors, but now ive manually rewrote a bunch of code in the multigpu nodes, so can't update it now, lol.
i did try there most recent version, it crashes if you have have dynamic vram on, so went back to my version which allows me to control it per node.
so i can turn off dynamic vram from vae and clip, but leave it on for unet if I want.
I have this same error/ problem. Not the remotest idea how to fix it. Was hoping for some speed improvements given that I have a 5090 and it's much more fp4 capable than other cards, but none of these fp4 models work.
@Minase460 its the loading of the model issue, comfy, at least of my last update, doesn't know how to load ltx2.3 right, it assumes ltx2 and errors. i use the checkpoint loader instead of unet/model loaders to fix it. (there is meta data in the files that tells the checkpoint loader how to use them, as long as you comfy ui is updated enough)
What is the extreme variant for?
more blocks are in fp4 making it smaller, and even some of the ones you shouldn't really put in fp4, i put in fp8 instead of leaving them at bf16, i just wanted to test pushing more of the model into fp4/fp8 to save on vram, 14.8gb vs 19gb, the extra 4gb means another 10 seconds to length or higher resolution (it will do 1920x960 10 seconds in 24gb vram)
even beyond that, if you are running on lower vram cards, the swap should be faster, i don't really activly swap while generating, but when i do, the more in fp4, the faster the swapping is.
Cool, LXT 2.3 distilled NVFP4.
I look forward to trying it.
Any point trying this on a 3090ti?
i don't know, not sure if 3xxx series can run fp4.
fp4 isn't "officially" supported by 4xxx series either but it works, not any faster but saves vram.
won't know unless you try, i would say maybe try to find a smaller model to test on so you don't waist time downloading 14-20gb.
the worst that would happen i think is it just expands it back out to fp8.
let me know if it does work though, im curious to know.
You could run it, but it won't get faster than FP8, so there's no point. This is for the Blackbell GPUs only
@GlowingGuardianGirl there is a point on non blackwell gpu's, vram savings. Even if no speed boost the model is still smaller, i run these on a 4090, speed isnt the only reason for fp4
I think I may have tried LTX 2's fp4 or some other fp4 model and I don't think it worked out to a benefit because I stopped using it. I use Kijas Fp8 it's small enough at around 20gb, I also play with Q8 GGUF sometimes
@FantasticFever the issue i have with gguf's and the reason i stick with fp4, is as soon as you add a lora to a gguf models, it starts swapping data, even if the model can fit in vram, fp4 doesn't do that, it just injects the lora into the fp4 model at fp4 weights, so if the model and latent fits in vram, no active swap so its faster. but again, like i say allot, my workflow is multi gpu, so model, gemma/clip, and vae's all have there own cards, so i do everything I can to prevent data swaps, everything is fully on a card. 1920x960 10 second gens in less then 2 minutes right now. and I can only do that because I have the fp4 distilled "extreme" down to 14gb, leaving almost 10gb for the latent on the 4090.
its all about use case, I have reasons for preferring fp4 over gguf, actually i kind of despise gguf's because the lora swap issue. i just don't like any swapping that isn't under my control with distorch.
@MrReclusive666 yeah I think fp8 does similar, at least it has dynamic vram so thats why I mostly use that now, with image 2 video its almost the same quality i find
@FantasticFever yeah, i had to turn dynamic vram off, with it on, my generations go from 3 minutes to 10 minutes.
@MrReclusive666 Which one do you recommend for i2v?
im still figuring that out, i have some small issue on my end with i2v, but not sure where its coming from yet, not sure if its model or something else in my workflow, i have alot of issues with decode in my setup, so my issue is probably related to that.
but even with the decode issue, my fp4 extreme distilled looked great on itv at 2048x1024 except for the small 5 frame glitch at the start.
@AiMetatron @DigitalPastel @taek75799 @darksidewalker @FX_FeiHou I hope you’ll add support for this AI model soon. ✌️🙏
What folder does the Text Projection model go into?
its a clip, if your using dual clip loader, put it in your clip folder, if your using it with the gemm3 loader put it in diffusion models and treat it as the "model"
how do you load the nvfp4 model? i cannot select nvfp4 in the dropdown so it falls back to bf16.
what loader?
i use distorchmultigpu loader, so it doesn't even ask, it just loads what ever it is.
the backend casts it back into bf16, no?
Found quantization metadata version 1
Detected mixed precision quantization
Using mixed precision operations
model weight dtype torch.bfloat16, manual cast: torch.bfloat16
@bobatoms it is a mixed precision model, one or 2 things are in bf16. but 95% is fp4/fp8 mix.
what happens in hardware that cant run in fp4, like mine, is it keeps it in fp4 in vram, and very quickly, during generation, expands to fp8, samples, discards fp8. and it does this on a per block layer, so its not like its doubling in size during generation, each block layer maybe consumes an extra 500mb-1gb during inference. it sits in vram at 13gb.
that's how all this work for non blackwell gpu's, as long as you can run fp8, you should be able to run these models, just not as fast, but still faster then swapping fp8 to and from ram/hd.
Karmaşık ve işe yaramaz bozuk nodeler ve tekrar yapılandırma zinciri ile uğraşmaya gerek yok! workflow güncellenirse tekrar deneyeceğim
any chances of an int8 version for 3xxx gpus?
check with the people posting ggufs, i haven't done much of anything with int8 outside llm's and from my understand int8 is horrible for image/videos models. the fp4's as far as I know do still work on 3x series cards for memory savings, just no speed boost that you would get on the blackwell cards, i don't even have a blackwell card, im on 4x series, so only memory savings, well, do get some speed boost vs fp8 or higher because don't need to swap during generation because my extreme varient is 14gb.
@MrReclusive666 yeah i'm using it right now and the memory save is nice, i'm using less than with a q4 gguf, but for now the quality is way worse. do you have a workflow i can try?
@ZelashZelash all my videos have workflows attached. they are all multi gpu setups. first thing I would suggest, turn off any lora's, this is a big issue with my extreme fp4 model, working on that, i don't really run that one with lora's. and it really prefers low steps, with dpm++ 2m sde heun gpu it runs at 4 steps, quality degrades at 5, euler a likes about 6 steps. (these are either beta11 or sgm uniform) this is my custom sigma i've been runing with dpm++ 2m sde heun gpu, 1.0, 0.925, 0.725, 0.421875, 0.0. play with the 0.925, between 0.95 and 0.90, depending need. to get that small size its very compressed so very fickle.
@MrReclusive666 thanks, i'm having good quality results with your workflow at 4 steps even with loras! i was using a workflow with a 8 steps low res first pass and then 4 steps for refining. i guess the latent upscaling messes up with the quality a lot
TBH I am using INT8 and I have used FP4 LTX 2.3 (not this guys models, i downloaded one and it was terrible output, it was the extreme one, im sure one of the others would have worked fine but i got the fp4 elsewhere after) Anyway, I feel the speeds between INT8 and FP4 seem comparable at least if you dont have enough memory to hold the INT8 file at once, I have 32gb vram and 8gb ram so the FP4 fits nicely (using cache none to dump other models and cache) but the INT8 is too big so I think it slows it down for me to where the end result in speed is similar to FP4.
Just my 2 cents, would be interested to hear your experience if you've tried the regular INT8 there's a distilled version on silveroxides quantops huggingface and winnougan has just converted a dev version.
@MrTitsworth id be curious to, i just know ive read a lot that dit models don't do well in int8, and was that a typo or are you really running a 5090 on 8gb ram?
i guess its a trade now, prices are as equally insane.
@ZelashZelash hey, just wanted to follow up on this. i run custom sigmas for stage 2 upscale, euler ancestor.
for quick run - 0.91218, 0.725, 0.0
for more detailed run - 0.91218, 0.909375, 0.725, 0.10546875, 0.052734375, 0.0
that second one helps when going from reaaly low res base, as it helps add detail and fix anatomical issues.
the reason for the reaaly crazy low number ones, is for some reason this, 0.421875, is mathematically significant, and those low numbers i based on that.
@MrReclusive666 Nah im on a 3070ti and no isues with the models.
I've been comparing, INT8 for me is similar in speed to FP4 models on my system where the FP4 is smaller so loads faster but the INT8 is optimized but is larger, so the fp4 can be slightly faster but the INT8 is better quality as its uncompressed.
If anyone is interested in INT8 just google silveroxides and Winnougan has made some conversions of the Dev and Transformers version of distilled so far.
@MrTitsworth yeah, its all about need, i made these 14gb fp4's because I wanted the model fully on card with no swap while still getting decent resolution/length outputs.
and the main reason is my 4090's are on 1x pcie risers (this machine was built for 3d rendering), so active swapping is a huge no for me, so 30gb models, i don't even look at.
Details
Files
ltx23FP4_ltx23VideoVae.safetensors
Mirrors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
ltx_23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors
LTX23_video_vae_bf16.safetensors