Where Is the Neovide Config File?
Neovide keeps its own TOML config per OS while most behavior still comes from your Neovim init file.
Last updated
Neovide settings live in a TOML config file that appeared in version 0.11. It covers window, font, and frame options. Everything else (keymaps, plugins, LSP) still comes from your regular Neovim init.lua, so most troubleshooting starts by deciding which of the two files owns the behavior.
The config path follows the XDG base directory on Linux and points inside AppData on Windows. macOS also uses ~/.config rather than Library/Preferences, which surprises people. An env variable can relocate the file if you sync dotfiles across machines.
Where Neovide stores this, by platform
C:\Users\<you>\AppData\Roaming\neovide\config.toml
TOML config for window, font, and frame options. Override the location with NEOVIDE_CONFIG. Your init.lua stays where Neovim always kept it.
~/.config/neovide/config.toml
Same filename under ~/.config, not in Library/Preferences. Crash logs sit in ~/Library/Application Support/neovide instead.
~/.config/neovide/config.toml
Respects XDG_CONFIG_HOME when set. Crash traces land in ~/.local/share/neovide/neovide_backtraces.log, overridable with NEOVIDE_BACKTRACES.
Frequently asked questions
How do I reset Neovide without touching my Neovim setup?
Delete or rename config.toml and restart. Neovide falls back to defaults while your Neovim init.lua keeps working. That split makes it easy to tell which layer a problem lives in.
Where does Neovide write crash logs?
Crash logs go to the data directory, not next to the config. On Linux that is ~/.local/share/neovide/neovide_backtraces.log. macOS and Windows use their own app data folders for the same file.
Notice an outdated path? Let us know.