Verdict
Official documentation reviewed, with caveats
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.
Ollama is one of the simplest ways to run local AI models from your own computer. Install the app for your operating system, open a terminal, run a small model first, and then decide whether you want to add a browser interface like Open WebUI later.
The fastest beginner path is:
- Install Ollama for your operating system.
- Open Terminal, PowerShell, or Command Prompt.
- Run a small starter model.
- Confirm that Ollama responds locally.
- Only then move to larger models, Open WebUI, document chat, or custom integrations.
Quick recommendation
Use Ollama if you want a lightweight local model runner, terminal workflow, local API access, or a backend for tools like Open WebUI. Use LM Studio instead if you want a beginner-friendly desktop app for finding, downloading, and chatting with local models through a graphical interface.
If you are new to local AI, do not start by downloading the largest model you can find. Start with a small model, confirm that the setup works, and then move up based on your RAM, VRAM, and patience.
Before you install Ollama
Ollama itself is not usually the hard part. The bigger issues are model size, storage, RAM, VRAM, and expectations.
| Question | Beginner answer | Evidence label |
|---|---|---|
| Do I need a GPU? | No for very small models, but a GPU or Apple Silicon unified memory usually makes the experience much better. | Conservative estimate, not a benchmark |
| Can I use an 8GB laptop? | Yes for small models and modest expectations. Do not expect large models or heavy PDF workflows to feel smooth. | Conservative estimate, not a benchmark |
| Is 16GB RAM enough? | Usually yes for a practical beginner setup with small or 7B/8B-class models. | Conservative estimate, not a benchmark |
| Does Ollama include a polished chat app? | Ollama is primarily a model runner, CLI, and local API. Add Open WebUI or another interface if you want a browser-based chat app. | Official documentation reviewed |
| Does local mean private? | Local inference can keep prompts on your machine, but model downloads, cloud features, web search, exposed local servers, and third-party tools can change the privacy profile. | Official documentation reviewed + Conservative estimate, not a benchmark |
System requirements and storage basics
Use this table as a practical starting point, not as a guarantee that every model will run well.
| Platform | Practical beginner notes | Evidence label |
|---|---|---|
| Mac | Prefer Apple Silicon for the best beginner experience. Keep enough free disk space for model files. | Official documentation reviewed + Conservative estimate, not a benchmark |
| Windows | Ollama runs as a native Windows application and supports NVIDIA and AMD Radeon GPU paths. Windows 10 22H2 or newer is the official Windows requirement. | Official documentation reviewed |
| Linux | Ollama provides a Linux install path and can be used as a service-style local runtime. Distribution details vary. | Official documentation reviewed |
| Storage | The app is only the start. Downloaded models can take many gigabytes, and a model library can grow quickly. | Official documentation reviewed + Conservative estimate, not a benchmark |
| RAM/VRAM | Model size, quantization, and context length determine whether the setup feels usable. | Conservative estimate, not a benchmark |
For Windows, Ollama’s documentation states that the binary install needs at least 4GB of space, with additional space required for large language models that can range from tens to hundreds of gigabytes depending on what you download.
Which first model should you run?
For a beginner install guide, the first model should be small enough to prove that the setup works. Your first model is not your forever model.
| Your machine | First model class to try | What to avoid at first | Evidence label |
|---|---|---|---|
| 8GB system RAM | Small 3B/4B-class model | Large 13B/14B+ models, long context, multiple apps open | Conservative estimate, not a benchmark |
| 16GB system RAM | Small model or 7B/8B-class model | Assuming every 14B model will be comfortable | Conservative estimate, not a benchmark |
| 32GB system RAM | 7B/8B comfortably; some larger models may be practical | Jumping straight to 70B-class models | Conservative estimate, not a benchmark |
| CPU-only machine | Small model with modest expectations | Treating CPU-only as equivalent to GPU acceleration | Conservative estimate, not a benchmark |
| Windows with NVIDIA GPU | Small model first, then test larger models based on dedicated VRAM | Planning around shared GPU memory as if it were dedicated VRAM | Conservative estimate, not a benchmark |
| Apple Silicon Mac | Small model first; move up based on unified memory | Forgetting that macOS and apps share the same memory pool | Conservative estimate, not a benchmark |
Local AI Stack’s testing protocol uses small and medium baseline model classes for repeatability. For an actual hands-on article, keep the exact model identifier constant across screenshots and measurements.
Install Ollama on Mac
1. Download Ollama
Go to the official Ollama download page and choose the macOS download.
Evidence label: Official documentation reviewed.
2. Open the app
Open the downloaded app and complete the normal macOS install flow. If macOS asks for permission to open the app, follow the standard macOS security prompt.
Evidence label: Official documentation reviewed.
3. Open Terminal
After the app is installed and running, open Terminal. The command line is where you will run your first model.
4. Check that the command works
Run:
ollama --versionIf the command returns a version, the CLI is available.
If the command is not found, quit and reopen Terminal. If it still fails, reopen the Ollama app and check the official macOS setup notes.
5. Run a small first model
Run a small model first. For example:
ollama run gemma3:4bThen ask a simple test question:
Explain local AI in one sentence.If the model replies, your basic install works.
Publisher note: Before final publication, verify that the starter model name is still available in the Ollama library. Replace it with your house baseline if Local AI Stack standardizes on a different model.
Install Ollama on Windows
1. Confirm your Windows version
Ollama’s Windows documentation lists Windows 10 22H2 or newer as the Windows requirement. If you are using an older Windows build, update before installing.
Evidence label: Official documentation reviewed.
2. Download the Windows installer
Download the official Windows installer from Ollama.
3. Run the installer
Ollama’s Windows documentation says the installer does not require Administrator rights and installs in your home directory by default.
Evidence label: Official documentation reviewed.
4. Open PowerShell, Command Prompt, or Windows Terminal
After installation, Ollama should run in the background, and the ollama command should be available in cmd, PowerShell, or your preferred terminal.
Run:
ollama --versionIf the command is recognized, continue.
5. Run your first model
Start with a small model:
ollama run gemma3:4bIf this is your first local model download, expect the first run to take longer because Ollama has to download the model before it can run it.
6. Verify the local API if you need it
Ollama’s Windows documentation states that its API is served at:
http://localhost:11434For most beginners, you do not need to use the API immediately. But if you are setting up Open WebUI or another local tool, this local endpoint is important.
A simple PowerShell test looks like this:
(Invoke-WebRequest -Method POST -Body '{"model":"gemma3:4b", "prompt":"Say hello in one sentence.", "stream": false}' -Uri http://localhost:11434/api/generate).ContentIf you receive a JSON response, the local API is responding.
Install Ollama on Linux
1. Use the official Linux install path
Follow Ollama’s official Linux installation documentation. The exact steps may vary depending on whether you want a normal local setup, service-style setup, GPU support, or Docker.
Evidence label: Official documentation reviewed.
2. Confirm the command is available
Run:
ollama --version3. Run a small first model
Run:
ollama run gemma3:4bThen ask a short test prompt.
4. Check whether the service is running
If ollama run fails because the local server is not available, check the official Linux troubleshooting and service documentation. Linux users are more likely than Mac or Windows beginners to encounter service, permission, or GPU-driver issues.
Do you need Docker for Ollama?
Most beginners do not need Docker just to install and use Ollama.
Use the normal app or OS install path first. Consider Docker only if:
- you already use Docker;
- you want an isolated deployment;
- you are following a specific Open WebUI setup that expects containers;
- you are deploying on a server;
- you need repeatable infrastructure rather than a normal desktop install.
If your goal is simply “run my first local AI model,” Docker is usually an unnecessary complication.
Where Ollama stores files
Model storage matters because the app may be small, but the models are not.
| Item | Windows location from Ollama docs | Mac/Linux practical note | Evidence label |
|---|---|---|---|
| Logs and updates | %LOCALAPPDATA%\Ollama | Check official docs for current paths | Official documentation reviewed for Windows |
| Binaries | %LOCALAPPDATA%\Programs\Ollama | App or binary path depends on install method | Official documentation reviewed for Windows |
| Models and config | %HOMEPATH%\.ollama | Commonly under ~/.ollama | Official documentation reviewed for Windows; verify for Mac/Linux before publication |
| Temporary files | %TEMP% with ollama* folders | Temporary paths vary | Official documentation reviewed for Windows |
If your system drive is small, solve storage before downloading several models.
How to move Ollama models to another drive on Windows
Ollama’s Windows documentation says you can change the model location by setting the OLLAMA_MODELS environment variable for your user account.
Beginner-safe outline:
- Create a folder on the target drive, such as
D:\OllamaModels. - Open Windows Settings or Control Panel.
- Search for environment variables.
- Edit environment variables for your user account.
- Create or edit
OLLAMA_MODELS. - Set it to the folder where you want downloaded models stored.
- Quit the Ollama tray app.
- Relaunch Ollama from the Start menu.
- Open a new terminal and run a small model.
Important: If you already downloaded models, moving the variable does not automatically move old model files. Back up before deleting anything.
How to verify Ollama is working
Use these checks in order.
| Check | Command or action | Success looks like | Evidence label |
|---|---|---|---|
| CLI exists | ollama --version | Version output appears | Official documentation reviewed |
| Model list works | ollama list | A table appears, even if empty | Official documentation reviewed |
| Model runs | ollama run gemma3:4b | Model downloads, loads, and replies | Official documentation reviewed + Conservative estimate, not a benchmark |
| Local API responds | POST to http://localhost:11434/api/generate | JSON response appears | Official documentation reviewed |
| Storage is understood | Check model folder | You know where downloaded files live | Official documentation reviewed for Windows; verify others |
Common Ollama install problems
| Problem | Likely cause | Fix | Evidence label |
|---|---|---|---|
ollama command not recognized | Terminal was opened before install, PATH not refreshed, or app not launched | Close and reopen the terminal; relaunch Ollama; check the official install notes | Conservative estimate, not a benchmark |
| Windows install uses the wrong drive | Default home-directory install path | Start the installer with a different directory flag or use documented storage settings | Official documentation reviewed |
| Models fill the C drive | Downloaded models are much larger than the app | Set OLLAMA_MODELS before building a model library | Official documentation reviewed |
| First run takes a long time | Model download is happening before inference | Wait for the download; start with a small model | Conservative estimate, not a benchmark |
| Responses are painfully slow | Model is too large, CPU-only fallback, not enough memory, or long context | Try a smaller model and close other memory-heavy apps | Conservative estimate, not a benchmark |
| Progress symbols look strange on Windows 10 | Terminal font may not render Ollama progress characters correctly | Change terminal font settings | Official documentation reviewed |
| Local API does not respond | Ollama background process is not running | Start Ollama, then retry localhost:11434 | Conservative estimate, not a benchmark |
| Open WebUI cannot see Ollama | Container/networking issue or Ollama not reachable from the UI | Finish this install first, then use the Open WebUI with Ollama guide | Conservative estimate, not a benchmark |
| User assumes it is fully private | Local model execution is only one part of the workflow | Read the privacy caveat and avoid cloud-connected features when handling sensitive data | Official documentation reviewed + Conservative estimate, not a benchmark |
Privacy notes for Ollama
Ollama can run models locally, and the local API is served from your own machine. But do not treat installation alone as a complete privacy plan.
A local setup can still involve network activity when you:
- download models;
- update the app;
- use hosted cloud models;
- enable web search or other cloud features;
- connect third-party tools;
- expose the local server beyond your own machine;
- use tunnels, proxies, or remote access;
- pair Ollama with an interface that connects to cloud APIs.
The safe beginner assumption is:
A model run locally through Ollama is more private than sending the same prompt to a cloud chatbot, but only the parts of your workflow that actually stay on your machine are local.
Do not expose localhost:11434 to the public internet unless you understand authentication, network binding, firewall rules, and the security consequences.
Should you install Open WebUI next?
Install Open WebUI after Ollama if you want a browser-based chat interface, multi-user-style UI, document workflows, or a more ChatGPT-like front end.
Do not install it immediately if you are still unsure whether Ollama works. First confirm:
ollama --versionworks.ollama run [model]works.- You know where models are stored.
- You have enough disk space.
- You understand that a local UI can still be configured to use cloud providers.
Should you install LM Studio instead?
Install LM Studio instead of Ollama if you want:
- a graphical model browser;
- a desktop chat interface;
- easier first-model discovery;
- built-in document chat;
- a local server only when you need it;
- fewer terminal commands at the start.
Use Ollama if you want:
- a lightweight local runtime;
- command-line model management;
- a local API backend;
- Open WebUI integration;
- developer tooling;
- automation workflows.
What to read next
- Ollama vs LM Studio
- How to Install LM Studio
- Best Local AI Setup for Mac
- Best Local AI Setup for Windows
- How to Install Open WebUI with Ollama
- Chat With PDFs Locally
- Is Local AI Actually Private?
Sources and evidence
Official and research sources used for this draft:
- Ollama Quickstart: https://docs.ollama.com/quickstart
- Ollama macOS installation: https://docs.ollama.com/macos
- Ollama Windows documentation: https://docs.ollama.com/windows
- Ollama Linux documentation: https://docs.ollama.com/linux
- Ollama Docker documentation: https://docs.ollama.com/docker
- Ollama API documentation: https://docs.ollama.com/api
- Ollama privacy page: https://ollama.com/privacy
- Local AI Stack keyword map and SERP research packet
- Local AI Stack source-of-truth research packet
- Local AI Stack compatibility foundation
- Local AI Stack privacy and security research packet
- Local AI Stack repeatable testing protocol