What GPU do I need to run ACE-Step/acestep-5Hz-lm-4B?

4.2B parameters, published in BF16. View on Hugging Face

4.2B
Parameters
BF16
Native precision
Qwen3ForCausalLM
Architecture
text-to-audio
Pipeline

acestep-5Hz-lm-4B is published by ACE-Step on Hugging Face, with 10,059 downloads and 53 likes to date. It's a Qwen3ForCausalLM model built for text-to-audio, published natively in BF16.

VRAM required & cheapest live GPU fit

Required VRAM = weight size at each precision times a flat 1.2 overhead for activations and fragmentation. The KV-cache grows with context and is not in that factor; it is listed per model below where the architecture is published. Full formula and assumptions: methodology.

PrecisionWeight sizeRequired VRAMCheapest live fitGPUs neededEst. $/hr (full fit)
BF167.8 GB9.4 GBRTX 30601$0.110/hr
FP8 (quantized)3.9 GB4.7 GBRTX 5060 Ti1$0.180/hr
INT4 (quantized)2.0 GB2.3 GBRTX 30701$0.088/hr

A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.

INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.

Cheapest way to run acestep-5Hz-lm-4B at its published (BF16) precision: 1× RTX 3060, at $0.110/hr per GPU ($0.110/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

acestep-5Hz-lm-4B: KV cache by context length

The KV cache is the memory the attention layers hold for every token of context, on top of the weights. It is not part of the flat 1.2x overhead in the table above, grows with context length and with every concurrent request, and is why a long-context deployment needs more VRAM than the table shows.

Grouped-query attention: every layer caches keys and values for a few shared KV heads. Cached per token: 147,456 bytes at 16-bit.

ContextKV cache, one sequence
4K0.56 GB
32K4.5 GB
40K (model maximum)5.6 GB

Computed from the layer, head and window counts in the model's own configuration (ACE-Step/acestep-5Hz-lm-4B), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.

acestep-5Hz-lm-4B: common questions

Does acestep-5Hz-lm-4B fit on a 12 GB GPU?

Yes. At BF16 it needs 9.4 GB of VRAM, so a 12 GB card holds it with 2.6 GB to spare. An 8 GB card is not enough for it at BF16.

What is the least VRAM acestep-5Hz-lm-4B can run in?

2.3 GB, at INT4 (quantized), which fits a 6 GB card, against 9.4 GB at BF16. That row assumes an INT4 checkpoint has actually been published for this model, so check its Hugging Face page before planning around it.

Does quantizing acestep-5Hz-lm-4B lower the GPU bill?

Yes. At BF16 the cheapest live fit is one RTX 3060 at $0.110/hr. At INT4 (quantized) it drops to one RTX 3070 at $0.088/hr, provided a quantized checkpoint exists for it.

Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.

ACE-Step models

Alternatives at this size

Other models for text-to-audio within about a third of acestep-5Hz-lm-4B's 4.2B parameters, from other model lines.

More on acestep-5Hz-lm-4B

Related reading: H100 pricing and specs, Whisper variants compared, and What AI inference is.

Your own GPU cloud accounts

One console for the GPU clouds you already rent from. Your keys stay on your machine.

$20 a month, flat

Connect your accounts

One console for the GPU clouds you already use.

Connect your accounts for $20 a month, flat. Your provider bills the GPU.

© 2026 Aquanode. All rights reserved.

All trademarks, logos and brand names are the property of their respective owners.