Where Does vim-plug Store Plugins?
vim-plug clones plugins into a plugged directory, defaulting under .vim. One folder per plugin keeps installs inspectable.
Last updated
vim-plug keeps the oldest simple layout in plugin managers: one plugged directory holding one folder per plugin, defaulting under the vim home. The vimrc declares the set with Plug lines, and the install command clones whatever is missing. No lockfiles, no registries, just git checkouts.
Neovim users get the same layout under their data or config roots depending on the plug call path in init files. The begin and end calls in config define the directory, so inherited configs may point anywhere. Read those two lines before hunting the filesystem.
Where Vim stores this, by platform
C:\Users\[Username]\vimfiles\plugged
One folder per plugin here per the plug call path in vimrc. Update pulls every checkout forward. Clean lists orphans from removed Plug lines.
~/.vim/plugged
Default vim home location. Neovim setups may redirect under the data root; check the plug begin path in config first.
~/.vim/plugged
Same default as macOS. The begin call in vimrc is authoritative when a setup relocates the folder.
Frequently asked questions
How do I fully remove a plugin?
Delete its folder under plugged and remove the Plug line, then restart. Leftover folders from removed lines sit inert. The clean command lists orphans for deletion.
How do I update all plugins?
Run the update command, which pulls every plugin forward. Snapshot first if the setup matters: plugin updates break configs on bad days, and the rollback is reinstalling the old commit by hand.
Notice an outdated path? Let us know.