Can Phi-4 14B run on RTX 2080 Ti 11GB?

YES — With NVFP4

B66Good
Estimated from fit model

Phi-4 14B needs ~13.2 GB VRAM. RTX 2080 Ti 11GB has 11.0 GB. With NVFP4 quantization, expect ~28 tok/s.

Runtime: OllamaCapacity: OffloadBandwidth: MediumStack: BasicBottleneck: Host offload
Share:

Operating mode

Choose the run profile you care about

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.

Phi-4 14B at Q4_K_M needs 13.9 GB — too much for RTX 2080 Ti 11GB (11.0 GB). Runs at NVFP4 (13.2 GB) with medium quality. 3 quantization levels fit.
Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) 13.9 GB, exceeds 11.0 GB available
13.9 GB required11.0 GB available
126% VRAM needed

2.9 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

22.0 tok/s

TTFT

8792 ms

Safe context

4K

Memory

13.9 GB / 11.0 GB

Offload

20%

Memory breakdown

Weights8.5 GB
KV Cache3.1 GB
Runtime1.2 GB
Headroom1.1 GB

See how fast it feels

With memory offload — actual speed may be lower
See how fast it feelsPhi-4 14B on RTX 2080 Ti 11GB
1st promptCold start — includes initialization
>Solve: If a train travels at 60 mph for 2.5 hours, how far does it go?
Let me work through this step by step. Given information: - Speed = 60 mph (miles per hour) - Time = 2.5 hours Formula: Distance = Speed x Time Calculation: Distance = 60 mph x 2.5 h = 150 miles The train travels 150 miles. Double-check: at 60 mph the train covers 60 miles each hour. In half an hour it covers 30 miles. So in 2.5 hours: 60 + 60 + 30 = 150 miles. Confirmed.
2nd promptWarm — model ready, no init overhead
>What if the train stops for 20 minutes halfway?
The stop doesn't change the total distance covered while moving, but it affects total trip time. Breakdown: - First half: 1.25 hours at 60 mph = 75 miles - Stop: 20 minutes (no distance) - Second half: 1.25 hours at 60 mph = 75 miles Total distance: 150 miles (same) Total time: 2.5 h + 0.33 h = 2.83 hours Average speed: 150 / 2.83 = 53 mph The distance stays the same but average speed drops to 53 mph because of the stop.
Estimated: 22.0 tok/s decode · 8.8s TTFT (warm) · 55 tok/s prefill

What limits this setup

It fits through host-memory offload, and offload is the main reason performance drops.

CPU or host-memory offload is active

About 20% 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.

Older PCIe generation

PCIe 3.0 is workable, but it compounds the penalty when you offload heavily or try to scale across multiple cards.

Best improvement path

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.3 GB of extra host RAM just for the offloaded portion, before OS and other tools.

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatAVery compromised (needs ~0.9 GB host RAM)28.4 tok/s3714 ms4K
CodingFToo heavy22.0 tok/s8792 ms4K
Agentic CodingFToo heavy14.2 tok/s19779 ms4K
ReasoningFToo heavy22.0 tok/s10390 ms4K
RAGFToo heavy14.2 tok/s24724 ms4K

Quantization options

How Phi-4 14B (14B params) fits at each quantization level on RTX 2080 Ti 11GB (11.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
5.5 GB
LowA84
Q3_K_S
3
6.9 GB
LowA84
NVFP4Best for your GPU
4
7.8 GB
MediumA83
Q4_K_M
4
8.5 GB
MediumF0
Q5_K_M
5
10.1 GB
HighF0
Q6_K
6
11.5 GB
HighF0
Q8_0
8
15.0 GB
Very HighF0
F16
16
28.7 GB
MaximumF0

Get started

Copy-paste commands to run Phi-4 14B on your machine.

Run

ollama run phi4

アップグレードオプション

Phi-4 14Bを快適に動かすハードウェア

Frequently asked questions

Can RTX 2080 Ti 11GB run Phi-4 14B?

Yes, RTX 2080 Ti 11GB can run Phi-4 14B at NVFP4 quantization (Very compromised (needs ~1.3 GB host RAM)). The recommended Q4_K_M requires 13.9 GB which exceeds available memory, but at NVFP4 it needs only 13.2 GB. Expected decode speed: 28.2 tok/s.

How much VRAM does Phi-4 14B need?

Phi-4 14B (14B parameters) requires approximately 13.9 GB at Q4_K_M quantization. On RTX 2080 Ti 11GB, it fits at NVFP4 using 13.2 GB.

What is the best quantization for Phi-4 14B?

The recommended quantization is Q4_K_M, but on RTX 2080 Ti 11GB the best fitting quantization is NVFP4, which uses 13.2 GB.

What speed will Phi-4 14B run at on RTX 2080 Ti 11GB?

On RTX 2080 Ti 11GB, Phi-4 14B achieves approximately 28.2 tokens per second decode speed with a time-to-first-token of 6862ms using NVFP4 quantization.

Can RTX 2080 Ti 11GB run Phi-4 14B for coding?

For coding workloads, Phi-4 14B on RTX 2080 Ti 11GB receives a F grade with 22.0 tok/s and 4K context.

What context window can Phi-4 14B use on RTX 2080 Ti 11GB?

On RTX 2080 Ti 11GB, Phi-4 14B can safely use up to 5K tokens of context at NVFP4 quantization. The model's official context limit is 16K, but available memory constrains the safe maximum.

What should I upgrade first if Phi-4 14B feels slow on RTX 2080 Ti 11GB?

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.

See all results for RTX 2080 Ti 11GBSee all hardware for Phi-4 14B
Embed this result

Paste this snippet into any page to show a live fit card.

<iframe src="https://willitrunai.com/embed/phi-4-14b-on-rtx-2080-ti-11gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: