How to Install Opera on Fedora Linux

Opera on Fedora makes sense when you want a Chromium-based browser with built-in VPN, ad blocking, sidebar tools, and battery-saving features without rebuilding the same setup through extensions. Fedora does not ship Opera in the default repositories, so the practical install paths are Opera’s official RPM repository for native packages or Flathub for the sandboxed Flatpak build.

Both methods are straightforward. The real choice is whether you want Opera integrated like a normal Fedora package or isolated in a Flatpak sandbox.

Install Opera on Fedora

Opera is not packaged in Fedora itself, so your choice here is mostly between native RPM integration and Flatpak isolation.

Method	Source	Builds Covered Here	Updates	Best For
Opera RPM repository	Official Opera packages	Opera Stable, Opera Beta, Opera Developer, Opera GX	dnf upgrade	Native installs, Opera GX, and preview channels
Flatpak from Flathub	Flathub	Opera stable	flatpak update	Sandboxed installs with self-contained runtimes

For most Fedora desktops, the RPM repository is the better default because it integrates with regular system updates and also gives you access to Opera GX, Opera Beta, and Opera Developer. Choose Flatpak when you want Opera contained in its own sandbox or you already manage desktop apps through Flathub.

Install Opera from the Official RPM Repository

Start with a normal Fedora update so the package database and dependency set are current before you add Opera’s repository.

sudo dnf upgrade --refresh

These commands use sudo whenever root privileges are required. If your account does not have sudo access yet, follow the guide on how to add a user to sudoers on Fedora.

Import Opera’s signing key:

sudo rpm --import https://rpm.opera.com/rpmrepo.key

Create the repository file Fedora will use for Opera packages:

sudo tee /etc/yum.repos.d/opera.repo <<RPMREPO
[opera]
name=Opera packages
type=rpm-md
baseurl=https://rpm.opera.com/rpm
gpgcheck=1
gpgkey=https://rpm.opera.com/rpmrepo.key
enabled=1
RPMREPO

Verify that Fedora can see the available Opera packages from the new repository:

dnf list --available 'opera*'

Available packages
opera-beta.x86_64      126.x.x opera
opera-developer.x86_64 129.x.x opera
opera-gx-stable.x86_64 127.x.x opera
opera-stable.x86_64    128.x.x opera

As of February 28, 2026, Fedora 43 installed opera-stable, opera-beta, opera-developer, and opera-gx-stable from Opera’s repository. The only verified RPM conflict in testing was opera-stable with opera-developer.

Package	Launcher	Tested Pairing Result	Practical Note
opera-stable	opera	Works with opera-beta and opera-gx-stable; conflicts with opera-developer	Best default for most users
opera-beta	opera-beta	Works with opera-stable, opera-developer, and opera-gx-stable	Good preview channel when you want to keep stable installed
opera-developer	opera-developer	Works with opera-beta and opera-gx-stable; conflicts with opera-stable	Use it instead of stable, not alongside it
opera-gx-stable	opera-gx	Worked with opera-stable, opera-beta, and opera-developer	Separate GX branch with its own launcher

Install Opera Stable on Fedora

Install the regular Opera browser with:

sudo dnf install opera-stable -y

The -y flag auto-confirms the package prompt. Check the installed version to confirm the browser is available from your shell:

opera --version

128.x.x

If you later need wider multimedia support in the native RPM build, the usual Fedora path is enabling RPM Fusion on Fedora for additional codec packages.

Install Opera GX on Fedora from the RPM Repository

Opera GX is packaged separately in the same repository and installs its own launcher as opera-gx:

sudo dnf install opera-gx-stable -y

Verify the GX build the same way:

opera-gx --version

127.x.x

Install Opera Beta on Fedora

Opera Beta tracks the next browser release and installs with its own opera-beta launcher:

sudo dnf install opera-beta -y

Verify the beta build with:

opera-beta --version

126.x.x

Install Opera Developer on Fedora (Unstable Preview)

If by “unstable” you mean Opera’s roughest preview channel, the Fedora package name is opera-developer. On Fedora 43, it coexisted with opera-beta and opera-gx-stable, but it conflicted with opera-stable, so remove stable first if that package is already on your system:

sudo dnf remove opera-stable
sudo dnf install opera-developer -y

If opera-stable is not installed, you only need the second line. Check the developer build with:

opera-developer --version

129.x.x

Install Opera from Flathub on Fedora

Fedora Workstation already includes Flatpak. If you are on Fedora Server, a minimal install, or the flatpak command is missing, install it first:

sudo dnf install flatpak -y

Add Flathub at system scope if it is not already configured:

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

Check that Fedora can see both the built-in Fedora remote and Flathub:

flatpak remotes

fedora	system,oci
flathub	system

Flathub currently ships only the regular Opera build, not Opera GX, and its listing notes that codecs and DRM support are available out of the box. Because you added Flathub at system scope, keep the install at system scope too:

sudo flatpak install --system flathub com.opera.Opera -y

Verify that the Flatpak build is installed:

flatpak list --app | grep -i opera

Opera	com.opera.Opera	127.x.x	stable	system

Launch Opera on Fedora

Launch Opera on Fedora from the Terminal

Use the command that matches the package you installed:

opera
opera-beta
opera-developer
opera-gx
flatpak run com.opera.Opera

Launch Opera on Fedora from Activities

If you prefer the graphical launcher, search for Opera in Activities and open the entry that matches your install:

• Search for Opera to launch the native RPM or Flatpak build
• Search for Opera Beta or Opera Developer if you installed one of the preview RPM channels
• Search for Opera GX if you installed the GX package from Opera’s RPM repository
• Use the matching terminal launcher name such as opera-beta or opera-developer when you want a specific channel
• Pin the launcher to your dock or favorites if you plan to use it regularly

Update or Remove Opera on Fedora

Update Opera RPM Packages on Fedora

If you installed Opera from the RPM repository, you can update it with the rest of Fedora or target only the package you use:

sudo dnf upgrade --refresh
sudo dnf upgrade opera-stable
sudo dnf upgrade opera-beta
sudo dnf upgrade opera-developer
sudo dnf upgrade opera-gx-stable

Use the full system upgrade command when you normally update everything at once. If you only want Opera, run the package-specific line that matches the RPM channel you installed.

Update the Opera Flatpak Build on Fedora

If you installed Opera from Flathub, update it with Flatpak:

sudo flatpak update --system

Remove Opera RPM Packages on Fedora

Remove the native package that matches your install or preview channel:

sudo dnf remove opera-stable
sudo dnf remove opera-beta
sudo dnf remove opera-developer
sudo dnf remove opera-gx-stable

If you no longer want Opera’s repository on the system, remove the repo file you created earlier:

sudo rm -f /etc/yum.repos.d/opera.repo

Check that the repository is gone:

dnf repo list --enabled | grep opera

(no output)

No output means Fedora no longer has the Opera repository enabled.

Remove the Opera Flatpak Build on Fedora

Remove the Flathub build with:

sudo flatpak uninstall --system com.opera.Opera

Remove Opera Profile Data

The following commands permanently remove browser data such as bookmarks, saved passwords, browsing history, and site data. Export anything you want to keep before you delete these directories.

Only remove these directories if you want a full browser reset:

rm -rf ~/.config/opera
rm -rf ~/.var/app/com.opera.Opera

Opera GX can create its own profile directory under ~/.config/. Check the folder name first instead of deleting blindly:

find ~/.config -maxdepth 1 -type d -iname '*opera*'

Look for the Opera GX directory in that output before removing it.

Troubleshoot Opera on Fedora

Opera Developer Conflicts with Opera Stable on Fedora

Current Fedora 43 testing showed only one RPM pairing conflict: opera-developer with opera-stable. Opera Beta coexisted with stable, developer, and GX, while Opera GX also installed alongside the preview channels.

Transaction failed: Rpm transaction failed.
  - file /usr/lib/.build-id/... from install of opera-developer-... conflicts with file from package opera-stable-...

Remove the stable package first, then install the developer channel on its own:

sudo dnf remove opera-stable
sudo dnf install opera-developer -y

If you want a preview build that still sits alongside stable, use opera-beta instead.

Flatpak Install Fails with “Deploy Not Allowed for User”

This error appears when Flathub was added at system scope but the install command is run without sudo:

Warning: Flatpak system operation Deploy not allowed for user
error: Failed to install org.freedesktop.Platform: Flatpak system operation Deploy not allowed for user

Re-run the install at system scope so the remote and package location match:

sudo flatpak install --system flathub com.opera.Opera -y

Force Opera to Use Another Language on Fedora

If Opera stays in English after you change your system locale, create a per-user launcher override instead of editing the package-managed desktop file under /usr/share/applications/:

mkdir -p ~/.local/share/applications
cp /usr/share/applications/opera.desktop ~/.local/share/applications/
sed -i 's/Exec=opera %U/Exec=opera --lang=de %U/' ~/.local/share/applications/opera.desktop

Replace de with the language code you want. For Opera GX, use the same pattern with opera-gx.desktop and Exec=opera-gx %U.

If Fedora is missing the matching locale data, install the language pack too:

sudo dnf install langpacks-de

Common language codes for Opera’s --lang flag include the following:

Language	Code
German	de
French	fr
Spanish	es
Italian	it
Portuguese	pt
Polish	pl
Japanese	ja
Korean	ko
Chinese (Simplified)	zh-CN
Russian	ru

Frequently Asked Questions

Conclusion

Opera fits Fedora cleanly once you pick the channel that matches how stable or experimental you want the browser to be. Use the RPM repository if you want native dnf updates, Opera GX, or the beta and developer preview channels, and use Flatpak if you want tighter sandboxing and simpler cleanup. If you are still comparing browsers, look at Chromium on Fedora, Google Chrome on Fedora, or Vivaldi on Fedora.