Where Does AstroNvim Store Config and Plugin Data?
AstroNvim lives in the standard Neovim folders: user config in one place, plugins and state in three more. All four are below.
Last updated
AstroNvim is a Neovim template, not a fork, so it uses stock Neovim paths. Your personal config (the cloned template with your user folder) lives in the config directory. Plugins, swap state, logs, and caches spread across data, state, and cache directories.
That split keeps troubleshooting tidy. Config problems mean editing the config dir. Broken plugins or stale bytecode mean wiping data or cache and letting them rebuild on next launch, which beats reinstalling Neovim itself.
Where AstroNvim stores this, by platform
~/.config/nvim
Cloned template plus your user config. Companions: ~/.local/share/nvim (plugins), ~/.local/state/nvim (logs, views), ~/.cache/nvim (bytecode, transient data).
~/.config/nvim
Identical four-folder layout as Linux. Homebrew and manual installs share these paths, so switching install methods keeps your setup.
%LOCALAPPDATA%\nvim
Config home on Windows. Data, state, and cache follow Neovim stdpath rules nearby; run :echo stdpath('data') inside Neovim to print the exact roots.
Frequently asked questions
How do I fully uninstall AstroNvim?
Delete the config, data, state, and cache folders for your OS, listed above. Your shell and terminal settings are separate and stay put.
How do I update AstroNvim?
Pull the template repo inside the config folder, then open Neovim and run its plugin update command. If startup breaks, clear the cache folder before retrying.
Notice an outdated path? Let us know.