How to Install Flatpak on Linux: A Complete Setup Guide

Flatpak has become one of the most widely used application packaging formats on Linux, giving users access to a massive library of apps that run consistently across different distributions. Whether you're on Ubuntu, Fedora, Arch, or something more niche, Flatpak aims to solve one of Linux's oldest headaches: software that works on one distro but not another.

This guide walks through what Flatpak is, how to install it, and what factors shape your experience depending on your specific setup.

What Is Flatpak and Why Does It Matter?

Flatpak is a universal packaging system for Linux applications. Unlike traditional packages (.deb for Debian-based systems, .rpm for Red Hat-based ones), Flatpak apps are distribution-agnostic — they bundle their own dependencies and run inside a sandboxed environment.

This matters for a few reasons:

• Apps behave the same regardless of which Linux distro you're running
• Developers can ship a single package to all Linux users
• The sandbox layer adds a degree of security isolation from the rest of your system
• You can often get newer app versions than what your distro's default repos carry

The most popular source for Flatpak apps is Flathub, a centralized repository hosting thousands of applications — from Firefox and LibreOffice to Spotify and Steam.

Does Your Distro Already Have Flatpak?

Before installing anything, it's worth checking whether Flatpak is already on your system. Some distributions ship it by default:

Run this in a terminal to check:

flatpak --version 

If you get a version number back, Flatpak is already installed and you can skip straight to adding Flathub.

How to Install Flatpak 🛠️

Installation varies slightly depending on your package manager, but the process is straightforward on most major distributions.

On Ubuntu and Debian-Based Distros

sudo apt install flatpak 

After installation, it's recommended to install the GNOME Software plugin if you use GNOME, which allows Flatpak apps to appear in the Software Center:

sudo apt install gnome-software-plugin-flatpak 

On Fedora

Flatpak is typically pre-installed, but if needed:

sudo dnf install flatpak 

On Arch Linux

sudo pacman -S flatpak 

On openSUSE

sudo zypper install flatpak 

On Other Distributions

The official Flatpak documentation maintains a full list of setup guides for dozens of distributions. If your distro isn't listed above, it's the most reliable place to check — the commands follow your distro's native package manager in every case.

Adding the Flathub Repository

Installing Flatpak alone only gives you the runtime. To actually access apps, you need to add a remote — essentially a source repository. Flathub is the standard choice for most users:

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

The --if-not-exists flag prevents errors if Flathub has already been added (common on distros like Fedora).

After this step, restart your system. This ensures desktop integration works correctly — app icons, file associations, and software center listings all depend on a fresh session to register properly.

Installing Apps via Flatpak

Once Flathub is added, you install apps using this pattern:

flatpak install flathub [app-id] 

For example, to install GIMP:

flatpak install flathub org.gimp.GIMP 

To search for an app by name:

flatpak search [keyword] 

To run an installed Flatpak app from the terminal:

flatpak run [app-id] 

Most desktop environments will also show Flatpak apps in the application launcher automatically after installation.

Variables That Affect Your Setup 🔧

Not every Flatpak installation plays out the same way. Several factors shape how smoothly things go:

Desktop environment — GNOME and KDE both have GUI software centers that integrate Flatpak well. On minimal or tiling window manager setups, you'll likely rely entirely on the terminal.

Distro policies — Some distributions (notably Ubuntu) have historically steered users toward Snap packages instead of Flatpak. On Ubuntu, Flatpak works perfectly well but isn't promoted by default, so apps won't appear in the Ubuntu Software Center without the plugin installed.

Disk space — Flatpak apps bundle their own runtimes. If you install many apps sharing the same runtime (like GNOME Platform), they share that runtime layer. But if you install apps using multiple different runtimes, storage use grows accordingly. This matters more on smaller SSDs or storage-constrained machines.

User vs. system installation — By default, flatpak install installs apps system-wide (available to all users). You can install for the current user only with the --user flag. This distinction matters on multi-user systems or if you don't have root/sudo access.

Sandboxing and permissions — Flatpak's sandbox restricts app access to files, devices, and system resources by default. Most apps request necessary permissions upfront, but some users find they need to manually grant additional access — for example, allowing a file manager Flatpak to see external drives. Tools like Flatseal (itself available as a Flatpak) give you a GUI for managing these permissions without touching the terminal.

What Shapes the Experience Across Different Setups

A user on Fedora Workstation with GNOME will likely find Flatpak nearly invisible in the best sense — apps install from the Software Center, appear in the launcher, and just work. A user on a minimal Arch system with a custom window manager is working entirely in the terminal and may need to handle desktop integration files manually. Someone on a machine with 32GB of storage will notice the space tradeoffs more acutely than someone with a 1TB drive.

The technical steps to install Flatpak are consistent, but how Flatpak fits into your workflow — and whether it becomes your primary way of installing software or just a supplemental option — depends entirely on your distribution, desktop preferences, available storage, and comfort level with the terminal.