How to Get Started with Neovim

Updated

Install Neovim from the official "Install Now" entry on neovim.io, then pick your learning path: if you already use Vim, run :help nvim-from-vim to see what carries over and what changes; if you are new to Vim-style editing, run :Tutor for the built-in interactive tutorial. Your configuration lives in init.lua, and plugins are available through the "Get Plugins" link on the site.

Install Neovim

The site's primary call to action is Install Now, which is the correct starting point for any platform. Neovim describes itself as having "one build-type, one command," so once installed, the nvim command is what you use everywhere.

After installing, verify the setup by launching nvim in a terminal. You should land in the editor with its default minimalist colorscheme — no "Press ENTER" prompts, since Neovim's UI (ui2) removes those.

Choose Your Path Based on Your Background

Your situation First command What it gives you
You already use Vim :help nvim-from-vim A guided explanation of differences and migration notes
You are new to Vim-style editing :Tutor An interactive lesson covering basic motions and commands
You want to configure or extend Edit init.lua Your personal config entry point

If you come from Vim

Neovim is a drop-in Vim: it is fully compatible with Vim's editing model and Vimscript v1. That means your existing habits — modes, motions, operators, registers — still apply. The :help nvim-from-vim page is the official bridge; run it inside Neovim rather than reading it elsewhere, so you can jump to linked help topics directly.

Vimscript is not going away. The FAQ states plainly that Neovim will not deprecate Vimscript, and it ships what the site calls "the world's most advanced Vimscript engine." Lua is built in alongside it, so you can adopt Lua gradually rather than rewriting everything at once.

If you are new

Run :Tutor first. It teaches the editing model interactively, which matters more than memorizing configuration. Only after basic motions feel natural should you move on to plugins and custom config.

Configure with init.lua

Your configuration lives in init.lua. This is where you set options, keymaps, and plugin setup. The site emphasizes that Lua plugins are easy to create and that the API is "discoverable, versioned, documented" — so when you want to know what a function does, the built-in help is the authoritative reference.

A practical order of operations:

  1. Get nvim running and complete :Tutor (or :help nvim-from-vim).
  2. Create init.lua and add a small number of settings you actually understand.
  3. Add plugins one at a time via the "Get Plugins" entry, so you can tell what each one changes.
  4. Use :help for any API or option before searching the web — the documentation ships with the editor.

What You Get Out of the Box

Several features are enabled by default rather than requiring setup:

  • Tree-sitter parsing for accurate syntax highlighting and text objects.
  • LSP for semantic code inspection and refactoring.
  • Built-in :terminal, which the site notes set the standard for treating a TTY as a basic component.
  • Modern terminal features on by default: progress bar, cursor styling, focus events, bracketed paste.
  • Multicursor, which replays commands and mappings across a set of marks.
  • Multiplexing via :connect, :detach, and :restart — described as tmux-like but working everywhere.

Because these are defaults, you do not need a large plugin list to get a capable editor. Add plugins for gaps, not for things already present.

Plugins and Compatibility

Neovim supports Vim 8.x plugins, so much of the existing Vim plugin ecosystem works. For anything new, the "Get Plugins" link on neovim.io is the official pointer. If you are deciding whether a plugin is necessary, check first whether LSP, Tree-sitter, or the built-in terminal already covers the need.

Common Sticking Points

  • Skipping :Tutor or :help nvim-from-vim. These are the two official onboarding paths; going straight to a large config makes problems harder to diagnose.
  • Assuming Vimscript is deprecated. It is not, so you can migrate to Lua at your own pace.
  • Treating Neovim as an IDE-first project. The site states its vision is to enable new applications "without compromising Vim's traditional roles," and notes it has 30% less source code than Vim. Expect an editor that extends well, not a preassembled IDE.
  • Checking version status. The FAQ lists the current stable release as 0.12, with an RSS feed for release news and a roadmap for plans. If a guide references a different version, confirm against the roadmap before following it.

Where to Get Help

Usage and configuration questions belong at GitHub Discussions or vi.stackexchange.com. For project chat, the site lists #neovim:matrix.org and #neovim on irc.libera.chat, plus @Neovim on X, Mastodon, and Bluesky. Bugs and feature requests go to GitHub.