Darkhn · text

L3.3-70B-Animus-V5-Pro

Darkhn/L3.3-70B-Animus-V5-Pro

L3.3-70B-Animus-V5-Pro at Q4_K_M is exactly 42,520,394,016 bytes (39.60 GiB / 42.52 GB) — an effective 4.821 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)
Parameters
70.6B
Architecture
llama
Context
native (config.json)
License
llama3.3

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_K24.56 GiB26,375,108,8962.991Darkhn-Quants
Q3_K_L34.59 GiB37,140,592,9284.211Darkhn-Quants
IQ4_NL37.30 GiB40,053,619,3284.542Darkhn-Quants
Q4_K_M39.60 GiB42,520,394,0164.821Darkhn-Quants
Q5_K_M46.52 GiB49,949,817,1205.664Darkhn-Quants

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 36.96 GiB. The real file is 39.60 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 L3.3-70B-Animus-V5-Pro need?
Q4_K_M is exactly 42,520,394,016 bytes (39.60 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of L3.3-70B-Animus-V5-Pro 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.