Best web search for Open WebUI: setup guide and provider comparison
Linkup Technical Staff
Enable web search in Open WebUI in 3 steps and ground every response in accurate, real-time facts with Linkup — the web search engine built for AI grounding.
TL;DR
- Fastest path: Admin Panel → Settings → Web Search → toggle Enable Web Search → select Linkup → paste your API key → Save.
- Docker path: set three env vars —
ENABLE_RAG_WEB_SEARCH=true,RAG_WEB_SEARCH_ENGINE=linkup,LINKUP_API_KEY=your_key. - Why Linkup: it's the only Open WebUI provider built specifically for AI grounding rather than repurposed general search — 92% F-score on Verified SimpleQA. You can get started for free.
- Common fix: if web search returns nothing on a free tier, set
WEB_SEARCH_CONCURRENT_REQUESTS=1— rate-limited free tiers reject parallel requests.
What web search does in Open WebUI
Web search in Open WebUI grounds model responses in live web data using retrieval-augmented generation (RAG). When enabled, Open WebUI sends the user query to a search provider, fetches results, extracts content, and injects that content into the prompt before the model answers. This is what stops a self-hosted Llama or Qwen model from answering with stale training data.
The quality of the answer depends on the quality of the retrieved content. Three things determine that:
- Accuracy of results returned. A provider that returns the wrong page produces a wrong grounded answer.
- Extraction quality. Raw HTML versus clean, model-ready content changes how much the model can use.
- Latency. Search runs on every query that triggers it, so a slow provider blocks the whole response
Open WebUI web search provider comparison
Linkup is the most accurate supported provider, SearXNG is the best free self-hosted web search engine, and Brave offers the most generous free tier among managed APIs. Pick based on priority: factual accuracy, zero cost, or a self-hosted result aggregator you fully control.
Linkup publishes its SimpleQA accuracy results through an open-source eval, scoring 92% F-score on Verified SimpleQA. SimpleQA is the benchmark that matters for Open WebUI because it measures factual question-answering against live web sources — the exact RAG grounding workload Open WebUI runs on every search-enabled query. For multi-step research beyond a single search, Linkup's /research endpoint scores 61% on SealQA-0.
How to set up Linkup web search in Open WebUI
Linkup is an officially supported Open WebUI provider — see the official Linkup setup guide in Open WebUI's docs for the full reference. You can configure it through the admin UI or environment variables.
Troubleshooting common Open WebUI web search issues
Most web search failures in Open WebUI come from concurrency limits, proxy config, or a missing toggle, not the provider itself. Work through these in order.
- No results on a free tier. Set
WEB_SEARCH_CONCURRENT_REQUESTS=1. Brave's free tier and other rate-limited plans reject parallel requests, so Open WebUI's default concurrency triggers a 429 and returns nothing. - Search runs but the model ignores results. Confirm
ENABLE_RAG_WEB_SEARCH=trueis set and that web search is toggled on per chat using the web search button in the message box. - Connection errors behind a corporate network. Set
HTTP_PROXYandHTTPS_PROXYenv vars so the container can reach the provider API. - API key not picked up. Env vars set in the UI override file env vars in some versions. If you set the key in
docker-compose.ymlbut it does not register, clear the field in Admin Panel → Settings → Web Search and re-save. - Slow responses. Latency stacks: search plus extraction plus generation. A sub-second search API like Linkup keeps the search portion off the critical path.
If results are accurate but sparse, increase the result count in the web search settings so the model has more grounding context to work with.
For a managed setup that meets a compliance and accuracy bar, Linkup is the most direct path: one env var plus an API key, 92% F-score on SimpleQA, and free tier.
https://app.linkup.so/sign-up or read the integration steps in the Linkup docs.
FAQ
How do I enable web search in Open WebUI?
Go to Admin Panel → Settings → Web Search, toggle Enable Web Search, select a provider, paste the API key, and save. For Docker, set ENABLE_RAG_WEB_SEARCH=true, RAG_WEB_SEARCH_ENGINE=<provider>, and the provider's API key env var.
What is the best web search provider for Open WebUI?
Linkup is the most accurate at 92% F-score on Verified SimpleQA. SearXNG is the best free self-hosted option, and Brave offers a free tier of 2,000 searches per month.
Is Linkup better than Tavily or Brave for Open WebUI?
Linkup scores 92% F-score on SimpleQA and starts at €5 per 1,000 searches with a free credit, while Tavily starts at $27 per month and Brave does not publish accuracy benchmarks. For grounded factual answers, accuracy is the deciding factor.
Why is Open WebUI web search returning no results?
The most common cause is concurrency on a rate-limited free tier. Set WEB_SEARCH_CONCURRENT_REQUESTS=1 so Open WebUI sends one request at a time and avoids 429 errors.
Can I use Open WebUI web search for free?
Yes. Linkup includes a free tier at sign-up. See more details here
Does Open WebUI web search send my queries to a third party?
Yes, unless you ask for ZDR or use a proprietary index such as Linkup.



