AI and models · Edition No. 55 · 19 Oct 2026

ggml-org/llama.cpp

A C and C++ library and command-line tool for running language models locally.

← AI and modelsRead the whole edition →
llama.cpp: models on your own machine. The engine most local model apps are built on.

131.7k stars · MIT · v0.7.0 (2026-10-15) · Track this in Scout

A C and C++ library and command-line tool for running language models locally.

▶Repo detailsthe review · specs · pros & cons · install

What it does

It loads a model stored in the GGUF file format and runs it on the processor, with optional help from a graphics card. There is a command-line tool for a single prompt or an interactive chat, and a local server that answers over HTTP with a familiar request format, so existing client code can point at it. Quantisation is the central idea: a model's numbers are stored at reduced precision, which cuts the memory needed by a large factor in exchange for some accuracy, and several levels are available. It supports Apple Silicon, CUDA, Vulkan, ROCm and plain processors, and it will split a model between graphics memory and main memory when the card is too small. A library interface lets other programs embed it, which is what most of the local-model applications do. It does not have a model catalogue or a graphical interface, it does not train or fine-tune models, and it will not choose a model for you.

Why it matters

Who it suits. Anyone who wants a language model running on hardware they control, with no outside service in the path, and who is willing to read about file formats and memory. Also anyone building a product that needs local inference inside it, since the library is the point. Skip it if you want to type one command and chat, because the friendlier wrappers exist for exactly that reason.

Verdict. This is the foundation, and that is both the recommendation and the warning. Edition 42 covered ollama/ollama, Edition 52 covered janhq/jan and mudler/LocalAI, and the easy experience those give you is built on the work in this repository. Come here when you want control the wrappers do not give you: a specific quantisation, a build tuned to your hardware, or an embedded library rather than a background service. The project moves very fast, with tagged builds most days, and the newest tag could not be read from the releases page today — code was last pushed on 5 October 2026, so currency is not in question. Build from a tag rather than from the tip if you want the same behaviour next month. For serving many users at once on server graphics cards, vllm-project/vllm is the better-suited engine.

Stars131.7k
LicenceMIT
Latestv0.7.0 (2026-10-15)
Good
  • Runs on ordinary hardware, including machines with no graphics card at all.
  • Quantisation levels let you trade accuracy for memory in steps you choose.
  • A real library, so other software can embed it rather than shelling out to it.
Watch for
  • You find, download and choose the model file yourself. That is the part beginners get wrong.
  • It changes daily, and build flags and option names have moved before.
  • Memory is the hard limit. A small model wants roughly 4 to 8 GB; a large one wants far more.
Similar repositories
Install
brew install llama.cpp
Screenshots
ggml-org/llama.cpp: GitHub preview cardggml-org/llama.cpp: Screenshot 1ggml-org/llama.cpp: Screenshot 2

On Stack Radar: AI & Automation › AI Models & Inference › Inference APIs.

Get the next edition in your inbox

A dozen repositories, opened and checked. The licence read, the last release dated, and the ones that did not make it named with the reason. It is the half most lists leave out.

No tracking pixels. One click to leave. The archive stays free either way.

We use your address to send the edition and nothing else. Confirm by email, leave in one click. How we handle it.