[GH-ISSUE #2551] Can we change where the models are stored in windows #63534

New Issue

GiteaMirror · 2026-05-03T14:04:08-05:00

GiteaMirror commented

2026-05-03 14:04:08 -05:00

Originally created by @Gyro0o on GitHub (Feb 16, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/2551

As far as I know the models are automatically downloaded to C:/Users/username/.ollama
But can we change the directory to another one due to storage issues?

Originally created by @Gyro0o on GitHub (Feb 16, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/2551 As far as I know the models are automatically downloaded to C:/Users/username/.ollama But can we change the directory to another one due to storage issues?

GiteaMirror closed this issue

2026-05-03 14:04:08 -05:00

GiteaMirror commented

2026-05-03 14:04:09 -05:00

@MartynKeigher commented on GitHub (Feb 16, 2024):

You are correct and 'Yes' you can move them anywhere you like, via the OLLAMA_MODELS environment variable.

Docs: https://github.com/ollama/ollama/blob/main/docs/faq.md#where-are-models-stored

@MartynKeigher commented on GitHub (Feb 16, 2024): You are correct and 'Yes' you can move them anywhere you like, via the `OLLAMA_MODELS` environment variable. Docs: https://github.com/ollama/ollama/blob/main/docs/faq.md#where-are-models-stored

GiteaMirror commented

2026-05-03 14:04:11 -05:00

@fixtse commented on GitHub (Feb 16, 2024):

To create an environment variable on Windows you can follow these instructions:

Open Windows Settings.
Go to System.
Select About
Select Advanced System Settings.
Go to the Advanced tab.
Select Environment Variables....
Click on New...
And create a variable called OLLAMA_MODELS pointing to where you want to store the models

@fixtse commented on GitHub (Feb 16, 2024): To create an environment variable on Windows you can follow these instructions: Open Windows Settings. Go to System. Select About Select Advanced System Settings. Go to the Advanced tab. Select Environment Variables.... Click on New... And create a variable called OLLAMA_MODELS pointing to where you want to store the models

GiteaMirror commented

2026-05-03 14:04:12 -05:00

@APISeeker commented on GitHub (Feb 16, 2024):

Thanks I will try it out later.

@APISeeker commented on GitHub (Feb 16, 2024): Thanks I will try it out later.

GiteaMirror commented

2026-05-03 14:04:13 -05:00

@Gyro0o commented on GitHub (Feb 17, 2024):

You are correct and 'Yes' you can move them anywhere you like, via the OLLAMA_MODELS environment variable.

Docs: https://github.com/ollama/ollama/blob/main/docs/faq.md#where-are-models-stored

Understood
Thanks

@Gyro0o commented on GitHub (Feb 17, 2024): > You are correct and 'Yes' you can move them anywhere you like, via the `OLLAMA_MODELS` environment variable. > > Docs: https://github.com/ollama/ollama/blob/main/docs/faq.md#where-are-models-stored Understood Thanks

GiteaMirror commented

2026-05-03 14:04:14 -05:00

@Gyro0o commented on GitHub (Feb 17, 2024):

To create an environment variable on Windows you can follow these instructions:

Open Windows Settings. Go to System. Select About Select Advanced System Settings. Go to the Advanced tab. Select Environment Variables.... Click on New... And create a variable called OLLAMA_MODELS pointing to where you want to store the models

Worked perfectly
Thank u

@Gyro0o commented on GitHub (Feb 17, 2024): > To create an environment variable on Windows you can follow these instructions: > > Open Windows Settings. Go to System. Select About Select Advanced System Settings. Go to the Advanced tab. Select Environment Variables.... Click on New... And create a variable called OLLAMA_MODELS pointing to where you want to store the models Worked perfectly Thank u

GiteaMirror commented

2026-05-03 14:04:14 -05:00

@lafe commented on GitHub (Feb 17, 2024):

For whatever reason the environment variable did not work (even though, I can access it through PowerShell and it contains the correct folder path). My workaround was to create a symbolic link between the original models folder and the new location.

Make sure ollama does not run.
Move the Models folder from the user profile (C:\Users<User>.ollama\models) to the new location
Create the symlink using the mklink command (if you want to use PowerShell, you have to use the New-Item Cmdlet with the SymbolicLink item type):
```
mklink /D C:\Users\<User>\.ollama\models E:\AI\Ollama\Models
```
- the /D ensures that a directory symlink is created.

Afterwards, it worked as before but the model files were located on the other disk.

@lafe commented on GitHub (Feb 17, 2024): For whatever reason the environment variable did not work (even though, I can access it through PowerShell and it contains the correct folder path). My workaround was to create a symbolic link between the original models folder and the new location. 1. Make sure ollama does not run. 2. Move the Models folder from the user profile (C:\Users\<User>\.ollama\models) to the new location 3. Create the symlink using the [`mklink`](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/mklink) command (if you want to use PowerShell, you have to use the [`New-Item`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/new-item?view=powershell-7.4) Cmdlet with the [`SymbolicLink` item type](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/new-item?view=powershell-7.4#example-7-create-a-symbolic-link-to-a-file-or-folder)): ```bash mklink /D C:\Users\<User>\.ollama\models E:\AI\Ollama\Models ``` - the `/D` ensures that a directory symlink is created. Afterwards, it worked as before but the model files were located on the other disk.

GiteaMirror commented

2026-05-03 14:04:16 -05:00

@roocell commented on GitHub (Feb 18, 2024):

OLLAMA_MODELS env variable also didn't work for me - do we have to reboot or reinstall ollama?
i assume it would just pick up the new path when we run "ollama run llama2"

@roocell commented on GitHub (Feb 18, 2024): OLLAMA_MODELS env variable also didn't work for me - do we have to reboot or reinstall ollama? i assume it would just pick up the new path when we run "ollama run llama2"

GiteaMirror commented

2026-05-03 14:04:17 -05:00

@lafe commented on GitHub (Feb 18, 2024):

OLLAMA_MODELS env variable also didn't work for me - do we have to reboot or reinstall ollama? i assume it would just pick up the new path when we run "ollama run llama2"

Normally, you have to at least reopen the "command line" process, so that the environment variables are filled (maybe restarting ollama is sufficient). If you use PowerShell, you can use $env:OLLAMA_MODELS to check if the environment variable is set. If you use the Windows command prompt ("cmd"), you can use set to get a list of all environment variables.

@lafe commented on GitHub (Feb 18, 2024): > OLLAMA_MODELS env variable also didn't work for me - do we have to reboot or reinstall ollama? i assume it would just pick up the new path when we run "ollama run llama2" Normally, you have to at least reopen the "command line" process, so that the environment variables are filled (maybe restarting ollama is sufficient). If you use PowerShell, you can use `$env:OLLAMA_MODELS` to check if the environment variable is set. If you use the Windows command prompt ("cmd"), you can use `set` to get a list of all environment variables.

GiteaMirror commented

2026-05-03 14:04:19 -05:00

@ninjanimus commented on GitHub (Feb 18, 2024):

For those the custom path is not considered even after adding OLLAMA_MODELS environment variable and restarting the Terminal. Try restarting the OS once, then it is working. Might be the environment variables are stored in memory of the running Ollama process.

@ninjanimus commented on GitHub (Feb 18, 2024): For those the custom path is not considered even after adding OLLAMA_MODELS environment variable and restarting the Terminal. Try restarting the OS once, then it is working. Might be the environment variables are stored in memory of the running Ollama process.

GiteaMirror commented

2026-05-03 14:04:21 -05:00

@uocnb commented on GitHub (Feb 27, 2024):

I found that the Ollama app.exe is running in the background caused the new env var not update. You can quit it by right click on the Ollama icon on the system tray.

@uocnb commented on GitHub (Feb 27, 2024): I found that the `Ollama app.exe` is running in the background caused the new env var not update. You can quit it by right click on the Ollama icon on the system tray.

GiteaMirror commented

2026-05-03 14:04:21 -05:00

@JuninhoFreitas commented on GitHub (Apr 5, 2024):

I just started the installer in cmd with the following directive:

$ .\OllamaSetup.exe /DIR=D:\MYDIRECTORY

@JuninhoFreitas commented on GitHub (Apr 5, 2024): I just started the installer in cmd with the following directive: ``` $ .\OllamaSetup.exe /DIR=D:\MYDIRECTORY ```

GiteaMirror commented

2026-05-03 14:04:22 -05:00

@phpgit commented on GitHub (Apr 6, 2024):

I just started the installer in cmd with the following directive:
$ .\OllamaSetup.exe /DIR=D:\MYDIRECTORY

What a life saver! It works great, thanks for sharing!

@phpgit commented on GitHub (Apr 6, 2024): > I just started the installer in cmd with the following directive: > > ``` > $ .\OllamaSetup.exe /DIR=D:\MYDIRECTORY > ``` What a life saver! It works great, thanks for sharing!

GiteaMirror commented

2026-05-03 14:04:23 -05:00

@arfans22 commented on GitHub (May 26, 2024):

OLLAMA_MODELS

worked really well at my first try!

@arfans22 commented on GitHub (May 26, 2024): > OLLAMA_MODELS worked really well at my first try!

GiteaMirror commented

2026-05-03 14:04:23 -05:00

@zombodotcom commented on GitHub (Jun 29, 2024):

tried this, and also the .\OllamaSetup.exe /DIR=D:\MYDIRECTORY

it still downloads them to the C drive.
Tried moving the models and making the OLLAMA_MODELS Variable does not solve the issue of putting the blobs into the new directory, still tries to download them and doesnt register that they are there.

It does download to the new directory though. which is a plus

@zombodotcom commented on GitHub (Jun 29, 2024): tried this, and also the .\OllamaSetup.exe /DIR=D:\MYDIRECTORY it still downloads them to the C drive. Tried moving the models and making the OLLAMA_MODELS Variable does not solve the issue of putting the blobs into the new directory, still tries to download them and doesnt register that they are there. It does download to the new directory though. which is a plus

GiteaMirror commented

2026-05-03 14:04:24 -05:00

@arfans22 commented on GitHub (Jun 30, 2024):

tried this, and also the .\OllamaSetup.exe /DIR=D:\MYDIRECTORY

it still downloads them to the C drive.
Tried moving the models and making the OLLAMA_MODELS Variable does not solve the issue of putting the blobs into the new directory, still tries to download them and doesnt register that they are there.

It does download to the new directory though. which is a plus

You have to make anothee variable named OLLAMA_ORIGIN and make the value just . (Dot)

@arfans22 commented on GitHub (Jun 30, 2024): > tried this, and also the .\OllamaSetup.exe /DIR=D:\MYDIRECTORY > > it still downloads them to the C drive. > Tried moving the models and making the OLLAMA_MODELS Variable does not solve the issue of putting the blobs into the new directory, still tries to download them and doesnt register that they are there. > > It does download to the new directory though. which is a plus You have to make anothee variable named OLLAMA_ORIGIN and make the value just . (Dot)

GiteaMirror commented

2026-05-03 14:04:25 -05:00

@zombodotcom commented on GitHub (Jun 30, 2024):

still making me redownload the 38gb model

@zombodotcom commented on GitHub (Jun 30, 2024): still making me redownload the 38gb model

GiteaMirror commented

2026-05-03 14:04:25 -05:00

@Kazakuba commented on GitHub (Jul 6, 2024):

Close all ollama tasks
Move whole models folder
Env variable needs to be added for user not as system variable or in path
Or try; mklink /D C:\Users<User>.ollama\models E:\New\Model\Location (for link to work you must first move folder from C)

@Kazakuba commented on GitHub (Jul 6, 2024): Close all ollama tasks Move whole models folder Env variable needs to be added for user not as system variable or in path Or try; mklink /D C:\Users\<User>\.ollama\models E:\New\Model\Location (for link to work you must first move folder from C)

GiteaMirror commented

2026-05-03 14:04:26 -05:00

@zombodotcom commented on GitHub (Jul 6, 2024):

Added to both before posting

@zombodotcom commented on GitHub (Jul 6, 2024): Added to both before posting

GiteaMirror commented

2026-05-03 14:04:26 -05:00

@gary0318 commented on GitHub (Jul 8, 2024):

Nothing was working for me. So, I killed Ollama app.exe and from there on I can not start ollama server. The server log is empty and the main log says server error. I've reinstalled ollama, rebooted the computer checked my environment variables... nothing is working. When it gives me the error it leaves Ollama app.exe running and I have to kill it again..

time=2024-07-08T03:30:58.766-04:00 level=WARN source=server.go:157 msg="server crash 10 - exit code 1 - respawning"
time=2024-07-08T03:30:59.589-04:00 level=INFO source=server.go:135 msg="starting server..."
time=2024-07-08T03:30:59.603-04:00 level=INFO source=server.go:121 msg="started ollama server with pid 11848"
time=2024-07-08T03:30:59.603-04:00 level=INFO source=server.go:123 msg="ollama server logs C:\Users\gary0\AppData\Local\Ollama\server.log"

server log: empty

@gary0318 commented on GitHub (Jul 8, 2024): Nothing was working for me. So, I killed Ollama app.exe and from there on I can not start ollama server. The server log is empty and the main log says server error. I've reinstalled ollama, rebooted the computer checked my environment variables... nothing is working. When it gives me the error it leaves Ollama app.exe running and I have to kill it again.. time=2024-07-08T03:30:58.766-04:00 level=WARN source=server.go:157 msg="server crash 10 - exit code 1 - respawning" time=2024-07-08T03:30:59.589-04:00 level=INFO source=server.go:135 msg="starting server..." time=2024-07-08T03:30:59.603-04:00 level=INFO source=server.go:121 msg="started ollama server with pid 11848" time=2024-07-08T03:30:59.603-04:00 level=INFO source=server.go:123 msg="ollama server logs C:\\Users\\gary0\\AppData\\Local\\Ollama\\server.log" server log: empty

GiteaMirror commented

2026-05-03 14:04:27 -05:00

@amirali-mi10 commented on GitHub (Aug 31, 2024):

if you guys get confused, let me explain step by step:

1-first of all uninstall ollama (if you already installed)

2-then follow this:
Open Windows Settings.
Go to System.
Select About
Select Advanced System Settings.
Go to the Advanced tab.
Select Environment Variables....
Click on New...
And create a variable called OLLAMA_MODELS pointing to where you want to store the models(set path for store models)

3-after adjusting that then open the path that you downloaded OllamaSetup.exe (setup file)

4-then on file explorer write cmd to open cmd on that path

5-on cmd write--> OllamaSetup.exe /DIR=D:\MYDIRECTORY

6-after installation everything should works well and both ollama and models will save same drive you defined for it

@amirali-mi10 commented on GitHub (Aug 31, 2024): if you guys get confused, let me explain step by step: 1-first of all uninstall ollama (if you already installed) 2-then follow this: Open Windows Settings. Go to System. Select About Select Advanced System Settings. Go to the Advanced tab. Select Environment Variables.... Click on New... And create a variable called OLLAMA_MODELS pointing to where you want to store the models(set path for store models) 3-after adjusting that then open the path that you downloaded OllamaSetup.exe (setup file) 4-then on file explorer write cmd to open cmd on that path 5-on cmd write--> OllamaSetup.exe /DIR=D:\MYDIRECTORY 6-after installation everything should works well and both ollama and models will save same drive you defined for it

GiteaMirror commented

2026-05-03 14:04:28 -05:00

@Luojz commented on GitHub (Sep 11, 2024):

I just started the installer in cmd with the following directive:我刚刚在命令提示符中使用以下指令启动了安装程序：
$ .\OllamaSetup.exe /DIR=D:\MYDIRECTORY

A thumbs-up from China："牛 B"

@Luojz commented on GitHub (Sep 11, 2024): > I just started the installer in cmd with the following directive:我刚刚在命令提示符中使用以下指令启动了安装程序： > > ``` > $ .\OllamaSetup.exe /DIR=D:\MYDIRECTORY > ``` A thumbs-up from China："牛 B"

GiteaMirror commented

2026-05-03 14:04:29 -05:00

@simpleetech commented on GitHub (Oct 11, 2024):

if you guys get confused, let me explain step by step:

1-first of all uninstall ollama (if you already installed)

2-then follow this: Open Windows Settings. Go to System. Select About Select Advanced System Settings. Go to the Advanced tab. Select Environment Variables.... Click on New... And create a variable called OLLAMA_MODELS pointing to where you want to store the models(set path for store models)

3-after adjusting that then open the path that you downloaded OllamaSetup.exe (setup file)

4-then on file explorer write cmd to open cmd on that path

5-on cmd write--> OllamaSetup.exe /DIR=D:\MYDIRECTORY

6-after installation everything should works well and both ollama and models will save same drive you defined for it

I'm not sure if it was just me, but it worked when I set the environment variable as a "User Variable" not a "System Variable"

@simpleetech commented on GitHub (Oct 11, 2024): > if you guys get confused, let me explain step by step: > > 1-first of all uninstall ollama (if you already installed) > > 2-then follow this: Open Windows Settings. Go to System. Select About Select Advanced System Settings. Go to the Advanced tab. Select Environment Variables.... Click on New... And create a variable called OLLAMA_MODELS pointing to where you want to store the models(set path for store models) > > 3-after adjusting that then open the path that you downloaded OllamaSetup.exe (setup file) > > 4-then on file explorer write cmd to open cmd on that path > > 5-on cmd write--> OllamaSetup.exe /DIR=D:\MYDIRECTORY > > 6-after installation everything should works well and both ollama and models will save same drive you defined for it I'm not sure if it was just me, but it worked when I set the environment variable as a "User Variable" not a "System Variable"

GiteaMirror commented

2026-05-03 14:04:31 -05:00

@zalito12 commented on GitHub (Oct 11, 2024):

OLLAMA_MODELS env variable also didn't work for me - do we have to reboot or reinstall ollama? i assume it would just pick up the new path when we run "ollama run llama2"

Normally, you have to at least reopen the "command line" process, so that the environment variables are filled (maybe restarting ollama is sufficient). If you use PowerShell, you can use $env:OLLAMA_MODELS to check if the environment variable is set. If you use the Windows command prompt ("cmd"), you can use set to get a list of all environment variables.

I can cornfirm you must restart Ollama, opening a new cmd is not enough.
Also, to see a var on cmd you can use echo, as echo %OLLAMA_MODELS%

@zalito12 commented on GitHub (Oct 11, 2024): > > OLLAMA_MODELS env variable also didn't work for me - do we have to reboot or reinstall ollama? i assume it would just pick up the new path when we run "ollama run llama2" > > Normally, you have to at least reopen the "command line" process, so that the environment variables are filled (maybe restarting ollama is sufficient). If you use PowerShell, you can use `$env:OLLAMA_MODELS` to check if the environment variable is set. If you use the Windows command prompt ("cmd"), you can use `set` to get a list of all environment variables. I can cornfirm you must restart Ollama, opening a new cmd is not enough. Also, to see a var on cmd you can use echo, as ``echo %OLLAMA_MODELS%``

GiteaMirror commented

2026-05-03 14:04:32 -05:00

@angusgee commented on GitHub (Nov 4, 2024):

I just started the installer in cmd with the following directive:
$ .\OllamaSetup.exe /DIR=D:\MYDIRECTORY

This is the one thank you for sharing 🔥🔥🔥

@angusgee commented on GitHub (Nov 4, 2024): > I just started the installer in cmd with the following directive: > > ``` > $ .\OllamaSetup.exe /DIR=D:\MYDIRECTORY > ``` This is the one thank you for sharing 🔥🔥🔥

GiteaMirror commented

2026-05-03 14:04:33 -05:00

@mumangguo commented on GitHub (Dec 12, 2024):

nice

@mumangguo commented on GitHub (Dec 12, 2024): nice

GiteaMirror commented

2026-05-03 14:04:34 -05:00

@AdityaAdaki21 commented on GitHub (Dec 17, 2024):

I just started the installer in cmd with the following directive:
$ .\OllamaSetup.exe /DIR=D:\MYDIRECTORY
What a life saver! It works great, thanks for sharing!

THANK YOU!!!!

@AdityaAdaki21 commented on GitHub (Dec 17, 2024): > > I just started the installer in cmd with the following directive: > > ``` > > $ .\OllamaSetup.exe /DIR=D:\MYDIRECTORY > > ``` > > What a life saver! It works great, thanks for sharing! THANK YOU!!!!

GiteaMirror commented

2026-05-03 14:04:35 -05:00

@jiriehrlich commented on GitHub (Dec 21, 2024):

Uninstall Ollama
Create System Variable OLLAMA_MODELS
Run OllamaSetup.exe /DIR=:\Ollama

@jiriehrlich commented on GitHub (Dec 21, 2024): Uninstall Ollama Create System Variable OLLAMA_MODELS Run OllamaSetup.exe /DIR=<your drive>:\Ollama

GiteaMirror commented

2026-05-03 14:04:36 -05:00

@omesh845 commented on GitHub (Dec 26, 2024):

Uninstall Ollama Create System Variable OLLAMA_MODELS Run OllamaSetup.exe /DIR=:\Ollama

thanks man!! it worked!!!

@omesh845 commented on GitHub (Dec 26, 2024): > Uninstall Ollama Create System Variable OLLAMA_MODELS Run OllamaSetup.exe /DIR=:\Ollama thanks man!! it worked!!!

GiteaMirror commented

2026-05-03 14:04:37 -05:00

@codeisnotcode commented on GitHub (Jan 5, 2025):

if you guys get confused, let me explain step by step:
1-first of all uninstall ollama (if you already installed)
2-then follow this: Open Windows Settings. Go to System. Select About Select Advanced System Settings. Go to the Advanced tab. Select Environment Variables.... Click on New... And create a variable called OLLAMA_MODELS pointing to where you want to store the models(set path for store models)
3-after adjusting that then open the path that you downloaded OllamaSetup.exe (setup file)
4-then on file explorer write cmd to open cmd on that path
5-on cmd write--> OllamaSetup.exe /DIR=D:\MYDIRECTORY
6-after installation everything should works well and both ollama and models will save same drive you defined for it

I'm not sure if it was just me, but it worked when I set the environment variable as a "User Variable" not a "System Variable"

I did the above and it did not work until I realized it is important for the original id_ed25519 and id_ed25519.pub key files to be retained in order to be able to see the moved Ollama Models. If you moved these with the models, when you reinstall ollama, it will create new a new set of keys (these two files) in C:\users<username>.ollama and then the previously loaded models can't be read by Ollama. The solution is to copy these two files from your moved model subdirectory back into C:\users<username>.ollama, overwriting the newly created keys.

@codeisnotcode commented on GitHub (Jan 5, 2025): > > if you guys get confused, let me explain step by step: > > 1-first of all uninstall ollama (if you already installed) > > 2-then follow this: Open Windows Settings. Go to System. Select About Select Advanced System Settings. Go to the Advanced tab. Select Environment Variables.... Click on New... And create a variable called OLLAMA_MODELS pointing to where you want to store the models(set path for store models) > > 3-after adjusting that then open the path that you downloaded OllamaSetup.exe (setup file) > > 4-then on file explorer write cmd to open cmd on that path > > 5-on cmd write--> OllamaSetup.exe /DIR=D:\MYDIRECTORY > > 6-after installation everything should works well and both ollama and models will save same drive you defined for it > > I'm not sure if it was just me, but it worked when I set the environment variable as a "User Variable" not a "System Variable" --- I did the above and it did not work until I realized it is important for the original id_ed25519 and id_ed25519.pub key files to be retained in order to be able to see the moved Ollama Models. If you moved these with the models, when you reinstall ollama, it will create new a new set of keys (these two files) in C:\users\<username>\.ollama and then the previously loaded models can't be read by Ollama. The solution is to copy these two files from your moved model subdirectory back into C:\users\<username>\.ollama, overwriting the newly created keys.

GiteaMirror commented

2026-05-03 14:04:38 -05:00

@manotawi commented on GitHub (Jan 27, 2025):

All my AI apps and models are installed in a ssd so I can move them with me. So to preserve that, here was my method:
1- Move the ollama installation where desired, example F:\AI\OLLAMA
2- Inside the ollama installation folder create a folder for the models, example F:\AI\OLLAMA\MODELS
3- create a bat file and add the following to it:
SET OLLAMA_MODELS=%~dp0MODELS
start "" "ollama app.exe"

and tada, with that you have a portable version of ollama, that does not care about the drive or folder it is installed in

@manotawi commented on GitHub (Jan 27, 2025): All my AI apps and models are installed in a ssd so I can move them with me. So to preserve that, here was my method: 1- Move the ollama installation where desired, example F:\AI\OLLAMA 2- Inside the ollama installation folder create a folder for the models, example F:\AI\OLLAMA\MODELS 3- create a bat file and add the following to it: SET OLLAMA_MODELS=%~dp0MODELS start "" "ollama app.exe" and tada, with that you have a portable version of ollama, that does not care about the drive or folder it is installed in

GiteaMirror commented

2026-05-03 14:04:40 -05:00

@JTMarsh556 commented on GitHub (Jan 30, 2025):

Am I reading this correctly, you cannot move all of the existing models you have? You need a fresh install?

You can't just set the variable and then copy the models in the new path?

@JTMarsh556 commented on GitHub (Jan 30, 2025): Am I reading this correctly, you cannot move all of the existing models you have? You need a fresh install? You can't just set the variable and then copy the models in the new path?

GiteaMirror commented

2026-05-03 14:04:42 -05:00

@pratyush0898 commented on GitHub (Feb 2, 2025):

thanks you, but more you can do is:

Move ollama: (folder) C:\Users\ADMIN\AppData\Local\Programs\Ollama to /path/to/Ollama
Change env variable:
- press Win + R
- type systempropertiesadvanced & perss enter
- Go to Environment variables
- Under User variables Doble-click (open) PATH (enviorment variable)
- Locate C:\Users\ADMIN\AppData\Local\Programs\Ollama & change it to `/path/to/Ollama/

here, you go, now your whole OLLAMA is in different location/drive you'd like

@pratyush0898 commented on GitHub (Feb 2, 2025): thanks you, but more you can do is: - **Move ollama**: (folder) C:\Users\ADMIN\AppData\Local\Programs\Ollama to /path/to/Ollama - **Change env variable**: - press `Win + R` - type `systempropertiesadvanced` & perss enter - Go to Environment variables - Under `User variables` Doble-click (open) PATH (enviorment variable) - Locate `C:\Users\ADMIN\AppData\Local\Programs\Ollama` & change it to `/path/to/Ollama/ here, you go, now your whole OLLAMA is in different location/drive you'd like

GiteaMirror commented

2026-05-03 14:04:44 -05:00

@ChanduTadanki commented on GitHub (Mar 5, 2025):

For those the custom path is not considered even after adding OLLAMA_MODELS environment variable and restarting the Terminal. Try restarting the OS once, then it is working. Might be the environment variables are stored in memory of the running Ollama process.

This worked for me. Thanks.

@ChanduTadanki commented on GitHub (Mar 5, 2025): > For those the custom path is not considered even after adding OLLAMA_MODELS environment variable and restarting the Terminal. Try restarting the OS once, then it is working. Might be the environment variables are stored in memory of the running Ollama process. This worked for me. Thanks.

GiteaMirror commented

2026-05-03 14:04:45 -05:00

@buffos commented on GitHub (Mar 22, 2025):

It depends if ollama was installed as system wide or just for the user.
You have two options when you create the Env variables in windows. System and User. Start with the user env, which will probably work and not a system env variable.

@buffos commented on GitHub (Mar 22, 2025): It depends if ollama was installed as system wide or just for the user. You have two options when you create the Env variables in windows. System and User. Start with the user env, which will probably work and not a system env variable.

GiteaMirror commented

2026-05-03 14:04:47 -05:00

@nikolatesla20 commented on GitHub (Jan 11, 2026):

To create an environment variable on Windows you can follow these instructions:

Open Windows Settings. Go to System. Select About Select Advanced System Settings. Go to the Advanced tab. Select Environment Variables.... Click on New... And create a variable called OLLAMA_MODELS pointing to where you want to store the models

Doesn't work

@nikolatesla20 commented on GitHub (Jan 11, 2026): > To create an environment variable on Windows you can follow these instructions: > > Open Windows Settings. Go to System. Select About Select Advanced System Settings. Go to the Advanced tab. Select Environment Variables.... Click on New... And create a variable called OLLAMA_MODELS pointing to where you want to store the models Doesn't work

GiteaMirror commented

2026-05-03 14:04:47 -05:00

@nityam1101 commented on GitHub (Jan 13, 2026):

You are correct and 'Yes' you can move them anywhere you like, via the OLLAMA_MODELS environment variable.

Docs: https://github.com/ollama/ollama/blob/main/docs/faq.md#where-are-models-stored

Updated Link: https://github.com/ollama/ollama/blob/main/docs/faq.mdx#where-are-models-stored

@nityam1101 commented on GitHub (Jan 13, 2026): > You are correct and 'Yes' you can move them anywhere you like, via the `OLLAMA_MODELS` environment variable. > > Docs: https://github.com/ollama/ollama/blob/main/docs/faq.md#where-are-models-stored Updated Link: https://github.com/ollama/ollama/blob/main/docs/faq.mdx#where-are-models-stored

GiteaMirror commented

2026-05-03 14:04:48 -05:00

@fkdp06 commented on GitHub (Mar 31, 2026):

From now you can change your models location from the settings:

@fkdp06 commented on GitHub (Mar 31, 2026): From now you can change your models location from the settings: <img width="1182" height="839" alt="Image" src="https://github.com/user-attachments/assets/48679757-058a-4567-9580-7181ec88b9fc" />

Sign in to join this conversation.

Branches Tags

main

parth-mlx-decode-checkpoints

dhiltgen/ci

hoyyeva/editor-config-repair

parth-launch-codex-app

hoyyeva/fix-codex-model-metadata-warning

hoyyeva/qwen

hoyyeva/launch-backup-ux

parth/hide-claude-desktop-till-release

hoyyeva/opencode-image-modality

parth-add-claude-code-autoinstall

release_v0.22.0

pdevine/manifest-list

codex/fix-codex-model-metadata-warning

pdevine/addressable-manifest

brucemacd/launch-fetch-reccomended

jmorganca/llama-compat

launch-copilot-cli

hoyyeva/opencode-thinking

release_v0.20.7

parth-auto-save-backup

parth-test

jmorganca/gemma4-audio-replacements

fix-manifest-digest-on-pull

hoyyeva/vscode-improve

brucemacd/install-server-wait

brucemacd/download-before-remove

parth/update-claude-docs

parth-anthropic-reference-images-path

brucemac/start-ap-install

pdevine/mlx-update

pdevine/qwen35_vision

drifkin/api-show-fallback

mintlify/image-generation-1773352582

hoyyeva/server-context-length-local-config

jmorganca/faster-reptition-penalties

jmorganca/convert-nemotron

parth-pi-thinking

pdevine/sampling-penalties

jmorganca/fix-create-quantization-memory

dongchen/resumable_transfer_fix

pdevine/sampling-cache-error

jessegross/mlx-usage

hoyyeva/openclaw-config

hoyyeva/app-html

pdevine/qwen3next

brucemacd/sign-sh-install

brucemacd/tui-update

brucemacd/usage-api

jmorganca/launch-empty

fix-app-dist-embed

mxyng/mlx-compile

mxyng/mlx-quant

mxyng/mlx-glm4.7

mxyng/mlx

brucemacd/simplify-model-picker

jmorganca/qwen3-concurrent

fix-glm-4.7-flash-mla-config

drifkin/qwen3-coder-opening-tag

brucemacd/usage-cli

fix-cuda12-fattn-shmem

ollama-imagegen-docs

parth/fix-multiline-inputs

brucemacd/config-docs

mxyng/model-files

mxyng/simple-execute

fix-imagegen-ollama-models

mxyng/async-upload

jmorganca/lazy-no-dtype-changes

imagegen-auto-detect-create

parth/decrease-concurrent-download-hf

fix-mlx-quantize-init

jmorganca/x-cleanup

usage

imagegen-readme

jmorganca/glm-image

mlx-gpu-cd

jmorganca/imagegen-modelfile

parth/agent-skills

parth/agent-allowlist

parth/signed-in-offline

parth/agents

parth/fix-context-chopping

improve-cloud-flow

parth/add-models-websearch

parth/prompt-renderer-mcp

jmorganca/native-settings

jmorganca/download-stream-hash

jmorganca/client2-rebased

brucemacd/oai-chat-req-multipart

jessegross/multi_chunk_reserve

grace/additional-omit-empty

grace/mistral-3-large

mxyng/tokenizer2

mxyng/tokenizer

jessegross/flash

hoyyeva/windows-nacked-app

mxyng/cleanup-attention

grace/deepseek-parser

hoyyeva/remember-unsent-prompt

parth/add-lfs-pointer-error-conversion

parth/olmo2-test2

hoyyeva/ollama-launchagent-plist

nicole/olmo-model

parth/olmo-test

mxyng/remove-embedded

parth/render-template

jmorganca/intellect-3

parth/remove-prealloc-linter

jmorganca/cmd-eval

nicole/nomic-embed-text-fix

mxyng/lint-2

hoyyeva/add-gemini-3-pro-preview

hoyyeva/load-model-list

mxyng/expand-path

mxyng/environ-2

hoyyeva/deeplink-json-encoding

parth/improve-tool-calling-tests

hoyyeva/conversation

hoyyeva/assistant-edit-response

hoyyeva/thinking

origin/brucemacd/invalid-char-i-err

parth/improve-tool-calling

jmorganca/required-omitempty

grace/qwen3-vl-tests

mxyng/iter-client

parth/docs-readme

nicole/embed-test

pdevine/integration-benchstat

parth/remove-generate-cmd

parth/add-toolcall-id

mxyng/server-tests

jmorganca/glm-4.6

jmorganca/gin-h-compat

drifkin/stable-tool-args

pdevine/qwen3-more-thinking

parth/add-websearch-client

nicole/websearch_local

jmorganca/qwen3-coder-updates

grace/deepseek-v3-migration-tests

mxyng/fix-create

jmorganca/cloud-errors

pdevine/parser-tidy

revert-12233-parth/simplify-entrypoints-runner

parth/enable-so-gpt-oss

brucemacd/qwen3vl

jmorganca/readme-simplify

parth/gpt-oss-structured-outputs

revert-12039-jmorganca/tools-braces

mxyng/embeddings

mxyng/gguf

mxyng/benchmark

mxyng/types-null

parth/move-parsing

mxyng/gemma2

jmorganca/docs

mxyng/16-bit

mxyng/create-stdin

pdevine/authorizedkeys

mxyng/quant

parth/opt-in-error-context-window

brucemacd/cache-models

brucemacd/runner-completion

jmorganca/llama-update-6

brucemacd/benchmark-list

brucemacd/partial-read-caps

parth/deepseek-r1-tools

mxyng/omit-array

parth/tool-prefix-temp

brucemacd/runner-test

jmorganca/qwen25vl

brucemacd/model-forward-test-ext

parth/python-function-parsing

jmorganca/cuda-compression-none

drifkin/num-parallel

drifkin/chat-truncation-fix

jmorganca/sync

parth/python-tools-calling

drifkin/array-head-count

brucemacd/create-no-loop

parth/server-enable-content-stream-with-tools

qwen25omni

mxyng/v3

brucemacd/ropeconfig

jmorganca/silence-tokenizer

parth/sample-so-test

parth/sampling-structured-outputs

brucemacd/doc-go-engine

parth/constrained-sampling-json

jmorganca/mistral-wip

brucemacd/mistral-small-convert

parth/sample-unmarshal-json-for-params

brucemacd/jomorganca/mistral

pdevine/bfloat16

jmorganca/mistral

brucemacd/mistral

pdevine/logging

parth/sample-correctness-fix

parth/sample-fix-sorting

jmorgan/sample-fix-sorting-extras

jmorganca/temp-0-images

brucemacd/parallel-embed-models

brucemacd/shim-grammar

jmorganca/fix-gguf-error

bmizerany/nameswork

jmorganca/faster-releases

bmizerany/validatenames

brucemacd/err-no-vocab

brucemacd/rope-config

brucemacd/err-hint

brucemacd/qwen2_5

brucemacd/logprobs

brucemacd/new_runner_graph_bench

progress-flicker

brucemacd/forward-test

brucemacd/go_qwen2

pdevine/gemma2

jmorganca/add-missing-symlink-eval

mxyng/next-debug

parth/set-context-size-openai

brucemacd/next-bpe-bench

brucemacd/next-bpe-test

brucemacd/new_runner_e2e

brucemacd/new_runner_qwen2

pdevine/convert-cohere2

brucemacd/convert-cli

parth/log-probs

mxyng/next-mlx

mxyng/cmd-history

parth/templating

parth/tokenize-detokenize

brucemacd/check-key-register

bmizerany/grammar

jmorganca/vendor-081b29bd

mxyng/func-checks

jmorganca/fix-null-format

parth/fix-default-to-warn-json

jmorganca/qwen2vl

jmorganca/no-concat

parth/cmd-cleanup-SO

brucemacd/check-key-register-structured-err

parth/openai-stream-usage

parth/fix-referencing-so

stream-tools-stop

jmorganca/degin-1

brucemacd/install-path-clean

brucemacd/push-name-validation

brucemacd/browser-key-register

jmorganca/openai-fix-first-message

jmorganca/fix-proxy

jessegross/sample

parth/disallow-streaming-tools

dhiltgen/remove_submodule

jmorganca/ga

jmorganca/mllama

pdevine/newlines

pdevine/geems-2b

jmorganca/llama-bump

mxyng/modelname-7

mxyng/gin-slog

mxyng/modelname-6

jyan/convert-prog

jyan/quant5

paligemma-support

pdevine/import-docs

jmorganca/openai-context

jyan/paligemma

jyan/p2

jyan/palitest

bmizerany/embedspeedup

jmorganca/llama-vit

brucemacd/allow-ollama

royh/ep-methods

royh/whisper

mxyng/api-models

mxyng/fix-memory

jyan/q4_4/8

jyan/ollama-v

royh/stream-tools

roy-embed-parallel

bmizerany/hrm

revert-5963-revert-5924-mxyng/llama3.1-rope

royh/embed-viz

jyan/local2

jyan/auth

jyan/local

jyan/parse-temp

jmorganca/template-mistral

jyan/reord-g

royh-openai-suffixdocs

royh-imgembed

royh-embed-parallel

jyan/quant4

royh-precision

jyan/progress

pdevine/fix-template

jyan/quant3

pdevine/ggla

mxyng/update-registry-domain

jmorganca/ggml-static

mxyng/create-context

jyan/v0.146

mxyng/layers-from-files

build_dist

bmizerany/noseek

royh-ls

royh-name

timeout

mxyng/server-timestamp

bmizerany/nosillyggufslurps

royh-params

jmorganca/llama-cpp-7c26775

royh-openai-delete

royh-show-rigid

jmorganca/enable-fa

jmorganca/no-error-template

jyan/format

royh-testdelete

bmizerany/fastverify

language_support

pdevine/ps-glitches

brucemacd/tokenize

bruce/iq-quants

bmizerany/filepathwithcoloninhost

mxyng/split-bin

bmizerany/client-registry

jmorganca/if-none-match

native

jmorganca/native

jmorganca/batch-embeddings

jmorganca/initcmake

jmorganca/mm

pdevine/showggmlinfo

modenameenforcealphanum

bmizerany/modenameenforcealphanum

jmorganca/done-reason

jmorganca/llama-cpp-8960fe8

ollama.com

bmizerany/filepathnobuild

bmizerany/types/model/defaultfix

rmdisplaylong

nogogen

bmizerany/x

modelfile-readme

bmizerany/replacecolon

jmorganca/limit

jmorganca/execstack

jmorganca/replace-assets

mxyng/tune-concurrency

jmorganca/testing

whitespace-detection

jmorganca/options

upgrade-all

scratch

cuda-search

mattw/airenamer

mattw/allmodelsonhuggingface

mattw/quantcontext

mattw/whatneedstorun

brucemacd/llama-mem-calc

mattw/faq-context

mattw/communitylinks

mattw/noprune

mattw/python-functioncalling

rename

mxyng/install

pulse

remove-first

editor

mattw/selfqueryingretrieval

cgo

mattw/howtoquant

api

matt/streamingapi

format-config

mxyng/extra-args

shell

update-nous-hermes

cp-model

upload-progress

fix-unknown-model

fix-model-names

delete-fix

insecure-registry

ls

deletemodels

progressbar

readme-updates

license-layers

skip-list

list-models

modelpath

matt/examplemodelfiles

distribution

go-opts

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/ollama#63534