How to Install Opera Browser on Fedora 44

Fedora’s own repositories cover Firefox and Chromium, but Opera’s built-in ad blocking, sidebar messengers, VPN toggle, workspace tools, and separate GX channel live outside Fedora’s package set. To install Opera on Fedora, use Opera’s official RPM repository for DNF-managed packages, or use Flathub when you prefer Flatpak packaging.

Fedora does not include Opera in its default repositories. The RPM path gives mutable Fedora systems Opera Stable, Beta, Developer, and GX packages on supported architectures, while Flathub currently publishes regular Opera and Opera GX Flatpaks for x86_64 desktops.

Install Opera Browser on Fedora

Choose an Opera Installation Method

Method	Source	Builds and Architecture	Updates	Best Fit
Opera RPM repository	Opera’s official RPM packages	Stable, Beta, Developer, and GX on x86_64; Stable and Developer also appear in the repo metadata for aarch64	dnf upgrade	Mutable Fedora desktops, native package integration, and access to every RPM channel
Opera Flatpak	Flathub package for com.opera.Opera	Regular Opera on x86_64	flatpak update	Fedora Atomic desktops, Flathub-centered app management, or users who want the regular browser as a Flatpak
Opera GX Flatpak	Flathub package for com.opera.opera-gx	Opera GX on x86_64	flatpak update	GX users who prefer Flathub packaging or cannot use the native RPM method

For most mutable Fedora desktops, start with the RPM repository. It follows Opera’s official Fedora instructions, keeps updates inside DNF, and exposes the preview channels. Use Flatpak when you run Fedora Silverblue, Kinoite, or another Atomic desktop, or when you already manage desktop apps through Flathub.

Searches for an Opera RPM download usually lead to the same source: Opera’s Linux download page and RPM repository. The repository is safer to document than a hard-coded versioned RPM filename because Opera publishes moving browser builds such as opera_stable-... and opera_gx_stable-... through repository metadata.

Opera needs a graphical desktop session to run. Fedora Server or minimal installations can use the package commands only after you add a desktop environment. On Fedora Atomic desktops, prefer the Flatpak method unless you intentionally manage layered RPM packages.

Update Fedora Before Installing Opera

Refresh Fedora first so DNF uses current package metadata before adding Opera’s repository:

sudo dnf upgrade --refresh

Commands that change system packages use sudo. If your account is not in the sudoers file yet, add a user to sudoers on Fedora before continuing.

Add the Official Opera RPM Repository

Opera publishes its Fedora repository setup in a small manual page. Import Opera’s current RPM signing key before creating the repo file:

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

The current Opera archive key fingerprint published by Opera is 6C86BE214648376680CA957B11EE8C00B693A745. Confirm the imported key by matching the fingerprint stored in the RPM database:

rpm -q gpg-pubkey --qf '%{VERSION}-%{RELEASE}\n' | grep -Ei '^6c86be214648376680ca957b11ee8c00b693a745-'

Relevant output includes:

6c86be214648376680ca957b11ee8c00b693a745-682b1270

Create the Opera repository file that Fedora will use for native packages:

printf '%s\n' \
'[opera]' \
'name=Opera packages' \
'type=rpm-md' \
'baseurl=https://rpm.opera.com/rpm' \
'gpgcheck=1' \
'gpgkey=https://rpm.opera.com/rpmrepo.key' \
'enabled=1' | sudo tee /etc/yum.repos.d/opera.repo > /dev/null

Confirm Fedora sees the repository:

dnf repo list --enabled | grep -E '^opera[[:space:]]'

Relevant output includes:

opera                  Opera packages

Check the Opera packages exposed by the repo:

dnf repoquery --repo=opera 'opera*' --queryformat '%{name}.%{arch}\n' | sort

Relevant package names currently include:

opera-beta.x86_64
opera-developer.aarch64
opera-developer.x86_64
opera-gx-stable.x86_64
opera-stable.aarch64
opera-stable.x86_64

Install an Opera RPM Channel

Choose the channel that matches how stable or experimental you want the browser to be. Install only the package you plan to use.

Build	RPM Package	Terminal Launcher	Best Fit
Stable	opera-stable	opera	Daily browsing and the safest default choice
Opera GX	opera-gx-stable	opera-gx	GX interface, sidebar, and gaming-focused controls
Beta	opera-beta	opera-beta	Previewing features before stable
Developer	opera-developer	opera-developer	Fastest-moving preview channel, with higher breakage risk

Install Opera Stable on Fedora

Install the regular Opera browser for normal day-to-day use:

sudo dnf install opera-stable

Verify the installed RPM package name:

rpm -q --queryformat '%{NAME}\n' opera-stable

opera-stable

Read the exact browser build on your system with opera --version. Opera versions move quickly, so treat that number as current-system output rather than a fixed article value.

Install Opera GX on Fedora

Install Opera GX from the same RPM repository when you want the GX interface and launcher:

sudo dnf install opera-gx-stable

Confirm the GX package is installed:

rpm -q --queryformat '%{NAME}\n' opera-gx-stable

opera-gx-stable

Install Opera Beta on Fedora

Install Opera Beta when you want the next regular browser release before it reaches stable:

sudo dnf install opera-beta

Verify the beta package:

rpm -q --queryformat '%{NAME}\n' opera-beta

opera-beta

Install Opera Developer on Fedora

Opera Developer is the roughest preview channel. Use it for testing browser changes, not as the safest daily driver:

sudo dnf install opera-developer

Verify the developer package:

rpm -q --queryformat '%{NAME}\n' opera-developer

opera-developer

If DNF reports a file conflict while switching between Stable and Developer, remove the older channel first, then repeat the install for the channel you want.

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

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 Flatpak from Flathub

Fedora Workstation includes Flatpak. On Fedora Server, minimal installs, or any mutable Fedora system where flatpak is missing, install it first:

sudo dnf install flatpak

Add Flathub at system scope:

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

Confirm the Flathub remote is available:

flatpak remotes --columns=name,options | grep -E '^flathub[[:space:]]'

flathub system

Install the regular Opera Flatpak with:

sudo flatpak install flathub com.opera.Opera

Install Opera GX from Flathub with the current GX app ID:

sudo flatpak install flathub com.opera.opera-gx

The Opera GX Flatpak ID is com.opera.opera-gx. Older or guessed forms such as com.opera.operagx do not match the current Flathub app record.

Verify whichever Opera Flatpak app you installed:

flatpak list --app --columns=application,branch,origin | grep -E '^com\.opera\.(Opera|opera-gx)[[:space:]]'

Relevant output includes the installed app ID:

com.opera.Opera      stable flathub
com.opera.opera-gx   stable flathub

Use Flatpak for Flathub packaging, Atomic desktops, or app/runtime separation. Do not choose the Opera Flatpaks only for stronger isolation: their current manifests grant broad desktop, device, and display access that browsers often need.

Launch Opera on Fedora

Launch Opera from the Terminal

Use the launcher that matches your install method and channel:

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

Launch Opera from Activities

For a graphical launch, open Activities and search for the browser entry you installed:

• Search for Opera to open the regular RPM or Flatpak build.
• Search for Opera GX when you installed the GX RPM or GX Flatpak.
• Search for Opera Beta or Opera Developer when you installed one of the preview RPM channels.
• Pin the matching launcher to your dock or favorites if you plan to use it regularly.

Update Opera on Fedora

Update Opera RPM Packages

Opera RPM packages update with the rest of the system after the repository is enabled:

sudo dnf upgrade --refresh

To update only an installed Opera RPM channel, use the package name you installed:

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

Run only the line for a package that is installed on your system. For scheduled package updates, DNF Automatic on Fedora covers unattended DNF upgrades.

Update Opera Flatpak Packages

Update all system-scope Flatpak apps and runtimes with:

sudo flatpak update

Target only the Opera Flatpak app you installed when you do not want to update every Flatpak app at once:

sudo flatpak update com.opera.Opera
sudo flatpak update com.opera.opera-gx

Remove Opera from Fedora

Remove Opera RPM Packages

Remove only the RPM package or packages you installed:

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

Check that no Opera RPM package remains installed:

rpm -q opera-stable opera-gx-stable opera-beta opera-developer

package opera-stable is not installed
package opera-gx-stable is not installed
package opera-beta is not installed
package opera-developer is not installed

If you no longer use Opera RPM packages, remove the repository file you created earlier:

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

Verify that DNF no longer has the Opera repository enabled:

dnf repo list --enabled | grep -E '^opera[[:space:]]' || echo "Opera repository is disabled"

Opera repository is disabled

After every Opera RPM package and the repo file are gone, you can also remove Opera’s imported RPM signing key:

sudo rpmkeys --delete 6C86BE214648376680CA957B11EE8C00B693A745 || echo "Opera RPM signing key is not installed."

Verify the Opera signing key is no longer present:

rpm -q gpg-pubkey --qf '%{VERSION}-%{RELEASE}\n' | grep -Ei '^6c86be214648376680ca957b11ee8c00b693a745-' || echo "Opera RPM signing key is not installed."

Opera RPM signing key is not installed.

Leave the key in place if any Opera RPM package or Opera repository remains on the system.

Remove Opera Flatpak Packages

Remove only the Opera Flatpak app you installed:

sudo flatpak uninstall com.opera.Opera
sudo flatpak uninstall com.opera.opera-gx

Confirm that no Opera Flatpak app remains installed:

flatpak list --app --columns=application | grep -E '^com\.opera\.(Opera|opera-gx)$' || echo "No Opera Flatpak apps are installed."

No Opera Flatpak apps are installed.

Flatpak may leave unused runtimes after removing Opera. Review the list before confirming cleanup:

sudo flatpak uninstall --unused

Remove Opera Profile Data

The following commands permanently remove Opera profile data, including bookmarks, saved passwords, browsing history, extensions, site data, and Flatpak sandbox data. Export anything you want to keep before deleting these paths.

Check for Opera profile paths in your account first:

find ~/.config ~/.var/app -maxdepth 2 -type d -iname '*opera*' -print 2>/dev/null

After reviewing the printed paths, remove common native and Flatpak profile directories only when you want a full browser reset:

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

Troubleshoot Opera on Fedora

DNF Cannot Find Opera Packages

DNF usually shows the problem as a missing package argument:

No match for argument: opera-stable

If DNF cannot find opera-stable, opera-gx-stable, opera-beta, or opera-developer, check that the Opera repository is enabled:

dnf repo list --enabled | grep -E '^opera[[:space:]]' || echo "Opera repository is not enabled"

If the repo is enabled but the package list looks stale, refresh DNF metadata:

sudo dnf clean metadata

Query the Opera repository again after the metadata refresh:

dnf repoquery --repo=opera 'opera*' --queryformat '%{name}.%{arch}\n' | sort

Relevant output includes the package names from the Opera repository:

opera-beta.x86_64
opera-developer.aarch64
opera-developer.x86_64
opera-gx-stable.x86_64
opera-stable.aarch64
opera-stable.x86_64

On x86_64 Fedora systems, all four RPM channels should appear. On aarch64 systems, the current repo metadata lists Stable and Developer, while Beta and GX are not currently listed for that architecture.

Flatpak Reports Deploy Not Allowed for User

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

Flatpak system operation Deploy not allowed for user

Keep the remote and install scope aligned by using sudo flatpak install for the system remote:

sudo flatpak install flathub com.opera.Opera
sudo flatpak install flathub com.opera.opera-gx

Confirm the installed app ID after the corrected install:

flatpak list --app --columns=application | grep -E '^com\.opera\.(Opera|opera-gx)$'

Relevant output includes whichever Opera Flatpak app you installed:

com.opera.Opera
com.opera.opera-gx

Opera GX Flatpak ID Is Not com.opera.operagx

Wrong guessed IDs fail before installation:

error: Error searching remote flathub: Can't find ref com.opera.operagx

Use com.opera.opera-gx for the current Opera GX Flatpak. Check the app record before installing when you want to verify the exact ID, architecture, branch, and runtime:

flatpak remote-info flathub com.opera.opera-gx | grep -E '^[[:space:]]*(ID|Ref|Arch|Branch|Runtime):'

            ID: com.opera.opera-gx
           Ref: app/com.opera.opera-gx/x86_64/stable
          Arch: x86_64
        Branch: stable
       Runtime: org.freedesktop.Platform/x86_64/25.08

Opera Developer Conflicts During a Channel Switch

If DNF reports an RPM file conflict while switching between Opera Stable and Opera Developer, remove the installed channel first, then install the replacement channel:

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

Confirm the replacement channel is installed before launching it:

rpm -q --queryformat '%{NAME}\n' opera-developer

opera-developer

Use opera-beta when you want a preview build but do not need the fastest-moving Developer channel.

Conclusion

Opera is installed on Fedora through either Opera’s RPM repository or Flathub, with launchers and update paths kept separate for Stable, GX, Beta, Developer, and Flatpak builds. If you are comparing Chromium-based browsers next, Chromium on Fedora, Google Chrome on Fedora, and Vivaldi on Fedora are worth checking from the same Fedora desktop context.