Inner-Reflections · video

VACE_Skyreels_V3_R2V_Merge

Inner-Reflections/VACE_Skyreels_V3_R2V_Merge

VACE_Skyreels_V3_R2V_Merge at Q4_K_M is exactly 11,627,589,408 bytes (10.83 GiB / 11.63 GB) — an effective 5.365 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)
Parameters
17.3B
Architecture
wan
Context
native (config.json)
License

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q3_K_M8.03 GiB8,624,197,4083.979BlackStone-Yu
Q3_K_M8.03 GiB8,624,197,4083.979mickmumpitz
Q4_K_M10.83 GiB11,627,589,4085.365BlackStone-Yu
Q4_K_M10.83 GiB11,627,589,4085.365mickmumpitz
Q5_K_M12.13 GiB13,025,472,2886.010BlackStone-Yu
Q5_K_M12.13 GiB13,025,472,2886.010mickmumpitz
Q8_017.37 GiB18,651,410,2088.606mickmumpitz

Pipeline components

a diffusion model is a graph of parts, not one file
ComponentSizeShareCan live on the CPU?
denoiser48.45 GiB100%no, must be resident
Full pipeline48.45 GiBresident if nothing is offloaded

The parameter count published for a diffusion model describes the denoiser alone. Running it also requires its text encoder and VAE, and the text encoder is often nearly as large as the denoiser — which is why offloading it is the standard first move when you run out of memory.

We publish component sizes here, not throughput. Community-submitted image-generation rates do exist for many GPUs and we show them on the hardware pages, but they aggregate runs at different resolutions, step counts and settings, so they cannot be attributed to one model. Peak memory during sampling is unmeasured by any public source, and we do not estimate it.

Compare with

same modality, comparable size

Will it run on your card?

full quant x context sweep

Why other calculators give a different number

A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 9.08 GiB. The real file is 10.83 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

Architecture unavailable — this repository is gated and no ungated mirror was found. Exact file sizes above are still authoritative; only the KV math needs the config.

Questions people ask

How much VRAM does VACE_Skyreels_V3_R2V_Merge need?
Q4_K_M is exactly 11,627,589,408 bytes (10.83 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of VACE_Skyreels_V3_R2V_Merge should I use?
Q4_K_M is the usual default. Pick the largest quantization that fits your card at the context you actually need — the table above gives exact sizes for every one published.