Neovim is a continuation of Vim that keeps Vim's editing model and Vimscript but adds a built-in Lua interface, LSP, Tree-sitter and modern defaults; stick with Vim if you rely on Vim9script, because Neovim won't support it.
Neovim's own vision page describes it as not a rewrite but a continuation and extension of Vim, for users who want the good parts of Vim, and more. So the useful way to compare them is as a changelog: what Neovim kept, and what it changed. Everything here is from the two projects' own sites, as of Nov 2026.
Its origin explains the overlap. Neovim is a terminal text editor forked from Vim, created to refactor Vim's original code and make it easier to maintain.
Where each one stands
Vim is a highly configurable text editor and an improved version of the vi editor distributed with most UNIX systems. Vim.org says it's included as vi with most UNIX systems and with Apple OS X. The current version on its home page is Vim 9.2.1316, and Vim 9.2 was released in February 2026 with modernised defaults and support for Wayland and XDG Base Directory specifications. Vim is charityware: free, with a request that you donate to help children in Uganda through the Kuwasha charity.
Neovim describes itself as a hyperextensible Vim-based text editor. Its current stable release is 0.12. It says it has 30% less source code than Vim, and its goals are short: extensible, usable, Vim.
What Neovim changed, as a changelog
- Added: a first-class Lua interface. Your config can live in
init.lua, and you can write Lua plugins. Lua is built in. - Kept: Vimscript. Neovim says it won't deprecate Vimscript and supports it with what it calls the world's most advanced Vimscript engine.
- Kept: Vim's editing model. Neovim says it's fully compatible with Vim's editing model and Vimscript v1, a drop-in for Vim.
- Added: LSP. Built-in language server support for semantic code inspection and refactoring.
- Added: Tree-sitter. Parsing for more accurate syntax highlighting and text objects.
- Added: an RPC API. Extensions can be written in any language, and GUIs, IDEs and web browsers can run
nvim --embedas an editor or script host. - Added: multicursor. Replays commands and mappings on a set of marks.
- Changed: defaults. Strong defaults, a minimalist colour scheme, and modern terminal features on by default, including cursor styling, focus events and bracketed paste.
- Removed: Press ENTER prompts. Neovim lists no Press ENTER messages as a feature.
- Added: session multiplexing.
:connect,:detachand:restart, which Neovim compares to tmux. - Changed: one build. Neovim says it works the same everywhere, with one build type and one command, across all libuv-supported platforms.
Notice what's not on that list. Neovim says it's not trying to turn Vim into an IDE. Its vision is to enable new applications without compromising Vim's traditional roles. In matters of taste, it favours tradition and compatibility, but prefers usability if the benefits are extreme.
What Vim still does its own way
Vim keeps moving too. Its 2026 news includes a GTK 4 GUI backend landing in Vim master alongside the existing GTK 2 and GTK 3 backends, opt-in for now. Vim can also be set up to work in a very simple, Notepad-like way called evim or Easy Vim. And it's honest about itself: Vim.org says it isn't an editor designed to hold its users' hands, and it's a tool you have to learn.
If you write about tech for a living, you'll know how a sharp structure helps readers. The same instinct that helps you explain tracking code structures applies here: list the change, then the reason.
The migration catch: Vim9script
Here's the one that trips people up. Neovim's vision page lists supporting Vim9script as a non-goal. Neovim supports Vimscript v1 and, it says, Vim 8.x plugins, but Vim9script, the newer scripting language in modern Vim, isn't on its roadmap.
So before you switch, check your plugins and your own config. Anything written in Vimscript v1 should carry over. Anything written in Vim9script won't run in Neovim, and you'll need a Lua or Vimscript replacement. If you've built your setup around newer Vim-only plugins, that's the real cost of moving, not the learning curve.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Neovim's tip for anyone coming over: start with :help nvim-from-vim if you already use Vim, or try :Tutor if you don't.
What neither site covers
Neither home page publishes speed or start-up comparisons, so there's no fair number to give on which is faster. For other developer topics, our guide to zip code APIs covers a different corner of the toolbox.
My verdict
If you're starting fresh in 2026, I'd go Neovim: Lua config, LSP and Tree-sitter built in, and the same editing model you'd learn in Vim anyway. If you've got a Vim setup you love, and especially if it leans on Vim9script, stay put. Vim is still maintained, still free, and still the vi that's already on most UNIX machines.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Quick answers
Is Neovim compatible with Vim?
Neovim says it's fully compatible with Vim's editing model and Vimscript v1 and supports Vim 8.x plugins.
Does Neovim support Vim9script?
No. Neovim lists supporting Vim9script as a non-goal, so Vim9script plugins and config won't run.
What is the latest version of Neovim and Vim?
Neovim's current stable release is 0.12, and Vim's home page lists Vim 9.2.1316 as the current version.
Can I configure Neovim with Lua?
Yes. Lua is built in and your config can live in init.lua, though Vimscript still works too.
