How to Install Open WebUI With Ollama

Evidence label: Official documentation reviewed, with caveats. Sources were reviewed on 2026-05-24. Local AI Guide test status: Not independently tested by Local AI Guide. This page does not contain local benchmark, install, privacy-audit, network-monitoring, storage-inspection, or screenshot evidence. Privacy framing: Documentation-backed guidance, not a privacy or security audit. A local model, local app, local UI, and local-only workflow are different things.

Quick answer: Install and verify Ollama first, then install Open WebUI as the browser interface. The usual beginner path is Docker: run Open WebUI in a container, persist its data in a volume, open it in your browser, create the first admin user, and confirm it can reach Ollama. The most common failure is not the model. It is the connection between a Docker container and Ollama running on the host machine.

Best for: users who already have Ollama working and want a ChatGPT-like browser UI for local models, file uploads, and a reusable workspace. Not for: users who have not yet installed Ollama, users who do not want Docker or local-server troubleshooting, or users who need a formal security-hardened deployment guide.

Privacy warning: Open WebUI can be local and private, but only if the connected model provider, embedding provider, files, storage, and network exposure are also local/private. A self-hosted Open WebUI connected to a cloud API is not a fully local AI workflow.

Before you start

Open WebUI is not the model runtime. It is the interface and workspace layer. Ollama is the runtime that loads and serves local models. That means your setup sequence should be:

1. Install Ollama.
2. Run at least one model in Ollama.
3. Verify Ollama responds locally.
4. Install Open WebUI.
5. Connect Open WebUI to Ollama.
6. Confirm the model list appears.
7. Only then add PDFs, knowledge bases, remote access, or cloud providers.

If Ollama does not work first, Open WebUI will not fix it.

What Open WebUI adds to Ollama

Requirements

Use this checklist before installing.

Step 1: Confirm Ollama works first

Before touching Open WebUI, run Ollama directly.

ollama list

If you do not see any models, pull or run a small starter model first. Then confirm the local API responds:

curl http://localhost:11434/api/tags

On Windows PowerShell, you may prefer:

Invoke-WebRequest http://localhost:11434/api/tags

Do not continue until Ollama is responding locally.

Step 2: Choose your Open WebUI install path

Most beginners should use Docker. It is not always the simplest conceptually, but it is the most common documented deployment path and makes updates/persistence more manageable when configured correctly.

For this beginner article, Docker should be the primary path.

Step 3: Install Open WebUI with Docker

Use the current official Open WebUI docs before publishing, because Docker commands and tags can change. The article should use the official command pattern and avoid pretending a stale command is guaranteed forever.

A typical Docker install needs three things:

1. The Open WebUI image.
2. A persistent volume for app data.
3. A way for the container to reach Ollama.

A typical Docker command will look conceptually like this:

docker run -d \
  --name open-webui \
  -p 3000:8080 \
  -v open-webui:/app/backend/data \
  --restart always \
  ghcr.io/open-webui/open-webui:main

Publication note: Before publishing, verify the exact current command against the official Open WebUI quick-start docs. If using :main, explain that a pinned version tag may be safer for stability. Do not present a moving tag as a stable production recommendation without that caveat.

After the container starts, open:

http://localhost:3000

You should see the Open WebUI setup screen.

Step 4: Create the first admin user

On a fresh Open WebUI install, the first account usually becomes the administrator. Use a test account for the first run, not a sensitive production deployment.

Do not expose Open WebUI to the internet just because it works on localhost.

Step 5: Connect Open WebUI to Ollama

This is the part that most often breaks.

If Open WebUI runs directly on the same host, localhost may work. If Open WebUI runs inside Docker, localhost from inside the container usually means the container itself, not the host machine. In many Docker Desktop setups, the host is reached through host.docker.internal.

Keep this distinction clear:

Browser localhost, container localhost, and host-machine localhost are not always the same place.

Step 6: Confirm models appear

After Open WebUI is connected to Ollama, the model picker should show the models available in Ollama.

If no models appear:

1. Confirm Ollama has a model with ollama list.
2. Confirm Ollama responds at http://localhost:11434/api/tags from the host.
3. Check the Ollama base URL configured inside Open WebUI.
4. If Docker is involved, test host.docker.internal.
5. Restart the Open WebUI container after changing connection settings.
6. Check container logs and Open WebUI settings.

Do not upload files or troubleshoot RAG until the basic model picker works.

Step 7: Run a simple local chat

Start with a trivial prompt:

Write one sentence explaining what local AI is.

Then run a second prompt that proves the same local model is still selected:

Give me a three-bullet checklist for choosing a small local model.

Record:

Optional: use Open WebUI for PDFs and documents

Open WebUI can support file uploads and knowledge/RAG workflows, but do not treat PDF chat as automatically private or accurate.

Before using sensitive documents, verify:

For document workflows, read Chat With PDFs Locally before uploading private material.

Common Open WebUI + Ollama problems

Windows notes

Windows users should expect extra setup friction because Docker Desktop and WSL 2 can affect networking. The safest beginner sequence is:

1. Install Ollama and confirm it works from Windows.
2. Install Docker Desktop.
3. Confirm WSL 2 is installed and Docker can run Linux containers.
4. Run Open WebUI.
5. Test whether Open WebUI can reach Ollama.
6. Fix networking before touching PDFs or plugins.

If a tutorial says “just use localhost” and it fails, the problem may be the container boundary, not Open WebUI itself.

Mac notes

On macOS, the common beginner path is:

1. Install Ollama for macOS.
2. Verify the local API.
3. Install Docker Desktop.
4. Run Open WebUI.
5. Open http://localhost:3000.
6. Confirm Open WebUI can see Ollama models.

Do not assume Docker gives GPU acceleration for every Mac workflow. Keep the UI layer and runtime layer conceptually separate: Ollama runs the model; Open WebUI provides the interface.

Linux notes

Linux users may have the cleanest server-style path, but more responsibility:

Linux is powerful, but it is not always the easiest beginner path.

Security and privacy checklist

Before using Open WebUI with real data:

• Confirm the selected model provider is local Ollama.
• Confirm embeddings are local if using documents.
• Keep the service on localhost or a trusted private network.
• Use a strong admin password.
• Do not expose the port to the public internet without a real hardening plan.
• Understand where uploads, vector data, chats, and settings are stored.
• Back up persistent data before updates.
• Disable or avoid features you do not understand, especially cloud providers, web search, plugins, and tools.
• Test offline behavior only after all required models and dependencies are downloaded.

When should you not install Open WebUI yet?

Wait if:

FAQ

Do I need Ollama before Open WebUI?

For this setup, yes. Open WebUI is the interface and Ollama is the local model runtime. You can connect Open WebUI to other providers, but this article is specifically about Open WebUI with Ollama.

What port does Open WebUI use?

A common Docker mapping exposes Open WebUI at localhost:3000 in the browser while the container listens internally on its own port. Always confirm the exact command you used.

Why can’t Open WebUI see my Ollama models?

Usually because Ollama has no models, Ollama is not running, or Open WebUI is pointing to the wrong Ollama URL. Docker networking is the most common source of confusion.

Should I use localhost or host.docker.internal?

It depends on where Open WebUI is running. From your browser, localhost means your computer. From inside a Docker container, localhost means the container. Many Docker Desktop setups use host.docker.internal to reach services running on the host.

Can Open WebUI run fully locally?

It can be configured for local workflows, but you must check the selected model provider, embedding provider, storage, web-search/tools settings, and network exposure. Do not assume local just because the UI is self-hosted.

Can I chat with PDFs in Open WebUI?

Yes, Open WebUI supports file and knowledge workflows, but accuracy and privacy depend on parsing, embeddings, retrieval settings, model quality, and provider configuration.

Is Open WebUI easier than LM Studio?

Not for a first local AI chat. LM Studio is usually easier as a desktop app. Open WebUI is more attractive once you already have Ollama working and want a browser-based workspace.

What to read next

• How to Install Ollama
• Ollama vs LM Studio
• Best Local AI Setup for Windows
• Best Local AI Setup for Mac
• Chat With PDFs Locally
• Is Local AI Actually Private?