The app bundle is the small part. What survives an ordinary uninstall is the model cache, and on a machine that has been running local models for a few months that is frequently the biggest folder on the disk. People discover this when they uninstall to reclaim space, empty the Trash, and find the space did not come back.
LM Studio does not publish an uninstall procedure, so the list below is locations to check rather than a vendor instruction. Look at each one before deleting it, because a couple of them may not exist on your install and one of them you probably want to keep.
Where does LM Studio put things on a Mac?
Four places, plus wherever you pointed the model directory if you moved it. The app is in /Applications. Models default to ~/.cache/lm-studio/models. The lms command-line tool lives under ~/.lmstudio. Settings and app state sit under ~/Library, in the usual macOS locations. Only the first is removed by dragging the app to the Trash.
The models directory is the one that matters, and it is also the one most likely to have moved. LM Studio's own docs note you can change the models directory from the app, and people with small startup disks routinely point it at an external drive. If you did that, the path below is not where your models are. Check the app's model directory setting before you uninstall, or you will delete an empty default and leave fifty gigabytes on a Thunderbolt drive.
Before you delete the models: they are portable
LM Studio stores models as plain GGUF files with real filenames, not as an opaque cache. Any other llama.cpp-based tool can load them from disk with no conversion and no export step. If you are uninstalling because you are switching apps rather than because you are done with local AI, moving the folder is faster than redownloading tens of gigabytes.
This is worth pausing on because it is the opposite of the situation with some other runners, where the weights live in a content-addressed store under sha256 filenames and getting them out takes manual digest mapping. LM Studio's storage is honest and unlocked. The full move is in the migration guide, and it is mostly one mv.
Delete them if you actually want the disk space back. Keep them if you are switching tools. Do not delete them by accident because they were in a hidden folder you did not know about.
Removing it completely
Work through these in order. Steps three and four are optional cleanup that matters if you are reinstalling to fix a broken install, and does not matter much otherwise.
What if you are uninstalling to fix something?
A clean reinstall is a reasonable move when an app will not start, but do it in the right order or you will lose data you did not mean to lose. Remove the app and the state under ~/Library, and leave the models directory alone. That gives you a fresh app against your existing library, which is the reinstall you actually wanted. The launch failures worth ruling out first are in the not-working guide, and several of them do not need a reinstall at all.
The alternative: somewhere you can see
If the reason you are here is that a hidden cache surprised you, that is a design choice rather than an accident, and it is one worth checking in whatever you install next.
ToolPiper stores models in ~/Library/Application Support/ToolPiper/models/ as plain, named GGUF files. Not a dotfolder, not a content-addressed store, not a cache directory. You can open it in Finder, see what each file is from its name, and point any llama.cpp-compatible tool at it. Leaving ToolPiper someday would need no guide at all, which is the same property that makes LM Studio's library easy to take with you.
The engine is upstream llama-server embedded directly, build b10068, so the models you keep from LM Studio load unchanged. Expect parity on speed rather than an improvement: our same-bytes benchmark on an M2 Max came in within single digits in both directions with the winner flipping by model. The free tier is the whole runner, including unlimited downloads, multi-model switching, the local OpenAI-compatible API, embeddings, all speech, browser automation, and an MCP server with over 420 tools. Local RAG over your files is the $10 Pro tier.
The honest limits: macOS 26 or newer and Apple Silicon only, which is a higher floor than LM Studio's macOS 14.0. If your Mac is older, keep what you have.
If the uninstall was a decision rather than a cleanup, the cost side is short. LM Studio's local app is free and its cloud tier bills per million tokens. Our runner is free with no account, and the paid tiers buy capabilities outside model running altogether. The comparison in full.