Close Menu
Linux All DayLinux All Day
    Facebook Bluesky Mastodon X (Twitter)
    Linux All DayLinux All Day
    • News
    • Operating Systems
      • Linux Distributions
      • Android-based OS
      • ChromeOS Alternatives
    • Software
      • Apps & Tools
      • Desktop Environments
      • Installation & Management
    • Tutorials
      • Linux Basic & Tips
      • System Optimization
      • Security & Privacy
    • Linux Gaming
      • Game News & Reviews
      • Emulators & Retro
      • Performance & Benchmarks
    • Comparisons
    Mastodon Bluesky Facebook
    Linux All DayLinux All Day
    Home - Software - Installation & Management - What Are Flatpak Remotes? A Beginner’s Guide to Managing Them

    What Are Flatpak Remotes? A Beginner’s Guide to Managing Them

    By Mitja Installation & Management October 31, 20257 Mins Read
    Share Facebook Bluesky Twitter Threads Reddit LinkedIn Telegram Tumblr Email Copy Link Pinterest
    Follow Us
    Facebook Mastodon Bluesky X (Twitter)
    A diagram showing the Flatpak logo connecting to various app store "remotes," explaining what are Flatpak remotes.
    Share
    Facebook Twitter Bluesky Reddit Threads Tumblr Email Copy Link

    If you’re new to the world of Flatpak, you’ve likely heard the term “remote” and wondered what it means. You might have installed a Flatpak application, but where did it actually come from? The answer to that question is the “remote.”

    Understanding this simple concept is the key to unlocking the full potential of Flatpak, giving you access to thousands of applications in a secure, sandboxed environment. This system of remotes is what makes Flatpak a universal package manager, independent of your specific distribution.

    This guide will explain in simple terms what are flatpak remotes, why Flathub is essential, and show you step-by-step how to add, list, and remove them on your Linux system.

    What Are Flatpak Remotes, Exactly? The “App Store” Analogy

    In the simplest terms, a Flatpak remote is a repository. It’s a server on the internet that hosts Flatpak applications and their runtimes.

    Think of it this way:

    • Flatpak: The technology on your system, like a universal shopping cart. It knows how to carry and manage packages.
    • Flatpak Remotes: The stores (like Flathub) where you get the products to put in your cart.

    When you type a command like flatpak install org.mozilla.firefox, Flatpak doesn’t magically find Firefox. It checks a list of all the “remotes” (stores) you have added to your system. It asks each one, “Do you have an application called org.mozilla.firefox?”

    If a remote has it, Flatpak downloads the app and all its necessary “runtimes” (shared libraries) from that specific remote. If you don’t have any remotes added, your flatpak command is useless—it’s a shopping cart with no stores to visit.

    This is why understanding what are flatpak remotes is the first real step to using Flatpak effectively.

    The One Remote to Rule Them All: Flathub

    While you can technically have many remotes, one is more important than all the others: Flathub.

    FLATHUB is the de-facto, official, and largest remote for Flatpak applications. It’s a massive, centralized repository that hosts thousands of apps, from major developers like Mozilla (Firefox), Google (Chrome), and Spotify, to countless independent and open-source projects.

    Many Linux distributions, like Fedora or Ubuntu, now come with Flatpak pre-installed. However, for philosophical and legal reasons, they may not have the Flathub remote enabled by default. They might only include their own curated remote (like Fedora’s fedora remote, which contains only select Fedora-packaged Flatpaks).

    This is a common point of confusion for new users. They try to install an app they see on the Flathub website, and the command fails. The reason? They have the “shopping cart” (Flatpak) but haven’t told it where the “store” (Flathub) is.

    Therefore, the first thing you should almost always do on a new Linux installation is add the Flathub remote.

    How to Manage Flatpak Remotes on Linux: The Complete Guide

    This section will walk you through everything you need to manage flatpak repositories linux. The commands are simple and powerful.

    Prerequisite: Installing Flatpak

    First, ensure Flatpak itself is installed. If you are on a modern distribution like Fedora, Zorin OS, or elementary OS, it likely already is. If not, you can install it easily.

    On Fedora (and derivatives):

    Bash

    sudo dnf install flatpak
    

    On Debian/Ubuntu/Zorin OS (and derivatives):

    Bash

    sudo apt install flatpak
    

    After installation, it’s a good idea to reboot your system to ensure all paths and integrations (like with GNOME Software or KDE Discover) are correctly set up.

    How to Add a Flatpak Remote

    There are two primary ways to add a remote. We will focus on adding Flathub.

    Method 1: The Graphical Way (Easy)

    1. Open your web browser and go to the official FLATHUB WEBSITE.
    2. On the homepage, click the link “Flathub repository file.”
    3. Your browser will download a file named flathub.flatpakrepo.
    4. Open your file manager and double-click this file. Your system’s software center (like GNOME Software) should open and ask you if you want to add this repository.
    5. Click “Install” or “Add” and enter your password. The remote will be added.

    Method 2: The Command Line Way (Recommended)

    This is the fastest, most reliable, and most common way to add the Flathub remote. Open your terminal and paste the following single command:

    Bash

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

    Let’s break down this command:

    • flatpak remote-add: This is the action—we are adding a remote.
    • --if-not-exists: This is a very useful safety flag. It tells the command: “Only add this remote if one with the same name doesn’t already exist.” This prevents errors if you accidentally run the command twice.
    • flathub: This is the short, local name you are giving the remote. This is what you’ll see when you list your remotes.
    • https://...: This is the URL pointing to the repository’s definition file.

    Understanding ‘System’ vs. ‘User’ Remotes

    You may see a --user flag in some guides. By default, the command above adds the remote for the entire system (available to all users). This is what you want 99% of the time.

    • System Remote (default): flatpak remote-add ...
      • Installs apps in /var/lib/flatpak/.
      • Available to all users on the computer.
      • Requires sudo or Polkit (password prompt) to add.
    • User Remote: flatpak remote-add --user ...
      • Installs apps in your Home directory (~/.local/share/flatpak/).
      • Available only to you.
      • Does not require a password to add.

    Recommendation: Stick to System remotes unless you have a specific reason not to, such as not having administrator rights on the machine.

    How to List Your Current Flatpak Remotes

    Now that you’ve added Flathub, how can you check if it worked? Use the flatpak remotes command:

    Bash

    flatpak remotes
    

    The output will look something like this:

    Name     Options
    flathub  system
    fedora   system,oci
    

    This shows you have two remotes: “flathub” and “fedora.” The “system” option confirms they are available to all users.

    How to Remove a Flatpak Remote

    If you no longer need a remote, you can easily remove it. For example, if you wanted to remove the “fedora” remote, you would use:

    Bash

    flatpak remote-delete fedora
    

    You will be asked to confirm, as this is a significant action.

    Warning: Be very careful when removing remotes. If you remove a remote (like Flathub), all the applications you installed from it will no longer receive updates. You must know what you are doing before deleting a remote.

    Beyond Flathub: Other Remotes You Might Encounter

    While Flathub is your main “store,” the Flatpak ecosystem is diverse. You might encounter other remotes, particularly if you are a developer or tester.

    For example, the GNOME and KDE projects run their own “Nightly” remotes for testing cutting-edge, unstable versions of their applications.

    To add the GNOME Nightly remote:

    Bash

    flatpak remote-add --if-not-exists gnome-nightly https://nightly.gnome.org/gnome-nightly.flatpakrepo

    To add the KDE Apps Nightly remote:

    Bash

    flatpak remote-add --if-not-exists kdeapps --from https://distribute.kde.org/kdeapps.flatpakrepo
    

    For most users, these are not necessary, but they are a great example of how the remote system allows for different software channels (stable, testing, etc.).

    Conclusion: Your Gateway is Now Open

    You now understand what are flatpak remotes and how to manage them. They are simply the “app stores,” or repositories, that Flatpak uses to find and download software.

    By adding the Flathub remote, you have just opened the door to the largest ecosystem of desktop Linux applications available. You can now browse the Flathub website or your graphical software center and install thousands of apps with a single click or command, all with the security and convenience of Flatpak.

    Important Security Note

    As a general rule, you should only add Flatpak remotes from sources you trust completely. Flathub, and the official remotes from projects like GNOME, KDE, and your distribution (like Fedora) are trusted. Adding a random remote from an unknown website is a security risk, just as adding a random PPA or third-party repository would be in a traditional package manager. Always verify the source.

    How to enable flatpak backend you can read HERE


    Was this guide helpful? What are your favorite applications you’ve found on Flathub? Do you use any other remotes besides the main ones? Let us know your thoughts and experiences in the comments section below

    Follow on Mastodon Follow on Bluesky
    Share. Facebook Twitter Bluesky Reddit Threads Telegram Email Copy Link

    Related post

    How to Install Apps on Linux (2025): The Ultimate Guide for Fedora, Debian, & Arch

    November 26, 2025

    How to Setup Flathub on Linux: A 2025 Guide (Fedora, Debian, Arch, openSUSE)

    November 12, 2025

    What is a Linux App Center? The Snap Store Explained (2025)

    November 4, 2025
    Leave A Reply Cancel Reply

    → Switch to Linux Today
    • Facebook
    • Twitter
    • Mastodon
    • Bluesky
    More From Linuxallday
    Beyond the Grid: Mastering the Zen Flow of Bryce Tiles
    Mozilla Confirms Full “AI Kill Switch” for Firefox, Arriving in Early 2026
    Rescuezilla Review 2025: The ‘Undo Button’ for Your Entire PC
    Tails OS Review 2025: The Ultimate Amnesic System for Total Privacy
    Facebook X (Twitter) Mastodon Bluesky Threads RSS
    • About Us
    • Cookie Policy
    • Terms & Conditions
    • Privacy Policy
    • Disclosure & Disclaimer
    • Contact
    • Our Authors
    • Cookie Policy (EU)
    © 2026 Designed by FeedCrux

    Type above and press Enter to search. Press Esc to cancel.

    Manage Consent
    To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
    Functional Always active
    The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
    Preferences
    The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
    Statistics
    The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
    Marketing
    The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
    • Manage options
    • Manage services
    • Manage {vendor_count} vendors
    • Read more about these purposes
    View preferences
    • {title}
    • {title}
    • {title}