Try or ByeTry or Bye

Why Is Neovim So Slow? (Startup Lag and Large Files)

Workaround available Windows, macOS, Linux Updated October 21, 2026

Quick answer

Neovim itself is fast; slowness almost always comes from plugins, syntax/Treesitter on huge files, LSP in big projects, or a slow terminal. Compare with nvim --clean, then profile.

Most likely fix: Confirm it's your config.

Symptoms

Startup taking seconds, typing lag, freezes on save, or stutter in large files.

Why it happens

  • Too many eagerly-loaded plugins
  • Heavy highlighting on very large files
  • LSP or formatter doing work on every save
  • Slow terminal emulator or a Debug build

How to fix it

Try these in order — the most common fix is first.

  1. 1. Confirm it's your config

    1. Run nvim --clean (or nvim -u NORC) and compare
    2. If clean is fast, bisect plugins by disabling half at a time

  2. 2. Profile startup

    1. Run nvim --startuptime startup.log and check the slowest entries
    2. With lazy.nvim, open :Lazy profile
    3. Lazy-load plugins by filetype, command or key

  3. 3. Handle big files

    1. Use a big-file plugin (e.g. bigfile.nvim) that disables Treesitter/LSP above a size threshold
    2. Or turn off highlighting for that buffer (:syntax off, or :lua vim.treesitter.stop())

  4. 4. Check build and terminal

    1. Run :version and make sure the build type is Release/RelWithDebInfo, not Debug
    2. Use a fast GPU terminal such as kitty or alacritty

This guide also covers

  • why is neovim so slow
  • neovim slow startup
  • neovim lag large file
  • neovim freezes on save

Still not working?

If Neovim keeps failing, you're not alone. See every Neovim problem users report or the alternatives people switch to.

Other Neovim errors