Start with the machine
The model choice begins with RAM, VRAM, runtime, quantization, and whether the computer can stay usable while the model answers.
2026-07-13
This page is maintained as a hardware-specific install path, not a static model catalog.
Latest maintenance note
Added a dedicated RTX 5080 guide instead of routing every GPU user to the RTX 4090 page.
Set the default picker to 64 GB RAM and 16 GB VRAM.
Clarified that this is a hardware-fit install path, not an official GPU vendor result.
Local LLM choices are easy to overstate. AI Jupyter treats a hardware page as a practical install order: what to try first, what to avoid, when to step down, and when the job should move to a stronger machine or hosted API.
Start with the machine
The model choice begins with RAM, VRAM, runtime, quantization, and whether the computer can stay usable while the model answers.
Separate load from comfort
A model that loads once is not automatically a good daily choice. The page favors models that still feel practical with normal apps open.
Prefer realistic limits
Large context, repository-wide coding, and long-document tasks are treated as separate workload limits instead of being hidden inside a single score.
Link to real test records
Where AI Jupyter has a real machine test, the guide links to screenshots, raw notes, and test JSON so the model pick can be checked.
The most useful local LLM choice is rarely the biggest model in the list. This profile turns the hardware tier into a practical decision: what to try first, what it is good for, what not to force, and when to move up.
Start with
16GB VRAM is the hard constraint. Use the first installs to prove speed, context length, and driver/runtime compatibility before chasing larger models.
Use it for
Good for private chat, coding tests, local API experiments, and comparing open models against hosted models with lower latency.
Do not force
A model that loads once is not enough. The guide favors models that leave room for context, tools, and repeated prompts.
Upgrade when
Move up when you need larger models comfortably, multiple models loaded, batch serving, shared access, or production-style uptime.
Targets 16 GB VRAM, the main constraint for RTX 5080 local LLM work.
Prioritizes 7B to 14B and selected 24B or MoE models models before treating larger models as stretch tests.
Uses VRAM fit, workload match, adoption signals, and install practicality rather than a single synthetic score.
Local model choice usually changes after one of three checks: measured hardware comfort, API fallback cost, or whether the task actually needs a stronger hosted model.
Use the measured 8GB VRAM boundary before deciding how far 16GB VRAM can stretch.
Use this when code quality, repository fixes, or agent behavior matters more than offline control.
Estimate when a hosted text model is cheaper, faster, or more reliable than forcing the local machine.
Good fit
Be careful
You need larger models to run comfortably instead of as compromise tests.
You want multiple models loaded, batch serving, shared access, or production uptime.
Long context, vision, or agent workloads push the GPU into memory pressure.
Start with 7B to 14B and selected 24B or MoE models models before pushing context length.
Use CUDA-aware runtimes such as Ollama, LM Studio, llama.cpp, or vLLM when the model supports them.
Watch VRAM during longer prompts because context and vision inputs can exhaust memory after the base model loads.
Hardware FAQ
The best choice depends on workload. This page defaults to 16 GB VRAM, then sorts models by whether they fit, how well they match the selected work, adoption signals, and remaining hardware headroom.
Start with 7B to 14B and selected 24B or MoE models models. Treat 32B dense models, long context, or vision-heavy workloads as a careful test until you have checked quantization, context length, runtime speed, and your real prompts.
Usually not comfortably as a daily default. It may be possible with aggressive quantization or CPU offload, but smaller models are normally faster and more reliable for interactive work.
Yes. System RAM supports the runtime, browser, IDE, vector store, model cache, and any CPU-side work. A GPU can have enough VRAM while the desktop still feels constrained.
No. It is a hardware-fit guide, not an official NVIDIA, Ollama, or LM Studio result. Use it to choose what to test first, then validate on your own machine.
More local LLM hardware guides
Practical local LLM picks for 8GB laptops and CPU-only machines.
Balanced local LLMs for 16 GB laptops and MacBooks.
Stronger local LLMs for 32 GB RAM systems.
Top-end single-GPU local LLM picks for 32 GB VRAM RTX 5090 builds.
Balanced 16 GB VRAM local LLM picks for RTX 5070 Ti machines.
12 GB VRAM local LLM picks for RTX 5070 desktop builds.
16 GB VRAM local LLM picks for RTX 5060 Ti 16GB systems.
8 GB VRAM local LLM picks for RTX 5060 Ti 8GB systems.
8 GB VRAM local LLM picks for RTX 5060 systems.
High-performance local LLMs for 24 GB VRAM RTX 4090 builds.
16 GB VRAM local LLM picks for RTX 4080 and RTX 4080 Super systems.
16 GB VRAM local LLM picks for RTX 4070 Ti Super desktops.
12 GB VRAM local LLM picks for RTX 4070 Ti builds.
12 GB VRAM local LLM picks for RTX 4070 and RTX 4070 Super systems.
16 GB VRAM local LLM picks for RTX 4060 Ti 16GB systems.
8 GB VRAM local LLM picks for RTX 4060 Ti 8GB systems.
8 GB VRAM local LLM picks for RTX 4060 systems.
24 GB VRAM local LLM picks for RTX 3090 workstations.
10 GB VRAM local LLM picks for RTX 3080 systems.
8 GB VRAM local LLM picks for RTX 3070 systems.
8 GB VRAM local LLM picks for RTX 3060 Ti systems.
12 GB VRAM local LLM picks for RTX 3060 systems.
MacBook-friendly local LLMs for Apple Silicon unified memory.