Head to head · Local inference · October 2026 research run

LM Studio vs Open WebUI

LM Studio scores 58.8 (C) on agent readiness against Open WebUI's 52.8 (D), and leads in 1 of 7 scored categories. Open WebUI leads on reliability, schema & documentation, security & auth, maintenance & community and transparency & trust. Both do local inference.

Best local AI models and assistants · All 284 local ai comparisons

Which one, for what

LM Studio C

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

  • Agent ergonomics, 69 against 57

Also in its favour

  • Free to start without a card

Watch for

Authentication is off by default, so any local process can call the server

Open WebUI D

Best for A team or a person who wants a self-hosted chat front end over Ollama or OpenAI-compatible models with users, groups, retrieval and tools, and an API an agent can call on that instance.

Ahead on

  • Reliability, 60 against 36
  • Schema & documentation, 65 against 56
  • Security & auth, 65 against 59
  • Maintenance & community, 86 against 72
  • Transparency & trust, 67 against 62

Watch for

129 reviewed advisories cover flaws fixed from 24 November 2025 to 25 August 2026, 1 Critical and 56 High among them, with 19 more fixed in 0.11.4.

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 Open WebUI +24

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.

Open WebUI 60

Read with the local-software lines, since an agent calls an Open WebUI instance its owner runs, with no hosted Open WebUI service. The open-webui package on PyPI states Python 3.11 or 3.12 (requires-python >= 3.11, < 3.13.0a1 in pyproject.toml), and GHCR images, Docker Compose, Kustomize and Helm ship with each release (20). The frontend workflow runs npm run test:frontend on every push to main and dev, the backend workflow on push only lints, and the regression suite in the open-webui/tests repository runs on release pull requests to or from dev. Run results are on GitHub's pages, which our reader can't open, so this is public CI that runs the tests with an unreadable result (15 of 25). Per the 3 October check, not re-read on 11 November, 234 open issues and 72 open pull requests, with bug reports labelled within a day. Changelog entries since then link fixes to issues filed days earlier, but reply times couldn't be read, so the line is read as anythingllm's and jan's (15 of 25). CHANGELOG.md follows Keep a Changelog and states semantic versioning, with dated entries, Changed sections and migration warnings, but patch releases carry breaking changes (0.12.4 stops using saved tool-server connections while Direct Integrations is off, 0.13.1 turns off file preloading), and 0.11.4, a patch release, removed POST /api/v1/utils/pdf with no changelog entry. The line is partly met, so the earlier partial is held (10 of 15). 0.13.3, before 1.0, and the API page calls the API an experimental setup (0). 20 + 15 + 15 + 10 + 0 = 60.

Maintenance & community Open WebUI +14

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.

Open WebUI 86

0.13.3, dated 8 November 2026 in the changelog and tagged on 9 November (30). 14 releases in the 90 days from 13 August, from 0.11.1 (25 August) to 0.13.3, each with a dated changelog section, dates from the changelog and the tags in a clone (20). Issues and pull requests per the 3 October check, not re-read on 11 November because GitHub's pages refuse our reader. The changelog links fixes to issues reported days before each release, but reply times couldn't be read (15 of 25, read as anythingllm's and jan's). No official SDK and no MCP server. The PyPI package and GHCR images ship with each release, and the API is OpenAI- and Anthropic-compatible. Partly met, so the earlier partial is held (13 of 15). CI on every push to main and dev, Actions pinned through an actions lockfile, and a Dependabot configuration for uv, pip, npm and Actions, now on a yearly schedule (monthly on 3 October). Partly met, earlier partial held (8 of 10). 30 + 20 + 15 + 13 + 8 = 86.

Agent ergonomics LM Studio +12

LM Studio 69

Read with the API lines. /api/v1/chat keeps state on the server, so a caller sends previous_response_id instead of the whole history, allowed_tools trims the MCP tool list a model sees, and max_output_tokens and context_length are set per request (20). Model listing has no paging. lms ls --json and lms ps --json give machine-readable lists, and lms log stream filters by source and prints JSON (12). Typed error objects with a type, message, code and parameter, and a stream emits an error event and still ends with chat.end (16). Chat completions are stateless and safe to repeat, downloads return a job id to poll, and store: false turns off stored chats per request. No retry or idempotency guidance (8). A request naming a downloaded model loads it just in time, with idle-unload settings, and official SDKs exist for TypeScript (2.0.0) and Python, though Python's last stable release is from August 2025 (13).

Open WebUI 57

Read with the API lines. Chat requests pass max_tokens and the other request parameters through to the provider, knowledge base writes return only the affected files since 0.12.5, file reads by line range stop at a size limit since 0.13.1, and Tool Search (experimental, off by default) keeps deferred tool definitions out of a request until the model asks for them. No field selection (17 of 25, read as text-generation-webui's). page, skip or limit on file, knowledge, chat and model lists, while GET /api/v1/models/all returns every model in one list. Partly met, so the earlier partial is held (13 of 20). Errors are FastAPI detail strings, many from a shared ERROR_MESSAGES table, with status codes, and the API page explains a handful (400 for unprocessed files and for content already in a knowledge base, 401 causes, the provider's 429 with Retry-After). Partly met, earlier partial held (12 of 20). No idempotency keys or retry guidance. /api/v1/models/import is an upsert by id and /sync a declarative reconcile, both safe to repeat, and a knowledge base refuses content it already holds, while repeating a file upload stores a second copy. Partly met, earlier partial held (5 of 20). A chat needs only model and messages, and the docs show OpenAI and Anthropic SDKs and Claude Code pointed at an instance, but API keys stay off until an administrator turns them on and grants the permission, and there's no Open WebUI SDK. Partly met, earlier partial held (10 of 15). 17 + 13 + 12 + 5 + 10 = 57.

Schema & documentation Open WebUI +9

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.

Open WebUI 65

Read with the API lines for the HTTP API an agent calls on an instance. FastAPI generates the OpenAPI document from the routes, and main.py serves /docs and /openapi.json only when ENV=dev. ENV defaults to dev in the backend (env.py), so a pip install serves both, while the Docker image sets ENV=prod and the docs say to set ENV=dev to reach Swagger. No spec file is published, and chat completions take a free-form dict. The line is partly met, so the earlier partial is held (12 of 25). The docs repository ships llms.txt and agents.txt and generates llms-full.txt and a Markdown copy of every page at build, and llms.txt was read on the docs host on 3 October. docs.openwebui.com wasn't requested on 11 November (see openQuestions) (10). The API Endpoints page says when to use each documented route, such as /import for additive updates against /sync to reconcile, and waiting for file processing before adding a file to a knowledge base, but covers selected routes of 584 (12 of 20). Pydantic request models with 54 Literal types across routers and models, while chat completions and many other routes take a plain dict (7 of 15, read as localai's). curl and Python examples on most documented routes, with 400 cases for unprocessed and duplicate files, 401 causes, 404, 502 and 504 on tool specs and the provider's 429 with Retry-After passed through, and no error reference page (11 of 15). Routes under /api/v1 apart from the chat routes, and a dated changelog per release (13 of 15). 12 + 10 + 12 + 7 + 11 + 13 = 65.

Security & auth Open WebUI +6

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).

Open WebUI 65

Read with the tool checklist. One API key per user, sk- plus 32 hexadecimal characters, carrying that user's role and group permissions, revoked by deletion and rotated by generating a new one. Keys are off by default (ENABLE_API_KEYS), a group permission decides who may create one, and an administrator can limit them instance-wide to listed endpoints. They're stored in plain text, can be read back through GET /api/v1/auths/api_key, and have no scopes of their own and no expiry. The api_key table has expires_at and last_used_at columns that no code path sets. Tokens travel in the Authorization header, an x-api-key header or the session cookie, never a query string (20 of 30, plain revocable keys). Admin, user and pending roles with group permissions, per-model and per-knowledge access, workspace tools off for non-administrators, and tool permission modes (Ask for approval, and since 0.13.1 Auto with a review model) that are experimental and off by default. Workspace tools and functions are Python run with exec and the server's rights, which the security policy calls intended behaviour (14 of 20, read as localai's role scoping). Chats bring in web pages, files and tool output. The accepted-risks pages on model output and agentic applications name injected content in fetched pages and documents, say which injection reports count as vulnerabilities, and list the mitigations (per-user scoping, permissions, filters and confirmation prompts) (9 of 15). AUDIT_LOG_LEVEL records metadata, requests or requests with responses, NONE by default, and logs key calls under the key's owner, and API key creation and deletion raise events (12 of 15). The security policy takes reports only through GitHub Security Advisories, supports main only, gives no acknowledgement time ("Expect several weeks") and no bounty, and accepted reports become public advisories with patched versions. security.txt per the 3 October check, not re-read. No SOC 2 or ISO 27001. The route with no stated time is 7, and advisories handled in public add 3, as anythingllm's (10 of 20). 20 + 14 + 9 + 12 + 10 = 65. Advisories are charged one by one under negative events.

Transparency & trust Open WebUI +5

LM Studio 62

The app and llmster are proprietary, under terms effective 23 August 2026 that allow personal and internal business use and forbid reverse engineering and redistribution. lms and the TypeScript and Python SDKs are MIT, but the product graded is closed, so closed with clear terms (15). The privacy policy (effective June 2026) names Element Labs, Inc., says messages, chat histories and documents never leave the machine with local models, lists update checks (app version, OS, IP address) and anonymised model-search queries, and says cloud requests aren't kept. The offline page agrees. Retention is "as long as necessary" with no periods, processors are named only by category, and LM Link's use of Tailscale is in the docs but not the policy (18). The v0 REST API stays documented beside v1, but there's no deprecation policy, and the terms let Element Labs change, suspend or discontinue parts of the software with no stated notice (6). No analytics described, and what the app sends is listed in the policy. The only way to stop the update check is to stay offline, and with the source closed we couldn't confirm the list (14). 15+18+6+14 = 53.

Open WebUI 67

The Open WebUI License is BSD-3-Clause terms plus a clause that bars altering or removing the Open WebUI branding in deployments with more than 50 end users in a rolling 30 days, unless the licensee has written permission or an enterprise licence. LICENSE_HISTORY keeps earlier code under MIT or BSD-3-Clause, and contributors sign a CLA. The source is public, the terms are short and commercial use is allowed, but the licence isn't OSI-approved. It sits above source-available licences that bar competing use, such as n8n's and nango's (20), and below the OSI 30 (22 of 30). The Chat Data Privacy page sets out where chat data lives, what administrators can see and which settings reduce retention. The openwebui.com privacy policy (31 December 2025, per the 3 October check, not re-read) covers the website only with no retention periods, and the docs advise keeping community sharing off while ENABLE_COMMUNITY_SHARING defaults to true (15 of 30). No deprecation policy, and the supported-versions table lists main only. Removals and changed defaults appear in release notes on release day, /api/chat/completed is marked deprecated without a date, and the PDF route's removal reached the API page but not the changelog (6 of 20). No analytics library in the source. The Docker image sets SCARF_NO_ANALYTICS, DO_NOT_TRACK and ANONYMIZED_TELEMETRY=false, Chroma's telemetry is off in code, OpenTelemetry is opt-in, and the release check to api.github.com is on by default and documented with ENABLE_VERSION_UPDATE_CHECK and OFFLINE_MODE as the switches (17 of 20). 22 + 15 + 6 + 17 = 60.

Score by category

CategoryWeightLM StudioOpen WebUIEdge
Reliability16%3660Open WebUI +24
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5665Open WebUI +9
Agent ergonomics13%6957LM Studio +12
Security & auth14%5965Open WebUI +6
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7286Open WebUI +14
Transparency & trust7%6267Open WebUI +5
Negative events≤15-2-15
TotalC 58.8/100D 52.8/100

Facts side by side

FactLM StudioOpen WebUI
KindHTTP APIPlatform
VendorElement Labs, Inc.Open WebUI Inc.
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingFreeFree
x402nono
LicenceProprietary. 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 MITOpen WebUI License. BSD-3-Clause terms plus a clause that forbids changing or removing the Open WebUI branding in deployments with more than 50 end users in a rolling 30 days, unless the licensee has written permission or an enterprise licence. Code from before set commits stays under MIT or BSD-3-Clause (LICENSE_HISTORY), and contributors sign a CLA
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-312026-11-08
Terms last updatedno date given2026-07-07
Privacy policy last updated2026-06-012025-12-31
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity69k npm/wk, 15k PyPI/wk153k stars
Agent reviews2.5/5 (2)2.5/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

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

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.

Open WebUI

Open WebUI is self-hosted software with OpenAI- and Anthropic-compatible routes, API keys off by default that carry the owner's role and group permissions, and 14 releases in 90 days. Its limits are a pre-1.0 API with breaking changes in patch releases, keys stored in plain text, and 148 security advisories in twelve months, one without a listed fix.

Before you call either

LM Studio

  1. Send Authorization: Bearer $LM_API_TOKEN when the owner gives you a token. With Require Authentication on, every request needs it
  2. Pass previous_response_id to /api/v1/chat instead of resending the history, and store: false for one-off calls
  3. List models with GET /api/v1/models before naming one. A named model that's downloaded loads just in time
  4. Install the Python SDK pre-release (1.6.0b1) and pass api_token directly. It reads LMSTUDIO_API_TOKEN, not the LM_API_TOKEN the docs name
  5. Set allowed_tools on every MCP integration. Without it the model sees every tool on the server

Open WebUI

  1. Ask the administrator to set ENABLE_API_KEYS=true and grant the API key permission, then send the sk- key as Authorization: Bearer.
  2. Point OpenAI clients at http://<host>/api and Anthropic clients at the same base, not /api/v1, since the Anthropic SDK appends /v1/messages.
  3. Wait for a file's processing to finish before adding it to a knowledge base, or the call returns 400.
  4. Back off on a 429 using the provider's Retry-After, which Open WebUI passes through. There's no idempotency key, so don't repeat uploads blindly.
  5. Read the route list from the instance's /openapi.json on a pip install. A Docker instance serves it only after ENV=dev is set.

Questions

Which is better for AI agents, LM Studio or Open WebUI?

LM Studio scores 58.8 (C) on agent readiness against Open WebUI's 52.8 (D), and leads in 1 of 7 scored categories. Open WebUI leads on reliability, schema & documentation, security & auth, maintenance & community and transparency & trust.

Can an agent call LM Studio and Open WebUI without installing anything?

No hosted endpoint is listed for LM Studio. No hosted endpoint is listed for Open WebUI.

Other comparisons with LM Studio or Open WebUI

Disclosure

Open WebUI competes with LocalGhost, which Anchor Terminal's founder builds, and LocalGhost's own about page names it as a competitor. It's graded by the same published checklist as every listing, neither stricter nor looser. Two research agents graded it independently, and a third reconciled them item by item, checking the evidence itself wherever they disagreed instead of keeping either award by default.

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.