How to Install NvChad

NvChad is installed as a plugin on top of an existing Neovim setup, not as a standalone editor. You need Neovim already installed, and you should expect to build your own configuration on top of NvChad's defaults rather than treat it as a finished config. The official site provides an Install entry point that leads to the current setup instructions — follow those rather than any older guide, since the project uses lazy.nvim for plugin management and updates.

What you need before starting

• Neovim installed and working. NvChad is a Neovim config, so Neovim must already run on your machine. The site does not state a minimum version, so check the official docs for the current requirement.
• A clean or backed-up Neovim config. NvChad is used as a plugin on top of which you make your own config, so it will occupy your Neovim configuration directory. If you already have a config you want to keep, move it aside first.
• Git and a terminal. The install path goes through the official docs and the project's GitHub repository.
• A Nerd Font (recommended). NvChad ships a UI with statusline, bufferline, and theme components; icon-based UI generally needs a patched font to render correctly. The site does not list this as a hard requirement, so treat it as a practical recommendation.

Install steps

1. Open the official site at nvchad.com and use the Install link. This is the authoritative entry point and points to the current instructions.
2. Follow the documented setup, which installs NvChad into your Neovim config location and bootstraps lazy.nvim as the package manager.
3. Launch Neovim. On first start, lazy.nvim pulls the plugins. Expect the first launch to take longer than later ones.
4. Verify the install by checking that NvChad's UI appears — the statusline, bufferline, and one of the built-in themes should be visible.
5. Start your own config. NvChad is designed to be extended: default plugins, UI, and configuration can be extended, disabled, or overridden. Put your changes in your own config files rather than editing NvChad's internals, so updates stay clean.

Verifying it worked

• Neovim starts without errors and shows NvChad's UI components.
• :Lazy opens the lazy.nvim interface, confirming the package manager is active.
• Startup is fast — NvChad lazy-loads plugins and modules wherever possible, so a slow start usually means something in your own config, not NvChad itself.

Common sticking points

• Treating NvChad as a complete config. It is a base. If you expect it to be your final setup with no further work, you will be surprised. Plan to write your own overrides.
• Editing NvChad's files directly. Because NvChad updates through lazy.nvim, local edits to its internals can be overwritten. Override instead.
• Skipping the docs for version requirements. The site does not publish a Neovim version floor, so confirm it in the official docs before troubleshooting.
• Icon or glyph problems. Broken or missing icons in the UI usually point to a missing or misconfigured Nerd Font, not a broken install.

What you get once installed

If you want a fast, good-looking Neovim base that you shape yourself, install NvChad from the official site and build on top of it. If you want a config you never have to touch, NvChad is the wrong fit — its whole design assumes you will write your own config over it.