Can an RTX 3070 run Qwen2.5 14B Instruct?

No

Only barely. It loads at IQ2_XXS, which compresses the weights far enough to visibly degrade the model, so the honest answer is that this pairing does not work.

The numbers

Qwen2.5 14B Instruct has 14.77 billion parameters across 48 layers. The GeForce RTX 3070 has 8 GB of VRAM at 448 GB/s, of which about 7.2 GB is left for a model once the operating system has taken its share.

QuantisationTotal neededFitsSpeed
Q8_0 17.03 GB no
Q6_K 13.69 GB no
Q5_K_M 12.2 GB no
Q4_K_M 10.72 GB no
IQ4_XS 9.72 GB no
Q3_K_M 9.14 GB no
IQ3_XXS degraded 7.68 GB no
Q2_K degraded 8.17 GB no
IQ2_XXS degraded 5.96 GB yes 72.9 t/s

1 of the 9 levels fit. Levels marked degraded are listed for completeness, not as advice.

What to do instead

The straightforward answer is a smaller model from the same family. These do fit on a GeForce RTX 3070, at a quantisation worth using:

Shortening the context window will not rescue this one: at 4k it still wants 9.81 GB against 10.72 GB at 8k, because the weights rather than the cache are what fill the card. The gap here is too large for settings to close.

Or the hardware that does run it

The cheapest device we track that runs Qwen2.5 14B Instruct at a quantisation worth using is the GeForce RTX 2060 12GB, around $160 used , running it at Q4_K_M at about 28.1 tokens per second. Check the current price (affiliate link; indicative price reviewed 2026-09-01). Compare every option.

See how fast it feels

GeForce RTX 3070 running Qwen2.5 14B Instruct at IQ2_XXS

Wait for the first word491 ms
Then writes at72.9 tok/s
Whole answer2.9 s

YouWhy does my model use more memory when the conversation gets longer?

Model

Because of the KV cache. Every token you send leaves behind a key and a value vector in each layer of the model, and those stay in memory for as long as the conversation lasts.

The weights are a fixed cost: load a 4-bit 8B model and that is about 4.8 GB, whether you write one word or ten thousand. The cache is the part that grows, and it grows in a straight line with the number of tokens in the window.

How steeply depends on the model's attention design. With grouped-query attention, several query heads share one key-value pair, which cuts the cache by that ratio. Without it, every head keeps its own, and a long context can cost more memory than the weights themselves.

If you are short on memory, the first thing to try is lowering the context window in your runtime, not the quantisation.

Simulated from our estimate at a 512-token question, not a recording. Assumes nothing else is competing for the GPU. The same answer on RTX 4090 at Q8_0 would take about 3.5 s.

Keep going

Everything the GeForce RTX 3070 runs, the full breakdown for Qwen2.5 14B Instruct, or check a different pairing in the calculator.