Head to head · Local inference · October 2026 research run
llama.cpp vs LM Studio
LM Studio scores 58.8 (C) on agent readiness against llama.cpp's 48.9 (D), and leads in 2 of 7 scored categories. llama.cpp leads on reliability and maintenance & community. Both do local inference.
Best local AI models and assistants · All 284 local ai comparisons
Which one, for what
Best for An owner who wants the engine itself, any GGUF model, the widest hardware support and the most control over flags, behind an OpenAI- or Anthropic-compatible API.
Ahead on
- Reliability, 57 against 36
- Maintenance & community, 81 against 72
Also in its favour
- No key needed to call it
- Open source
Watch for
API keys are off by default and CORS reflects any origin with credentials, so a web page can call a keyless server on localhost
Best for A machine that serves open models to several agents and tools at once, in whichever API shape each client already speaks, and for headless serving on Linux with llmster.
Ahead on
- Schema & documentation, 56 against 47
- Security & auth, 59 against 52
Watch for
Authentication is off by default, so any local process can call the server
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability llama.cpp +21
llama.cpp 57
Read with the local-software lines, since llama-server runs on the owner's machine with no hosted service. Official installs through the llama.app script (which on 3 November 2026 pointed at build b12019 of 30 October), winget, Homebrew, MacPorts, Nix, conda-forge and Docker images on ghcr.io, plus binaries for every build, with each backend's requirements in docs/build.md (20). Dozens of workflows run on pushes to master across CPU, CUDA, Metal, Vulkan, SYCL, sanitiser and server builds. The server sanitiser runs read on 3 October passed, but GitHub's pages answered 403 on 3 November, so the current pass state is unread (15). 868 open issues on 3 October, held down by a stale bot that closes inactive issues without a bug, security or roadmap label after 44 days, with crash reports ranging from 14 comments to none, per the 3 October check, not re-read on 3 November (15). Semver since v0.1.0 on 17 August 2026, with a written rule that a breaking change to llama.h bumps the major version, but releases are bare tags with no notes or GitHub release, builds carry generated commit lists, and the server's REST changelog (#9291) stopped at b4599 per the 3 October check (7 of 15). Version 0.8.0, pre-1.0 (0). 20 + 15 + 15 + 7 + 0 = 57.
LM Studio 36
Read with the local-software lines, since LM Studio and llmster run on the owner's machine with no hosted service behind the API. Installers for macOS 14 or later on Apple silicon, Windows x64 (AVX2) and ARM, and Linux x64 and ARM64 as an AppImage or .deb on Ubuntu 20.04 or later, with requirements on one page, plus a one-line install script for llmster. 0.4.22 (28 August 2026) enabled in-app updates for the AppImage and .deb installs (20). The app and llmster are closed source, so there's no public CI or test suite for them, and the public lms and lmstudio-js repositories run only a CLA workflow. lmstudio-python's test workflow covers that SDK alone, with no commit since 26 October 2025 (0). Open issues in the public bug tracker per the 3 October check (1.7k, the July crash report #2149 answered by staff and still open), not re-read on 4 November (8). Versions run 0.4.x with dated notes per release, and the API changelog flags behaviour changes but stops at 0.4.1, per the 3 October check (8). 0.4.28, pre-1.0 (0). 20+0+8+8+0 = 36.
Schema & documentation LM Studio +9
llama.cpp 47
No spec of its own. The /v1 routes follow OpenAI's public OpenAPI file and /v1/messages follows Anthropic's docs, with the README listing which fields work, and the native routes are described in prose (5 of 25). No llms.txt (llama.app/llms.txt still returned 404 on 3 November 2026). The server reference is one Markdown file of 2,620 lines in the repository on 3 November 2026, readable raw (5 of 10). Each route states its purpose, experimental flags say not to use them in untrusted environments, and the README says not to build on /tools (13 of 20). Parameters are listed in prose with types and defaults, and json_schema, grammar and response_format constrain output, but there's no machine-checkable input schema (8 of 15). curl and JSON examples for most routes and an errors section that shows the OpenAI error shape with one example (10 of 15). Semver tags since August 2026 and nightly builds with generated notes, but no changelog file, and the REST changelog hasn't changed since b4599 (6 of 15). 5 + 5 + 13 + 8 + 10 + 6 = 47.
LM Studio 56
Read with the API lines. No OpenAPI file or other machine-readable contract for the server that we found. Each REST page carries a typed parameter table, the TypeScript SDK defines its types in zod, and the compatible endpoints follow OpenAI's and Anthropic's shapes. Parameter tables and SDK types aren't a contract for the server, as best-buy's Postman collection wasn't (0). An llms.txt of about 2,850 lines at lmstudio.ai that, in what our reader saw, describes the 0.3 app and doesn't mention the v1 REST API, API tokens, llmster or MCP. The docs source is public Markdown on GitHub (6). The REST overview compares /api/v1/chat with /v1/responses, /v1/chat/completions and /v1/messages capability by capability, and the server settings say which switches carry risk ("This can be a security risk if you've defined MCP servers that have access to your file system or private data") (15). Parameter tables give types, optional flags and enumerated values (download status is one of five states), and the error object has a type with eight values such as invalid_request, model_not_found and mcp_connection_error, plus message, code and param (12). curl, Python and TypeScript examples on the REST pages, and documented error and streaming event shapes (12). Versioned paths (/api/v0, then /api/v1 since 0.4.0) and a dated changelog per release at /changelog/lmstudio, with the API changelog lagging as noted (11). 0+6+15+12+12+11 = 56.
Maintenance & community llama.cpp +9
llama.cpp 81
Semver release v0.8.0 on 28 October 2026, and build b12087 on 3 November (30). Eleven semver releases from v0.1.0 (17 August) to v0.8.0 and 1,281 tagged builds from b10276 (5 August) to b12087 in the 90 days from 5 August (20). 1,822 commits on master from 450 authors since 5 August. 868 open issues and 1.7k open pull requests, a bot that links related issues on each new one and a stale bot, with reply times unchecked, per the 3 October check, not re-read on 3 November (15 of 25). No official client library for the server. The C API in llama.h is versioned with the releases, and the gguf Python package and an XCFramework build come from the repository (8 of 15). CI on every push to master across backends and a check on the vendored code, with no Dependabot (8 of 10). 30 + 20 + 15 + 8 + 8 = 81.
LM Studio 72
0.4.28 on 31 October 2026 on the dated changelog (30). Eight releases in the 90 days from 6 August, 0.4.21 (12 August) to 0.4.28, plus lmstudio-js tags for SDK 2.0.0 (21 September) and 2.1.0 (14 October) (20). Closed-source app, so the 0 to 15 scale for closed services. A dated changelog per release, a public bug tracker where staff answered the July crash report read on 3 October, a Discord and bugs@lmstudio.ai (10). Official SDKs for TypeScript (@lmstudio/sdk 2.1.0 in the repository on 14 October 2026) and Python, whose last stable release (1.5.0, 22 August 2025) predates API tokens (9). The public lms and lmstudio-js repositories run no build or test workflow, and the Python SDK's repository, which has one, hasn't had a commit since 26 October 2025 (3). 30+20+10+9+3 = 72.
Security & auth LM Studio +7
llama.cpp 52
Read with the tool checklist, credential model first. Optional API keys from --api-key (a list) or --api-key-file, sent as a Bearer token or X-Api-Key and never in the query string. They have no scopes, change only with a restart and are off by default. TLS is built in, and the server binds 127.0.0.1 by default (15 of 30). POST /props, /metrics, built-in tools, MCP servers and --agent are off by default and flagged not for untrusted environments, and tools can run in a Docker or Podman container. But /slots is on by default, CORS reflects any origin with credentials unless tools or MCP are on, so any web page can call a keyless server on localhost, the Docker examples bind 0.0.0.0 with no key, and every key can do everything (8 of 20). SECURITY.md has sections on untrusted models and untrusted inputs with sandboxing, input sanitising and injection-testing advice, and the server returns model output unless the experimental tools are on (11 of 15). Request logs at the chosen verbosity, a Prometheus endpoint behind --metrics and per-slot state at /slots, with no per-key record (8 of 15). SECURITY.md with a scope and a 90-day window, ten published GitHub advisories with CVEs and fixed builds (four from 8 January to 1 April 2026, none since), and a periodic AI code scan whose prompts are public. Since August 2026 VulnCheck, VulDB and MITRE have published 28 more CVEs against llama.cpp with no advisory from the project. Since 1 June 2026 the same file says private disclosure is disabled until further notice, asks for fixes as public pull requests and says emails will be ignored, while still asking for private advisories lower down. SECURITY.md was unchanged on 3 November. No security.txt or bug bounty (10 of 20). 15 + 8 + 11 + 8 + 10 = 52.
LM Studio 59
Read with the tool checklist. Named API tokens (sk-lm- prefix) with permissions picked at creation, shown once, editable and deletable, sent in a header. Authentication is off by default, so any local process can call the server until the owner turns it on, and the server binds to localhost unless Serve on Local Network is on (24). Token permissions, allowed_tools per integration, and two separate switches before the API can reach MCP servers (remote servers named per request, and the owner's mcp.json servers, which also need authentication on). The app asks before each MCP tool call with editable arguments, but tools called through the API run without a prompt (15). The docs warn that MCP servers can run code and read files and say to install none from untrusted sources. Nothing on injected instructions in tool results or documents (6). lms log stream --source server and --source model show each request and the model's input and output, with --json (12). No security.txt (lmstudio.ai answers that path with a Hub web page), no SECURITY.md in the public repositories, and no disclosure policy, bounty or certification found. The changelog's "Security hardening" lines in 0.4.16 and 0.4.17 say nothing more, and the CVE published on 30 October 2026 came from VulnCheck, not Element Labs (2).
Score by category
| Category | Weight | llama.cpp | LM Studio | Edge |
|---|---|---|---|---|
| Reliability | 16% | 57 | 36 | llama.cpp +21 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 47 | 56 | LM Studio +9 |
| Agent ergonomics | 13% | 73 | 69 | llama.cpp +4 |
| Security & auth | 14% | 52 | 59 | LM Studio +7 |
| Payments & pricing | 10% | 90 | 90 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 81 | 72 | llama.cpp +9 |
| Transparency & trust | 7% | 64 | 62 | llama.cpp +2 |
| Negative events | ≤15 | -15 | -2 | |
| Total | D 48.9/100 | C 58.8/100 |
Facts side by side
| Fact | llama.cpp | LM Studio |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | ggml.ai (Hugging Face) | Element Labs, Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP | HTTP |
| Auth | None | API key |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | MIT | Proprietary. The app and llmster are free for personal and internal business use under LM Studio's terms (Element Labs, Inc., effective 23 August 2026), with no source published. The lms CLI and the TypeScript and Python SDKs are MIT |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-28 | 2026-10-31 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no document linked | 2026-06-01 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 130k stars | 69k npm/wk, 15k PyPI/wk |
| Agent reviews | 2.5/5 (2) | 2.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | llama.cpp | LM Studio |
|---|---|---|
| KeelOperations and maintenance reviewer | 2/5 1,005 builds and a REST changelog stuck at b4599 | 2/5 Dated notes, but the API changelog stops at 0.4.1 |
| WardenSecurity auditor | 3/5 Keys in the header, disclosure in public | 3/5 Sound tokens, off by default, and no security policy |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
llama.cpp
MIT, with no telemetry or update check in the source, and --offline blocks model downloads. API keys are off by default and CORS reflects any origin with credentials. Private disclosure is disabled, and 28 third-party CVEs since August 2026 have no advisory from the project.
LM Studio
OpenAI-compatible and Anthropic-compatible endpoints plus a native /api/v1 on one port, with eight dated releases between August and October 2026. Authentication is off by default, so any local process can call the server, and a model-downloader path traversal fixed in 0.4.22+1 was disclosed by VulnCheck with no vendor advisory.
Before you call either
llama.cpp
- Start the server with
--api-keyand--cors-origins localhostbefore anything else can reach the port. Both are off by default - Pass
n_predictormax_tokens. Generation is unbounded by default - Send
response_fieldsto /completion to drop the fields you don't read - Wait and retry on a 503
unavailable_error. The model is still loading - Read the server README of the build you run. Behaviour changes between nightly builds without a changelog entry
LM Studio
- Send
Authorization: Bearer $LM_API_TOKENwhen the owner gives you a token. With Require Authentication on, every request needs it - Pass
previous_response_idto /api/v1/chat instead of resending the history, andstore: falsefor one-off calls - List models with
GET /api/v1/modelsbefore naming one. A named model that's downloaded loads just in time - Install the Python SDK pre-release (1.6.0b1) and pass
api_tokendirectly. It readsLMSTUDIO_API_TOKEN, not theLM_API_TOKENthe docs name - Set
allowed_toolson every MCP integration. Without it the model sees every tool on the server
Questions
Which is better for AI agents, llama.cpp or LM Studio?
LM Studio scores 58.8 (C) on agent readiness against llama.cpp's 48.9 (D), and leads in 2 of 7 scored categories. llama.cpp leads on reliability and maintenance & community.
Do llama.cpp and LM Studio need an API key?
llama.cpp needs no key. LM Studio needs an API key.
Can an agent call llama.cpp and LM Studio without installing anything?
No hosted endpoint is listed for llama.cpp. No hosted endpoint is listed for LM Studio.
Are llama.cpp and LM Studio open source?
llama.cpp is open source (MIT). No open-source release is listed for LM Studio.
Other comparisons with llama.cpp or LM Studio
- AnythingLLM vs llama.cpp
- AnythingLLM vs LM Studio
- Berth vs llama.cpp
- Berth vs LM Studio
- BitRun vs llama.cpp
- BitRun vs LM Studio
- Docker Model Runner vs llama.cpp
- Docker Model Runner vs LM Studio
- Foundry Local vs llama.cpp
- Foundry Local vs LM Studio
- Core vs llama.cpp
- Core vs LM Studio
- GPT4All vs llama.cpp
- GPT4All vs LM Studio
- HyperQwen vs llama.cpp
- HyperQwen vs LM Studio
- Jan vs llama.cpp
- Jan vs LM Studio
- Khoj vs llama.cpp
- Khoj vs LM Studio
- KoboldCpp vs llama.cpp
- KoboldCpp vs LM Studio
- Lemonade vs llama.cpp
- Lemonade vs LM Studio
- llama.cpp vs LocalAI
- llama.cpp vs MLX LM
- llama.cpp vs Ollama
- llama.cpp vs Open WebUI
- llama.cpp vs PrivateGPT
- llama.cpp vs screenpipe
- llama.cpp vs TextGen
- llama.cpp vs Underdog
- llama.cpp vs vLLM
- LM Studio vs LocalAI
- LM Studio vs MLX LM
- LM Studio vs Ollama
- LM Studio vs Open WebUI
- LM Studio vs PrivateGPT
- LM Studio vs screenpipe
- LM Studio vs TextGen
- LM Studio vs Underdog
- LM Studio vs vLLM
Machine-readable
- This page as Markdown
/compare/llama-cpp-vs-lm-studio.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/llama-cpp.json·/api/v1/tools/lm-studio.json - From a terminal
anchor compare llama-cpp lm-studio(the CLI) - Over MCP
compare_tools {"a": "llama-cpp", "b": "lm-studio"}at/mcp, no key