Error messages

Error: pull model manifest: file does not exist

Error: pull model manifest: file does not exist

Ollama prints this when you run or pull a model it can't find on the registry (the server it downloads models from, ollama.com by default):

pulling manifest
Error: pull model manifest: file does not exist

The wording sends people off to check their own disk. We read the code in Ollama 0.34.3, and "file does not exist" there is Go's stock text for a missing file (which is where the confusion starts), used here to stand for an HTTP 404 from the registry. Ollama asked for a manifest (the small index file listing a model's parts), and the registry said it had nothing by that name. It's a well-worn error: 76 issues in the ollama/ollama repo quote it in full as of September 23, 2026.

Why the registry says no

The registry looks up the exact name and tag you typed, so the usual cause is a spelling or a tag that doesn't exist. A size tag that the model was never published in fails the same way as a misspelled name. Other refusals from the registry look different: any error code other than 404 is printed as the number followed by the registry's own explanation, so digits after the colon mean some other problem.

Models that only exist in the cloud

Some models on ollama.com are published only as a :cloud tag, which runs on Ollama's servers instead of your machine, and asking for the default tag of one of those gives this error. Newer versions check for exactly that. When you ask for a name without a tag and the pull fails with this message, Ollama quietly asks whether a :cloud version exists, and at a terminal it prompts Did you mean with that name. In a script, where nobody can answer a prompt, it adds a hint to the error instead:

Error: pull model manifest: file does not exist

"kimi-k3:cloud" is available as a cloud model. Try:
  ollama run kimi-k3:cloud

The model name there is the example from the source comments; yours will differ. The check only runs for the default registry (a custom one never gets the hint), and only when you didn't type a tag.

What to do

Look the model up on ollama.com and copy the name and tag from its page rather than typing them. If you added a tag, try without one, which asks for the model's default. ollama list shows what's already on your machine, and if the model's in that list under a slightly different name, use that name, because a run of a model you have locally doesn't touch the registry at all.

For a private or custom registry, the same message means the path on that server is wrong, and the cloud suggestion won't appear.

When /save prints it

Here the error is Ollama's fault. An open issue from August 14 (#17735) has /save, the command inside ollama run that saves your session as a new model, failing with this exact message for a model that was pulled and running fine, with a valid manifest on disk. Two fixes were open as pull requests on September 23 (#17797 and #17806), both making /save fall back to the running model when it can't find the original locally. Until one ships, your download is fine and the model keeps working for everything else.