What is Neovim?
Neovim is a fork of Vim that keeps Vim's modal editing and its key bindings, then rebuilds everything around them. Configuration is written in Lua rather than Vimscript, the editor embeds a Language Server Protocol client so completion and diagnostics work without plugins, tree-sitter is built in for syntax highlighting, and there is a terminal emulator and an API that other programs can drive. The result is a terminal editor that behaves like a modern IDE once configured, at the cost of configuring it. It is free and open source under Apache-2.0, with parts under the Vim licence, and it ships as separate Apple Silicon and Intel builds for macOS 10.15 and later. The current release is 0.12.5.
Verified product facts
- Type
- code editorEditorially reviewed
- Platform
- macOS
- Apple Silicon
- Yes
- Pricing
- Open sourceDeveloper-stated
- Open source
- Yes
- Developer
- Neovim contributorsDeveloper-stated
- Relationship to Nuanyue
- Third-party product — not published by NuanyueEditorially reviewed
- Licence
- Apache-2.0, with parts under the Vim license
- Current version
- 0.12.5Developer-stated
- Official website
- neovim.io
Last updated . Facts marked developer-stated come from the developer and are not independently confirmed; editorially reviewed marks a Nuanyue judgement.
Key features
What Neovim does at a glance.
Keeps Vim's modal editing, key bindings, macros and registers, so existing Vim habits carry over
Configuration
In Lua instead of Vimscript, with the whole editor exposed through a Lua API
A built-in Language Server Protocol client
So completion, diagnostics and refactoring work without a separate plugin manager setup
tree-sitter integration
For syntax highlighting and structural text objects
A built-in terminal emulator
So a shell runs inside the editor
Asynchronous plugin architecture
Keeps the interface responsive while plugins work
An RPC API
Lets other programs and GUIs drive the editor, which is how the various Neovim front ends work
A default configuration
Works out of the box before you write a single line of Lua
Support for the XDG base directory layout, keeping configuration and data out of the home directory root
What you can use Neovim for
- Editing code in a terminal, over SSH or inside a tmux session
- Keeping a Vim workflow while gaining LSP completion and diagnostics
- Writing configuration in Lua rather than Vimscript
- Building a custom editor setup that is reproducible from a dotfiles repository
- Driving the editor from another program through its RPC API
Who is Neovim for?
- People already comfortable with Vim who want a maintained, extensible successor
- Developers who prefer to work in a terminal rather than a windowed IDE
- Anyone who wants an editor they can configure entirely as text and version in Git
Who is Neovim not for?
- Anyone who wants an editor that is productive immediately — VS Code or Zed are the better starting point
- Users who do not want to maintain a configuration, since Neovim's strength is also its setup cost
- People on macOS 10.14 or earlier, as the pre-built binaries require macOS 10.15
Limitations
- The pre-built macOS binaries require macOS 10.15 Catalina or later
- Apple Silicon and Intel Macs need different downloads; there is no single universal build
- The macOS tarballs are not notarized, so the release notes instruct you to run `xattr -c` on the archive to avoid an unknown developer warning
- There is no graphical installer or app bundle: the tarball extracts to a directory you add to your PATH
- Being productive depends on configuration, and a broken plugin update can break the editor until it is fixed
- Licensing is split: Apache-2.0 for most of the project, with parts contributed under the Vim licence
Strengths and trade-offs
What Neovim does well, and what to weigh before choosing it. Points marked developer-stated come from the developer’s own material and have not been independently confirmed.
Strengths
- Free and open source, with no paid tier, account or telemetry.
- Language Server Protocol support and tree-sitter are built in rather than bolted on, so completion and diagnostics need no extra plugin layer.Developer-stated
- Configuration is Lua, and the entire editor is exposed through a Lua API.Developer-stated
- Publishes separate Apple Silicon and Intel macOS builds, so neither kind of Mac runs the editor under translation.
- Keeps Vim's key bindings and modal model, so an existing Vim workflow transfers without relearning.Editorially reviewed
Trade-offs
- Productivity depends on configuration; the editor is minimal until you write or adopt a config.Editorially reviewed
- The macOS builds are not notarized, so the archive needs `xattr -c` before it will open without a warning.Developer-stated
- No universal macOS build and no installer: you choose an architecture and extract a tarball onto your PATH.
- Requires macOS 10.15 or later for the pre-built binaries.Developer-stated
First-use experience
What the app asks of you when you set it up. Only established facts appear here; anything we could not confirm is left out rather than guessed at.
- Installation
- Install with `brew install neovim`, or download `nvim-macos-arm64.tar.gz` for Apple Silicon or `nvim-macos-x86_64.tar.gz` for Intel, run `xattr -c` on the archive, extract it and add the `bin` directory to your PATH.
- First launch Developer-stated
- Running `nvim` with no configuration opens a working editor with sensible defaults, including syntax highlighting. Your own configuration belongs in ~/.config/nvim/init.lua.
- System integration Developer-stated
- Runs inside a terminal emulator rather than as a windowed app, so it has no dock icon or menu bar of its own. It reads the XDG base directories for configuration and data, and exposes an RPC API that other programs can use to drive it.
- Apple Silicon
- Supported
What it is
Neovim is a fork of Vim. It keeps the parts of Vim that people are attached to — modal editing, the key bindings, macros, registers — and rebuilds everything underneath them. Configuration moved from Vimscript to Lua, and the entire editor is exposed through a Lua API rather than a partial one.
The bigger change is what is built in rather than added. A Language Server Protocol client ships with the editor, so completion, diagnostics and refactoring work without assembling a plugin stack first. tree-sitter handles syntax highlighting and structural text objects. There is a terminal emulator, so a shell runs inside the editor rather than beside it.
Why it is set up rather than installed
The honest summary is that Neovim is a toolkit as much as an editor. Running
nvim with no configuration gives you a working editor with sensible defaults —
including syntax highlighting — but the version most people use is the one they
built, usually from a dotfiles repository that grows over years.
That is the trade. Compared with VS Code or Zed, Neovim asks for configuration before it returns the productivity. Compared with Vim, it returns considerably more once configured: asynchronous plugins that keep the interface responsive, an LSP client that needs no glue, and an RPC API that lets other programs drive the editor, which is how the various graphical front ends work.
Installing it on a Mac
The Homebrew route is brew install neovim. The manual route is a tarball:
nvim-macos-arm64.tar.gz for Apple Silicon or nvim-macos-x86_64.tar.gz for
Intel, with no universal build. The pre-built binaries require macOS 10.15
Catalina or later.
Two things catch people out. The tarballs are not notarized, so the release
notes tell you to run xattr -c on the archive before extracting it or macOS
will complain that the developer cannot be verified. And there is no installer
or app bundle — the archive extracts to a directory, and it is up to you to put
its bin folder on your PATH.
Licensing
Most of Neovim is Apache-2.0. The LICENSE file notes that parts of the project were contributed under the Vim licence, which is why the repository’s licence field reads “Other” rather than naming a single SPDX identifier. Anyone redistributing Neovim should read the licence file rather than the summary.
The current release is 0.12.5, published on 23 August 2026.
Release history
Dated releases recorded for Neovim, newest first, each with the source it was read from.
0.12.5
Current stable release, built with LuaJIT and published as separate Apple Silicon and Intel macOS tarballs.
Source: Source repository
0.12.4
Maintenance release on the 0.12 line, published six weeks before 0.12.5.
Source: Source repository
0.12.3
Point release continuing the 0.12 series, which has been the stable line through 2026.
Source: Source repository
Questions about Neovim
Is Neovim free?
Yes. It is free and open source, with no paid tier, account or telemetry. Development is funded through donations and sponsorships.
What is the difference between Neovim and Vim?
Neovim keeps Vim's modal editing and key bindings but rebuilds the internals: configuration is Lua rather than Vimscript, a Language Server Protocol client and tree-sitter are built in, there is an embedded terminal, and an RPC API lets other programs drive the editor.Editorially reviewed
Which macOS version does Neovim need?
The pre-built binaries require macOS 10.15 Catalina or later, according to the project's install documentation.Developer-stated
Does Neovim run natively on Apple Silicon?
Yes. Releases include a separate `nvim-macos-arm64.tar.gz` for Apple Silicon alongside `nvim-macos-x86_64.tar.gz` for Intel Macs. There is no universal build.
Why does macOS warn that the developer cannot be verified?
Because the macOS builds are not notarized. The release notes instruct you to run `xattr -c ./nvim-macos-arm64.tar.gz` on the downloaded archive before extracting it.Developer-stated
What licence is Neovim under?
Apache-2.0 for most of the project, with parts contributed under the Vim licence. The LICENSE file states both.
Alternatives to Neovim
Apps that could replace this one — the same job, a different trade-off.
Vim
An old terminal-based editor.
Neovim is a fork of Vim that keeps the modal editing model and key bindings while replacing the internals with Lua, LSP and tree-sitter.
Competitors
Direct competitors: overlapping features aimed at the same users.
Helix
Modal terminal editor built around multiple selections.
Both are modern modal editors for the terminal, but Helix uses selection-first key bindings and its own configuration while Neovim keeps Vim's model and Lua.
Similar apps
Related in purpose, but not a straight swap.
Visual Studio Code
Free MIT-licensed code editor with a large extension marketplace.
Both are free code editors with extension ecosystems, at opposite ends of the GUI-versus-terminal spectrum.
Works well with
Not a replacement — apps commonly used alongside this one.
iTerm2
Terminal emulator with split panes, search and shell integration.
Neovim runs inside a terminal emulator, so a terminal such as iTerm2 supplies the window, tabs and scrollback the editor itself does not have.
Links
Sources
Facts on this page are checked against the sources below. Last updated .
- Neovim — official websiteGrade B
- Neovim contributors — developer websiteGrade B
- Neovim — documentationGrade C
- Neovim — source repositoryGrade D
