RunLocal

Hardware-aware · Open source · Updated weekly

Local AI: run open source models on your own computer.

The hub for local LLMs, install guides and a hardware picker.

You can run AI models like the ones behind ChatGPT or Claude directly on your laptop or desktop, without sending your data anywhere. RunLocal shows you which open source model to choose for your hardware, which free software to install (Ollama, LM Studio, llama.cpp), and how to get started in about ten minutes. No prior knowledge required.

New to this? Start with the glossary for plain-language definitions, or jump straight to the hardware picker to see what your computer can run.

Models worth your disk space

A short list, opinionated. Full catalog in the directory.

See all models →

Qwen 3.8

Alibaba (Qwen team) · China

2026
License
Apache 2.0 on the 27B; custom Qwen licence on the 2.4T MoE
Context
262k tokens
Sizes
27B dense · 2.4T-A95B MoE
CodingMultimodal workflowsMultilingualLocal workstations

August 2026, and the most-liked open-weight release of the summer. The 27B is dense, Apache 2.0, natively multimodal, and had GGUF builds from unsloth and bartowski within days — which makes it the current default for a 24 GB card. The 2.4T MoE sibling is frontier-scale and carries a different licence.

DeepSeek V4 Flash

DeepSeek AI · China

2026
License
MIT
Context
1M tokens (65k native, extended 16x with YaRN)
Sizes
304B-A13B MoE (284B before the DSpark decoder)
Agentic codingLong documentsHigh-memory workstations

The most-downloaded open-weight model on the Hub, and the largest entry here that a single machine can still load. 256 routed experts with 6 active per token means roughly 13B parameters fire on any given token, so it answers far faster than 304B suggests. The 0731 checkpoint supersedes the June preview and carries a DSpark speculative-decoding module, which is where the extra weights over the 284B base come from. Weights ship natively in FP8, so a Q8 build costs only about 7 GB more than Q4.

Qwen 3.6

Alibaba (Qwen team) · China

2026
License
Apache 2.0 on official open-weight checkpoints
Context
262k native on 27B; long-context extensions available
Sizes
27B dense · 35B-A3B MoE · additional large MoE variants
CodingMultimodal workflowsMultilingualLocal workstations

The previous open-weight Qwen generation, still widely deployed and the base for most community quantization work, including the 1-bit and ternary Bonsai builds. Qwen 3.8 supersedes it for new installs.

Qwen 3.5

Alibaba (Qwen team) · China

2026
License
Apache 2.0
Context
262k native; selected variants support longer contexts
Sizes
2B · 9B · 27B · 35B-A3B MoE · 122B-A10B MoE · 397B-A17B MoE
MultimodalMultilingualCodeCost-sensitive deployments

Released in 2026. The smaller checkpoints remain excellent local choices when Qwen 3.6 is too large.

Snapshot · Sep 14, 2026

Trending on Hugging Face

Auto-curated from the Hugging Face Hub by a weighted mix of downloads, community likes and recency. Refreshes weekly via GitHub Action. License tier is a quick visual hint, not legal advice.

GLM-5.2

zai-org

Permissive

MIT

Downloads
947.1k
Likes
5.1k
Updated
12 days ago
View on HF →score 0.87

DeepSeek-V4-Flash-0731

deepseek-ai

Permissive

MIT

Downloads
4.5M
Likes
4.0k
Updated
1 months ago
View on HF →score 0.86

Qwen3.8-27B-Uncensored-GGUF

JonathanColetti · 27B

Permissive

Apache 2.0

Downloads
2.9M
Likes
1.1k
Updated
16 days ago
View on HF →score 0.83

GLM-5.3

zai-org

Open weight

Custom license

Downloads
712.6k
Likes
1.8k
Updated
10 days ago
View on HF →score 0.82

Qwen3.8-27B-OBLITERATED

OBLITERATUS · 27B

Permissive

Apache 2.0

Downloads
1.2M
Likes
1.2k
Updated
20 days ago
View on HF →score 0.81

Ternary-Bonsai-27B-gguf

prism-ml · 27B

Permissive

Apache 2.0

Downloads
644.3k
Likes
1.3k
Updated
13 days ago
View on HF →score 0.80

MiniCPM5-2B

openbmb · 2B

Permissive

Apache 2.0

Downloads
206.8k
Likes
1.4k
Updated
2 days ago
View on HF →score 0.79

DeepSeek-V4-Pro

deepseek-ai

Permissive

MIT

Downloads
610.6k
Likes
5.6k
Updated
2 months ago
View on HF →score 0.79

The tools that actually run them

Runtimes, GUIs and inference servers, with their real trade-offs.

See all tools →

Ollama

Runtime

MIT

The fastest way to get a local LLM running with one command.

macOSLinuxWindows

Strengths

  • One-line install, one-line model pulls
  • Built-in OpenAI-compatible API on localhost:11434
  • Active model library with 4,500+ tagged variants

Trade-offs

  • Less raw throughput than vLLM under heavy concurrent load
  • Configuration is opinionated; advanced tuning means dropping into llama.cpp anyway

llama.cpp

Runtime

MIT

Maximum control and the broadest hardware coverage in the open ecosystem.

macOSLinuxWindowsAndroidiOS

Strengths

  • Runs almost anywhere: CUDA, ROCm, Metal, Vulkan, CPU-only
  • Tight GGUF quantization control
  • Reference implementation behind most desktop LLM tools

Trade-offs

  • Command-line first; the UX assumes you read READMEs
  • Quantization options multiply quickly, easy to pick the wrong one

DwarfStar (ds4)

Runtime

MIT

Running DeepSeek V4 Flash at usable speed on one 128 GB machine, and deliberately little else.

macOSLinux

Strengths

  • Asymmetric 2-bit quantization of the routed MoE experts only, which is what puts a 300B-class model inside 128 GB
  • Metal, CUDA and ROCm backends, with benchmarks published per machine rather than as a single headline number
  • On-disk KV cache, so a long session survives a restart

Trade-offs

  • Wants 96-128 GB of RAM to hold the Q2 build in memory, 256 GB or more for Q4; below that you are on the slower SSD-streaming path
  • Runs one model family on purpose: DeepSeek V4 Flash and PRO, plus GLM 5.2
  • The author calls it beta quality and the code changes fast
Visit project →No guide yet

LM Studio

GUI

Proprietary

Browsing, comparing and chatting with local models in a desktop GUI.

macOSLinuxWindows

Strengths

  • Polished chat UI with side-by-side model comparison
  • Built-in Hugging Face model browser
  • Local OpenAI-compatible API server with one click

Trade-offs

  • Closed source; the engine is llama.cpp but the shell is not
  • Less scriptable than CLI-first tools

Install guides

Latest writing

Why bother running AI locally?

The big cloud services are easier to start with. But there are real reasons to do it yourself. Three of them.

Your data stays with you

What you type and what the model answers never leave your computer. Handy when you are working with personal notes, client documents, internal code, or anything you would not paste into a public website.

It works even when the cloud does not

The model file lives on your disk. If the company that made it shuts down, raises prices, or simply changes its terms, your setup keeps working. The model you download today still runs in 2030 if your computer does.

No surprise bills

Cloud AI charges per use. Local AI costs you the price of your computer, plus electricity. After the first month, the marginal cost of an extra question is essentially zero.