A local AI model running on your own PC is private and free to use, but it only knows what was in its training data. Ask it about this week's news or a driver released yesterday and it will either say it doesn't know or, worse, make something up. Open WebUI, the popular browser-based front end for Ollama and other local AI servers, can fix that by searching the web and feeding the results to your model. This guide follows Open WebUI's official documentation and assumes you already have Open WebUI running; if not, start with our Open WebUI and Ollama setup guide. Forge PC hasn't tested every search provider, and results depend on your model and the provider you choose.
How web search works in Open WebUI
Open WebUI's documentation splits web search into two jobs:
The search engine finds links for your query, with short previews.
The web loader opens those links and reads the page text when the model needs more detail. It can also read a link you paste into a chat.
You choose a service for each job, but you don't need to configure both to start. Open WebUI's advice is to pick one search engine and leave the web loader at its default setting.
One privacy point before you begin: a local model keeps your chats on your PC, but web search sends your search queries to the provider you choose. Open WebUI lets admins require confirmation before a search runs, so queries aren't sent to an external provider unintentionally (covered below).
Option 1: DDGS, the quickest setup (no account, no API key)
DDGS (Dux Distributed Global Search) is a metasearch engine that ships with Open WebUI. The documentation says there's nothing to install and no account or API key needed:
Open Admin Panel > Settings > Web Search.
Turn on Web Search.
Set Web Search Engine to DDGS.
Choose a DDGS Backend. Auto (Random) is the default, and Open WebUI calls it the most reliable choice because each search picks a provider at random, so one provider refusing a request doesn't stop searching altogether.
Save.
Open WebUI notes that DDGS reaches providers through their public pages rather than paid APIs, so results can be less reliable than an official API. If you configure Open WebUI with environment variables, the engine value is duckduckgo (not ddgs), and the DDGS entry isn't available on the slim Docker image.
Option 2: A self-hosted SearXNG instance
SearXNG is a free, self-hosted metasearch engine. Open WebUI describes it as useful when you want a privacy-preserving option you run yourself, though it notes that result quality depends on SearXNG's upstream engines, rate limits and configuration. Open WebUI's SearXNG guide is a community contribution, but the key steps are:
Run SearXNG in Docker (the guide uses the official searxng-docker repository).
Enable JSON output. In SearXNG's settings.yml, add json to the formats list under search, alongside html, then restart SearXNG. Without this, SearXNG blocks Open WebUI's queries and you'll see 403 Client Error: Forbidden in Open WebUI's logs.
In Open WebUI, go to Admin Panel > Settings > Web Search, turn on Web Search and set the engine to searxng.
Set the Searxng Query URL to your instance's /search endpoint, for example http://localhost:8080/search, or http://searxng:8080/search if both containers share a Docker network. Open WebUI adds the query parameters itself.
Adjust Search Result Count and Concurrent Requests if needed, and save.
Option 3: A hosted search API
For the strongest results, Open WebUI recommends starting with a hosted search API built for AI workflows; its documentation names Exa, Tavily, SearchApi, Serper, SerpApi, Brave and Kagi. These usually need an account and an API key, and some charge for searches. Pick one, follow its page in Open WebUI's provider list, paste the key into the Web Search settings and save. If you're comparing the cost of hosted services with running everything at home, our cloud AI vs local LLM guide may help.
Using web search in a chat
Turning it on in the admin settings doesn't make every chat search the web. Open WebUI's SearXNG guide says to open the + menu in a chat and turn on Web Search, and that the toggle applies per session, so reloading the page or switching chats turns it off again.
The documentation also lists three "gates" that must all be open for searching to work: Web Search enabled globally, enabled on the model (in Admin Panel > Settings > Models, edit the model), and enabled in the chat. The DDGS page adds that the model must not be set to Legacy function calling.
Require confirmation before searching
If you share Open WebUI with others, or just want to be sure nothing leaves your PC by accident, admins can turn on search confirmation in Settings > Web Search (admin section). The switch appears while Web Search is on, and can also be set with the ENABLE_WEB_SEARCH_CONFIRMATION environment variable.
Fixing common problems
403 Forbidden with SearXNG. JSON output isn't enabled. Add json to SearXNG's formats list and restart it.
Search works but answers ignore the content, or pages come back empty. Open WebUI's troubleshooting guide says web pages often contain 4,000 to 8,000 or more tokens, and that if your model runs at Ollama's 4,096-token default (which applies to GPUs under 24GiB), you're missing most of the content. It recommends increasing the context length to 16,384 tokens or more in the model's Advanced Params. Bigger context uses more VRAM; our Ollama context length guide and context length and VRAM explainer show how to balance it.
The model never searches. With everything configured, Open WebUI says this is usually down to model capability: in Native (agentic) mode the model must decide to call the search_web tool, and older or smaller models can miss it or produce malformed tool calls. It recommends a modern model with good tool calling, and checking that Function Calling is set to Native in the model's Advanced Params.
Timeouts. Reduce concurrent requests (Open WebUI says WEB_SEARCH_CONCURRENT_REQUESTS=1 is required for Brave's free tier) and make sure Open WebUI can reach both the search engine and the result pages.
Behind a proxy. Turn on Trust Proxy Environment in the Web Search settings so the web loader uses your proxy settings.
Our verdict
Adding web search turns a local chatbot from a frozen snapshot into something that can answer questions about today. Start with DDGS: it's built in, needs no account and takes a minute to switch on. Move to a self-hosted SearXNG instance if you want more control (remember to enable JSON output), or a hosted search API if result quality matters most. Then raise your model's context length to at least 16K tokens and use a model with reliable tool calling, or you'll get thin answers however good the search is.