The Vim vs Neovim comparison on OctoCounts shows side-by-side source line counts for vim/vim and neovim/neovim, counted under the rules and on the dates stated below: files, total lines, code lines, comment lines, blank lines, and per-language totals, pinned to the exact commits listed below.
This page compares the source lines of code (SLOC) of vim/vim and neovim/neovim using cached OctoCounts reports. Code size is not code quality: a larger count only means more source material, not a better or worse project.
As of 2026-11-15, vim/vim contains 1,711,244 total lines (1,334,803 code) across 3,468 files, while neovim/neovim contains 1,054,757 total lines (736,174 code) across 2,679 files as of 2026-11-15. vim/vim has about 1.8x the counted code lines of neovim/neovim under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.
| Metric | vim/vim | neovim/neovim |
|---|---|---|
| Files | 3,468 | 2,679 |
| Total lines | 1,711,244 | 1,054,757 |
| Code lines | 1,334,803 | 736,174 |
| Comment lines | 176,479 | 196,603 |
| Blank lines | 199,962 | 121,980 |
| Languages counted | 46 | 26 |
Top languages in vim/vim: Vim Script (42.6% of code), C (33.4% of code), PO File (18.1% of code). Top languages in neovim/neovim: C (37.4% of code), Vim Script (32.3% of code), PO File (15.9% of code). Vim Script, C, PO File, C Header appear in both top language lists; Makefile appears only in vim/vim's top languages; Lua appears only in neovim/neovim's top languages.
Methodology: both counts come from cached OctoCounts reports generated with tokei. vim/vim was counted at ref master (commit 6b8b82ff5c5d) on 2026-11-15; neovim/neovim was counted at ref master (commit f1d176d1ab6e) on 2026-11-15. See the counting methodology for ignored directories and analysis options.
Both reports use the same engine and effective counting rules. Repository declarations, when enabled, are specific to each repository. vim/vim: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed. neovim/neovim: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed.
Background observations recorded on 2026-09-16; language descriptions here are historical context, not claims about the current filtered shares. Use this page's measured language breakdown for current counts. Repository layout before counting filters: vim/vim is the Vim repository: the C core, the large runtime directory of syntax, indent, and filetype scripts, documentation, and test directories. neovim/neovim is the Neovim repository: its C core (a fork of Vim), a Lua-based runtime, documentation, tests, and bundled third-party sources. Both repositories include far more than the editor core itself, and their measurements were taken on the dates shown above.
The per-language tables show Neovim's Lua runtime alongside its C core, while Vim's counted code is C with its runtime scripts written in Vim's own script language — a reflection of each project's plugin and configuration story.
Editor repository size does not indicate features, startup time, or resource use; both projects ship runtime files that most users load selectively, so line count is a poor proxy for what an editor does.
Sources: vim/vim repository · neovim/neovim repository. Statements verified 2026-09-16.
Evidence and next steps:
Saved reports remain subject to cache cleanup and replacement. Export their JSON for durable citation; live report URLs can change.
Note: code size is not code quality. OctoCounts only reports reproducible line counts and makes no claim that either project is better.
As of 2026-11-15, vim/vim contains 1,711,244 total lines (1,334,803 code) across 3,468 files, while neovim/neovim contains 1,054,757 total lines (736,174 code) across 2,679 files as of 2026-11-15. vim/vim has about 1.8x the counted code lines of neovim/neovim under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.
Not necessarily. SLOC measures size, not complexity, quality, or maintainability. A larger codebase can mean more features, more generated or vendored code, more verbose language idioms, or more tests — none of which imply the code is harder to work with. Use SLOC to gauge the scale of what you'd be reading or maintaining, not as a quality signal for vim/vim, neovim/neovim, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. vim/vim was counted at ref master (commit 6b8b82ff5c5d) on 2026-11-15; neovim/neovim was counted at ref master (commit f1d176d1ab6e) on 2026-11-15. See the counting methodology for ignored directories and analysis options.
Yes. This page shows the default branch for each repository. Use the interactive comparison tool to pick any public GitHub repository, branch, tag, or commit SHA for both sides and get a fresh side-by-side report.