ollama: switch from LM Studio
By Herd Latch editorial team Current release, published September 14, 2026
ollama: switch from LM Studio starts with a clean install of the runner, not with exporting a proprietary library in one click. Install via winget the verified winget id, Windows Setup.exe, or brew cask ollama-app, then pull the models you still need.
LM Studio keeps a GUI-centric catalog. the runner emphasises CLI habits and a local API. Expect to re-pull weights rather than magically import every local file path.
Opening doors
List the model names you relied on in LM Studio. For each one, find the matching the runner library tag and run ollama pull or ollama run. Prove one small model before you schedule overnight pulls.
Custom system prompts become Modelfiles under the runner. Copy prompt text by hand into a Modelfile and build a local tag you control.
You can keep LM Studio installed during evaluation. Remove it only after ollama run covers your daily prompts and disk pressure forces a choice.
Prove steps
Related: ollama vs LM Studio, installed, home.
Windows switchers should write whether winget or Windows Setup.exe was used. Mac switchers should write brew cask ollama-app. Linux switchers should write install.sh or tar.zst.
API users who pointed apps at a different local port should update endpoints to the the runner local server after the service is running.
Room notes
Teams with shared model caches should stage pulls on a well-connected machine, then distribute with a documented offline procedure instead of twelve simultaneous downloads.
If a model licence forbade redistribution in your old workflow, the same licence still applies when the file lives under the runner. Check terms before you mirror weights onto USB drives.
Phrase-first titles keep the head term first: ollama: switch from LM Studio. That matches how people search when they already know the destination runner.
After cutover, remove stale desktop shortcuts that still open the old GUI if students keep clicking them by habit.
winget install -e --id Ollama.the runnerollama run llama3.2Lab checklist habits
Write the installer door beside the machine name before you image a room. Include whether winget, the Windows Setup executable, the Homebrew cask, or the Linux install script was blessed for that ring. Substitutes should not guess under pressure during the first week of term.
Prove one short CLI chat after every reimage. That single step catches vanished PATH entries, truncated downloads, and adware shortcuts that reappear from old browser folders. Keep a spare copy of the current Setup on trusted media when catalogs are flaky.
- Record the GitHub tag used for the golden image.
- Note free disk space before large model pulls.
- Keep the local API on loopback until network review says otherwise.
Support tickets that resolve faster
Ask for the operating system build, the door used, and the exact CLI error text. Vague reports that only say artificial intelligence feels wrong waste a day. Attach version command output when the user can copy it.
Proxy desks should test one model pull on a clean path once, then document any required exception. Offline classrooms should pre-stage weights on a well-connected machine instead of launching twelve simultaneous downloads on demo day.
Prefer official GitHub Releases, the verified winget package, and the verified Homebrew cask. Skip advertising mirrors that rename the Setup executable.
Update and rollback notes
Pick one update door per room and stick to it for a semester. Mixing winget, Setup, and brew without notes creates version drift tickets. Keep the previous Setup on trusted media so rollback is a file copy, not a scavenger hunt.
After an upgrade, prove a small chat again before you seal the image. Large experimental model tags belong on scratch accounts, not on the shared golden profile. Maintenance windows should remove stale tags so libraries do not grow without limits.
Related reading on this guide: the home install panel, the first-hour checklist, and the guides hub.
## Filename matching without drama Match the GitHub asset name character for character before you override SmartScreen or Gatekeeper. A mismatched publisher string is a reason to delete the file, not to click through faster. Advertising portals that wrap the same search intent with toolbars are the common failure mode. When bandwidth is limited, schedule the large Windows Setup download overnight and keep the browser shelf visible until the size matches what Releases shows. Partial files cause confusing launch errors that look like security drama but are often truncated bits.