How to Install Neovim on Fedora 44

Neovim keeps Vim’s modal editing, but it is much easier to extend with Lua, LSP clients, and modern plugin managers. That makes it straightforward to install Neovim on Fedora for coding, quick config edits, or remote work after you set up SSH on Fedora, with the DNF package as the cleanest place to start.

Fedora’s repositories already include neovim, so most readers can install it with one command and get the normal nvim executable in every shell. Flathub also ships a Flatpak build for desktop users who prefer that packaging model, while upstream source and generic binary downloads are usually less convenient on Fedora because the packaged methods keep updates simple.

Install Neovim on Fedora

Fedora already packages Neovim, so you do not need RPM Fusion, a COPR repo, or a manual RPM just to get started. The DNF package is the better default if you want the plain nvim command, host shell integration, and the fewest surprises with plugins or remote shells. Use the Flatpak method only when you specifically want Flathub app delivery.

Method	Source	Terminal command	Update behavior	Best fit
DNF package	Fedora packages	nvim	Fedora system updates	Most users, SSH sessions, plugin-heavy setups
Flatpak build	Flathub	flatpak run io.neovim.nvim	Flatpak app updates	Flatpak-first desktop workflows

The DNF package is the best default for most Fedora systems because it gives you a normal nvim command, works cleanly over SSH, and avoids Flatpak path, scope, and host-tooling differences.

Flathub currently marks the Neovim listing as unverified and potentially unsafe, and its manifest grants broad host filesystem access so the editor can open normal files. Treat Flatpak as a packaging and update choice here, not as a stronger isolation boundary.

Neovim’s upstream install page also offers Linux tarballs, AppImages, and source builds. Those paths are useful for special version or portability needs, but they shift update and removal work away from Fedora’s package tools, so they are not the default Fedora workflow.

Install Neovim with DNF on Fedora

Start with the Fedora package if you want the usual terminal workflow and the least setup.

sudo dnf upgrade --refresh

These commands use sudo for tasks that need root privileges. If your account is not in the sudoers file yet, run the commands as root or follow the guide to add a user to sudoers on Fedora.

sudo dnf install neovim

The Fedora package adds the nvim command for terminal use and a Neovim launcher in GNOME Activities on Fedora Workstation. On Server or minimal installs without a desktop session, launch it from the terminal instead.

Verify that Fedora installed the editor and registered the package:

rpm -q neovim
nvim --version | head -1

The exact version follows your Fedora release and enabled updates, but a working install prints an installed neovim package name and an NVIM v... version line.

Install Neovim with Flatpak on Fedora

Use Flatpak when you already manage desktop apps through Flathub or want the Flathub app build. Fedora Workstation includes Flatpak by default, while Server or minimal installs usually need the package first.

sudo dnf install flatpak

Add Flathub as a system remote if it is not configured yet:

sudo flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo

Install the Neovim Flatpak from Flathub:

sudo flatpak install flathub io.neovim.nvim

This method uses sudo because Fedora Workstation normally keeps Flathub as a system-scoped remote. A plain flatpak install can fail with a “Flatpak system operation … not allowed for user” error when the remote is system-scoped.

If you do not have administrator access, do not mix these system-scoped Flatpak commands with a user-scoped setup. A no-admin Flatpak install needs matching --user remote, install, update, and uninstall commands, so treat it as a separate workflow.

Verify that Flatpak registered the application correctly:

flatpak info io.neovim.nvim | grep -E '^[[:space:]]*(ID|Ref|Arch|Branch|Version|Origin|Installation|Runtime):'

The output should show ID: io.neovim.nvim, Origin: flathub, and the installation scope used on your system.

Start Using Neovim on Fedora

After installation, start with the terminal first. That immediately tells you which command belongs to the method you chose and avoids confusion later when you open files over SSH or from a shell script.

Open Neovim from the Terminal

# DNF package
nvim

# Flathub build
flatpak run io.neovim.nvim

If the Flatpak method leaves nvim unavailable in your shell, that is expected. Use flatpak run io.neovim.nvim, or add an alias in your shell profile only if you want a shorter command.

Open or Create a File in Neovim

Neovim creates a new file if the path does not exist, so the same command works for editing an existing file or starting a fresh note.

# DNF package
nvim ~/notes/todo.md

# Flathub build
flatpak run io.neovim.nvim ~/notes/todo.md

Inside Neovim, press i to enter Insert mode and start typing. Press Esc to leave Insert mode, use :wq to save and quit, and use :q! to leave without saving changes.

Launch Neovim from Activities on Fedora Workstation

The DNF package installs /usr/share/applications/nvim.desktop, and the Flatpak build adds its own launcher. On Fedora Workstation, search for “Neovim” in Activities and open it from the results. On Server or minimal systems without GNOME, stick with the terminal commands above.

Configure Neovim on Fedora

Neovim supports both Lua and Vimscript configuration on Fedora. New setups usually start with init.lua, while older Vimscript-based setups can still use init.vim. The configuration directory depends on the install method: the DNF package uses ~/.config/nvim, while the Flatpak build reads its config from ~/.var/app/io.neovim.nvim/config/nvim.

Create a Minimal init.lua for the DNF Package

Create the normal Neovim configuration directory if you installed the DNF package:

mkdir -p ~/.config/nvim

Then write a small Lua config that enables line numbers, spaces for indentation, true color, and clipboard integration when a provider is available:

cat <<'EOF' > ~/.config/nvim/init.lua
vim.g.mapleader = " "
vim.opt.number = true
vim.opt.relativenumber = true
vim.opt.expandtab = true
vim.opt.shiftwidth = 4
vim.opt.tabstop = 4
vim.opt.termguicolors = true
vim.opt.clipboard = "unnamedplus"
EOF

Open the file again with nvim ~/.config/nvim/init.lua whenever you want to extend the setup. The unnamedplus option uses the system clipboard once a Wayland or X11 clipboard provider is available.

Create a Minimal init.lua for the Flatpak Build

The Flatpak build uses a different user configuration root, so place the same Lua file under the app’s sandbox data directory:

mkdir -p ~/.var/app/io.neovim.nvim/config/nvim

cat <<'EOF' > ~/.var/app/io.neovim.nvim/config/nvim/init.lua
vim.g.mapleader = " "
vim.opt.number = true
vim.opt.relativenumber = true
vim.opt.expandtab = true
vim.opt.shiftwidth = 4
vim.opt.tabstop = 4
vim.opt.termguicolors = true
vim.opt.clipboard = "unnamedplus"
EOF

Open the Flatpak-specific config file with the Flatpak command when you need to edit it later:

flatpak run io.neovim.nvim ~/.var/app/io.neovim.nvim/config/nvim/init.lua

Choose a Neovim Plugin Manager or Starter Configuration

lazy.nvim is the better fit if you want to keep the minimal config above and add plugins one at a time. It works well when you want fast startup and a setup you understand piece by piece.

kickstart.nvim makes more sense when you would rather start from a working Lua template with LSP, Treesitter, Telescope, and keymaps already wired up. That is often the faster path if you are building Neovim into a full development environment instead of a lightweight editor.

Both options clone files from GitHub, so make sure git --version works first. If it does not, install Git on Fedora before you start pulling plugin managers or starter configs.

git --version

Modern Lua plugin managers do not require Fedora’s Python provider by default. If :checkhealth provider or a specific plugin asks for Python support, install Fedora’s optional Neovim Python provider package:

sudo dnf install python3-neovim

Run :checkhealth provider again after installing it. Skip this package when your plugin set does not need Python-backed Neovim integration.

Update or Remove Neovim on Fedora

Update Neovim Installed with DNF

The repository package updates through normal Fedora system upgrades. This also updates optional DNF-installed companions such as python3-neovim if you installed them.

sudo dnf upgrade --refresh

Update Neovim Installed with Flatpak

The Flathub build updates through Flatpak:

sudo flatpak update io.neovim.nvim

Remove the DNF Neovim Package

DNF5 removes the package and can clean unused dependencies through its normal removal behavior. Review the transaction before confirming so you know which related packages will also leave the system.

sudo dnf remove neovim

If you installed the optional Python provider and no longer need it, remove that package separately:

sudo dnf remove python3-neovim

Remove the Flatpak Neovim Build

Use the system-scoped uninstall command if you installed Neovim from Flathub with sudo:

sudo flatpak uninstall io.neovim.nvim

If you also want Flatpak to remove runtimes that nothing else uses, run this optional cleanup step afterward:

sudo flatpak uninstall --unused

Delete Neovim Configuration and Plugin Data

The following commands permanently delete your Neovim configuration, plugins, state files, and Flatpak sandbox data. Back up anything you want to keep before removing these directories.

If you followed the DNF configuration section, ~/.config/nvim contains your own settings. After Neovim runs, it also creates state under ~/.local/share/nvim and ~/.local/state/nvim. The Flatpak build stores its config, data, and cache under ~/.var/app/io.neovim.nvim.

rm -rf ~/.config/nvim
rm -rf ~/.local/share/nvim
rm -rf ~/.local/state/nvim
rm -rf ~/.var/app/io.neovim.nvim

Some plugin combinations also create ~/.cache/nvim. Remove it too if that directory exists on your system:

rm -rf ~/.cache/nvim

Verify that the package and the Flatpak build are both gone:

rpm -q neovim
flatpak list --system --app --columns=application | grep -Fx io.neovim.nvim || echo "Flatpak app not installed"

package neovim is not installed
Flatpak app not installed

The Flatpak check prints Flatpak app not installed when the Flathub build has been removed from the system scope.

Troubleshoot Neovim on Fedora

Fix “command not found: nvim” After the Flatpak Install

This usually happens when Neovim was installed from Flathub instead of DNF. The Flatpak build runs through the app ID, so a plain shell may not expose a normal nvim binary.

zsh: command not found: nvim

Verify that the Flatpak build works by launching it directly:

flatpak run io.neovim.nvim --version | head -1

A working Flatpak launch prints an NVIM v... version line. If you want the plain nvim command in every shell, reinstall Neovim with the DNF method. Otherwise keep using flatpak run io.neovim.nvim or add a shell alias in your preferred profile.

Fix Clipboard Warnings in Neovim

If copying and pasting does not work, check Neovim’s provider health from inside the editor:

:checkhealth provider

Clipboard (optional) ~
- WARNING No clipboard tool found. Clipboard registers (`"+` and `"*`) will not work.

This warning is common in plain SSH sessions because the remote shell has no access to your local desktop clipboard. Fedora’s Neovim package recommends clipboard helpers, but stripped-down installs or systems with weak dependencies disabled may still miss them. On Wayland sessions, install wl-clipboard. On X11 sessions, install xsel.

# Wayland sessions
sudo dnf install wl-clipboard

# X11 sessions
sudo dnf install xsel

Restart Neovim inside your graphical session and run :checkhealth provider again. If you edit files only over SSH without X11 or Wayland forwarding, clipboard integration with your local desktop still will not work until that remote session can reach a real clipboard provider.

Conclusion

Neovim is ready on Fedora with either the native nvim command from DNF or the Flathub app command for Flatpak-first desktops. If plugins are next, install Git on Fedora. For remote config edits and server work, set up SSH on Fedora and keep the DNF build in your shell.