BGE M3 needs ~5.2 GB VRAM. MacBook Air M1 16GB has 11.5 GB. With F16 quantization, expect ~8 tok/s.
Operating mode
Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.
Current mode
Balanced
Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.
Select quantization to explore
Fit status
Runs well
Decode
8.0 tok/s
TTFT
24346 ms
Safe context
8K
Memory
5.2 GB / 11.5 GB
This setup is broadly balanced for this model.
Shared-memory contention still exists
The OS, browser, and inference runtime all compete for the same physical memory pool, so real-world headroom is less forgiving than raw capacity suggests.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | A | Runs well | 8.0 tok/s | 13280 ms | 8K |
| Coding | A | Runs well | 8.0 tok/s | 24346 ms | 8K |
| Agentic Coding | A | Runs well | 8.0 tok/s | 35412 ms | 8K |
| Reasoning | A | Runs well | 8.0 tok/s | 28773 ms | 8K |
| RAG | A | Runs well | 8.0 tok/s | 44266 ms | 8K |
Inference speed
Estimated decode speed (tokens/sec) for BGE M3 at F16 across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~8 tok/s. Speed is memory-bandwidth bound, so cards that fit the whole model in VRAM run far faster than ones that offload to system RAM.
| GPU / Mac | Memory | Quant | Speed (tok/s) | Fits? |
|---|---|---|---|---|
| 32 GB | F16 | 8.0 | Fits | |
| 24 GB | F16 | 8.0 | Fits | |
| 16 GB | F16 | 8.0 | Fits | |
| 24 GB | F16 | 8.0 | Fits | |
| 12 GB | F16 | 8.0 | Fits | |
| 12 GB | F16 | 8.0 | Fits | |
| 8 GB | F16 | 8.0 | Fits | |
RX 7900 XTX 24GB | 24 GB | F16 | 8.0 | Fits |
MacBook Pro M4 Max 128GB | 128 GB | F16 | 8.0 | Fits |
Mac Studio M3 Ultra 256GB | 256 GB | F16 | 8.0 | Fits |
Mac Studio M2 Ultra 128GB | 128 GB | F16 | 8.0 | Fits |
Mac Studio M1 Ultra 128GB | 128 GB | F16 | 8.0 | Fits |
MacBook Pro M4 Max 64GB | 64 GB | F16 | 8.0 | Fits |
MacBook Pro M3 Max 64GB | 64 GB | F16 | 8.0 | Fits |
MacBook Pro M1 Max 64GB | 64 GB | F16 | 8.0 | Fits |
MacBook Pro M4 Pro 48GB | 48 GB | F16 | 8.0 | Fits |
Estimates for single-stream decoding at F16; real tokens/sec varies with prompt length, context, batch size, and runtime build. Prompt processing (prefill) is faster than the decode figures shown here.
How BGE M3 (0.5680000185966492B params) fits at each quantization level on MacBook Air M1 16GB (11.5 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 0.2 GB | Low | A82 |
Q3_K_S | 3 | 0.3 GB | Low | A83 |
NVFP4 | 4 | 0.3 GB | Medium | A83 |
Q4_K_M | 4 | 0.3 GB | Medium | A83 |
Q5_K_M | 5 | 0.4 GB | High | A83 |
Q6_K | 6 | 0.5 GB | High | A83 |
Q8_0 | 8 | 0.6 GB | Very High | A83 |
F16Best for your GPU | 16 | 1.2 GB | Maximum | A83 |
Copy-paste commands to run BGE M3 on your machine.
Run
docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \
--hf-repo "BAAI/bge-m3" \
--hf-file "bge-m3-F16.gguf" \
-c 4096 -ngl 99Your hardware
| Model | Params | Grade | Decode | Capabilities |
|---|---|---|---|---|
| 9B | S | 8 tok/s | ||
| 4B | S | 18 tok/s | ||
| 8B | S | 9 tok/s | ||
| 3.8B | S | 18.9 tok/s | ||
| 0.57B | A | 8 tok/s |
Yes, MacBook Air M1 16GB can run BGE M3 with a A grade (Runs well). Expected decode speed: 8.0 tok/s.
BGE M3 (0.5680000185966492B parameters) requires approximately 5.2 GB of memory with F16 quantization.
The recommended quantization for BGE M3 is F16, which balances quality and memory efficiency.
On MacBook Air M1 16GB, BGE M3 achieves approximately 8.0 tokens per second decode speed with a time-to-first-token of 24346ms using F16 quantization.
For coding workloads, BGE M3 on MacBook Air M1 16GB receives a A grade with 8.0 tok/s and 8K context.
On MacBook Air M1 16GB, BGE M3 can safely use up to 8K tokens of context. The model's official context limit is 8K, but available memory constrains the safe maximum.
Not always. MacBook Air M1 16GB can often fit larger models thanks to unified memory, but a discrete GPU with dedicated high-bandwidth VRAM may still decode faster once the model fits. For this combination, the important distinction is capacity versus sustained throughput.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/bge-m3-on-m1-16gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview: