
Fedora 45 shipped on November 3, 2026, after a couple of delays. Many people are now running a fresh install or an upgrade. The next job is usually the same: get a browser onto the machine that isn’t Firefox, because a specific extension, a work profile or a sync setup needs Chromium. Brave is a common pick. Its shields block trackers and ads by default, and the Chromium base means the sites and web apps you need will work.
Installing Brave on Fedora looks simple, and it mostly is. A few details trip people up, though. Fedora 41 and later use DNF5, so the old --add-repo syntax from many tutorials fails. Fedora defaults to Wayland, and the GNOME builds are Wayland only, which changes how Chromium-based browsers behave. Some users hit blurry text, a blank window or a browser that won’t start. Others find out too late that the Flatpak and the RPM have different sandbox rules.
This guide covers the install methods and when each fits. It also covers the Wayland flags, updates, a lightweight hardening pass, and the errors that show up in practice. The commands come from Brave’s own Linux instructions. The rest comes from running Chromium-based browsers on Fedora workstations and shared lab machines. Work through it in order, or jump to the section you need.
Pick an Install Method
Fedora gives you three realistic options.
| Method | Updates | Sandbox | Best for |
|---|---|---|---|
| Official RPM repo (DNF) | Through dnf upgrade with the system |
Native Chromium sandbox | Most desktops and laptops |
| Install script | Adds the same repo | Native | Quick setups |
| Flatpak (Flathub) | Through flatpak update |
Flatpak sandbox | Immutable systems such as Silverblue |
For a normal Fedora Workstation, use the official repo. Brave publishes the RPM itself, so you get releases when Brave ships them, not when a third-party packager gets to them. Brave’s page notes that it supports 64-bit AMD/Intel and ARM (arm64/aarch64). On an old 32-bit machine you are out of luck.
One caution. Some users report problems with the Flathub build and moved to the terminal install instead. The Flatpak is still a valid choice on Atomic desktops, but it limits what the browser can reach, and that affects things like password managers and native messaging.
Check Your System First
A short check saves time later. Confirm the release and architecture.
cat /etc/fedora-release
uname -m
echo $XDG_SESSION_TYPE
You want Fedora release 45, x86_64 or aarch64, and a session type of wayland or x11. That last value matters in the troubleshooting section.
Then bring the system up to date. Installing a new repo on a half-updated box is a good way to create dependency confusion.
sudo dnf upgrade --refresh
If the kernel updated, reboot before continuing. It takes a minute and removes a whole class of “was it the update?” questions.
Install Brave With the Official Repo
This is the method to use. On Fedora 41 and newer, which includes Fedora 45, Brave documents these commands:
sudo dnf install dnf-plugins-core
sudo dnf config-manager addrepo --from-repofile=https://brave-browser-rpm-release.s3.brave.com/brave-browser.repo
sudo dnf install brave-browser
What each line does
The first line installs dnf-plugins-core, which provides the config-manager subcommand. On many Fedora installs it is already present, so DNF will simply say there is nothing to do.
The second line downloads the .repo file and drops it into /etc/yum.repos.d/. The addrepo --from-repofile= form is the DNF5 syntax. The older --add-repo form that Brave lists for Fedora earlier than 41 and for Rocky/RHEL will produce an error on Fedora 45.
The third line installs the browser. DNF will ask you to accept Brave’s GPG key the first time. Check that the fingerprint prompt appears and accept it. This is the signature check that protects you from a tampered package, so don’t pass -y blindly on the first install if you care about verifying it.
Verify the install
rpm -q brave-browser
dnf repolist | grep -i brave
brave-browser --version
You should see the package version, the repo listed as enabled, and a version string. Launch it from the application grid or run brave-browser in a terminal. Running it from a terminal the first time is a good habit, because any startup errors print right there.
The Install Script Alternative
Brave also offers a one-line script:
curl -fsS https://dl.brave.com/install.sh | sh
It works, and it ends up configuring the same repo. Still, piping a remote script into a shell is a habit worth avoiding on servers and managed machines. If you want to use it, download it first and read it:
curl -fsSO https://dl.brave.com/install.sh
less install.sh
sh install.sh
On a personal laptop the risk is low. On a workstation under change control, stick with the explicit repo commands, which are easier to audit and to script into Ansible.
Install the Flatpak Version
If you run Fedora Silverblue or Kinoite, or just prefer sandboxed apps, use Flatpak.
flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
flatpak install flathub com.brave.Browser
flatpak run com.brave.Browser
Updates come through flatpak update. Be aware of the trade-offs. The browser’s own sandbox sits inside the Flatpak sandbox, file access is limited to what portals allow, and integration with a native password manager needs extra permissions. If something works in the RPM build and not in the Flatpak, this is the first thing to suspect.
You can inspect and adjust permissions with:
flatpak info --show-permissions com.brave.Browser
flatpak override --user --filesystem=xdg-download com.brave.Browser
Grant only what you need.
Run Brave Natively on Wayland
Fedora Workstation runs Wayland, and GNOME builds no longer ship an X11 session in recent releases. Chromium has moved toward picking Wayland on its own, and a Brave issue thread notes the situation improved because Chromium eventually defaulted to Wayland. That said, behavior still varies by release and by desktop.
Check what Brave is really using. Open brave://gpu and look at the Ozone platform line, or run:
ps -ef | grep -i brave | head -n 3
To force native Wayland for one launch:
brave-browser --enable-features=UseOzonePlatform --ozone-platform=wayland
That is the same pair of flags that users on Fedora have relied on for years. A cleaner route is the ozone-platform-hint flag in brave://flags, set to Wayland or Auto.
Make the flags permanent
Editing the system .desktop file works but gets overwritten on updates. Copy it to your home directory instead:
mkdir -p ~/.local/share/applications
cp /usr/share/applications/brave-browser.desktop ~/.local/share/applications/
Open the copy and add the flags to each Exec= line, for example:
Exec=/usr/bin/brave-browser-stable --enable-features=UseOzonePlatform --ozone-platform=wayland %U
Then refresh the desktop database:
update-desktop-database ~/.local/share/applications
Some people use a brave-flags.conf file under ~/.config. This has been suggested as the tidier option, but results are mixed: one 2026 bug report says flags set in a flags file did not show up in brave://version on Fedora 44 with KDE. Always confirm in brave://version that your flags actually reached the command line. Don’t assume.
Screen sharing
On Wayland, screen sharing depends on PipeWire. If sharing a window in a meeting shows a black screen, enable “WebRTC PipeWire support” in brave://flags and relaunch. Check that xdg-desktop-portal and the portal backend for your desktop are installed:
rpm -q xdg-desktop-portal xdg-desktop-portal-gnome
On KDE, swap in xdg-desktop-portal-kde.
First-Run Setup Worth Doing
A fresh Brave profile is decent, but a few settings are worth a look.
- Open
brave://settings/shieldsand decide on the default tracker and ad blocking level. Standard is the sane default. Aggressive breaks more sites. - Review
brave://settings/privacyand turn off anything you don’t want, such as usage pings or the optional rewards features. - Set your search engine and decide whether to use sync. Sync chains are end-to-end encrypted, but keep the chain code safe.
- Enable “Use secure DNS” if your network resolver is not trusted. Pick a provider you actually trust.
- Add
brave://settings/extensionsitems sparingly. Every extension adds attack surface and memory use.
Make Brave the default browser with:
xdg-settings set default-web-browser brave-browser.desktop
xdg-settings get default-web-browser
Keeping Brave Updated
Because the repo is enabled, updates arrive with everything else.
sudo dnf upgrade --refresh
Browsers are one of the most attacked pieces of software on a desktop, so do not let updates lag. Chromium-based browsers regularly ship security fixes, and a browser that has been open for three weeks has probably not applied them. After an update, fully restart Brave. Check the version in brave://settings/help, which will also tell you if a restart is pending.
For unattended updates on a machine you don’t touch daily, use dnf5-plugin-automatic:
sudo dnf install dnf5-plugin-automatic
sudo systemctl enable --now dnf5-automatic.timer
Then check /etc/dnf/automatic.conf (or the DNF5 equivalent under /usr/etc/dnf/) and decide whether it should only download updates or also apply them. On a personal laptop applying them is fine. On shared machines, test first.
If you need to hold a version while a regression is investigated:
sudo dnf install python3-dnf-plugin-versionlock
On DNF5 the versionlock plugin is dnf5-plugin-versionlock. Check what your system offers with dnf search versionlock before relying on a name from memory.
Troubleshooting Common Problems
“Unknown argument –add-repo” or similar DNF error
You used the pre-Fedora 41 command. DNF5 expects the addrepo --from-repofile= form shown earlier.
Brave won’t launch, or the window never appears
Start it from a terminal and read the output.
brave-browser
If the cause looks display related, try each backend. On Fedora with Wayland, one report was resolved by testing both modes:
brave-browser --ozone-platform=x11
brave-browser --enable-features=UseOzonePlatform --ozone-platform=wayland
Whichever one works tells you where the problem is. On a GNOME session without X11 support, the x11 flag may not work at all, so rely on the Wayland one.
Blank or black window after an upgrade
Often a GPU cache issue. Try:
brave-browser --disable-gpu
If that works, the problem is GPU acceleration. Rename the GPU cache folder inside the profile, update Mesa and drivers, and reboot. Then re-enable acceleration.
Blurry text on HiDPI screens
Native Wayland with fractional scaling is usually better than XWayland. Try the Wayland flags above. Also check the scaling in your desktop settings, then test again.
Input method problems (Fcitx5, IBus)
Chinese, Japanese and Korean input can fail on Wayland. A 2026 bug report describes Fcitx5 with Mozc failing in Brave on Fedora 44 KDE even after trying several flag combinations. If you hit this, try --enable-wayland-ime and test X11 as a fallback, and check the upstream issue for the current status. Indonesian and most Latin-script users won’t see this.
Screen sharing shows black
Enable PipeWire in flags, confirm the portal packages, and restart the portal service:
systemctl --user restart xdg-desktop-portal
GPG key or signature error during install
Refresh metadata and retry.
sudo dnf clean all
sudo dnf makecache
sudo dnf install brave-browser
If the key still fails, check your system clock with timedatectl. A wrong date can break signature validation.
Repo returns 404 or times out
The repo is hosted on S3. A proxy, VPN or DNS filter may block it. Test with:
curl -I https://brave-browser-rpm-release.s3.brave.com/brave-browser.repo
A 200 response means the network path is fine.
Upgrading Fedora with Brave installed
Before a major release upgrade, update fully and note third-party repos. After the upgrade, confirm the Brave repo is still enabled with dnf repolist. If packages seem stuck, run sudo dnf distro-sync after checking what it plans to change.