ACE-Step-1.5 requirements — can you run it?
~44.2B parameters · 5 quantizations measured · updated 2026-09-12 · source: Serveurperso/ACE-Step-1.5-GGUF
# llama.cpp (auto-downloads the GGUF) llama-cli -hf Serveurperso/ACE-Step-1.5-GGUF:Q4_K_M # Ollama (pulls straight from Hugging Face) ollama run hf.co/Serveurperso/ACE-Step-1.5-GGUF:Q4_K_M # LM Studio: search "Serveurperso/ACE-Step-1.5-GGUF" in the model browser
Commands load the exact quant measured on this page.
Every quantization: real file size vs what you actually need
| Quant | File (measured) | VRAM/RAM needed (8K ctx) | Runs on (first fit) |
|---|---|---|---|
| Q4_K_M | 20.6 GB | 26.3 GB | RTX 5090 32GB |
| Q5_K_M | 27.3 GB | 34.3 GB | RTX PRO 6000 96GB |
| Q6_K | 31.7 GB | 39.5 GB | RTX PRO 6000 96GB |
| Q8_0 | 47.0 GB | 57.9 GB | RTX PRO 6000 96GB |
| BF16 | 88.4 GB | 107.6 GB | Mac 128GB unified |
KV cache uses a flat +20% context/overhead rule because this repo does not publish its config; exact numbers may differ for long contexts. MoE models keep all experts in memory — total size counts, not just active params. Longer context grows the KV cache — use the selector above.
Can I run ACE-Step-1.5 on my GPU? (Q4_K_M recommended quant)
| Hardware | Memory | Verdict | Est. speed |
|---|---|---|---|
| RTX 3060 12GB | 12 GB | no | |
| RTX 4060 Ti 16GB | 16 GB | no | |
| RTX 3090 24GB | 24 GB | no | |
| RTX 4090 24GB | 24 GB | no | |
| RTX 5090 32GB | 32 GB | RUNS | ~65 tok/s |
| RTX PRO 6000 96GB | 96 GB | RUNS | ~65 tok/s |
| Mac 16GB unified | 16 GB | no | |
| Mac 32GB unified | 32 GB | RUNS | ~5 tok/s |
| Mac 64GB unified | 64 GB | RUNS | ~10 tok/s |
| Mac 128GB unified | 128 GB | RUNS | ~15 tok/s |
| Mac 256GB unified | 256 GB | RUNS | ~20 tok/s |
| Mac 512GB unified | 512 GB | RUNS | ~30 tok/s |
| 32GB system RAM (CPU) | 32 GB | RUNS | ~2 tok/s |
| 64GB system RAM (CPU) | 64 GB | RUNS | ~2 tok/s |
| 128GB system RAM (CPU) | 128 GB | RUNS | ~3 tok/s |
| 256GB system RAM (CPU) | 256 GB | RUNS | ~3 tok/s |
| 1TB server RAM (CPU) | 1024 GB | RUNS | ~7 tok/s |
| 2TB server RAM (CPU) | 2048 GB | RUNS | ~7 tok/s |
Speed = decode tok/s estimated from memory bandwidth ÷ measured file size (× MoE active share). Real numbers vary ±30% by runtime and settings.
How much VRAM does ACE-Step-1.5 need?
The honest answer: 26.3 GB at the Q4_K_M quant with 8K context — that is the measured
file size (20.6 GB) plus KV cache and runtime overhead. The smallest published build needs
26.3 GB; the lossless one needs 107.6 GB.
Cheapest hardware that runs it: New RTX 5090 32GB (~$2500, used market) — see which GPU to buy.
Can I run it with CPU offload?
Yes, if combined RAM+VRAM ≥ file size — but generation speed is limited by memory bandwidth. Expect roughly: DDR5 dual channel ~10-30 tok/s for small MoE actives, single digits for big ones, 0.1-1 tok/s when experts page from disk. CPU-only is fine for batch jobs, painful for chat.
Why do other sites show different numbers?
Most pages compute weights from a formula (params × bits/8). We use the actual file sizes published in GGUF repos, which include the embedding table, unquantized tensors, and container overhead — that is why our numbers can differ from a naive calculation.
FAQ
How much VRAM does ACE-Step-1.5 need?
The measured answer: 26.3 GB at the Q4_K_M quant with 8K context. The smallest published build needs 26.3 GB; the lossless (F16/BF16) build needs 107.6 GB. These are real GGUF file sizes from Hugging Face, not formula estimates.
Can I run ACE-Step-1.5 on a 24GB GPU (RTX 3090/4090)?
Not at Q4_K_M (26.3 GB). Nothing fits 24GB — the smallest build needs 26.3 GB. Use the hosted API or a smaller model.
How fast will ACE-Step-1.5 run?
Decode speed is memory-bandwidth-bound. At Q4_K_M: roughly 37 tok/s on an RTX 4090, 34 tok/s on an RTX 3090, 15 tok/s on an M-series Mac with 128GB, and 1.8 tok/s on CPU with dual-channel DDR4 — estimates from measured file size, MoE active-parameter share and memory bandwidth.
Can I run ACE-Step-1.5 on CPU with system RAM?
Yes, if your usable RAM is at least the file size. At Q4_K_M you need ~26.3 GB of RAM. CPU generation is memory-bandwidth-bound: expect single-digit tok/s for large MoE models, 10-30 tok/s for small active params, and below 1 tok/s when experts page from disk.
Why do VRAM numbers for ACE-Step-1.5 differ between sites?
Most sites compute weights from a formula (params x bits/8). ModelFit uses the actual GGUF file sizes published on Hugging Face, which include the embedding table, unquantized tensors, and container overhead — so our numbers reflect what you really download and load.