How do you move Ollama models to a new computer?

Updated November 3, 2026.

You move Ollama models by copying the model store, with its blobs and manifests intact, and pointing the new machine at that store before you delete the old one. Re-downloading every model works, but it wastes time and bandwidth, especially for large models, and a careful copy preserves the exact models you already have, including any custom models you created.

Where Ollama keeps models

Ollama stores downloaded models under a model directory that depends on the operating system. On macOS, the default is in the user's home folder under a hidden Ollama folder, in a models subfolder. On Linux, a system service install uses a different default path, under the Ollama service user's home folder, while a manual user install uses the user's home folder. On Windows, the default is under the user's profile folder, in a hidden Ollama folder, in a models subfolder. The project's frequently asked questions list those defaults and explain how to change the location with an environment variable.

Inside the model store, there are two important subfolders: blobs, which hold the model data, and manifests, which describe each model. Copy both, with their relative structure intact, and do not copy only the largest files, because a model without its manifest will not be recognised. Before copying, run the model list command on the old machine and record which models are present, so you can compare that list with the new machine after the move. That comparison is the test that the move worked, not the size of the copied folder alone.

Copy first, then switch, then verify

Stop Ollama on both machines before copying, so no model is being written while it is copied. Copy the contents of the old model store to the new machine, keeping the original intact until the new machine is verified. On the new machine, either place the copied store at the default location for that operating system, or set the environment variable that points Ollama at a different directory, making sure the account that runs Ollama can read and write that directory. On Linux, when Ollama runs as a system service, the service account needs read and write access to the new directory, and the environment variable must be set where the service reads it, not only in a personal shell.

Start Ollama on the new machine and list the models. The list should match the list recorded from the old machine. Then run a small prompt with a model that was moved, using its exact name, and confirm that it responds. Only after that verification should the old model store be removed, and even then, keep a backup until you have used the new machine for a few days. If the list on the new machine is empty, Ollama is reading a different path than the one you copied to; check the environment variable, the service account, and the folder structure before re-copying.

Custom models and other files to check

Custom models created with a model file are stored in the same model store, and they should move with the same copy, because their manifests are in the same manifests folder. Check any custom model by name on the new machine, and run a prompt with it, because a custom model that depends on a base model file that was not copied will fail even if its manifest is present. Other Ollama state, such as configuration and logs, lives outside the model store in the same hidden Ollama folder, and that state is not required for the models themselves to run. If you want the same settings on the new machine, copy or recreate the configuration separately, and do not delete the whole hidden folder on the old machine until you are sure you no longer need it.

If the new machine has less disk space than the old model store, do not start by copying everything. List the models, remove the ones you no longer use from the old machine with the remove command, or copy only the models you need, keeping their blobs and manifests together. A partial move that is verified is better than a full move that runs out of disk space halfway through and leaves a corrupted store. Disk space, model list, and a test prompt are the three checks that make a move safe, and they take only a few minutes.

Frequently asked questions

Do I have to re-download models on a new computer?

No. Copy the model store, with blobs and manifests intact, to the new machine, and point Ollama at that store. Re-downloading is a fallback, not the only option.

What is the environment variable for a different model location?

It is the variable that names the model directory, and it must be set where the service or application that runs Ollama reads it. On Linux, the service account also needs read and write access to that directory.

How do I know the move worked?

List the models on the new machine and compare that list with the list recorded on the old machine, then run a small prompt with a moved model. Only remove the old store after that verification.

Sources

Ollama project, frequently asked questions on model storage

Sources checked November 3, 2026. Figures that depend on your exact model, runtime or machine are estimates; check the source or test on your own hardware.

Adults only (18+). Private uncensored AI · Terms · Privacy · All guides