Phi 3 Medium 14B needs ~13.7 GB VRAM. RX 7700 XT 12GB has 12.0 GB. With Q4_K_M quantization, expect ~19 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
1.7 GB over capacity — needs offload or smaller quantization
Fit status
Very compromised (needs ~1.1 GB host RAM)
Decode
18.5 tok/s
TTFT
10443 ms
Safe context
7K
Memory
13.7 GB / 12.0 GB
Offload
10%
It fits through host-memory offload, and offload is the main reason performance drops.
CPU or host-memory offload is active
About 10% of the working set spills out of accelerator memory, which usually hurts latency and sustained decode throughput.
Very little memory headroom
You can run the model, but there is not much room left for longer context, bigger batches, extra apps, or future model updates.
Remove offload with more accelerator memory
Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.
Buy headroom, not only minimum fit
A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.
Increase host RAM if you keep offloading
This setup may need roughly 1.1 GB of extra host RAM just for the offloaded portion, before OS and other tools.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | B | Runs with offload (needs ~0.1 GB host RAM) | 23.8 tok/s | 4442 ms | 7K |
| Coding | C | Very compromised (needs ~1.1 GB host RAM) | 18.5 tok/s | 10443 ms | 7K |
| Agentic Coding | F | Too heavy | 12.1 tok/s | 23201 ms | 7K |
| Reasoning | C | Very compromised (needs ~1.1 GB host RAM) | 18.5 tok/s | 12342 ms | 7K |
| RAG | F | Too heavy | 12.1 tok/s | 29001 ms |
How Phi 3 Medium 14B (14B params) fits at each quantization level on RX 7700 XT 12GB (12.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 5.5 GB | Low | B63 |
Q3_K_S | 3 | 6.9 GB | Low | B63 |
NVFP4 | 4 |
Copy-paste commands to run Phi 3 Medium 14B on your machine.
Run
ollama run phi3:mediumUpgrade options
Removes host-memory offload, which is usually the single biggest latency and throughput win.
Adds memory headroom for longer context windows and future model growth.
~$329 MSRP
Removes host-memory offload, which is usually the single biggest latency and throughput win.
Raises estimated decode speed by about 37%.
~$349 MSRP
Removes host-memory offload, which is usually the single biggest latency and throughput win.
Raises estimated decode speed by about 170%.
~$479 MSRP
Yes, RX 7700 XT 12GB can run Phi 3 Medium 14B with a C grade (Very compromised (needs ~1.1 GB host RAM)). Expected decode speed: 18.5 tok/s.
Phi 3 Medium 14B (14B parameters) requires approximately 13.7 GB of memory with Q4_K_M quantization.
The recommended quantization for Phi 3 Medium 14B is Q4_K_M, which balances quality and memory efficiency.
On RX 7700 XT 12GB, Phi 3 Medium 14B achieves approximately 18.5 tokens per second decode speed with a time-to-first-token of 10443ms using Q4_K_M quantization.
For coding workloads, Phi 3 Medium 14B on RX 7700 XT 12GB receives a C grade with 18.5 tok/s and 7K context.
On RX 7700 XT 12GB, Phi 3 Medium 14B can safely use up to 7K tokens of context. The model's official context limit is 128K, but available memory constrains the safe maximum.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/phi-3-medium-14b-on-rx-7700-xt-12gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview:
| 7K |
7.8 GB |
| Medium |
| B63 |
Q4_K_MBest for your GPU | 4 | 8.5 GB | Medium | B63 |
Q5_K_M | 5 | 10.1 GB | High | F0 |
Q6_K | 6 | 11.5 GB | High | F0 |
Q8_0 | 8 | 15.0 GB | Very High | F0 |
F16 | 16 | 28.7 GB | Maximum | F0 |
Remove offload with more accelerator memory. Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.