LLMBOTTLENECK.COM
DeepSeek / deepseek_v4

DeepSeek-V4-Pro

1.6T total · 49B active parameters, routing 6 of 384 experts per token.

The official DeepSeek V4 card declares 1.6T total and 49B activated parameters. The native FP4/FP8 checkpoint's safetensors element total is kept as source metadata but is not used as an unqualified logical count. Open the official parameter note ↗

Open in the calculator →

Architecturepublished data
Quick answer
DeepSeek-V4-Pro needs about 971.2 GB at Q4_K_M — the format most people download — with 8,192 tokens of context. None of the 18 common devices listed below holds it entirely at this setting. No hardware for it? Rent a GPU that runs it, priced live.

Sized at 8,192 tokens of context with the whole model in device memory, across 18 common devices. Speeds are estimates, not benchmarks.

Weight-file size by format

FormatSizeRangeBasis
FP163214.7 GB3186.1 GB – 3243.3 GBreconstructed size
Q8_01708.1 GB1692.9 GB – 1723.3 GBreconstructed size
Q6_K1318.9 GB1307.2 GB – 1330.7 GBreconstructed size
Q5_K_M1139.3 GB1129.2 GB – 1149.5 GBreconstructed size
Q5_01105.6 GB1095.8 GB – 1115.5 GBreconstructed size
Q4_K_M970.3 GB961.6 GB – 978.9 GBreconstructed size
Q4_0904.9 GB896.8 GB – 912.9 GBreconstructed size
Q3_K_M791.8 GB733.3 GB – 850.3 GBreconstructed size
Q2_K580.8 GB555.3 GB – 606.3 GBreconstructed size

A file size is not the memory a run needs: the KV cache and the runtime reserve come on top, and the calculator adds both.

What the labels mean
published data
Read from a published source — a file's byte count, a model's configuration or a manufacturer's specification — or exact arithmetic on such values. Not a measurement on a machine.
reconstructed size
Weight size reconstructed from the pinned architecture, because no published file exists.
size range
Only a lower and an upper bound are claimed for this weight size.

Hardware ladder

Q4_K_M at 8,192 tokens · 0 of 18 devices hold it entirely
DeviceMemoryVerdictDecodeCalculator
NVIDIA GeForce RTX 5070971.2 GB of 12 GB61 layers on system RAM~1.2 tok/s with offloadOpen →
AMD Radeon™ RX 9070 XT971.2 GB of 16 GB61 layers on system RAM~1.2 tok/s with offloadOpen →
NVIDIA GeForce RTX 4080971.2 GB of 16 GB61 layers on system RAM~1.2 tok/s with offloadOpen →
NVIDIA GeForce RTX 5080971.2 GB of 16 GB61 layers on system RAM~1.2 tok/s with offloadOpen →
NVIDIA GeForce RTX 5070 Ti971.2 GB of 16 GB61 layers on system RAM~1.2 tok/s with offloadOpen →
NVIDIA GeForce RTX 5060 Ti 16GB971.2 GB of 16 GB61 layers on system RAM~1.2 tok/s with offloadOpen →
NVIDIA GeForce RTX 4090971.2 GB of 24 GB60 layers on system RAM~1.3 tok/s with offloadOpen →
AMD Radeon™ RX 7900 XTX971.2 GB of 24 GB60 layers on system RAM~1.3 tok/s with offloadOpen →
NVIDIA GeForce RTX 3090971.2 GB of 24 GB60 layers on system RAM~1.3 tok/s with offloadOpen →
NVIDIA GeForce RTX 5090971.2 GB of 32 GB60 layers on system RAM~1.3 tok/s with offloadOpen →
NVIDIA RTX 6000 Ada Generation971.2 GB of 48 GB59 layers on system RAM~1.3 tok/s with offloadOpen →
Apple M4 Pro971.2 GB of 64 GBdoes not fitnot calibratedOpen →
Apple M5 Pro971.2 GB of 64 GBdoes not fitnot calibratedOpen →
AMD Ryzen AI Max+ 395 with Radeon 8060S971.2 GB of 128 GBdoes not fitnot calibratedOpen →
Apple M3 Max971.2 GB of 128 GBdoes not fitnot calibratedOpen →
Apple M4 Max971.2 GB of 128 GBdoes not fitnot calibratedOpen →
NVIDIA DGX Spark971.2 GB of 128 GBdoes not fitnot calibratedOpen →
Apple M2 Ultra971.2 GB of 192 GBdoes not fitnot calibratedOpen →

Decode is a calibrated estimate from the published calibration; capacity is the manufacturer's published ceiling, not guaranteed free memory. Fitting in memory is not the same as loading: whether the runtime and version you have supports this architecture and format on that machine has not been tested here. Offloaded rows assume there is enough system RAM for the overflow — the calculator checks that against the RAM you declare. Each “Open” link keeps this model, format and context.

Run it in the cloud

Rent a GPU that runs DeepSeek-V4-Pro

Every rentable machine that holds the whole model, from Vast.ai and RunPod, with this site's speed estimate for each and the provider's own price, read live. Cheapest first; sort by cost per token or speed instead, or switch the format.

Prices · 18:30 UTC, 22 Sept
1 configuration in stock · 4 out of stock
MachineSpeedPer hourPer M tokensWhereRent
8× H2001128 GBrecommendedcheapestbest valuefastest~524 tok/sFaster than you read$26.52$14.05Vast.aiMarketplace · 99.3% reliableRent on Vast.ai
No GPU at all

Use DeepSeek-V4-Pro by the token

For one person chatting, that is about 7.8× cheaper than the best-value rented card above ($14.05 per million tokens). A rented GPU pays off when you keep it busy — many requests batched together, long agent runs — or when the data must stay on a machine you control, or the exact file you want is not served anywhere.

First time renting a GPU? How it works, in four steps
  1. Create an account and add credit. Both providers are prepaid: $10 is enough to try any card on this page for hours. A new RunPod account that arrives through a referral link gets a one-time $5 credit when it first adds $10.
  2. Pick the card and the count shown here, and a template: llama.cpp or vLLM for an OpenAI-compatible API, or one with a web chat if you only want to talk to the model. “How to launch it” below gives the exact image and command.
  3. Wait for the download. The weights are fetched on the machine; tens of gigabytes take a few minutes on a data-centre connection. You pay by the second from the moment it starts.
  4. Stop it when you are done. A running machine bills even when idle. A stopped one costs nothing per hour, though its disk is usually still billed until you delete it.
How to launch it

No Q4_K_M file of DeepSeek-V4-Pro is catalogued here, so there is no exact command to vouch for. Start the machine from the llama.cpp server image ghcr.io/ggml-org/llama.cpp:server-cuda and point -hf at a Q4_K_M build from the publisher or a quantizer you trust — search Hugging Face for one. Check its file size against the memory figure on this page before you rent.

Every machine holds the whole model at Q4_K_M and 8,192 tokens of context, no offload. Speeds are this site’s single-stream decode estimates; prices are what each provider’s own API quoted, on-demand, for the whole machine. Vast hosts below 98% measured reliability are left out.

Referral links Vast.ai, RunPod and Novita pay us a share of what you spend if you sign up through these buttons. It costs you nothing, and it never decides an order or a recommendation: both are computed from the live price and the speed, and options that pay us nothing are listed and recommended on the same terms. How we rank

Buying a card instead, or paying by the token? Compare a year of DeepSeek-V4-Pro three ways →

Under the hood

Architecture, read from the publisher’s file

The numbers every figure above is computed from, with the file they came from.

Architecture

✓ Architecture read from the published config.json

Retrieved 2026-09-01 at pinned commit b5968e9190ef; the native packed/fused checkpoint metadata is not used as a logical parameter total.

Architecture
deepseek_v4
Layers
61
Hidden size
7,168
Attention heads
128
KV heads
1
Head dimension
512
Vocabulary
129,280
Context ceiling
1,048,576
Sliding window
128
RoPE theta
10,000
Experts
384
Experts / token
6
Expert width
3,072
Shared experts
1

Where the memory goes

tokenembedding× 61 decoder blocksGrouped-query attention128 query · 1 KV headswindow 128Routed experts6 of 384 per tokenall residentoutputprojectiongrows with contextcapacity ≠ traffic

Grouped-query attention shares each key/value head across 128 query heads, so the KV cache is 1% of what multi-head attention would need at the same context.

Open the exact official config.json ↗

More from DeepSeek

deepseek-coder-6.7b-instructdeepseek-coder-7b-instruct-v1.5DeepSeek-Coder-V2-Lite-InstructDeepSeek-R1DeepSeek-R1-0528DeepSeek-R1-0528-Qwen3-8BDeepSeek-R1-Distill-Llama-70BDeepSeek-R1-Distill-Llama-8B

Use this answer in your own product

As JSON, from the API
curl -s https://llmbottleneck.com/v1/analyze \
  -H "Authorization: Bearer $LLMB_KEY" -H "content-type: application/json" \
  -d '{"model":"deepseek-ai-deepseek-v4-pro","quantization":"Q4_K_M","context":8192,"hardware":"nvidia-geforce-rtx-4090"}'

Same engine, same evidence, every field sourced. Free key in one step →

On your page, as a widget
<script src="https://llmbottleneck.com/widget.js"
  data-model="deepseek-ai-deepseek-v4-pro" data-quantization="Q4_K_M"
  data-hardware="nvidia-geforce-rtx-4090" data-context="8192"></script>

No key needed. Unbranded, with your own buy button, on Pro and Business →

Citing this page

LLM Bottleneck. “DeepSeek-V4-Pro VRAM and hardware requirements.” Architecture from deepseek-ai/DeepSeek-V4-Pro at revision b5968e9190ef, retrieved 2026-09-01. https://llmbottleneck.com/models/deepseek-ai-deepseek-v4-pro

Every figure above is either the published value or a reconstruction whose measured error is on the accuracy page.

llmbottleneck
catalogue 2026-10-03models 327devices 135