LTX-2.5-Quantized

Model overview

LTX-2.5 generates picture and sound in one pass. It is also 42 GB of bf16 weights, and the text encoder beside it is another 26 GB. This repo is the set of weights that make it run on a card that does not have that. Sizes are measured, not estimated. "Fits 16 GB" assumes the text encoder is not resident at the same time — ComfyUI frees it before sampling — and tiled VAE decode. File sizes are decimal GB (bytes / 10^9); card capacities are the usual binary GiB, so a 15.9 GB file occupies 14.8 GiB of a 16 GiB card. The gap is real and it is where your activation pool lives. On the text encoder: at bf16 it is 26.3 GB and at Lightricks' int8 15.4 GB, which on a 16 GB card means the encoder alone owns the machine for the one step that just makes an embedding. **No GGUF of the LTX-2.5 encoder exists** — ComfyUI-GGUF gates text encoders on `TXT_ARCH_LIST`, which carries `gemma3` but not `gemma4`, so LTX-2.3's gemma3 encoder does have GGUFs and this one cannot. The open request (#450, 2026-05-28) has not been picked up — but comfy-native quantisations of it do exist and landed the same day as ours (Winnougan's w4a8-convrot at 10.6 GB, DmitryDB's nvfp4 at 11.2, vonkaiser's nvfp4-torchao at 8.9). Ours is w4a8 at 10.60 GB, within 2 MB of Winnougan's — the same format at the same size, published independently. Treat it as a mirror, not a first.

Key features

特点摘要待依据来源补齐，不凭模型名称推断能力。

Limitations & considerations

Sources are insufficient to establish specific limitations. Verify task performance, latency, data policies, licensing and version lifecycle.

Source prices & cost analysis

Prices vary by channel, region and configuration. Channel quotes are listed independently and are not treated as a single official provider price.

Public benchmarks & run configuration

暂无已采集的可核验公开评分。模型未上榜不代表能力较低。

Frequently asked questions

Sources & traceability

许可证：other。模型介绍与第三方评测均以原来源的具体版本和方法为准。