Vivaldi gives you tab stacking, split-screen views, a built-in mail client, and deep UI customization out of the box, making it a strong alternative to Chrome or Firefox for users who want more control over their browsing workflow. Vivaldi is not available in Fedora’s default repositories, so this guide walks you through how to install Vivaldi on Fedora from the official Vivaldi RPM repository, verify the installation, and manage updates or removal through DNF.
Install Vivaldi Browser on Fedora
Update Fedora System Packages
Refresh your system packages before adding external repositories so DNF has the latest metadata:
sudo dnf upgrade --refresh
This guide uses
sudofor commands that need root privileges. If your user is not in the sudoers file yet, follow the guide on how to add and manage sudo users on Fedora.
Import the Vivaldi RPM Repository on Fedora
Vivaldi is not available in Fedora’s default repositories. Add the official Vivaldi RPM repository, which delivers updates directly from Vivaldi Technologies:
sudo dnf config-manager addrepo --from-repofile=https://repo.vivaldi.com/stable/vivaldi-fedora.repo
This downloads the repository configuration to /etc/yum.repos.d/ and includes GPG key verification for package authenticity. Confirm the repository appears in your repo list:
dnf repolist | grep vivaldi
vivaldi vivaldi
Install Vivaldi Stable or Snapshot Build
Install the stable build for daily browsing:
sudo dnf install vivaldi-stable
Verify the installation:
vivaldi --version
Vivaldi 7.8.3925.66 stable
To test upcoming features instead, install the snapshot build. Both builds can coexist on the same system with separate profile directories:
sudo dnf install vivaldi-snapshot
vivaldi-snapshot --version
Vivaldi 7.9.3950.5 snapshot
Choose Your Vivaldi Build for Fedora
Vivaldi offers two build channels. The table below compares their differences to help you decide which suits your workflow.
| Build | Update Frequency | Best For | Trade-offs |
|---|---|---|---|
| Stable | Every 4-6 weeks | Daily browsing and production use | New features take longer to arrive |
| Snapshot | Weekly or more | Testing new features and reporting bugs | May contain incomplete features or regressions |
For most users, the stable build is recommended because it undergoes thorough QA testing. Install the snapshot alongside stable only if you want to preview upcoming features without risking your primary browsing setup.
Launch Vivaldi Browser on Fedora
Launch Vivaldi from the Terminal
Launch Vivaldi directly from the command line, which is useful for diagnosing startup problems since console output remains visible:
vivaldi
Launch Vivaldi from the GNOME Desktop
Open Vivaldi through the GNOME desktop:
- Click Activities in the top-left corner of your screen.
- Type Vivaldi in the search bar or click Show Applications (grid icon).
- Click the Vivaldi icon to launch the browser.
Manage Vivaldi Browser on Fedora
Update Vivaldi Browser
DNF checks the Vivaldi repository during system upgrades and installs new versions automatically:
sudo dnf upgrade --refresh
The --refresh flag forces DNF to reload repository metadata, ensuring you receive the latest available version. For hands-free updates, see DNF Automatic on Fedora to configure scheduled background updates.
Remove Vivaldi Browser
Remove the stable build:
sudo dnf remove vivaldi-stable
Remove the snapshot build (if installed):
sudo dnf remove vivaldi-snapshot
Both commands preserve your profile data in ~/.config/vivaldi and ~/.config/vivaldi-snapshot, so bookmarks, history, and settings remain available if you reinstall.
Remove the Vivaldi Repository
After uninstalling Vivaldi, remove the repository configuration files to stop DNF from checking for updates:
sudo rm /etc/yum.repos.d/vivaldi*.repo
Vivaldi’s installer creates additional
.repofiles alongside the one you imported. The wildcardvivaldi*.reporemoves all of them. You will need to re-add the repository if you decide to reinstall Vivaldi later.
Remove Vivaldi User Data and Profiles
Uninstalling the Vivaldi package leaves your profile data intact. For a complete removal including all personal data, delete the configuration and cache directories.
The following commands permanently delete your Vivaldi bookmarks, saved passwords, browsing history, and all customizations. Export any data you want to keep before proceeding.
rm -rf ~/.config/vivaldi ~/.cache/vivaldi
Remove snapshot profile data (if installed):
rm -rf ~/.config/vivaldi-snapshot ~/.cache/vivaldi-snapshot
Troubleshooting Vivaldi on Fedora
GPG Key Import Errors
If GPG key verification fails during installation:
Error: GPG check FAILED
Check whether the Vivaldi signing key is imported:
rpm -qa gpg-pubkey* | xargs rpm -qi | grep -i vivaldi
If no output appears, import the key manually and verify:
sudo rpm --import https://repo.vivaldi.com/stable/linux_signing_key.pub
rpm -qa gpg-pubkey* | xargs rpm -qi | grep -i vivaldi
Summary : Vivaldi Package Composer KEY11 <packager@vivaldi.com> public key
Retry the installation command after the key imports successfully.
DNF config-manager –add-repo Error
If you see this error when adding the repository:
unknown argument "--add-repo" for command "config-manager"
This means your system uses DNF5, which changed the subcommand syntax. Use addrepo (no dashes) instead of the old --add-repo flag:
sudo dnf config-manager addrepo --from-repofile=https://repo.vivaldi.com/stable/vivaldi-fedora.repo
Repository Connection Failures
If DNF cannot reach the Vivaldi repository during updates:
Cannot download repodata/repomd.xml
Verify the repository server is accessible:
curl -I https://repo.vivaldi.com/stable/vivaldi-fedora.repo
HTTP/2 200 content-type: application/octet-stream
An HTTP 200 response means the server is reachable and the problem is on your end. Check firewall rules, DNS resolution, or VPN connections. If you receive connection timeouts or HTTP errors, the Vivaldi server may be temporarily unavailable. Wait a few minutes and retry. For more curl command options, see the dedicated guide.
Vivaldi Won’t Launch on Fedora
If Vivaldi fails to start from the desktop, launch it from the terminal to capture error output:
vivaldi
A common error pattern involves missing shared libraries:
error while loading shared libraries: libXss.so.1: cannot open shared object file
Reinstall Vivaldi to restore any missing dependencies:
sudo dnf reinstall vivaldi-stable
If the issue involves a corrupted profile, rename your profile directory to force a fresh start:
mv ~/.config/vivaldi ~/.config/vivaldi-backup
Launch Vivaldi again. If it starts successfully, selectively copy bookmarks and settings from the backup directory.
Frequently Asked Questions
No. Vivaldi is proprietary software and is not packaged in Fedora’s repositories. You must add Vivaldi’s official RPM repository to install it through DNF.
Yes. The stable and snapshot builds use separate binaries, desktop entries, and profile directories, so they coexist without conflict.
Vivaldi includes built-in features like tab stacking, split-screen browsing, a mail client, and extensive UI customization that other Chromium-based browsers typically require extensions to achieve. It also offers a dedicated snapshot channel for early feature testing.
Fedora 41 and later use DNF5, which changed the syntax from --add-repo to addrepo (no dashes). Use: sudo dnf config-manager addrepo --from-repofile=URL
Conclusion
You now have Vivaldi installed on Fedora from the official RPM repository with automatic updates through DNF. The stable build handles everyday browsing, while the snapshot channel lets you preview upcoming features. For alternative Chromium-based browsers, see Google Chrome on Fedora, Opera on Fedora, or Chromium on Fedora.


‘sudo dnf config-manager –add-repo https://repo.vivaldi.com/stable/vivaldi-fedora.repo’
throws error “Unknown argument “–add-repo” for command “config-manager”. Add “–help” for more information about the arguments.”
It has to be rewritten or changed to:
‘sudo dnf-3 config-manager –add-repo https://repo.vivaldi.com/stable/vivaldi-fedora.repo’
https://github.com/rpm-software-management/dnf5/issues/1537
Thanks for the detailed report and GitHub issue link, alex. You were absolutely right. The article had the old DNF4 syntax when you commented in September, and the
--add-repoflag no longer works in DNF5. The article has been updated with the correct syntax for current Fedora releases.The correct command for Fedora 42/43 and onwards (DNF5) is:
Your
dnf-3 config-manager --add-repoworkaround was the right solution during the transition period and still works if you have the DNF4 compatibility packages installed.