How to install 1Password for Linux?

The 1Password Linux page offers a `.deb` beside an `.rpm`, and choosing by filename alone can feel like a guess. It makes me wonder how the desktop app brings the passwords in your account into reach on Linux.

Look at the desktop app itself, beyond its package label. Consider what 1Password for Linux installs and how it connects to your account.

What 1Password for Linux installs

The Linux desktop app from 1Password connects to your account and stores your passwords in the app. Your distribution and CPU architecture determine the package, while an active membership gives you access to the account.

The official Linux downloads page offers Debian and RPM packages, while the installation instructions cover other distributions and sandboxed options.

Check your distribution and CPU architecture

Run uname -m before downloading because the reported architecture selects the matching 1Password package.

uname -m

The official .deb and .rpm files target amd64 or x86_64 systems. For aarch64, use the arm64 .tar.gz archive from 1Password’s support page.

Install 1Password with your distribution’s package manager

Download the package from 1Password’s Linux page and follow the steps for your distribution. The official native package configures its repository, so future updates can use the same package manager.

Step 1: Install 1Password on Debian or Ubuntu

Download the .deb package and keep its original filename. From the directory containing the download, run:

cd ~/Downloads
sudo apt install ./1password-latest.deb

APT shows the package changes before it applies them. Review the package name and dependency list before confirming the transaction.

The ./ prefix tells apt to install a local file rather than search for a package name. Because the official package configures its signing key and repository, later upgrades can stay in apt, and LinuxForDevices’ DEB installation guide explains the local-file behavior.

Step 2: Install 1Password on Fedora or RHEL

Download the .rpm package, then install the local file with DNF:

cd ~/Downloads
sudo dnf install ./1password-latest.rpm

The official RPM package configures 1Password’s signing key and repository as it installs. For the local-file step, see LinuxForDevices’ guide to installing RPM packages on Fedora and RHEL.

Step 3: Install 1Password on openSUSE

For x86_64 openSUSE, import 1Password’s signing key and add its RPM repository. Then install the package with zypper:

sudo rpm --import https://downloads.1password.com/linux/keys/1password.asc
sudo zypper addrepo https://downloads.1password.com/linux/rpm/stable/x86_64 1password
sudo zypper install 1password

The repository URL is for x86_64, which means you should check uname -m before adding it. Later zypper updates use that repository.

Step 4: Build the Arch package

The community-maintained AUR package uses the vendor’s signing key and makepkg, which builds and installs it as a regular user:

curl -sS https://downloads.1password.com/linux/keys/1password.asc | gpg --import
git clone https://aur.archlinux.org/1password.git
cd 1password
makepkg -si

Unlike 1Password’s Debian and RPM repositories, the Arch package is maintained by the community. LinuxForDevices’ Pacman guide for Arch covers the package tools used by this route.

The Linux installation page links to community packages for Gentoo and NixOS. It also links a separate NixOS note on app and browser integrations.

Choose Snap or Flathub when their limits fit

Snap and Flathub are alternatives when a native package does not fit your distribution. The vendor says these sandboxed packages lack integrations with system authentication and the SSH agent. They also cannot use the desktop app to lock the browser extension.

The Snap Store lists a verified 1Password publisher and provides this install command for x86 systems:

sudo snap install 1password

The Snap Store lists 8.11.14 as latest/stable, last updated October 15, 2025, while the official Debian repository lists 8.12.36, last modified September 9, 2026. Choose the native repository when you need current vendor releases and desktop integrations. See LinuxForDevices’ Snap package overview for how Snap fits into Linux.

Flathub lists 1Password for x86_64 and aarch64, but the company does not directly maintain the package, so releases may lag. The listing shows 8.12.12 while official Debian metadata shows 8.12.36. Its Install button opens your software manager or offers a .flatpakref file, and LinuxForDevices’ Flatpak setup guide explains the Flathub remote.

Check the package when installation or launch fails

Start with the package source and the system type. A package can install correctly on one Linux edition and still fail on a different architecture or an immutable host.

• If the package reports an incompatible architecture, run uname -m and choose the matching amd64, x86_64, or arm64 download.
• If the signing check fails, use 1Password’s current repository instructions rather than disabling signature verification.
• If you use Fedora Silverblue or another immutable edition, do not assume the standard DNF RPM path applies. A Fedora Discussion report from July 2026 describes a 1Password RPM post-install failure on Silverblue, so check the reported Atomic Fedora issue against your own error before changing the host.
• If the app opens but GNOME has no tray icon, 1Password’s support page recommends the AppIndicator GNOME Shell extension.

For an open-source alternative, LinuxForDevices has separate install guides for KeePassXC and Bitwarden. Those are different account and storage choices, not drop-in replacements for a 1Password vault.

Keep updates on the package source you installed

The official Debian package sets up an apt repository, so routine upgrades can stay in apt instead of relying on a manually downloaded file. Because that repository now supplies 1Password, run this command when you need an update:

sudo apt update && sudo apt upgrade 1password

Use the package manager and repository that match your installation. That keeps signature checks and update delivery attached to the source that supplied the app.

Frequently asked questions