Where Does Mason Store Neovim Tools?
Mason installs LSP servers, linters, and formatters into a mason folder under Neovim data. Binaries and packages stay per tool.
Last updated
Mason turns tool installation into a Neovim command: servers, linters, formatters, and debug adapters land in a mason folder under Neovim data, each in its own packages subfolder with binaries beside. No system package manager, no sudo, no version drift between machines beyond what you pin.
The data folder is disposable by design. New machine plus Mason install plus one sync command reproduces the toolchain. Do not version control the binaries; version the Mason spec and lock compatible server versions in config instead. PATH shims in bin make the tools callable outside the editor too.
Where Neovim stores this, by platform
%LOCALAPPDATA%\nvim-data\mason
Per tool package folders with binaries beside. Reinstall from the Mason UI on new machines rather than copying. Bin shims expose tools outside the editor.
~/.local/share/nvim/mason
Same packages layout as other platforms. Spec files in config reproduce the set anywhere.
~/.local/share/nvim/mason
Identical under XDG data home. Registry metadata sits beside packages and refreshes from the UI.
Frequently asked questions
How do I update language servers?
Open the Mason UI and update all, then restart the editor. Servers version independently of plugins, so editor updates rarely require tool reinstalls. The registry tracks available versions.
Can I use Mason tools outside Neovim?
Yes through the bin shims beside the packages folder. Add that bin directory to PATH for terminal use. Versions stay managed by Mason regardless of caller.
Notice an outdated path? Let us know.