How to Install Opera Browser on Debian

Opera Browser provides a Chromium-based browsing experience with built-in privacy tools that eliminate the need for separate extensions. The integrated VPN masks your IP address without requiring third-party software, while the ad blocker speeds up page loads by filtering tracking scripts and advertisements before they reach your browser.

Common uses include private browsing sessions where a VPN is essential, managing multiple social accounts through the sidebar workspace, and testing web applications across different browser engines. By the end of this guide, you will have Opera installed from the official APT repository with automatic updates enabled, plus the knowledge to switch between stable, beta, and developer builds when testing new features.

This guide covers Debian 11 (Bullseye), Debian 12 (Bookworm), and Debian 13 (Trixie). Operaโ€™s repository uses a universal โ€œstableโ€ branch that works across all supported Debian versions without version-specific configuration.

Choose Your Opera Installation Method

Two installation methods are available, each with different trade-offs. Review the comparison below to choose the approach that fits your needs.

MethodChannelUpdatesGPG Key ManagementBest For
extrepo (Recommended)Opera APT RepositoryAutomatic via APTAutomaticMost users; quick setup with minimal configuration
Manual RepositoryOpera APT RepositoryAutomatic via APTManual downloadScripted deployments, custom configurations, or learning APT internals

Most users should choose extrepo because Debian maintains the GPG keys and repository configuration, reducing maintenance overhead. The extrepo tool automatically handles key downloads, version detection, and placement in the correct directories. However, the manual method offers more transparency if you want to understand exactly what gets added to your system, or if you need to customize the repository settings for automation scripts.

Update Debian Before Installation

Before installing Opera, update your Debian system to ensure package dependencies are current:

sudo apt update && sudo apt upgrade

This command retrieves the latest package information and upgrades installed packages to their newest versions, which helps prevent potential conflicts during Opera installation.

Method 1: Install Opera with extrepo (Recommended)

The extrepo tool is Debianโ€™s official utility for managing external repositories. It handles GPG key downloads, repository configuration, and version detection automatically, which makes it the simplest way to install Opera on Debian.

Install extrepo

First, install the extrepo package from Debianโ€™s repositories:

sudo apt install extrepo

Enable Non-Free Repository Policy

Since Opera is proprietary software, extrepo requires enabling the non-free policy before you can add Operaโ€™s repository. You can do this with a single command:

sudo sed -i 's/# - non-free/- non-free/' /etc/extrepo/config.yaml

This command uncomments the - non-free line in the extrepo configuration file, enabling access to proprietary software repositories.

If you prefer to edit the file manually, open /etc/extrepo/config.yaml in a text editor and remove the # character from the - non-free line under enabled_policies.

Verify Opera Availability

Before enabling the repository, confirm that extrepo can find Operaโ€™s repository definition:

extrepo search opera

You should see output similar to the following:

Found opera_stable:
---
description: The Opera Browser (final releases)
policy: non-free
source:
  Architectures: amd64 i386
  Components: non-free
  Suites: stable
  Types: deb
  URIs: https://deb.opera.com/opera-stable

This output confirms that extrepo recognizes the Opera repository and has the correct metadata to configure it.

Enable the Opera Repository

With the non-free policy enabled, add Operaโ€™s official repository:

sudo extrepo enable opera_stable

Despite the name opera_stable, this repository provides all three Opera builds: stable, beta, and developer. You only need to enable this single repository to access all versions.

Next, update the package index to include packages from the newly added repository:

sudo apt update

Then, verify that APT recognizes the Opera repository and lists available packages:

apt search opera

You should see all three Opera builds available:

opera-beta/stable 126.0.5750.11 amd64
  Fast and free alternative web browser (beta stream)

opera-developer/stable 126.0.5748.0 amd64
  Fast and free alternative web browser (developer stream)

opera-stable/stable 125.0.5729.49 amd64
  Fast and free alternative web browser

Finally, confirm the repository source by checking the package policy:

apt-cache policy opera-stable
opera-stable:
  Installed: (none)
  Candidate: 125.0.5729.49
  Version table:
     125.0.5729.49 500
        500 https://deb.opera.com/opera-stable stable/non-free amd64 Packages

The version numbers in your output will reflect the current Opera releases at the time of installation. The key indicator of success is seeing the https://deb.opera.com URL in the version table.

Once verified, continue to the Install Opera Browser section below to complete the installation.

Method 2: Configure Repository Manually

Alternatively, if you prefer explicit control over repository configuration or need to script the installation, you can set up Operaโ€™s repository manually using the modern DEB822 format. This approach gives you full visibility into the GPG key and repository configuration being added to your system.

Install Prerequisites

Before proceeding, install the required tools for downloading and verifying the GPG key:

sudo apt install curl gpg -y

The curl command handles the download, while gpg converts the key from ASCII-armored format to the binary format APT requires.

Import the Opera GPG Key

Next, download and install Operaโ€™s GPG signing key to verify package authenticity:

curl -fsSL https://deb.opera.com/archive.key | sudo gpg --dearmor -o /usr/share/keyrings/opera.gpg

This command downloads the GPG key using curl, converts it from ASCII-armored format to binary using gpg --dearmor, and saves it directly to the keyrings directory. The -fsSL flags ensure silent operation with error reporting, following redirects as needed.

Add the Opera Repository

Now, create the repository configuration file using 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 configuration specifies the repository type, location, suite, component, architecture, and GPG key path for package verification. The DEB822 format uses explicit field names, making the configuration more readable and less error-prone than the older one-line format.

The DEB822 .sources format is the modern standard for APT repository configuration. All supported Debian versions (11, 12, 13, and newer) fully support this format, which offers clearer syntax and better error messages than legacy .list files.

Verify Repository Configuration

First, update the package index to include the new repository:

sudo apt update

Look for output confirming the Opera repository was fetched:

Get:4 https://deb.opera.com/opera-stable stable InRelease [2416 B]
Get:5 https://deb.opera.com/opera-stable stable/non-free amd64 Packages [1161 B]

Then, confirm that APT recognizes the Opera repository:

apt-cache policy opera-stable
opera-stable:
  Installed: (none)
  Candidate: 125.0.5729.49
  Version table:
     125.0.5729.49 500
        500 https://deb.opera.com/opera-stable stable/non-free amd64 Packages

This output shows Opera available from the official repository with a 500 priority, which confirms successful setup.

Install Opera Browser

With the repository configured (using either method above), you can now install Opera Browser. Opera offers three release channels: stable for everyday use, beta for previewing upcoming features, and developer for testing experimental capabilities. You can install multiple versions simultaneously since they use separate binaries and configuration directories.

Install Stable Build

Install the stable version of Opera for everyday browsing:

sudo apt install opera-stable

During installation, you may be prompted to configure Opera for version upgrades. Select NO and press Enter. However, Operaโ€™s installer creates a duplicate .list file regardless of your selection, so you need to remove it after installation to prevent APT warnings.

After installation completes, remove the duplicate repository file that Operaโ€™s installer created:

sudo rm -f /etc/apt/sources.list.d/opera-stable.list

This cleanup step applies to both extrepo and manual repository methods. Operaโ€™s postinst script always creates this .list file, which duplicates your existing .sources configuration and triggers APT warnings during updates.

Finally, verify the installation by checking the version:

opera --version
125.0.5729.49

Install Beta Build (Optional)

The beta channel provides early access to features planned for the next stable release. You can install it alongside or instead of stable:

sudo apt install opera-beta

As before, select NO when prompted. After installation, remove the duplicate repository file:

sudo rm -f /etc/apt/sources.list.d/opera-beta.list

Then verify the installation:

opera-beta --version
126.0.5750.11

Install Developer Build (Optional)

The developer channel provides early access to experimental features for testing purposes. This version may contain bugs, so avoid using it for daily browsing:

sudo apt install opera-developer

Again, select NO when prompted. After installation, remove the duplicate repository file:

sudo rm -f /etc/apt/sources.list.d/opera-developer.list

Then verify the installation:

opera-developer --version
126.0.5748.0

Launch Opera Browser

Launch from Terminal

Start Opera directly from the terminal using the command for your installed version. To start the stable version:

opera

Alternatively, launch the beta or developer versions with their respective commands:

opera-beta
opera-developer

Launch from Applications Menu

You can also launch Opera from your desktop environment:

  1. Click on Activities in the top-left corner of your screen (or press the Super key).
  2. Type โ€œOperaโ€ in the search bar.
  3. Click on the Opera icon for the version you want to launch (Stable, Beta, or Developer).

Enable Built-in Features

After launching Opera for the first time, you can enable its built-in privacy features:

  • VPN: Click the VPN badge in the address bar or go to Settings โ†’ Privacy and Security โ†’ VPN to enable the free built-in VPN.
  • Ad Blocker: Go to Settings โ†’ Privacy and Security โ†’ Block ads and surf the web up to three times faster.
  • Sidebar Workspaces: Click the three-line menu in the sidebar to access social apps like Messenger, WhatsApp, and Telegram without leaving the browser.

Update Opera Browser

Opera receives updates through your regular system upgrade cycle. To update all packages including Opera:

sudo apt update && sudo apt upgrade

Alternatively, to update only Opera without upgrading other packages, use the --only-upgrade flag:

sudo apt update && sudo apt install --only-upgrade opera-stable

For beta or developer builds, substitute the package name:

sudo apt install --only-upgrade opera-beta
sudo apt install --only-upgrade opera-developer

Afterwards, verify the update completed by checking the version:

opera --version

Troubleshoot Opera Installation

Duplicate Repository Sources Warning

If you see a warning during apt update about duplicate repository sources, Operaโ€™s installer created its own .list files that conflict with your existing configuration. This typically looks like:

W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/extrepo_opera_stable.sources:1 and /etc/apt/sources.list.d/opera-stable.list:4

To resolve this, remove the duplicate .list files created by Operaโ€™s installer:

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

Then verify the warning is resolved:

sudo apt update

Regular apt upgrade operations do not regenerate these duplicate files. Only a fresh install or reinstall of Opera triggers the installerโ€™s postinst script, so deleting the files once is sufficient.

extrepo Non-Free Policy Not Enabled

If you see โ€œrepository โ€˜opera_stableโ€™ is disabled by policiesโ€ when trying to enable the Opera repository, the non-free policy is not active. Check the current configuration:

grep -A5 "enabled_policies" /etc/extrepo/config.yaml

The output should show - non-free without a leading #:

enabled_policies:
- main
# - contrib
- non-free

If the line is still commented, run the sed command to enable it:

sudo sed -i 's/# - non-free/- non-free/' /etc/extrepo/config.yaml

Then retry enabling the repository:

sudo extrepo enable opera_stable

GPG Key Import Fails

If the manual GPG key import fails with an error like โ€œgpg: no valid OpenPGP data found,โ€ verify that the key URL is accessible:

curl -fsSL https://deb.opera.com/archive.key | head -5

You should see the beginning of a PGP key block:

-----BEGIN PGP PUBLIC KEY BLOCK-----

mQGNBGgrEnABDAC3S++y9OPF79pFJApWv5Ke0czoirWLN7a0rzScY2v+9LYWYVfU
XrZkDoVLJrxI6U/WvNbLqyrsyg9D9jZNksp0x5K9Fe9Phr6xAdRrpdmXu5xYGpBP

If you see HTML content or an error message instead, check your network connection or try again later. If the issue persists, consider using the extrepo method instead, which handles key management automatically.

Package Not Found After Adding Repository

If apt-cache policy opera-stable shows no candidate version after adding the repository, verify the repository file was created correctly:

cat /etc/apt/sources.list.d/opera.sources

The output should match the configuration shown in the manual installation section. If the file is empty or incorrect, recreate it using the tee command from Method 2. Then run:

sudo apt update
apt-cache policy opera-stable

Remove Opera Browser

Uninstall Opera Packages

To uninstall Opera Browser, remove the package for your installed version:

sudo apt remove --purge opera-stable

For beta or developer versions, run the corresponding commands:

sudo apt remove --purge opera-beta
sudo apt remove --purge opera-developer

Next, remove orphaned dependencies that were installed alongside Opera:

sudo apt autoremove

Remove Opera Repository

If you no longer plan to use Opera, you should also remove the repository configuration and GPG key to keep your system clean.

If you used extrepo (Method 1):

sudo extrepo disable opera_stable
sudo rm -f /etc/apt/sources.list.d/extrepo_opera_stable.sources

The extrepo disable command adds Enabled: no to the configuration file, but does not delete it. Removing the file ensures a complete cleanup.

If you configured the repository manually (Method 2):

sudo rm /etc/apt/sources.list.d/opera.sources
sudo rm /usr/share/keyrings/opera.gpg

Finally, refresh the package cache and verify the repository is removed:

sudo apt update
apt-cache policy opera-stable

You should see the following output, confirming removal (no repository URL appears):

opera-stable:
  Installed: (none)
  Candidate: (none)
  Version table:

Remove Opera User Data

The following command permanently deletes your Opera browsing data, including bookmarks, history, saved passwords, and extensions. Back up your profile first if you want to preserve anything: cp -r ~/.config/opera ~/.config/opera-backup.

To completely remove Opera user data:

rm -rf ~/.config/opera ~/.config/opera-beta ~/.config/opera-developer
rm -rf ~/.cache/opera ~/.cache/opera-beta ~/.cache/opera-developer

Restore Repository Configuration

If you accidentally remove the wrong file and need to restore the Opera repository, use the appropriate method based on how you originally configured it.

For extrepo:

sudo extrepo enable opera_stable
sudo apt update

For manual configuration:

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
sudo apt update

Conclusion

You now have Opera Browser installed on Debian with automatic updates through the official APT repository. The integrated VPN and ad blocker work immediately after installation, and you can switch between stable, beta, and developer builds depending on your testing needs. For alternative browsers on Debian, consider Brave for privacy, Vivaldi for customization, Google Chrome for web app compatibility, or Firefox for broader web standards support.

3 thoughts on “How to Install Opera Browser on Debian”

  1. I had Opera 119 installed (I can’t remember how I did it), but, it wasn’t upgrading. Following your instructions I got Opera 123.

    There was one little hitch. “apt update” complained about stuff configured multiple times. I was able to get rid of the complaints by renaming /etc/apt/sources.list.d/opera-stable.list (I assume that was created when I initially installed Opera 119 (your instructions create opera.list)), but, something recreated it as an empty file. How do I clean that up?

    Reply
    • Thanks for reporting this, Christopher, and glad you’re on Opera 123 now. The duplicate entries warning happens because Opera’s installer creates its own opera-stable.list file alongside the opera.sources file configured in the guide.

      Simply delete the duplicate file:

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

      This is a one-time fix. The file is only created during initial installation and will not be recreated during future updates. After removing it, run sudo apt update and the warnings should be gone.

      1
      Reply

Leave a Comment