How to Install Opera Browser on Debian Linux

Opera Browser delivers a fast, Chromium-based browsing experience with integrated privacy tools including a built-in VPN and ad blocker. Unlike Chrome or Firefox, Opera includes native features for social media integration, cryptocurrency wallet support, and a sidebar workspace that reduces tab clutter. It’s available in stable, beta, and developer builds for users who want bleeding-edge features or production stability.

On Debian, you can install Opera using the official APT repository, which provides automatic updates and access to all three release channels. This guide covers repository setup using the modern DEB822 format, GPG key verification, and troubleshooting repository conflicts when running multiple Opera versions simultaneously.

Update Debian Before Opera Browser Installation

First, update your Debian system to prevent any issues during installation:

sudo apt update && sudo apt upgrade

The “apt update” command retrieves package information from the configured sources, while “apt upgrade” installs the latest versions of all packages currently installed on your system.

Install Required Packages For Opera Installation

Next, install the necessary dependencies to facilitate the Opera Browser installation. Run the following command:

sudo apt install software-properties-common apt-transport-https curl ca-certificates -y

These standard packages enable secure repository access on Debian: software-properties-common manages APT sources, apt-transport-https allows HTTPS repositories (similar to Windows requiring security certificates for downloads), curl downloads remote files, and ca-certificates verifies package authenticity.

Import Opera APT Repository

Before importing the Opera repository, you’ll need to import the GPG key to verify the authenticity of the installed packages. This ensures you’re installing genuine packages from the official source. Use the following command to import the GPG key:

curl -fSsL https://deb.opera.com/archive.key | gpg --dearmor | sudo tee /usr/share/keyrings/opera.gpg > /dev/null

This command downloads the GPG key using curl, processes it with gpg –dearmor, and saves it to the /usr/share/keyrings/opera.gpg file.

Next, add the Opera repository to your system. Debian 12 (Bookworm), Debian 13 (Trixie), and all future Debian versions use the modern DEB822 format:

sudo tee /etc/apt/sources.list.d/opera.sources > /dev/null <<EOF
Types: deb
URIs: https://deb.opera.com/opera-stable/
Suites: stable
Components: non-free
Architectures: amd64
Signed-By: /usr/share/keyrings/opera.gpg
EOF

This creates the repository configuration file using the DEB822 format (think of it as a modern, easier-to-read way to configure software sources, similar to how configuration files work in other programs). The command specifies the repository type (deb), location (URIs), suite (stable), component (non-free), architecture (amd64), and the GPG key path for package verification.

Debian 12 (Bookworm) is the oldest currently supported stable Debian version and uses the modern DEB822 .sources format shown above. All current and future Debian releases (12, 13 Trixie, and onwards) use this format as standard. Debian 11 (Bullseye) still uses the legacy .list format, so if you run Debian 11, use the command provided below instead.

echo "deb [arch=amd64 signed-by=/usr/share/keyrings/opera.gpg] https://deb.opera.com/opera-stable/ stable non-free" | sudo tee /etc/apt/sources.list.d/opera.list

Update Package Lists

After adding the Opera repository, update the package list, which is essential and cannot be skipped:

sudo apt update

This command ensures your system is aware of the latest packages available from the Opera repository, allowing you to install the desired version of the Opera browser.

Install Opera Browser

Once you have imported the repository, you can install the Opera browser. You can select to install stable, beta, or developer browser builds or all three, as they share separate installations.

Stable Build Installation

As you have already updated the repository list in the previous section, you can directly install the stable version of Opera with the following command:

sudo apt install opera-stable

During the installation, you may be prompted to configure Opera to allow for more recent version upgrades. Select “NO” and press the “ENTER KEY” to finish the installation. Choosing “YES” may lead to multiple conflicts during future updates. If you encounter issues, refer to the troubleshooting section at the end of the tutorial.

Remember that this prompt appears for each version (stable, beta, and developer). Always select “NO” so the installer does not import duplicate sources.list entries.

Beta Build Installation

To install Opera’s beta version with new features, use this command:

sudo apt install opera-beta

Please note that the beta version may not always be ahead of the stable version, depending on Opera’s release cycle. You could end up with an older client, so exercise caution when using the beta version.

Developer Build Installation

For those interested in trying out the bleeding-edge features and improvements, the developer version of Opera provides early access to experimental capabilities. To install the developer version, run the following command:

sudo apt install opera-developer

Remember that the developer version is experimental and may be unstable or contain bugs. It is not recommended for daily use or in critical environments.

Launch Opera Browser

Terminal Launch Commands

You can start Opera directly from the terminal by using the appropriate command for the version you installed:

Stable command:

opera

Beta command:

opera-beta

Developer:

opera-developer

Desktop Application Launch

You can launch it from your desktop environment for a more user-friendly way to start Opera. Depending on the version you installed, follow the path below:

1. Click on Activities in the top-left corner of your screen.
2. Select Show Applications (usually represented by a grid icon) at the bottom of the sidebar.
3. Search for “Opera” in the search bar or locate the Opera icon for the version you want to launch (Stable, Beta, or Developer).
4. Click on the Opera icon for the release channel you installed to start the browser.

Manage Opera Updates and Removal

Update Opera Browser

To update Opera Browser manually, first update your system’s package list:

sudo apt update

If an update is available, use the upgrade option:

sudo apt upgrade

Alternatively, rerun the install command for your Opera channel to upgrade just that package. Swap opera-stable for opera-beta or opera-developer if you track a different release:

sudo apt install --only-upgrade opera-stable

Remove Opera Browser

To uninstall the Opera Browser, execute the appropriate terminal command based on the version you want to remove:

sudo apt remove opera-stable

sudo apt remove opera-beta

sudo apt remove opera-developer

Remove Opera Repository and GPG Key

If you no longer plan to install or use the Opera Browser on your system, remove the Opera Repository and GPG key to keep your system clean. To delete the Opera Repository, execute:

sudo rm /etc/apt/sources.list.d/opera.sources

Debian 11 (Bullseye) users should remove the legacy format file instead:

sudo rm /etc/apt/sources.list.d/opera.list

Finally, delete the GPG key.

sudo rm /usr/share/keyrings/opera.gpg

Fix Repository Conflicts

Remove Duplicate Repository Files

When running multiple versions of Opera Browser (such as stable, beta, and developer) on your Debian system, you may encounter issues during the apt update process. These complications typically stem from each version of Opera adding its own source list in the /etc/apt/sources.list.d/ directory.

To resolve these issues, begin by removing any redundant source lists while keeping the primary opera.sources entry (or opera.list on Debian 11). Use the following command to delete only the duplicate .list files:

sudo rm /etc/apt/sources.list.d/opera-*.list

Some Opera installations also create a separate opera-stable.list file (and similar files for beta or developer builds) that can be recreated as empty files even after you delete them, which triggers the “configured multiple times” warning during apt update. You can prevent this by removing the extra files, then leaving a read-only placeholder in place for the stable list:

sudo rm /etc/apt/sources.list.d/opera-stable.list
sudo touch /etc/apt/sources.list.d/opera-stable.list
sudo chmod 444 /etc/apt/sources.list.d/opera-stable.list

This keeps a harmless, empty repository file that Opera’s installer cannot modify, while your main opera.sources file (or opera.list on Debian 11) continues to manage updates from the official Opera APT repository without duplicate entry warnings.

If you accidentally remove all source lists, you can restore the Opera repository. For Debian 12 (Bookworm), Debian 13 (Trixie), and all newer versions, use the modern DEB822 format:

sudo tee /etc/apt/sources.list.d/opera.sources > /dev/null <<EOF
Types: deb
URIs: https://deb.opera.com/opera-stable/
Suites: stable
Components: non-free
Architectures: amd64
Signed-By: /usr/share/keyrings/opera.gpg
EOF

For Debian 11 (Bullseye), use the legacy format:

echo "deb [arch=amd64 signed-by=/usr/share/keyrings/opera.gpg] https://deb.opera.com/opera-stable/ stable non-free" | sudo tee /etc/apt/sources.list.d/opera.list

This command reinstates the Opera stable repository with the architecture specification, keyring for security verification, and repository URL.

Refresh Package Lists

After consolidating sources, refresh the package list:

sudo apt update

This command updates APT’s database, ensuring it retrieves package information from the correct, consolidated sources list.

Keep Opera Maintained on Debian

Opera Browser delivers integrated privacy tools, cryptocurrency wallet support, and sidebar workspaces through three release channels: stable, beta, and developer builds. The official APT repository keeps every build patched automatically while letting you pick the balance between stability and new features.

Keep the DEB822 repository definition in place, block redundant .list files with read-only placeholders, and rerun the channel-specific install command whenever a new release appears. With those safeguards, Debian users can test Opera’s upcoming capabilities without breaking system upgrades or relying on manual downloads.