BigBang V1 36B-A3B

At the default Q4_K_M, 0 of 139 phones have enough estimated usable memory; 0 also reach 3+ tokens/s. On Mac, 45 of 54 exact configurations pass using that quant or a smaller tracked fallback.

Params
36B (3B active)
Family
bigbang
Released
2026-08
Tags
chat · coding · vision · reasoning

Downloads & memory by quant

The download is only the weights — add KV cache and runtime to get what your phone actually needs. “Memory-fit” only means it can load; “usable” also requires an estimated 3+ tokens/s. Each row uses that row's quant. ★ = recommended.

QuantDownloadMemory neededPhone reality
Q2_K13.1 GB~16.9 GB3 memory-fit · 3 usable
Q3_K_M16.7 GB~20.7 GB0 memory-fit
IQ4_XS19.3 GB~23.4 GB0 memory-fit
Q4_020.4 GB~24.5 GB0 memory-fit
Q4_K_S21.1 GB~25.3 GB0 memory-fit
Q4_K_M21.9 GB~26.1 GB0 memory-fit
Q5_K_M25.5 GB~29.9 GB0 memory-fit
Q6_K30.5 GB~35.1 GB0 memory-fit
Q8_037.8 GB~42.8 GB0 memory-fit

BigBang V1 36B-A3B at Q4_K_M on 139 phones

This table is fixed to the recommended Q4_K_M, on each phone's largest RAM option. Counts for smaller quants above will differ. All phones are shown, sorted by fit and estimated experience; tap one for the full report.

PhoneChip · RAMNeedsSpeedVerdict

~ = bandwidth-based estimate · ✓ = measured on real hardware

BigBang V1 36B-A3B on 54 Mac configurations

Each Mac uses the recommended Q4_K_M at 4K context when it fits, or the largest smaller tracked quant that fits. Each row links to the full report with a macOS-specific setup guide.

MacUnified memoryQuantWorking budgetNeedsEstimated speedVerdict

FAQ

How much RAM do I need to run BigBang V1 36B-A3B on a phone?

At Q4_K_M, BigBang V1 36B-A3B needs ~26.1GB of usable memory (weights + KV cache + runtime). In practice that means no current Android phone or no current iPhone — iOS lets a single app use less of its RAM than Android does.

How fast does BigBang V1 36B-A3B run on a flagship phone?

It doesn't fit on any of the 139 phones we track at Q4_K_M — it needs ~26.1GB of usable memory.

Can an iPhone run BigBang V1 36B-A3B?

Not really: the best iPhone we track (iPhone 16 Pro Max) has ~5.2GB usable, but BigBang V1 36B-A3B needs 26.1GB at Q4_K_M.

What is the best quantization of BigBang V1 36B-A3B for mobile?

Q4_K_M (21.9GB download) is the size/quality sweet spot of the 9 quants available. Total memory needed is ~26.1GB once the KV cache and runtime are counted — the download size alone understates it.

How many phones can run BigBang V1 36B-A3B?

0 of the 139 phones we track have enough estimated usable memory at Q4_K_M; 0 also reach our usable-speed threshold of 3 tokens/s, and 0 run smoothly. Memory-fit alone does not mean a good experience.

Which Macs can run BigBang V1 36B-A3B?

45 of the 54 exact Mac configurations we track have enough estimated working memory. Each Mac uses the recommended Q4_K_M when it fits, or the largest smaller tracked quant that fits, and separates installed unified memory, the macOS reserve, and estimated speed.

What is BigBang V1 36B-A3B good for on a phone?

It's tagged for chat, coding, vision, reasoning. At 36B parameters (3B active — it's a MoE, so it decodes faster than its size suggests), it prioritizes answer quality over speed — expect slower decoding.

Similar models

Qwen 3.5 35B-A3BQwen 3.6 35B-A3BOrnith 1.0 35B-A3BXYZ-Aquila mini 35B-A3BKAT-Coder V2.5 Dev