Ollama and LM Studio system requirements: minimum specs, RAM and VRAM by model size
By CanRun · Updated October 21, 2026
Ollama and LM Studio ask little of the PC itself: a supported OS, plus an AVX2 CPU for LM Studio on x64. The model you load decides how much RAM and VRAM you need; on the 8GB GeForce RTX 4060, Qwen3 8B fits fully on the GPU and Runs great. On the GeForce RTX 5060 Ti 16GB, gpt-oss-20b Runs great, and a public benchmark backs that speed. On the 24GB GeForce RTX 3090, the MoE model Qwen3.6 35B-A3B fits entirely on the GPU and Runs great.
What Ollama and LM Studio need to install
Ollama
Ollama's Windows page asks for Windows 10 22H2 or newer (Home or Pro), with NVIDIA driver 551.61 or newer on NVIDIA cards (Ollama docs, checked 2026-10-19). It installs into your home folder without administrator rights. Models need disk space of their own, many gigabytes for large ones; to move them, set OLLAMA_MODELS under "Edit environment variables for your account".
Ollama's hardware support page asks for an NVIDIA GPU with compute capability 5.0 or higher and driver 550 or newer; cards with compute capability 5.0–6.2 need driver 570 or newer (Ollama docs, checked 2026-10-19). The two pages give different minimum NVIDIA drivers. nvidia-smi shows yours; if it is older than either page asks, update it. The RTX 4060, RTX 3060, RTX 5060 Ti, RTX 3090 and RTX 5090 all appear in that page's compute capability table.
On a Mac, Ollama needs macOS Sonoma (14) or newer on an Apple M-series chip (CPU and GPU) or an Intel (x86) Mac; Intel Macs run on the CPU only (Ollama docs, checked 2026-10-19). None of these requirement sections lists a RAM or VRAM minimum. Ollama's quickstart recommends VRAM only for its example model, Gemma 4 E2B, and adds that with less VRAM Ollama can use system RAM but may answer more slowly. In CanRun's calculation, E2B at Q4_K_M fits fully on an 8GB card such as the RTX 4060.
LM Studio
For Windows PCs, LM Studio lists a CPU with AVX2 on x64 PCs, with at least 16 GB of RAM and 4 GB of dedicated VRAM recommended (LM Studio docs, checked 2026-10-19). AVX2 is required on x64, while the RAM and VRAM figures are recommendations, not minimums. It also runs on Windows on Arm (Snapdragon X Elite).
For Macs, it lists an Apple Silicon Mac (M1–M4; Intel Macs are not supported) on macOS 14.0 or newer, with 16 GB of RAM or more recommended (LM Studio docs, checked 2026-10-19). So an Intel Mac can run Ollama, on the CPU only, but not LM Studio.
AMD, Intel and Linux
Ollama runs supported Radeon cards through ROCm; its hardware support page has separate Windows and Linux lists, and the Windows list is shorter. Other GPUs, AMD and Intel included, run through Vulkan, which is on by default and comes with most Windows drivers. For some RX 6000-series (RDNA2) systems that may not expose ROCm on current Windows drivers, the Windows page recommends Vulkan.
LM Studio has separate llama.cpp runtimes for CUDA, Vulkan, ROCm and the CPU, and Ctrl+Shift+R opens the screen where you pick one.
On Linux, Ollama installs with a script, and the CUDA and ROCm drivers are separate, optional installs. LM Studio ships as an AppImage for x64 and ARM64. For Radeon and Arc cards, see AMD Radeon and Intel Arc for local LLMs: ROCm, Vulkan and what runs.
Minimum and recommended specs come from the model
Neither app decides how much memory you need; the model, its quant and the context do. Qwen3 8B, the smallest model here, needs 6.5 GB at 8k, which is already more VRAM than LM Studio's recommendation. Qwen3.6 35B-A3B needs 21.8 GB.
The table uses Q4_K_M, the usual 4-bit default, except for gpt-oss-20b in MXFP4, its native 4-bit format. Totals include the KV cache, the memory that holds the conversation. Three models are MoE: a mixture-of-experts model reads only a few experts per token, so experts that do not fit can sit in system RAM.
| Model | Parameters | Default quant, weights on the GPU | KV cache at 8k | Total at 8k |
|---|---|---|---|---|
| Qwen3 8B | 8.2B | Q4_K_M · 4.7 GB | 1.2 GB | 6.5 GB |
| Gemma 4 12B | 11.96B | Q4_K_M · 7.1 GB | 0.1 GB | 7.8 GB |
| Qwen3 14B | 14.8B | Q4_K_M · 8.6 GB | 1.3 GB | 10.5 GB |
| gpt-oss-20b | 20.9B (3.6B active) | MXFP4 · 11.5 GB | 0.2 GB | 12.3 GB |
| Gemma 4 26B-A4B | 26.54B (4B active) | Q4_K_M · 16.9 GB | 0.2 GB | 17.7 GB |
| Qwen3.6 35B-A3B | 35.95B (3B active) | Q4_K_M · 21.1 GB | 0.2 GB | 21.8 GB |
On a graphics card the OS keeps some VRAM (about 0.6 GB on a Windows display GPU). llama.cpp keeps the input embedding table in system RAM and does not load an MTP block by default, so the weights here are a little smaller than the file; a Mac counts the whole file.
Read "minimum" as the smallest card whose usable memory covers the 8k total. The OS keeps some VRAM on a display GPU, so an 8GB card has 7.4 GB to use. Qwen3 8B fits on 8GB. Gemma 4 12B needs more than that, so part of it goes to system RAM, but it fits fully on 12GB. Qwen3 14B fits on 12GB with little margin — check ollama ps.
gpt-oss-20b needs just over what a 12GB card can use, so some experts go to RAM there, and it fits fully on 16GB. Gemma 4 26B-A4B and Qwen3.6 35B-A3B keep experts in RAM on 16GB and fit fully on 24GB.
"Recommended" means the minimum plus room for the context you want, because the KV cache grows with it. How much VRAM do local LLMs need? 8–32 GB tiers (2026) works through that headroom tier by tier.
System RAM counts too, because spilled layers and experts live there. In CanRun's calculation, Qwen3.6 35B-A3B on an 8GB card does not fit with 16GB of system RAM, and at 32GB it fits with experts in RAM.
What to run on 8GB to 32GB cards
The summary counts our whole catalog by verdict on one card per tier, at 8k, f16 KV cache and 32GB of DDR5.
| Hardware | Memory | Runs great | Runs well | Runs slowly | Won't run | Largest model that fits on the GPU alone |
|---|---|---|---|---|---|---|
| GeForce RTX 4060 | 8 GB | 19 | 11 | 13 | 15 | Gemma 4 12B IQ4_XS |
| GeForce RTX 3060 12GB | 12 GB | 24 | 11 | 13 | 10 | Kanana 1.5 15.7B-A3B IQ4_XS |
| GeForce RTX 5060 Ti 16GB | 16 GB | 28 | 9 | 11 | 10 | Muse Glimmer 30B IQ4_XS |
| GeForce RTX 3090 | 24 GB | 44 | 4 | 0 | 10 | Qwen3.5 35B-A3B Q4_K_M |
| GeForce RTX 5090 | 32 GB | 48 | 1 | 1 | 8 | K2-Horizon MoVA 36B-A4B Q4_K_M |
The grid shows this guide's six models under the same conditions; the Qwen3 14B and gpt-oss-20b cells link to combo pages. Its legend sets one rule for MoE models: a model with experts in system RAM is capped at Runs well, because Runs great needs the whole model on the GPU.
| Hardware | Qwen3 8B | Gemma 4 12B | Qwen3 14B | gpt-oss-20b | Gemma 4 26B-A4B | Qwen3.6 35B-A3B |
|---|---|---|---|---|---|---|
| GeForce RTX 40608 GB | Runs great est. 30.5 tok/s26.9–34.2calibrated estimate ±12% | Runs well est. 21.9 tok/s17.6–26.3calibrated estimate ±20% | Runs well est. 36.9 tok/s25.9–48.0theoretical estimate ±30% gpt-oss-20b verdict on the GeForce RTX 4060 | Runs well est. 30.6 tok/s21.4–39.7theoretical estimate ±30% | Runs well est. 43.6 tok/s30.5–56.6theoretical estimate ±30% | |
| GeForce RTX 3060 12GB12 GB | Runs great est. 40.4 tok/s35.6–45.2calibrated estimate ±12% | Runs great est. 34.7 tok/s30.6–38.9calibrated estimate ±12% | Runs well est. 24.4 tok/s21.4–27.3calibrated estimate ±12% Qwen3 14B verdict on the GeForce RTX 3060 12GB | Runs well est. 63.9 tok/s44.8–83.1theoretical estimate ±30% gpt-oss-20b verdict on the GeForce RTX 3060 12GB | Runs well est. 40.7 tok/s28.5–53.0theoretical estimate ±30% | Runs well est. 54.7 tok/s38.3–71.1theoretical estimate ±30% |
| GeForce RTX 5060 Ti 16GB16 GB | Runs great est. 50.3 tok/s44.2–56.3calibrated estimate ±12% | Runs great est. 43.2 tok/s38.0–48.4calibrated estimate ±12% | Runs great est. 30.3 tok/s26.7–34.0calibrated estimate ±12% Qwen3 14B verdict on the GeForce RTX 5060 Ti 16GB | Runs great 111.6 tok/s8k estimate 104.3 tok/s (83.5–125.2, calibrated estimate ±20%)measured (1 run, 2k context) gpt-oss-20b verdict on the GeForce RTX 5060 Ti 16GB | Runs well est. 59.2 tok/s41.4–76.9theoretical estimate ±30% | Runs well est. 69.5 tok/s48.7–90.4theoretical estimate ±30% |
| GeForce RTX 309024 GB | Runs great est. 105.0 tok/s92.4–117.6calibrated estimate ±12% | Runs great est. 90.3 tok/s79.5–101.2calibrated estimate ±12% | Runs great 162.0 tok/s8k estimate 201.1 tok/s (160.9–241.3, calibrated estimate ±20%)measured (1 run, 2k context) gpt-oss-20b verdict on the GeForce RTX 3090 | Runs great 108.0 tok/s8k estimate 134.9 tok/s (108.0–161.9, calibrated estimate ±20%)measured (1 run, 32k context) | Runs great est. 164.6 tok/s131.6–197.5calibrated estimate ±20% | |
| GeForce RTX 509032 GB | Runs great 234.3 tok/s8k estimate 201.1 tok/s (177.0–225.2, calibrated estimate ±12%)measured (1 run, 512 context) | Runs great est. 172.9 tok/s152.2–193.7calibrated estimate ±12% | Runs great est. 121.3 tok/s106.7–135.8calibrated estimate ±12% Qwen3 14B verdict on the GeForce RTX 5090 | Runs great 282.3 tok/s8k estimate 338.9 tok/s (271.1–406.7, calibrated estimate ±20%)measured (1 run, 2k context) gpt-oss-20b verdict on the GeForce RTX 5090 | Runs great 216.1 tok/s8k estimate 210.4 tok/s (168.3–252.4, calibrated estimate ±20%)measured (2 runs, 512/8k context) | Runs great est. 229.8 tok/s183.9–275.8calibrated estimate ±20% |
Theoretical estimates (±30%) mark setups whose real speed varies a lot, such as MoE experts kept in system RAM. There we assume as many experts as fit stay on the GPU and only the rest sit in RAM.
8GB: 8B models, and MoE models with system RAM
On the RTX 4060, qwen3:8b Runs great. At 8k it has little margin — check ollama ps — but Ollama starts this card at 4k anyway. gemma4:12b puts a small part in system RAM and Runs well; the IQ4_XS route is in the LM Studio section.
On the same card, qwen3:14b puts part of its weights in system RAM and Runs slowly. A dense model reads every weight per token, so the part in system RAM slows every token.
Where the memory goes: Qwen3 14B (Q4_K_M) on the GeForce RTX 4060
- Weights
- 5.5 GB
- KV cache
- 1.3 GB
- Compute buffer
- 0.6 GB
- OS reserve
- 0.6 GB
- Weights in system RAM
- 3.5 GB
The three MoE models do better on this card. gpt-oss-20b, Gemma 4 26B-A4B and Qwen3.6 35B-A3B each Runs well with experts in RAM, all as theoretical estimates (±30%). Qwen3.6 35B-A3B needs 32GB of system RAM for this, not 16GB.
12GB: Gemma 4 12B and Qwen3 14B on the GPU
On the RTX 3060 12GB, gemma4:12b Runs great. qwen3:14b stays on the GPU and Runs well, with little margin — check ollama ps.
Our page for Qwen3 14B on the GeForce RTX 3060 12GB shows where longer contexts start to spill.
gpt-oss:20b needs just over what the card can use, so experts go to RAM and it Runs well, a theoretical estimate.
16GB: gpt-oss-20b on the GPU alone
On the RTX 5060 Ti 16GB, qwen3:14b Runs great. gpt-oss:20b fits on the GPU alone and Runs great, and its speed comes from a public llama.cpp benchmark (llama-bench, not an Ollama run).
gemma4:26b Runs well with experts in RAM, a theoretical estimate. The smaller IQ4_XS file fits fully, with about a gigabyte to spare, and Runs great:
ollama run hf.co/unsloth/gemma-4-26B-A4B-it-GGUF:UD-IQ4_XS
qwen3.6:35b also Runs well with experts in RAM, again as a theoretical estimate. Even its IQ4_XS file keeps experts in RAM on this card.
24GB and 32GB: the whole grid on the GPU
On both the GeForce RTX 3090 and the GeForce RTX 5090, each of the six grid models Runs great: Qwen3 8B, Gemma 4 12B, Qwen3 14B, gpt-oss-20b, Gemma 4 26B-A4B and Qwen3.6 35B-A3B. Here the standard gemma4:26b and qwen3.6:35b tags need no smaller quant.
What 32GB adds is room for context. In CanRun's calculation, Qwen3.6 35B-A3B stays fully on the GPU of the RTX 5090 even at 128k with an f16 KV cache. The Qwen3.6 35B-A3B page compares other cards.
Ollama tags and the context Ollama starts with
Ollama picks its default context length from the GPU memory it finds: 4k tokens below 24 GiB, 32k tokens from 24 to 48 GiB, and 256k tokens at 48 GiB or more (Ollama docs, checked 2026-09-29). Ollama's code puts the cut-offs slightly below the documented values, so 24GB cards such as the RTX 3090 start at 32k, as does the 32GB RTX 5090. The 8, 12 and 16GB cards start at 4k.
On the RTX 4060, Qwen3 8B fits fully at 4k, while Gemma 4 12B spills even at 4k. Raising Qwen3 8B to 16k with an f16 KV cache pushes part of its weights into system RAM, and a q8_0 KV cache keeps it on the GPU. Ollama quantizes the KV cache only when the server starts with OLLAMA_KV_CACHE_TYPE (f16, q8_0 or q4_0) and flash attention on; the setting applies to every model the server runs (Ollama docs, checked 2026-09-29). Ollama slow or forgetting your prompt? Context length defaults shows how to change the context.
On the RTX 3090, Qwen3.6 35B-A3B at Ollama's 32k fits on the GPU with little margin — check ollama ps, because the qwen3.6:35b tag also bundles a vision projector that CanRun does not count. At 64k with an f16 KV cache, some experts move to system RAM; with a q8_0 KV cache, 64k stays on the GPU. The table shows the speeds.
| Context | KV f16 | KV q8_0 | KV q4_0 |
|---|---|---|---|
| 4k | 21.7 GBRuns great est. 168.1 tok/s134.5–201.7calibrated estimate ±20% | 21.7 GBRuns great est. 169.8 tok/s135.8–203.8calibrated estimate ±20% | 21.7 GBRuns great est. 170.7 tok/s136.6–204.9calibrated estimate ±20% |
| 8k | 21.8 GBRuns great est. 164.6 tok/s131.6–197.5calibrated estimate ±20% | 21.8 GBRuns great est. 167.8 tok/s134.3–201.4calibrated estimate ±20% | 21.7 GBRuns great est. 169.7 tok/s135.7–203.6calibrated estimate ±20% |
| 16k | 22.1 GBRuns great est. 157.9 tok/s126.3–189.5calibrated estimate ±20% | 21.9 GBRuns great est. 164.1 tok/s131.3–196.9calibrated estimate ±20% | 21.8 GBRuns great est. 167.6 tok/s134.1–201.1calibrated estimate ±20% |
| 32k | 22.6 GBRuns great est. 146.1 tok/s116.9–175.3calibrated estimate ±20% | 22.2 GBRuns great est. 157.0 tok/s125.6–188.4calibrated estimate ±20% | 22.1 GBRuns great est. 163.6 tok/s130.9–196.3calibrated estimate ±20% |
| 64k | 23.5 GBRuns well est. 117.6 tok/s82.3–152.9theoretical estimate ±30% | 22.9 GBRuns great est. 144.6 tok/s115.7–173.5calibrated estimate ±20% | 22.6 GBRuns great est. 156.1 tok/s124.9–187.4calibrated estimate ±20% |
| 128k | 25.5 GBRuns well est. 84.6 tok/s59.2–110.0theoretical estimate ±30% | 24.2 GBRuns well est. 111.6 tok/s78.1–145.0theoretical estimate ±30% | 23.6 GBRuns well est. 131.2 tok/s91.8–170.6theoretical estimate ±30% |
| 256k | 29.4 GBRuns well est. 54.2 tok/s37.9–70.5theoretical estimate ±30% | 26.9 GBRuns well est. 76.6 tok/s53.6–99.6theoretical estimate ±30% | 25.5 GBRuns well est. 99.4 tok/s69.6–129.3theoretical estimate ±30% |
S = Runs great · A = Runs well · B = Runs slowly · F = Won't run
In a public report, an Ollama user on Windows 11 with an RTX 3090 ran gemma4:26b at a 32k context with flash attention off, and ollama ps showed 100% GPU. Gemma 4 26B-A4B Runs great on the RTX 3090, and the table below shows this report's speed. That build is now listed as gemma4:26b-a4b-it-q4_K_M; gemma4:26b points to a different one. CanRun also keeps 32k fully on the GPU.
What the tag pages listed when we checked (= marks the same build):
qwen3:8b=qwen3:8b-q4_K_M=qwen3:latest, andqwen3:14b=qwen3:14b-q4_K_M.gpt-oss:20b=gpt-oss:latest, Ollama's own MXFP4 build.gemma4:12bandgemma4:26b(=gemma4:26b-a4b) list MLX and llama.cpp variants. The llama.cpp one is Q4_K_M plus a vision projector and a small "draft" model.qwen3.6:35b=qwen3.6:35b-a3b=qwen3.6:latest, with the same two variants; the llama.cpp one is Q4_K_M plus a vision projector.- Bare
gemma4is the small E4B, which fits fully on the RTX 4060 in CanRun's calculation; name the size to get the 12B or 26B. Gemma 4 12B vs 26B-A4B vs 31B: differences, VRAM and which size fits your GPU covers E4B and E2B.
These are Ollama's own builds, not the Hugging Face GGUF files CanRun calculates. For the exact files, use the hf.co form:
ollama run hf.co/unsloth/Qwen3-8B-GGUF:Q4_K_M
ollama run hf.co/unsloth/Qwen3-14B-GGUF:Q4_K_M
ollama run hf.co/ggml-org/gpt-oss-20b-GGUF:MXFP4
ollama run hf.co/bartowski/Qwen_Qwen3.6-35B-A3B-GGUF:Q4_K_M
To match CanRun's 8k on Windows, use the context slider in the app's settings, or quit the app and start the server in PowerShell:
$env:OLLAMA_CONTEXT_LENGTH="8192"; ollama serve
On macOS and Linux, run OLLAMA_CONTEXT_LENGTH=8192 ollama serve. ollama ps then shows SIZE, PROCESSOR (100% GPU, 100% CPU or a CPU/GPU split) and CONTEXT; for a split you did not expect, see Ollama or LM Studio not using your GPU? Check the split and fix the offload.
LM Studio: memory estimate and GPU offload
LM Studio's model search (Ctrl+Shift+M) browses Hugging Face, so you can download the same GGUF repos CanRun calculates. Search for unsloth/gemma-4-12b-it-GGUF, for example.
| Quant | Quality group | Verdict | Speed | Memory |
|---|---|---|---|---|
| Q8_0 | Near-lossless | Runs slowly | est. 5.9 tok/s4.7–7.0calibrated estimate ±20% | 8.0 / 8.0 GB + 6.0 GB RAM |
| Q4_K_M | Good balance | Runs well | est. 21.9 tok/s17.6–26.3calibrated estimate ±20% | 8.0 / 8.0 GB + 0.4 GB RAM |
| IQ4_XS | Good balance | Runs well | est. 29.2 tok/s25.7–32.7calibrated estimate ±12% | 7.7 / 8.0 GB |
| UD-Q2_K_XL | Heavy loss | Runs great | est. 39.7 tok/s34.9–44.5calibrated estimate ±12% | 5.9 / 8.0 GB |
Gemma 4 12B's IQ4_XS file fits fully on the RTX 4060 and Runs well, with little margin — check ollama ps if you run it as ollama run hf.co/unsloth/gemma-4-12b-it-GGUF:IQ4_XS. UD-Q2_K_XL Runs great, but it is a Heavy loss quant, and LM Studio's own advice is to choose a 4-bit option or higher if your machine can run it. Q8_0 spills part of its weights and Runs slowly.
The load panel has sliders for context length and GPU offload. The memory estimate updates as you move them, and LM Studio warns you before loading if you are likely to run out of memory, a guardrail you can override. From the command line, without loading:
lms load --estimate-only <model> --context-length 8192 --gpu max
--gpu takes max, off or a value from 0 to 1; left unset, LM Studio picks the offload itself. For LM Studio, its own estimate is a better guide than CanRun's tables. Its documentation gives no default context, so set 8192 to match CanRun.
No graphics card, or a Mac
Without a GPU, the whole model sits in system RAM. Qwen3 8B fits in 16GB, and on dual-channel DDR5-5600 it lands at Runs slowly, the cap CanRun puts on every CPU-only setup. gpt-oss-20b does not fit in 16GB but fits in 32GB. Running LLMs without a GPU: CPU-only speed and how much RAM you need covers each RAM size.
On a Mac, CanRun counts the whole model as needed memory and about 70% of unified memory as usable by the GPU. On a 16GB M4, Qwen3 8B stays on the GPU and Runs well. gpt-oss-20b needs 12.9 GB on a Mac, so it does not fit on the 16GB M4 and needs the 24GB configuration. Both apps' MLX engines are outside CanRun's calculation. See Running local LLMs on a Mac (M4, M5): how much unified memory?.
How sure are these numbers?
Memory is calculated by formula from the GGUF files and model configs. Speeds are estimates with a band and a confidence label. Calibrated means ±12% for dense models fully on an NVIDIA or AMD card, and ±20% for MoE models, partial offload and other hardware. Theoretical (±30%) covers every cell with MoE experts in RAM on the 8, 12 and 16GB cards. Measured cells rest on a public benchmark: gpt-oss-20b on the 16, 24 and 32GB cards, Gemma 4 26B-A4B on the 24 and 32GB cards, and Qwen3 8B on the RTX 5090.
CanRun counts only the language-model file, not the vision projector and draft model that the gemma4 and qwen3.6 tags bundle. Ollama's builds also differ from CanRun's files, so check ollama ps. The tables assume Windows with the card driving the display, 32GB of DDR5 system RAM, and one model and one request at a time.
Verdict names in the text refer to 8k with an f16 KV cache. Qwen3 8B, Qwen3 14B and Qwen3.6 35B-A3B think by default and gpt-oss-20b always thinks, so their speed thresholds are 1.5× higher. Gemma 4 has thinking off by default. The thresholds:
How to read the verdicts
- Runs great
- Fully on the GPU at 20 tok/s or more
- Runs well
- Fully on the GPU at 8–20 tok/s; MoE experts in system RAM at 20 tok/s or more; or at least 90% on the GPU at 8 tok/s or more
- Runs slowly
- 2–8 tok/s; CPU-only; less than 90% on the GPU; or MoE experts in system RAM below 20 tok/s
- Won't run
- Does not fit, or under 2 tok/s
Where to go next
- Ollama vs llama.cpp vs LM Studio: same engine, different defaults: how the three apps differ.
- Ollama slow or forgetting your prompt? Context length defaults: setting Ollama's context and keeping it in VRAM.
- Running MoE models bigger than your GPU: gpt-oss-120b with system RAM: how MoE experts in system RAM work.
- KV cache explained: how context length eats VRAM: how the KV cache grows and what q8_0 saves.
- Korean open LLMs (EXAONE, Kanana, HyperCLOVA X SEED, Solar): hardware guide: Korean models and how to run them.
- Gemma 4 12B vs 26B-A4B vs 31B: differences, VRAM and which size fits your GPU: the Gemma 4 sizes side by side.
FAQ
What are Ollama's minimum requirements?
Ollama's requirement pages set OS and GPU-driver requirements, not a RAM or VRAM minimum, so the model you load decides the memory. On Windows it asks for Windows 10 22H2 or newer (Home or Pro), with NVIDIA driver 551.61 or newer on NVIDIA cards (Ollama docs, checked 2026-10-19). For scale, Qwen3 8B fits fully on an 8GB card, and without a GPU it fits in 16GB of system RAM.
What can I run on 8GB of VRAM?
Qwen3 8B fits fully on an 8GB card, and on the RTX 4060 it Runs great. On the same card, Gemma 4 12B puts a small part in system RAM and Runs well. gpt-oss-20b fits with experts in system RAM; its speed there is a theoretical estimate (see the grid).
Does LM Studio need a better PC than Ollama?
Not for the model: both run GGUF files on llama.cpp, so the weights and KV cache take the same memory in either app. The differences are platform rules and defaults. LM Studio needs AVX2 on x64 PCs and does not support Intel Macs, while Ollama starts at a 4k context on cards below 24GB. Ollama vs llama.cpp vs LM Studio: same engine, different defaults compares the rest.
How much system RAM do I need?
Enough for the part of the model that does not fit in VRAM, plus what the OS uses; CanRun's tables assume 32GB. With an 8GB card, gpt-oss-20b fits with 16GB. Qwen3.6 35B-A3B does not fit with 16GB and needs 32GB. Without a GPU the whole model sits in RAM, so gpt-oss-20b does not fit in 16GB but fits in 32GB.
Which model should I pull for Korean?
CanRun does not rank models for Korean, because it does not rate answer quality in any language; it shows fit and speed. Korean models such as EXAONE, Kanana and HyperCLOVA X SEED are covered in Korean open LLMs (EXAONE, Kanana, HyperCLOVA X SEED, Solar): hardware guide, with hf.co commands. Kanana 1.5 8B, for example, fits fully on the RTX 4060 with about a gigabyte to spare.
Sources
- Ollama: Windows: requirements, install,
OLLAMA_MODELS, AMD. - Ollama: macOS: macOS and chip requirements.
- Ollama: hardware support: NVIDIA requirements, AMD lists, Vulkan.
- Ollama: Linux: install script and optional drivers.
- Ollama: quickstart: the example model's VRAM recommendation.
- Ollama: context length: defaults, slider,
ollama ps. - Ollama FAQ: PROCESSOR column, KV cache type.
- Ollama: server/routes.go: default-context thresholds in code.
- Ollama library: qwen3 tags: Qwen3 aliases.
- Ollama library: gpt-oss tags: the MXFP4 build.
- Ollama library: gemma4 tags: E4B default, 26B builds.
- Ollama library: gemma4:12b: variants, projector, draft model.
- Ollama library: gemma4:26b: variants, projector, draft model.
- Ollama library: qwen3.6 tags: Qwen3.6 aliases.
- Ollama library: qwen3.6:35b: variants, vision projector.
- Hugging Face: Ollama: the
hf.coform. - LM Studio: system requirements: Windows, Mac and Linux.
- LM Studio: download a model: the 4-bit advice.
- LM Studio blog: load estimates: memory estimate and guardrail.
- LM Studio: lms load:
--estimate-onlyand--gpu. - LM Studio blog: Model Search: the shortcut.
- llama.cpp: gpt-oss benchmarks: the RTX 5060 Ti 16GB run.
- Ollama issue: gemma4 on RTX 3090: the 32k run, flash attention off.
Speeds on this page are estimates with an error band and a confidence label, or public measurements with their source. Verdicts assume the setup stated with each table.