AI Prompt Generator
Turn a rough idea into a structured prompt that gets a usable answer.
Work out how much GPU memory a local LLM needs to run or fine-tune.
Read these from the model's config.json: num_hidden_layers, num_key_value_heads and head_dim (or hidden_size ÷ num_attention_heads).
The GPU VRAM Calculator works out how much video memory a local language model needs — weights at your chosen quantization, KV cache from the real layer and attention-head counts, and runtime overhead — for inference or QLoRA, LoRA and full fine-tuning, and checks it against common GPUs and Macs.
Whether a local model runs on your card comes down to three numbers: the size of the weights at the quantization you choose, the KV cache that grows with every token of context, and the runtime overhead. Guess wrong and the model either refuses to load or spills into system RAM and slows to a crawl.
Pick a model — Llama, Qwen, Mistral, Mixtral, Gemma, Phi or Command R — or enter any parameter count, then choose the weights precision from F16 down to 2-bit GGUF quants, the KV cache precision, the context length and the number of parallel sequences. The breakdown shows where every gigabyte goes, using the real architecture — layers, key-value heads and head size — so grouped-query attention is accounted for rather than guessed.
Switch to QLoRA, LoRA or full fine-tuning to add gradients, optimizer states and activations. A table then checks the result against common cards from the RTX 3060 to the H100 and Apple Silicon Macs, and for inference shows the longest context each card can hold beside the weights.
Uses layers, key-value heads and head size, so grouped-query attention is counted correctly.
From F16 down to IQ2_XS, with KV cache at F16, Q8_0 or Q4_0.
QLoRA, LoRA and full fine-tuning add adapters, gradients, optimizer states and activations.
RTX 3060 to H100 and Apple Silicon, marked fits, tight or needs more cards.
Shows the longest context each GPU can hold beside the weights.
Pick from the list, or enter the parameter count and architecture from config.json.
Q4_K_M is the usual choice for running locally; F16 for full quality.
Context length and parallel sequences decide the size of the KV cache.
See which cards fit, which are tight, and the longest context each can handle.
About 6 GB at Q4_K_M with an 8K context, and about 17 GB at F16. A 12 GB card runs an 8B model comfortably at 4 or 5 bits.
Around 43 to 45 GB at Q4_K_M with an 8K context, which means two 24 GB cards, a 48 GB card, or a Mac with 64 GB of unified memory.
Stored attention keys and values for every token in the context, kept so earlier tokens are not recomputed. It grows linearly with context length and can exceed the size of the weights at long contexts.
Yes, by offloading some layers to system RAM in llama.cpp or Ollama, but generation slows sharply. A smaller quant or a smaller model is usually the better trade.
Roughly the 4-bit weights, plus about one percent of parameters for adapters and their optimizer states, plus activations that grow with sequence length. An 8B model is typically trainable on a 16 to 24 GB card.
What people who use the GPU VRAM Calculator for LLMs think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the GPU VRAM Calculator for LLMs. It takes half a minute and no account.
Write the first reviewTurn a rough idea into a structured prompt that gets a usable answer.
Generate robots.txt rules to block GPTBot, ClaudeBot, CCBot and other AI crawlers.
Read the prompt, seed and settings saved inside an AI-generated PNG.
Work out what an AI feature will cost per call, per day and per month.
Compare GPT, Claude, Gemini, DeepSeek and Llama by price, context and monthly cost.
Build a structured system prompt for a chatbot, assistant or custom GPT.
Clean up a pasted chat log into a tidy transcript, Q&A pairs, JSON or CSV.
Fill a prompt template from spreadsheet rows and get one prompt per row.