LM Studio Taking Up Mac Storage? Check Downloaded Models

Check LM Studio’s My Models directory before clearing generic Mac caches. Downloaded model files are intentional assets and can remain on disk after you unload a model or close a chat. If the storage increase followed several model experiments, start with that inventory.

This guide does not assume a fixed model-directory path. Use the location configured in your installation, especially if you previously moved downloads to another drive.

Separate downloaded models from loaded models

LM Studio’s command-line tool can show both views:

lms ls
lms ps

The official CLI guide identifies ls as the on-disk model inventory and ps as the loaded-model list. If the command is unavailable, inspect My Models in the application rather than installing another tool solely to find a folder.

For a memory problem, unloading may be appropriate. For a full SSD, inspect the downloaded files. The load and unload reference describes memory management separately from storage.

Check whether you kept multiple variants

Model entries with a shared family name may be different quantizations, sizes, or formats. LM Studio’s download guide explains quantization choices and the models-directory setting in My Models.

Create a simple keep-or-review list. Retain the variant that works for your real task, and flag experiments you no longer use. Do not delete by family name alone: one version might be your daily model while another was a performance comparison.

Remove a verified unused download

1. Record the model’s exact identity, format, and purpose.
2. Finish active requests and unload the model.
3. Use the installed app’s model-management controls to locate the corresponding download.
4. If removing files in Finder, quit the app first and remove only the model files you have positively identified. Preserve complete sets for any retained multi-file model.
5. Reopen LM Studio and verify the models you intend to keep still load.

Do not delete the entire application-support directory to remove one download. That broad action does not distinguish model weights from chats, preferences, or other state you may want.

Relocate if you still need the collection

My Models provides a way to change the model directory. Before using it, record the old location and check whether your installed version offers to move existing files or only changes where models are discovered and downloaded. Verify the result rather than assuming a path change copied the collection.

For an external drive, test one model from the destination before removing the old copy. Keep the drive connected for the normal workflow, and avoid making the only copy of a custom or difficult-to-obtain model part of a cleanup experiment.

Look for separate stores if the numbers still do not add up

Other tools may keep independent copies of related models. Our Ollama cleanup guide and Hugging Face cache guide cover those stores. Inspect each owner separately.

Finish by opening your everyday chat or local API workflow and making a normal request. The useful outcome is a smaller, understood collection that still supports your work, not simply an empty models folder.