How to Find Neovim Plugins on neovimcraft
Updated
neovimcraft is a curated directory of Neovim plugins, and you can find what you need in two ways: type a keyword into the search box, or browse the category list on the homepage. Each category shows how many plugins it contains, so you can judge at a glance whether a topic is well covered before you click into it. The directory currently lists 1,368 results.
Search by keyword
If you already know roughly what you want, search is the faster path. Enter a term such as a plugin name, a language, or a feature ("fuzzy finder", "statusline", "golang") and the directory filters the curated list down to matching entries.
What you get back is a plugin entry, not just a link. Each result shows:
- Repository name in
owner/repoform, for examplenvim-telescope/telescope.nvim - Star count, a rough signal of how widely a plugin is used
- Created and updated dates, so you can tell whether a plugin is actively maintained
- A short description of what the plugin does
That combination is what makes the directory more useful than a raw GitHub search: you can compare popularity and recency side by side before opening anything.
Browse by category
The homepage lists categories with a count next to each one. The largest groups, based on the counts shown, are:
| Category | Plugins |
|---|---|
| colorscheme | 163 |
| editing-support | 114 |
| programming-languages-support | 108 |
| lsp | 80 |
| utility | 78 |
| git | 56 |
| ai | 52 |
| bars-and-lines | 44 |
| code-runner | 39 |
| markdown-and-latex | 38 |
| note-taking | 36 |
| terminal-integration | 36 |
| pre-made-configuration | 35 |
Smaller, more specific categories also exist, including debugging (25), file-explorer (26), formatting (26), fuzzy-finder (18), session (13), tmux (12), snippet (10), and plugin-manager (10). At the narrow end there are single-entry categories such as discord, jupyter, and jj.
The counts are useful for a practical reason: a category with 163 entries needs a second filter (search within it, or sort by stars), while a category with 3 entries you can just read through.
Reading a plugin entry
Entries follow a consistent format, which makes scanning fast. For example, the pre-made configuration section shows:
nvim-lua/kickstart.nvim— 31,524 stars, created 2022-06-23, updated 2026-09-14, described as "A launch point for your personal nvim configuration"siduck76/NvChad— 28,503 stars, created 2021-03-07, updated 2026-07-03, described as a fast Neovim framework with solid defaults and a UILazyVim/LazyVim— listed under the samepre-made-configurationcategory
The updated date is the field worth checking first. A high star count with an old update date tells a different story than a moderately starred plugin updated recently.
Choosing between similar plugins
When several entries in a category look equivalent, compare them on the same four fields rather than on description alone:
- Stars — a proxy for adoption, not quality.
- Updated date — whether the project is still receiving changes.
- Created date — how long it has existed; a very new plugin may still be settling.
- Description — whether it actually matches your use case, since categories are broad (for instance,
utilitycovers 78 unrelated things).
If you are starting from nothing, the pre-made-configuration category is the place to look first, since those entries bundle many plugins together. If you already have a config and want to add one capability, go straight to the specific category — lsp, git, fuzzy-finder, formatting — and compare entries there.
Related tools on the site
The site also links to a small set of companion tools, which are separate from the plugin directory:
nvim.sh— search for plugins from the terminalpgs.sh— deploy static sites with a single commandtuns.sh— host public web services on localhost using SSHprose.sh— write a blog in markdownbower.sh— a personal blog
If you prefer not to leave Neovim to search, nvim.sh is the relevant one.
Submitting a plugin
If a plugin you use is missing, the directory has a Submit a plugin option. This is how the curated list grows, so entries are reviewed rather than crawled automatically — which is also why the counts per category are modest compared to a full GitHub search.