Neovim is a free, open-source text editor built on Vim’s modal editing model, with a focus on extensibility and a decoupled architecture. It runs in a terminal on Windows, macOS, Linux, FreeBSD and OpenBSD. It can also sit behind separate graphical front ends or inside other applications. The project’s contributors maintain it. It uses the Apache 2.0 license, while older Vim-derived parts retain the Vim license.
Vim users keep the same modes, motions, operators and Vimscript. Neovim adds a built-in Lua runtime, a language server client, Tree-sitter parsing, a terminal emulator and a programmable API on top of that base.
Vim compatibility and different defaults
Neovim reads Vimscript and supports most Vim plugins, including older Python and Ruby plugins. Those plugins run in separate processes that communicate with Neovim over RPC. Vim9script, the newer Vim language, is not part of Neovim.
Several settings that Vim users typically add by hand are already on. These include filetype detection, syntax highlighting, automatic indentation, incremental and highlighted search, mouse support, an always-visible status line and true colour where the terminal supports it. EditorConfig files and a :Man page viewer also work by default. Configuration, swap, undo and backup files live in standard XDG locations. The main config is therefore init.lua or init.vim under the user’s config folder rather than a .vimrc.
Neovim saves command history, registers, marks and similar state in a ShaDa (“shared data”) file. Several running Neovim instances can read and update this file. New users can work through the interactive lessons in :Tutor, and :checkhealth reports problems with the setup, providers or plugins.
Lua scripting and plugins
Lua is built into Neovim alongside Vimscript. A configuration can set options, define key mappings and autocommands, and call the editor API directly from Lua. Plugin authors use the same tools.
Neovim includes its own plugin manager, vim.pack, which installs, updates and deletes plugins from Git repositories. It keeps them in a dedicated data folder and records each plugin’s exact state in a lockfile. Users can place this lockfile under version control to reproduce the same plugin set elsewhere. It requires Git and is still marked experimental.
Language server support
Neovim includes a client for the Language Server Protocol (LSP). Language servers themselves come from third parties. The user installs a server for a language, then describes it with vim.lsp.config(). This configuration specifies the command to start it, the filetypes it handles and the files that mark a project root. The user then activates it with vim.lsp.enable(). When a matching file opens, Neovim starts the server and attaches it to the buffer. Files in the same project share one connection.
Once attached, the server supplies go-to-definition, references, hover documentation, completion, renaming, code actions, signature help and formatting. Neovim maps many of these to default keys, such as K for hover and a set of gr commands for rename, references and code actions. Features such as inlay hints and code lenses are off until enabled.
Errors and warnings from servers or linters go through Neovim’s diagnostic framework. It sorts them into error, warning, info and hint severities, shows them in the buffer and lets the user jump between them or collect them in the quickfix list.
Tree-sitter parsing
Neovim uses the Tree-sitter library to build a syntax tree of a buffer and update it incrementally as text changes. That tree drives syntax highlighting and structural text objects, so a selection can expand to the enclosing node instead of relying on regular-expression patterns. Neovim includes parsers for C, Lua, Markdown, Vimscript, Vim help files and diffs. Users can add parsers for other languages. Query files define highlighting and other behaviour. Users and plugins can replace these files.
Terminal inside the editor
The :terminal command opens a shell or any other program in a Neovim buffer, backed by a built-in VT220/xterm terminal emulator. Typing goes to the program in terminal mode. Pressing Ctrl-\ Ctrl-N returns to normal mode. There, users can scroll, search and copy the output like any other buffer, in a split next to the code.
Editor server, API and front ends
The Neovim core runs as a server. Every user interface, including the default terminal interface, is a client that connects to it. Several clients can attach to the same running editor. :connect moves the current interface to another server, :detach leaves the session running, and :restart restarts Neovim and reattaches the open interfaces.
Clients use a versioned API over MessagePack-RPC. This lets developers write extensions and tools in almost any language, with client libraries for Python, Node.js, Go, Rust, Ruby and many others.
Independent projects use this design to build graphical front ends such as Neovide, Neovim Qt, GNvim, Goneovim and the macOS app VimR. Others embed Neovim with nvim --embed: vscode-neovim runs it as the editing engine inside Visual Studio Code, and Firenvim puts it into browser text fields.




