Where Does NvChad Store Custom Config and Plugins?
NvChad keeps user config in ~/.config/nvim with custom modules under lua/custom, while plugins and Mason data live in ~/.local/share/nvim.
Last updated
NvChad organizes Neovim config with a strict custom versus core split. Your files live under lua/custom inside ~/.config/nvim, safe from upstream updates. Core NvChad files stay pristine and update cleanly.
Plugin data follows standard Neovim XDG paths in local share, including Mason language servers. That separation means updates touch code while your custom tree persists untouched. New machines assemble from a repo clone plus your custom folder.
Where NvChad stores this, by platform
~/.config/nvim/lua/custom
User custom modules under lua/custom survive updates. Core files stay untouched. Share folder holds plugins and Mason servers.
~/.config/nvim/lua/custom
Same custom tree layout as Linux. Config plus share folder migrate together. Terminal Nerd Fonts required for icons.
%USERPROFILE%\AppData\Local\nvim\lua\custom
Windows mirrors the config and share split. Keep custom files platform guarded where paths differ. Lazy restores plugins on launch.
Frequently asked questions
Where do NvChad customizations go?
Edit files under ~/.config/nvim/lua/custom which survives NvChad updates, unlike core files. Mappings, plugins, and plugin configs each get their module. Never edit base NvChad files directly.
How do I migrate NvChad?
Back up ~/.config/nvim for config plus ~/.local/share/nvim for plugins and Mason. Fresh installs clone NvChad then restore custom on top. Lazy syncs plugins from the restored lists.
Notice an outdated path? Let us know.